Tested 2026-08-17 06:54:17 using Chrome 151.0.7922.75 (runtime settings)
This page is fast to paint, snappy to interact with, visually stable and follows best practices, but weak on user privacy.
Visual metrics
Google Web Vitals
The page has 1 image (out of 1) without a decoding hint. Add decoding="async" to non-critical images so the browser can decode them off the main thread.
The page ships 1 image (out of 1) 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.
The page has 2 CPU long tasks with the total of 285 ms. The total blocking time is 0 ms and 2 long tasks before first contentful paint with total time of 285 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.
Timings summary
| Metric | Min | Median | Mean | Max |
|---|---|---|---|---|
| First visual change | 367 ms | 367 ms | 367 ms | 367 ms |
| Last visual change | 367 ms | 367 ms | 367 ms | 367 ms |
| Speed index | 367 ms | 367 ms | 367 ms | 367 ms |
| Visual readiness | 0 ms | 0 ms | 0 ms | 0 ms |
| Visual complete 85 | 367 ms | 367 ms | 367 ms | 367 ms |
| Visual complete 95 | 367 ms | 367 ms | 367 ms | 367 ms |
| Visual complete 99 | 367 ms | 367 ms | 367 ms | 367 ms |
Run 1 SpeedIndex median
The red band on the timeline marks when the main thread was busy with long tasks: moments when the page could not paint or respond, however the video looks.
Download videoUse --filmstrip.showAll to show all filmstrips.
Click a frame to seek the video to that moment. The dot marks frames where the page changed visually.
Rendering was not meaningfully delayed. First paint landed at 372 ms on a 15 ms first byte.
Want to see how much CSS style-recalculation work delayed FCP and LCP, plus CPU long tasks? Run with --cpu.
Blocking requests delay both paints: the browser renders nothing until they arrive, so they push First Contentful Paint and everything after it, including the largest paint (LCP). Requests that block the parser inside the body stall everything after them in the document. Load JavaScript with defer or async, and keep non-critical CSS off the critical path with media attributes. Bars show when each request loaded on a clock that runs to the last paint; the gap after the bars is style and layout work.
| Request | When it loaded | Transfer | Download |
|---|---|---|---|
document | 15 ms | 31.2 KB | 14 ms |
gt-ie9-507b16b6be.jsblocks parser in body | 8 ms | 1.5 KB | 8 ms |
index-34f340e24a.jsblocks parser in body | 7 ms | 9.4 KB | 7 ms |
LCP resource | 11 ms | 16.4 KB | 11 ms |
093 ms186 msFCP · LCP 372 ms |
The 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.
decodingAsyncThe page has 1 image (out of 1) 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
modernImageFormatsThe page ships 1 image (out of 1) 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
longTasksThe page has 2 CPU long tasks with the total of 285 ms. The total blocking time is 0 ms and 2 long tasks before first contentful paint with total time of 285 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.
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
cacheHeadersLongThe page has 4 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.
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
unnecessaryHeadersThere are 5 responses that sets both a max-age and expires header. There are 6 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.
referrerPolicyNo <meta name="referrer"> tag was found on the page. Set a Referrer-Policy response header (preferred) or add a meta tag, for example <meta name="referrer" content="strict-origin-when-cross-origin">.
Without an explicit referrer policy the browser falls back to the user-agent default and may leak the full URL of the previous page (including query strings) to every cross-origin request. Set a Referrer-Policy response header (preferred) or a <meta name="referrer"> tag in the document. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy
contentSecurityPolicyHeaderSet a Content-Security-Policy header to mitigate cross-site scripting attacks. You can start with a Content-Security-Policy-Report-Only header, which only reports violations rather than blocking them.
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
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/.
xContentTypeOptionsHeaderSet X-Content-Type-Options: nosniff on the document response to prevent MIME-sniffing.
X-Content-Type-Options: nosniff prevents browsers from interpreting files as a different MIME type than what is declared in the Content-Type header. This blocks a class of cross-site scripting and content-type confusion attacks and should be set on every response. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options
A snapshot of what the browser actually built for this page: the document, how big and deep the DOM tree is and what it kept in storage. Big, deep trees are slower to style and lay out, so the counts Chrome warns about carry a flag.
Document
What the page says it is and how large it rendered.
DOM structure
How much markup the browser has to build, style and lay out.
What the page stored on the client, and the network it was tested on.
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 1
0.0s0.1s0.2s0.4sWhen the page main content is rendered, collected via the Largest Contentful Paint API. Read more about Largest Contentful Paint.
body#www-wikipedia-org > main > div:eq(0) > 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.
Timing data the server chose to expose through Server-Timing response headers on the main document — typically backend time, cache status or experiment flags.
| Name | Duration | Description |
|---|---|---|
cache | 0 ms | hit-front |
host | 0 ms | cp4040 |
co_id | 0 ms | 2693447307 |
There are no custom configured scripts.
There are no custom extra metrics from scripting.
How the page is built.
| Header | Value |
|---|---|
accept-ranges | bytes |
age | 29087 |
cache-control | s-maxage=86400, must-revalidate, max-age=3600 |
content-encoding | gzip |
content-length | 30635 |
content-type | text/html |
date | Sun, 16 Aug 2026 22:49:31 GMT |
etag | W/"1d629-65738a87fd940" |
last-modified | Wed, 22 Jul 2026 20:05:17 GMT |
nel | { "report_to": "wm_nel", "max_age": 604800, "failure_fraction": 0.05, "success_fraction": 0.0} |
report-to | { "group": "wm_nel", "max_age": 604800, "endpoints": [{ "url": "https://intake-logging.wikimedia.org/v1/events?stream=w3c.reportingapi.network_error&schema_uri=/w3c/reportingapi/network_error/1.0.0" }] } |
server | ATS/9.2.13 |
server-timing | cache;desc="hit-front", host;desc="cp4040",co_id;desc="2693447307" |
strict-transport-security | max-age=106384710; includeSubDomains; preload |
x-analytics | |
x-cache | cp4040 miss, cp4040 hit/155371 |
x-cache-status | hit-front |
x-client-ip | 13.87.216.115 |
x-request-id | 0bef8c92-6943-4f3c-900b-de9a11f282b9 |
| URL | Type | Transfer Size | Content Size |
|---|---|---|---|
| https://www.wikipedia.org/ | html | 31.2 KB | 117.5 KB |
| https://www.wikipedi...rite-e49fbf32.svg | svg | 18.7 KB | 50.0 KB |
| https://www.wikipedi...pedia-logo-v2.png | image | 16.4 KB | 15.5 KB |
| https://www.wikipedi...dex-34f340e24a.js | javascript | 9.4 KB | 23.6 KB |
| https://www.wikipedi...con/wikipedia.ico | favicon | 1.8 KB | 2.7 KB |
| https://www.wikipedi...ie9-507b16b6be.js | javascript | 1.5 KB | 580 B |
Transfer size79.1 KB
Content size209.8 KB
Requests6
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 31.2 KB | 117.5 KB | 1 |
| javascript | 0 b | 10.9 KB | 24.1 KB | 2 |
| image | 0 b | 16.4 KB | 15.5 KB | 1 |
| favicon | 0 b | 1.8 KB | 2.7 KB | 1 |
| svg | 0 b | 18.7 KB | 50.0 KB | 1 |
| Total | 0 b | 79.1 KB | 209.8 KB | 6 |
| Domain | Total download time | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| www.wikipedia.org | 73 ms | 79.1 KB | 209.8 KB | 6 |
| type | min | median | max |
|---|---|---|---|
| Expires | 1 hour | 1 day | 1 year |
| Last modified | 4 weeks | 4 weeks | 6 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 | 0 b | 0 |
| font | 0 b | 0 |
| favicon | 1.8 KB | 1 |
| Total | 1.8 KB | 1 |
Includes requests done after DOM content loaded.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 0 b | 0 |
| javascript | 0 b | 0 |
| image | 0 b | 0 |
| font | 0 b | 0 |
| favicon | 1.8 KB | 1 |
| Total | 1.8 KB | 1 |
--enableProfileRun to see where main-thread time went, blocking time and CPU cost per script, module and function, forced reflows and frame stability. The data is collected in one extra run, so the timing metrics of your measured runs stay untouched.Tasks ≥ 50 ms blocking the main thread, collected via the Long Task API.
A long animation frame (LOAF) is a frame that took ≥ 50 ms from input to the next paint. The part beyond the threshold is blocking time, the number that hurts Interaction to Next Paint and Total Blocking Time. Break long tasks up (scheduler.yield(), smaller chunks) or move the work off the main thread. Read more about the Long Animation Frames API.
The browser did not report which script was responsible for this frame — typically its own style/layout work, or a cross-origin script it will not name.
The browser did not report which script was responsible for this frame — typically its own style/layout work, or a cross-origin script it will not name.
Third party requests categorised by Third party web version 0.29.2.
No third-party requests detected
Every request on this page resolved to a first-party domain. There are no entries in Third party web to attribute, no third-party tools to enumerate, and no third-party cookies set. If you expected to see entries here you can fine-tune the first-party domain list with --firstParty.
Calculated using (.*wikipedia.*||.*wikimedia.*) (use --firstParty to configure).
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 31.2 KB | 117.5 KB | 1 |
| css | 0 b | 0 b | 0 b | 0 |
| javascript | 0 b | 10.9 KB | 24.1 KB | 2 |
| image | 0 b | 16.4 KB | 15.5 KB | 1 |
| font | 0 b | 0 b | 0 b | 0 |
| favicon | 0 b | 1.8 KB | 2.7 KB | 1 |
| svg | 0 b | 18.7 KB | 50.0 KB | 1 |
| Total | N/A | 79.1 KB | 209.8 KB | 6 |