Tested 2026-05-26 06:21:13 using Chrome 148.0.7778.96 (runtime settings)
| Metric | min | median | mean | max |
|---|---|---|---|---|
| Visual Metrics | ||||
| FirstVisualChange | 800 ms | 800 ms | 800 ms | 800 ms |
| LastVisualChange | 1.667 s | 7.033 s | 5.244 s | 7.033 s |
| SpeedIndex | 1.342 s | 1.544 s | 1.523 s | 1.682 s |
| LargestImage | 1.600 s | 1.667 s | 1.711 s | 1.867 s |
| Heading | 800 ms | 800 ms | 800 ms | 800 ms |
| LargestContentfulPaint | 1.600 s | 1.667 s | 1.711 s | 1.867 s |
| LastMeaningfulPaint | 1.600 s | 1.667 s | 1.711 s | 1.867 s |
| VisualReadiness | 867 ms | 6.233 s | 4.444 s | 6.233 s |
| VisualComplete85 | 1.600 s | 1.667 s | 1.711 s | 1.867 s |
| VisualComplete95 | 1.600 s | 1.667 s | 1.711 s | 1.867 s |
| VisualComplete99 | 1.667 s | 7.000 s | 5.222 s | 7.000 s |
| Google Web Vitals | ||||
| Time To First Byte (TTFB) | 395 ms | 396 ms | 398 ms | 404 ms |
| Largest Contentful Paint (LCP) | 1.592 s | 1.668 s | 1.703 s | 1.848 s |
| Cumulative Layout Shift (CLS) | 0 | 0 | 0 | 0 |
| More metrics | ||||
| firstPaint | 780 ms | 800 ms | 797 ms | 812 ms |
| loadEventEnd | 2.471 s | 2.530 s | 2.543 s | 2.628 s |
| User Timing | ||||
| mwStartup | 809 ms | 818 ms | 850 ms | 924 ms |
| CPU | ||||
| Total Blocking Time | 616 ms | 636 ms | 642 ms | 674 ms |
| Max Potential FID | 240 ms | 241 ms | 243 ms | 248 ms |
| CPU long tasks | 10 | 11 | 11 | 11 |
| CPU last long task happens at | 3.595 s | 3.661 s | 3.662 s | 3.730 s |
Run 2 SpeedIndex median
Use --filmstrip.showAll to show all filmstrips.
0 s0.7 sCPU Long Task duration 109 ms
0.8 sFirst Visual Change 800 msHeading 800 ms0.9 sFirst Contentful Paint 812 msCPU Long Task duration 50 msmwStartup 818 ms
1 s
1.1 sCPU Long Task duration 59 ms
1.2 sCPU Long Task duration 121 ms
1.3 s
1.4 sCPU Long Task duration 76 ms
1.5 sDOM Content Loaded Time 1.453 s
1.6 sCPU Long Task duration 210 msLCP <IMG> 1.592 sVisual Complete 85% 1.600 sVisual Complete 95% 1.600 sLargest Image 1.600 s
1.7 s
1.8 sCPU Long Task duration 105 ms
1.9 s
2 s
2.1 sCPU Long Task duration 56 ms
2.2 sCPU Long Task duration 240 ms
2.3 s
2.4 s
2.5 sCPU Long Task duration 73 ms
2.6 sPage Load Time 2.525 s
2.7 s
2.8 sFully Loaded 2.713 s
2.9 s
3 s
3.1 s3.7 sCPU Long Task duration 146 ms
7 sVisual Complete 99% 7.000 s
7.1 sLast Visual Change 7.033 sThe coach helps you find performance problems on your web page using web performance best practice rules. And gives you advice on privacy and best practices. Tested using Coach-core version 9.2.1.
longTasksThe page has 10 CPU long tasks with the total of 1.223 s. The total blocking time is 674 ms and 1 long task before first contentful paint with total time of 99 ms. However the CPU Long Task is depending on the computer/phones actual CPU speed, so you should measure this on the same type of the device that your user is using. Use Geckoprofiler for Firefox or Chromes tracelog to debug your long tasks.
Long CPU tasks locks the thread. To the user this is commonly visible as a "locked up" page where the browser is unable to respond to user input; this is a major source of bad user experience on the web today. However the CPU Long Task is depending on the computer/phones actual CPU speed, so you should measure this on the same type of the device that your user is using. To debug you should use the Chrome timeline log and drag/drop it into devtools or use Firefox Geckoprofiler.
modernImageFormatsThe page ships 14 images (out of 14) in JPEG/PNG/GIF without a modern alternative. Wrap them in a <picture> with a <source type="image/avif"> or "image/webp" before the legacy <img>, or serve modern formats from your image pipeline directly. AVIF and WebP usually deliver 25–50% smaller files at the same quality.
AVIF and WebP routinely deliver 25–50% smaller files than JPEG and PNG at the same perceived quality, and every browser version still under support understands at least one of them. Ship modern formats either through a <picture> element with <source type="image/avif"> / "image/webp" entries in front of the legacy <img>, or directly from a content-negotiating image pipeline that returns AVIF / WebP when the client accepts it. https://web.dev/articles/serve-images-webp
cacheHeadersThe page has 11 requests that are missing a cache time. Configure a cache time so the browser doesn't need to download them every time. It will save 333.9 kB the next access.
The easiest way to make your page fast is to avoid doing requests to the server. Setting a cache header on your server response will tell the browser that it doesn't need to download the asset again during the configured cache time! Always try to set a cache time if the content doesn't change for every request.
javascriptSizeThe total JavaScript transfer size is 378.4 kB and the uncompressed size is 1.7 MB. This is totally crazy! There is really room for improvement here.
A lot of JavaScript often means you are downloading more than you need. How complex is the page and what can the user do on the page? Do you use multiple JavaScript frameworks?
lazyLoadingImagesThe page has 11 below-the-fold images without loading="lazy". Add loading="lazy" so the browser defers downloading and decoding them until the user scrolls them into view.
Adding loading="lazy" to an <img> tells the browser not to download or decode it until it is close to the viewport. For images that the user may never see (deep in the page, behind a tab, in a footer carousel), this saves bandwidth and main-thread time during initial render. The LCP image and any image in the initial viewport should NOT be lazy-loaded — that delays the first paint. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#loading
avoidScalingImagesThe page has 3 images that are scaled more than 100 pixels. It would be better if those images are sent so the browser don't need to scale them.
It's easy to scale images in the browser and make sure they look good in different devices, however that is bad for performance! Scaling images in the browser takes extra CPU time and will hurt performance on mobile. And the user will download extra kilobytes (sometimes megabytes) of data that could be avoided. Don't do that, make sure you create multiple version of the same image server-side and serve the appropriate one.
lcpImageHintsThe LCP image is missing fetchpriority="high". Adding it tells the browser to fetch the image with high priority instead of the default heuristic (which often deprioritises hero images that are loaded after the HTML has been parsed).
When the Largest Contentful Paint element is an image, the browser priority hints applied to that element directly affect the LCP metric. The image must NOT be loading="lazy" (that defers the fetch until near-viewport, which is the opposite of what an LCP image needs) and SHOULD be fetchpriority="high" (so the browser fetches it with high priority instead of guessing). https://web.dev/articles/fetch-priority
decodingAsyncThe page has 5 images (out of 18) without a decoding hint. Add decoding="async" to non-critical images so the browser can decode them off the main thread.
Setting decoding="async" on an <img> tells the browser it can decode the image off the main thread, which keeps the page responsive to user interactions while images are being processed. The default ("auto") leaves the choice to the browser. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#decoding
privateAssetsThe page has 3 requests with private headers. The main page has a private header. It could be right in some cases where the user can be logged in and served specific content. But if your asset is static it should never be private. Make sure that the assets really should be private and only used by one user. Otherwise, make it cacheable for everyone.
If you set private headers on content, that means that the content are specific for that user. Static content should be able to be cached and used by everyone. Avoid setting the cache header to private.
cacheHeadersLongThe page has 17 requests that have a shorter cache time than one year (but still a cache time).
Setting a cache header is good. Setting a long cache header (a year) is even better because the asset will stay in the browser cache across visits. For content-hashed URLs (e.g. app.4af2.css) you can safely use Cache-Control: max-age=31536000, immutable. For unversioned URLs that may change, use a revalidating strategy instead.
assetsRedirectsThe page has 1 redirect. 1 of the redirects are from the base domain, please fix them!
A redirect is one extra step for the user to download the asset. Avoid that if you want to be fast. Redirects are even more of a showstopper on mobile.
optimalCssSizehttps://www.mediawiki.org/w/load.php?lang=en&modules=ext.discussionTools.init.styles%7Cext.wikimediamessages.styles%7Cmediawiki.hlist%7Cmediawiki.skins.legacy%7Cmediawiki.widgets.styles%7Cmobile.init.styles%7Coojs-ui-core.icons%2Cstyles%7Coojs-ui.styles.indicators%7Cskins.minerva.codex.styles%7Cskins.minerva.content.styles.images%7Cskins.minerva.icons%2Cstyles%7Cskins.minerva.mainPage.styles&only=styles&skin=minerva size is 33.7 kB (33676) and that is bigger than the limit of 25 kB. Try to keep each CSS response under 25 kB.
Render-blocking CSS holds up the first paint until it has fully downloaded, parsed and applied, so smaller CSS files mean a faster start. Split your CSS into a small critical bundle inlined or eagerly loaded, with the rest lazy-loaded.
| URL | Transfer | Content |
|---|---|---|
| https://www.mediawiki.org/w/load.php...ki.org/w/load.php | 32.9 KB | 268.1 KB |
inlineCssThe page has both inline CSS and CSS requests even though it uses a HTTP/2-ish connection. If you have many users on slow connections, it can be better to only inline the CSS. Run your own tests and check the waterfall graph to see what happens.
In the early days of the Internet, inlining CSS was one of the ugliest things you can do. That has changed if you want your page to start rendering fast for your user. Always inline the critical CSS when you use HTTP/1 and HTTP/2 (avoid doing CSS requests that block rendering) and lazy load and cache the rest of the CSS. It is a little more complicated when using HTTP/2. Does your server support HTTP push? Then maybe that can help. Do you have a lot of users on a slow connection and are serving large chunks of HTML? Then it could be better to use the inline technique, becasue some servers always prioritize HTML content over CSS so the user needs to download the HTML first, before the CSS is downloaded.
avoidRenderBlockingThe page has 2 blocking requests and 0 in body parser blocking (0 JavaScript and 2 CSS). There are 1 potentially render blocking requests. You need to verify if it is render blocking: https://www.mediawiki.org/w/load.php?lang=en&modules=startup&only=scripts&raw=1&skin=minerva
The critical rendering path is what the browser needs to do to start rendering the page. Every file requested inside of the head element will postpone the rendering of the page, because the browser need to do the request. Avoid loading JavaScript synchronously inside of the head (you should not need JavaScript to render the page), request files from the same domain as the main document (to avoid DNS lookups) and inline CSS for really fast rendering and a short rendering path.
metaDescriptionThe page is missing a meta description.
Use a page description to make the page more relevant to search engines.
imageAltTextThe page has 6 images without an alt attribute. Add alt="..." with a description, or alt="" if the image is purely decorative.
Every <img> needs an alt attribute. Use alt="meaningful description" for content images so assistive technologies can announce them, or alt="" (or role="presentation" / aria-hidden="true") for purely decorative images so they are skipped. A missing alt attribute leaves screen reader users with no information at all. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#alt
unnecessaryHeadersThere are 20 responses that sets both a max-age and expires header. There are 32 responses that sets a server header.
Do not send headers that you don't need. We look for p3p, cache-control and max-age, pragma, server and x-frame-options headers. Have a look at Andrew Betts - Headers for Hackers talk as a guide https://www.youtube.com/watch?v=k92ZbrY815c or read https://www.fastly.com/blog/headers-we-dont-want.
thirdPartyThe page do 31% requests to third party domains (10 requests and 333.9 kB). First party is 22 requests and 462.3 kB. The regex .*mediawiki.* was used to calculate first/third party requests.
Do not load most of your content from third party URLs.
longHeadershttps://www.mediawiki.org/wiki/MediaWiki has a header content-security-policy that is 4500 characters long. https://www.mediawik...ki.org/w/load.php has a header sourcemap that is 1000 characters long.
Do not send response headers that are too long.
crossOriginEmbedderPolicyHeaderSet a Cross-Origin-Embedder-Policy header (typically require-corp or credentialless) on the document response to control cross-origin embedding.
Cross-Origin-Embedder-Policy (COEP) makes the page refuse to load cross-origin subresources unless they explicitly opt in via CORP or CORS. Together with Cross-Origin-Opener-Policy it puts the page in a cross-origin isolated context, which mitigates cross-window side-channel attacks (Spectre) and unlocks high-resolution timers and SharedArrayBuffer. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Embedder-Policy
crossOriginOpenerPolicyHeaderSet a Cross-Origin-Opener-Policy header (typically same-origin) on the document response to isolate the page from cross-origin windows.
Cross-Origin-Opener-Policy (COOP) lets a page sever its window-group ties to cross-origin documents that opened it or that it opens. Together with Cross-Origin-Embedder-Policy it puts the page in a cross-origin isolated context, which mitigates cross-window side-channel attacks (Spectre) and unlocks high-resolution timers and SharedArrayBuffer. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Opener-Policy
crossOriginResourcePolicyHeaderSet a Cross-Origin-Resource-Policy header (same-origin, same-site or cross-origin) on the document response to limit who may embed it.
Cross-Origin-Resource-Policy (CORP) is a per-response opt-in that tells the browser which origins are allowed to embed the resource. It blocks cross-origin or cross-site no-cors embedding (img, script, iframe, etc.) and is one of the building blocks of cross-origin isolation. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Resource-Policy
permissionsPolicyHeaderSet a Permissions-Policy header to control which browser features the page can use.
The Permissions-Policy response header (the successor to Feature-Policy) lets a site explicitly opt in or out of powerful browser features such as camera, microphone, geolocation, payment and clipboard. Setting a strict policy reduces the attack surface and limits what embedded third parties can do. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy
referrerPolicyHeaderSet a referrer-policy header to make sure you do not leak user information.
Referrer Policy is a new header that allows a site to control how much information the browser includes with navigations away from a document and should be set by all sites. https://scotthelme.co.uk/a-new-security-header-referrer-policy/.
thirdPartyCookiesThe page sets 9 third party cookies.
Third party cookies are used to track the user. They are automatically blocked in Safari and Firefox.
contentSecurityPolicyHeaderThe policy allows 'unsafe-inline', which lets the browser execute inline scripts and styles directly from the page. Move to nonces or hashes plus 'strict-dynamic' so that inline injection cannot run. The policy allows 'unsafe-eval', which lets the page call eval() and Function(). Almost no application needs this; remove it.
A Content-Security-Policy response header tells the browser which sources of script, style, and other content are allowed. The most effective form is a strict CSP using nonces or hashes together with strict-dynamic; the worst is a missing header, with unsafe-inline and unsafe-eval close behind. https://web.dev/articles/strict-csp
Data collected using
Coach-core version 9.2.1. With updated code from
Webappanalyzer 2026-05-04. Use
--browsertime.firefox.includeResponseBodies html or
--browsertime.chrome.includeResponseBodies html to help Wappalyzer find more information about technologies used.
Data from run 2
0.0s1.0s1.4s1.8s2.2s2.6s3.0s7.1sWhen the page main content is rendered, collected via the Largest Contentful Paint API. Read more about Largest Contentful Paint.
body > div#mw-mf-viewport > div#mw-mf-page-center > main#content > div#bodyContent > div#mw-content-text > div:eq(0) > section#mf-section-0 > div#lang_dir > div:eq(1) > figure > a > img
The LCP element is highlighted in the screenshot. If nothing is highlighted the element was removed before the screenshot or the LCP API couldn't find it.
The Largest Contentful Paint API matched this image:
How much the page's content shifts as it loads, collected via the Cumulative Layout Shift API.
No layout shifts were detected on this page.
A long animation frame (LOAF) is a frame that took ≥ 50 ms from input to the next paint. The breakdown shows where that time went. Read more about the Long Animation Frames API.
Showing the top 10 longest animation frames.
No script attribution available for this frame.
No script attribution available for this frame.
No script attribution available for this frame.
No script attribution available for this frame.
| Name | Duration | Description |
|---|---|---|
cache | 0 ms | hit-front |
host | 0 ms | cp3070 |
There are no custom configured scripts.
There are no custom extra metrics from scripting.
How the page is built.
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 19.2 KB | 61.8 KB | 1 |
| css | 0 b | 34.4 KB | 269.1 KB | 2 |
| javascript | 0 b | 369.6 KB | 1.6 MB | 6 |
| image | 0 b | 332.2 KB | 321.4 KB | 10 |
| favicon | 0 b | 8.2 KB | 15.0 KB | 1 |
| svg | 0 b | 12.1 KB | 5.9 KB | 10 |
| json | 0 b | 1.7 KB | 263 B | 1 |
| Total | 0 b | 777.5 KB | 2.2 MB | 31 |
| Domain | Total download time | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| www.mediawiki.org | 4.235 s | 451.4 KB | 1.9 MB | 22 |
| upload.wikimedia.org | 6.039 s | 324.7 KB | 314.6 KB | 9 |
| auth.wikimedia.org | 185 ms | 1.4 KB | 254 B | 1 |
| type | min | median | max |
|---|---|---|---|
| Expires | 0 seconds | 2 weeks | 1 year |
| Last modified | 4 days | 9 weeks | 40 weeks |
Includes requests done after load event end.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 0 b | 0 |
| javascript | 0 b | 0 |
| image | 7.6 KB | 1 |
| font | 0 b | 0 |
| favicon | 8.2 KB | 1 |
| Total | 15.8 KB | 2 |
Includes requests done after DOM content loaded.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 0 b | 0 |
| javascript | 29.9 KB | 3 |
| image | 7.6 KB | 1 |
| font | 0 b | 0 |
| favicon | 8.2 KB | 1 |
| Total | 45.7 KB | 6 |
Render blocking information directly from Chrome.
| Blocking | In body parser blocking | Potentially blocking |
|---|---|---|
| 2 | 0 | 1 |
| URL | Type |
|---|---|
| https://www.mediawik...ki.org/w/load.php | non_blocking |
| https://www.mediawik...ki.org/w/load.php | blocking |
| https://www.mediawik...ki.org/w/load.php | potentially_blocking |
| https://www.mediawik...ki.org/w/load.php | non_blocking |
| https://www.mediawik...ki.org/w/load.php | non_blocking |
| https://www.mediawik...ki.org/w/load.php | non_blocking |
| https://www.mediawik...ki.org/w/load.php | blocking |
| https://auth.wikimed...gin/checkLoggedIn | non_blocking |
| https://www.mediawik...alAutoLogin/start | non_blocking |
Download the Chrome trace and drag-and-drop it into Performance in DevTools.
Tasks ≥ 50 ms blocking the main thread, collected via the Long Task API.
How much each script blocked the main thread, derived from the Long Animation Frame API. The script that started each long frame is credited with the frame's blocking time — the closest answer to "which script should I fix to improve TBT" the platform exposes.
Calculated from the Chrome trace.
A forced reflow happens when JavaScript reads a layout-triggering property (offsetTop, getBoundingClientRect, …) inside a handler, forcing the browser to synchronously recompute layout. The scripts below caused most of the page's reflows — fix them in priority order.
Each long animation frame reports how much time each script spent forcing synchronous style and layout — i.e. JavaScript reading layout-triggering properties mid-execution. Same actionable answer as forced reflows above but measured directly by the browser instead of inferred from the trace.