Tested 2026-05-26 04:35:01 using Firefox 150.0.2 (runtime settings)
| Metric | min | median | mean | max |
|---|---|---|---|---|
| Visual Metrics | ||||
| FirstVisualChange | 867 ms | 867 ms | 887 ms | 933 ms |
| LastVisualChange | 1.967 s | 2.000 s | 2.013 s | 2.067 s |
| SpeedIndex | 918 ms | 923 ms | 939 ms | 981 ms |
| LargestImage | 1.167 s | 1.200 s | 1.193 s | 1.200 s |
| Heading | 867 ms | 867 ms | 887 ms | 933 ms |
| LargestContentfulPaint | 1.167 s | 1.200 s | 1.193 s | 1.200 s |
| LastMeaningfulPaint | 1.167 s | 1.200 s | 1.193 s | 1.200 s |
| VisualReadiness | 1.100 s | 1.133 s | 1.127 s | 1.134 s |
| VisualComplete85 | 867 ms | 867 ms | 887 ms | 933 ms |
| VisualComplete95 | 1.167 s | 1.200 s | 1.193 s | 1.200 s |
| VisualComplete99 | 1.433 s | 1.467 s | 1.487 s | 1.533 s |
| Google Web Vitals | ||||
| Time To First Byte (TTFB) | 406 ms | 407 ms | 407 ms | 408 ms |
| Largest Contentful Paint (LCP) | 1.136 s | 1.186 s | 1.173 s | 1.187 s |
| More metrics | ||||
| firstPaint | 807 ms | 841 ms | 841 ms | 873 ms |
| loadEventEnd | 1.361 s | 1.399 s | 1.397 s | 1.428 s |
| User Timing | ||||
| mwStartup | 796 ms | 835 ms | 835 ms | 876 ms |
Run 4 SpeedIndex median
Use --filmstrip.showAll to show all filmstrips.
0 s
0.9 sDOM Content Loaded Time 826 msFirst Contentful Paint 832 msmwStartup 835 msFirst Visual Change 867 msVisual Complete 85% 867 msHeading 867 ms
1 s
1.1 s
1.3 s
1.4 s
1.5 sPage Load Time 1.428 s
1.6 sVisual Complete 99% 1.533 s
1.7 s
1.8 sFully Loaded 1.731 s
1.9 s
2 sLast Visual Change 2.000 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.
modernImageFormatsThe page ships 13 images (out of 13) 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 56.7 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 390.2 kB. This is quite large.
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?
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 4 images (out of 17) 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
avoidScalingImagesThe page has 1 image 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.
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.
cacheHeadersLongThe page has 10 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.
optimalCssSizehttps://www.mediawiki.org/w/load.php?lang=en&modules=ext.discussionTools.init.styles%7Cext.uls.pt%7Cext.visualEditor.desktopArticleTarget.noscript%7Cext.wikimediamessages.styles%7Cmediawiki.skins.legacy%7Cmediawiki.widgets.styles%7Coojs-ui-core.icons%2Cstyles%7Coojs-ui.styles.indicators%7Cskins.vector.icons%2Cstyles%7Cskins.vector.search.codex.styles&only=styles&skin=vector-2022 size is 36.4 kB (36379) 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 | 35.5 KB | 0 b |
avoidRenderBlockingThe style https://www.mediawiki.org/w/load.php?lang=en&modules=ext.discussionTools.init.styles%7Cext.uls.pt%7Cext.visualEditor.desktopArticleTarget.noscript%7Cext.wikimediamessages.styles%7Cmediawiki.skins.legacy%7Cmediawiki.widgets.styles%7Coojs-ui-core.icons%2Cstyles%7Coojs-ui.styles.indicators%7Cskins.vector.icons%2Cstyles%7Cskins.vector.search.codex.styles&only=styles&skin=vector-2022 is larger than the magic number TCP window size 14.5 kB. Make the file smaller and the page will render faster. The page has 1 render blocking CSS request and 0 blocking JavaScript request inside of head.
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.
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.
cumulativeLayoutShiftLayout Shift is not supported in this browser
Cumulative Layout Shift measures the sum total of all individual layout shift scores for unexpected layout shift that occur. The metric is measuring visual stability by quantify how often users experience unexpected layout shifts. It is one of Google Web Vitals.
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
viewportThe viewport meta tag does not contain width=device-width, the browser may use a desktop-width fallback.
The viewport meta tag tells the browser how to lay out the page on small screens. Without it (or without width=device-width) the page is rendered at a desktop fallback width and scaled down, which makes text unreadable on mobile. Disabling zoom (user-scalable=no, maximum-scale<=1) is also an accessibility regression. https://developer.mozilla.org/en-US/docs/Web/HTML/Viewport_meta_tag
thirdPartyThe page do 36% requests to third party domains (10 requests and 55.6 kB). First party is 18 requests and 478.3 kB. The regex .*mediawiki.* was used to calculate first/third party requests.
Do not load most of your content from third party URLs.
unnecessaryHeadersThere are 14 responses that sets both a max-age and expires header. There are 28 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.
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 1066 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 10 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 4
0.0s1.0s1.1s1.3s1.5s1.7s1.8s2.0sWhen the page main content is rendered, collected via the Largest Contentful Paint API. Read more about Largest Contentful Paint.
body > div:eq(2) > div > div:eq(2) > main#content > div#bodyContent > div#mw-content-text > div:eq(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:
| 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 | 6.2 KB | 22.3 KB | 0 b | 1 |
| css | 2.4 KB | 37.3 KB | 0 b | 2 |
| javascript | 9.5 KB | 381.0 KB | 0 b | 7 |
| image | 12.6 KB | 60.4 KB | 0 b | 10 |
| favicon | 1005 B | 8.4 KB | 0 b | 1 |
| svg | 6.5 KB | 10.9 KB | 0 b | 6 |
| Total | 38.2 KB | 520.2 KB | 0 b | 27 |
| Domain | Total download time | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| www.mediawiki.org | 3.487 s | 467.1 KB | 0 b | 18 |
| upload.wikimedia.org | 6.190 s | 52.7 KB | 0 b | 9 |
| auth.wikimedia.org | 184 ms | 1.6 KB | 0 b | 1 |
| type | min | median | max |
|---|---|---|---|
| Expires | 0 seconds | 5 minutes | 1 year |
| Last modified | 11 hours | 9 weeks | 1 year |