Tested 2026-05-26 03:55:39 using Chrome 148.0.7778.96 (runtime settings)
| Metric | min | median | mean | max |
|---|---|---|---|---|
| Visual Metrics | ||||
| FirstVisualChange | 733 ms | 733 ms | 733 ms | 733 ms |
| LastVisualChange | 10.900 s | 10.900 s | 10.900 s | 10.900 s |
| SpeedIndex | 1.001 s | 1.171 s | 1.137 s | 1.171 s |
| LargestImage | 733 ms | 733 ms | 733 ms | 733 ms |
| Heading | 733 ms | 766 ms | 759 ms | 766 ms |
| LargestContentfulPaint | 733 ms | 733 ms | 733 ms | 733 ms |
| LastMeaningfulPaint | 733 ms | 766 ms | 759 ms | 766 ms |
| VisualReadiness | 10.167 s | 10.167 s | 10.167 s | 10.167 s |
| VisualComplete85 | 733 ms | 766 ms | 759 ms | 766 ms |
| VisualComplete95 | 733 ms | 766 ms | 759 ms | 766 ms |
| VisualComplete99 | 9.066 s | 9.066 s | 9.066 s | 9.066 s |
| Google Web Vitals | ||||
| Time To First Byte (TTFB) | 413 ms | 413 ms | 413 ms | 414 ms |
| Largest Contentful Paint (LCP) | 728 ms | 748 ms | 743 ms | 752 ms |
| Cumulative Layout Shift (CLS) | 0 | 0 | 0 | 0 |
| More metrics | ||||
| firstPaint | 728 ms | 748 ms | 743 ms | 752 ms |
| loadEventEnd | 699 ms | 718 ms | 714 ms | 719 ms |
| CPU | ||||
| Total Blocking Time | 0 ms | 0 ms | 0 ms | 0 ms |
| Max Potential FID | 0 ms | 0 ms | 0 ms | 0 ms |
| CPU long tasks | 1 | 1 | 1 | 1 |
| CPU last long task happens at | 521 ms | 522 ms | 522 ms | 524 ms |
Run 1 SpeedIndex median
Use --filmstrip.showAll to show all filmstrips.
0 s0.6 sCPU Long Task duration 154 ms
0.8 sDOM Content Loaded Time 710 msPage Load Time 718 msLayout Shift 0.00003 726 msFirst Visual Change 733 msLargest Image 733 msFirst Contentful Paint 752 msLCP <IMG> 752 msVisual Complete 85% 766 msVisual Complete 95% 766 msHeading 766 ms
0.9 sFully Loaded 817 ms
1 s
1.1 s
1.2 s
1.3 s
9.1 sVisual Complete 99% 9.066 s
9.2 s
9.3 s
9.4 s
9.5 s
9.6 s
9.7 s
9.8 s
9.9 s
10 s
10.1 s
10.2 s
10.3 s
10.4 s
10.5 s
10.6 s
10.7 s
10.8 s
10.9 sLast Visual Change 10.900 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.
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
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
avoidRenderBlockingThe page has 1 blocking requests and 1 in body parser blocking (2 JavaScript and 0 CSS).
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.
longTasksThe page has 1 CPU long task with the total of 154 ms. The total blocking time is 0 ms and 1 long task before first contentful paint with total time of 154 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.
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
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.0s1.0s1.3s9.4s9.8s10.2s10.5s10.9sWhen 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.
Sorted by individual shift score (higher = bigger shift). The top entries usually account for most of the page's CLS.
body#www-wikipedia-org > main > div:eq(1) > form#search-form > fieldset > div#search-input > div:eq(0)
Elements that shifted by more than 0.01 are highlighted in the screenshot. If an element shifted outside the viewport, it won't appear here — check the video or filmstrip to see the shift.
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.
| 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.
| 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.8 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 |
| 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.8 KB | 50.0 KB | 1 |
| Total | 0 b | 79.1 KB | 209.7 KB | 6 |
| Domain | Total download time | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| www.wikipedia.org | 1.270 s | 79.1 KB | 209.7 KB | 6 |
| type | min | median | max |
|---|---|---|---|
| Expires | 1 hour | 1 day | 1 year |
| Last modified | 2 weeks | 9 weeks | 9 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 |
Render blocking information directly from Chrome.
| Blocking | In body parser blocking | Potentially blocking |
|---|---|---|
| 1 | 1 | 0 |
| URL | Type |
|---|---|
| https://www.wikipedi...dex-34f340e24a.js | blocking |
| https://www.wikipedi...ie9-507b16b6be.js | in_body_parser_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.
Calculated from the Chrome trace.
Animations that fell back from the compositor to the main thread, blocking each frame instead of running on the GPU. Each chip below is a CSS property the page tried to animate that Chrome couldn't hand to the compositor — swap it for a transform or opacity equivalent where you can.
border-bottom-color1×border-left-color1×box-shadow1×border-right-color1×border-top-color1×