Tested 2026-08-06 13:36:28 using Chrome 150.0.7871.186 (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 6 CPU long tasks with the total of 591 ms. The total blocking time is 65 ms and 3 long tasks before first contentful paint with total time of 376 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.
The total JavaScript transfer size is 253.1 kB and the uncompressed size is 837.9 kB. This is quite large.
The LCP image has loading="lazy", which delays its download until the browser thinks it is near the viewport — and so directly delays the LCP metric. Remove loading="lazy" from the LCP image. The 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).
Timings summary
| Metric | Min | Median | Mean | Max |
|---|---|---|---|---|
| First visual change | 334 ms | 334 ms | 334 ms | 334 ms |
| Last visual change | 668 ms | 668 ms | 668 ms | 668 ms |
| Speed index | 369 ms | 369 ms | 369 ms | 369 ms |
| Visual readiness | 334 ms | 334 ms | 334 ms | 334 ms |
| Visual complete 85 | 334 ms | 334 ms | 334 ms | 334 ms |
| Visual complete 95 | 601 ms | 601 ms | 601 ms | 601 ms |
| Visual complete 99 | 634 ms | 634 ms | 634 ms | 634 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 592 ms on a 40 ms first byte; the 2 render-blocking requests were done by 134 ms and the remaining ~458 ms is style and layout work.
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 dashed line is FCP, the clock ends at LCP); the gap after the bars is style and layout work.
| Request | When it loaded | Transfer | Download |
|---|---|---|---|
document | 32 ms | 5.0 KB | 31 ms |
0xchftebhgqgq.cssblocking | 54 ms | 22.0 KB | 54 ms |
0zt1xsc7qj.mw.cssblocking | 30 ms | 2.9 KB | 30 ms |
155bi7ep2xvb5.jspotentially blocking | 102 ms | 71.2 KB | 102 ms |
0_y091_uv9n6r.jspotentially blocking | 97 ms | 23.3 KB | 97 ms |
0gwjhb~p~0typ.jspotentially blocking | 93 ms | 9.1 KB | 93 ms |
0uqgm3y7qfyr6.jspotentially blocking | 88 ms | 37.0 KB | 88 ms |
10iw-qettv3df.jspotentially blocking | 85 ms | 15.5 KB | 85 ms |
13hun948hb15q.jspotentially blocking | 79 ms | 15.7 KB | 79 ms |
| 7 more requests | all done by 160 ms | 74.3 KB | |
LCP resource | 66 ms | 4.1 KB | 66 ms |
0167 ms334 msFCP 592 msFCP · LCP 668 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.
longTasksThe page has 6 CPU long tasks with the total of 591 ms. The total blocking time is 65 ms and 3 long tasks before first contentful paint with total time of 376 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.
javascriptSizeThe total JavaScript transfer size is 253.1 kB and the uncompressed size is 837.9 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 has loading="lazy", which delays its download until the browser thinks it is near the viewport — and so directly delays the LCP metric. Remove loading="lazy" from the LCP image. The 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
cacheHeadersThe page has 2 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 4.8 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.
privateAssetsThe page has 2 requests with private headers. 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.
responseOkThe page has 1 error response. The page has 1 response with code 404.
Your page should never request assets that return a 400 or 500 error. These requests are never cached. If that happens something is broken. Please fix it.
cacheHeadersLongThe page has 1 request 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.
unnecessaryHeadersThere are 1 response that sets a pragma no-cache header (that is a request header). There are 20 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
nelHeaderSet a NEL header (paired with Reporting-Endpoints) to collect connection-level error reports from the field.
The NEL (Network Error Logging) response header tells the browser to record connection-level failures (DNS, TLS, HTTP errors) and ship them to a reporting endpoint. NEL pairs with the Reporting-Endpoints / Report-To header — the page declares the endpoint group and NEL points at it. Together they give you visibility into errors that never reach your origin server. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/NEL
reportingEndpointsHeaderSet a Reporting-Endpoints header (or the legacy Report-To header) so CSP reports, NEL data and other Reporting-API events have an endpoint to land at.
The Reporting-Endpoints response header (the successor to Report-To) names the URLs that browsers should POST reports to. Without it, CSP report-to directives, Cross-Origin-Opener-Policy reports, NEL data and other Reporting-API events have nowhere to go. The legacy Report-To header is still accepted for older Chromium versions. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Reporting-Endpoints
strictTransportSecurityHeaderSet a strict transport header to make sure the user always use HTTPS.
The HTTP Strict-Transport-Security response header (often abbreviated as HSTS) lets a web site tell browsers that it should only be accessed using HTTPS, instead of using HTTP. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security.
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.3s0.4s0.5s0.6s0.7sWhen the page main content is rendered, collected via the Largest Contentful Paint API. Read more about Largest Contentful Paint.
body > div:eq(1) > div > 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.
There are no custom configured scripts.
There are no custom extra metrics from scripting.
How the page is built.
| Header | Value |
|---|---|
cache-control | s-maxage=31536000 |
content-encoding | gzip |
content-type | text/html; charset=utf-8 |
date | Thu, 06 Aug 2026 13:36:29 GMT |
etag | "24ez52j0y3jon" |
permissions-policy | camera=(), microphone=(), geolocation=() |
referrer-policy | strict-origin-when-cross-origin |
server | nginx/1.24.0 (Ubuntu) |
vary | rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding |
x-content-type-options | nosniff |
x-frame-options | DENY |
x-nextjs-cache | HIT |
x-nextjs-prerender | 1 1 |
x-nextjs-stale-time | 300 |
x-powered-by | Next.js |
x-xss-protection | 1; mode=block |
Transfer size281.8 KB
Content size1009.7 KB
Requests19
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 5.0 KB | 24.9 KB | 1 |
| css | 0 b | 24.9 KB | 162.9 KB | 2 |
| javascript | 0 b | 247.2 KB | 818.3 KB | 14 |
| image | 0 b | 4.1 KB | 3.6 KB | 1 |
| json | 0 b | 584 B | 2 B | 1 |
| Total | 0 b | 281.8 KB | 1009.7 KB | 19 |
| Domain | Total download time | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| cms.streamplay.ai | 1.245 s | 285.9 KB | 1.0 MB | 20 |
| type | min | median | max |
|---|---|---|---|
| Expires | 0 seconds | 1 year | 1 year |
| Last modified | 1 week | 1 week | 1 week |
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 | 0 b | 0 |
| json | 584 B | 1 |
| Total | 4.7 KB | 2 |
Includes requests done after DOM content loaded.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 0 b | 0 |
| javascript | 0 b | 0 |
| image | 4.1 KB | 1 |
| font | 0 b | 0 |
| favicon | 0 b | 0 |
| json | 584 B | 1 |
| Total | 8.7 KB | 3 |
--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.
| Script | Frames | Time running | Blocking (share by run time) | Forced style & layout | Triggered by |
|---|---|---|---|---|---|
| TimerHandler:setTimeout | 1 | 238.8 ms | 188.8 ms | – | timer or animation callback |
| 155bi7ep2xvb5.js | 3 | 216.5 ms | 66.9 ms | – | event handler |
A frame's blocking time is split between its scripts by their share of the frame's work, capped at each script's own run time — blocking from work no script owns (HTML parsing, browser internals) stays unattributed. The per-script blocking view below uses the same attribution.
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.
1 more long frame carried no blocking time (nothing ran past the 50 ms threshold) — long, but harmless to INP and TBT.
How much each script blocked the main thread, derived from the Long Animation Frame API. Each frame's blocking time is split between its scripts by their share of the frame's work, capped at each script's own run time — blocking from work no script owns (HTML parsing, browser internals) is not attributed (older data credits the script that started the frame). The closest answer to "which script should I fix to improve TBT" the platform exposes.
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 .*streamplay.* (use --firstParty to configure).
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 5.0 KB | 24.9 KB | 1 |
| css | 0 b | 24.9 KB | 162.9 KB | 2 |
| javascript | 0 b | 247.2 KB | 818.3 KB | 14 |
| image | 0 b | 4.1 KB | 3.6 KB | 1 |
| font | 0 b | 0 b | 0 b | 0 |
| favicon | 0 b | 0 b | 0 b | 0 |
| json | 0 b | 584 B | 2 B | 1 |
| Total | N/A | 285.9 KB | 1.0 MB | 20 |