Tested 2026-08-06 13:59:22 using Chrome 150.0.7871.186 (runtime settings)
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 996 ms on a 785 ms first byte, with no render-blocking requests: the ~199 ms after the document 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 gap after the bars is style and layout work.
None. Nothing except the document itself blocked rendering.
| Request | When it loaded | Transfer | Download |
|---|---|---|---|
document | 797 ms | 6.2 KB | 796 ms |
0249 ms498 msFCP · LCP 996 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 1 CPU long task with the total of 200 ms. The total blocking time is 0 ms and 1 long task before first contentful paint with total time of 200 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.
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.
compressAssetsThe page has 1 request that are served uncompressed. You could save a lot of bytes by sending them compressed instead.
In the early days of the Internet there were browsers that didn't support compressing (gzipping) text content. They do now. Make sure you compress HTML, JSON, JavaScript, CSS and SVG. It will save bytes for the user; making the page load faster and use less bandwith.
| URL | Transfer | Content |
|---|---|---|
| https://skin.healnova.ai/cdn-cgi/challenge-platform/h/b/scripts/jsd/8eb6d5cd556e/main.js? | 9.6 KB | 20.1 KB |
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 3 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.
metaDescriptionThe page is missing a meta description.
Use a page description to make the page more relevant to search engines.
imageAltTextThe page has 1 image 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 5 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://skin.healnov.../a26e8fd1ee8569ae has a header cf-chl-out-s that is 1713 characters long.
Do not send response headers that are too long.
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/.
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.
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.
0.0s0.9s1.0s1.1sWhen the page main content is rendered, collected via the Largest Contentful Paint API. Read more about Largest Contentful Paint.
body > div > h1
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.
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 |
|---|---|---|
cfExtPri | 0 ms | – |
There are no custom configured scripts.
There are no custom extra metrics from scripting.
How the page is built.
| Header | Value |
|---|---|
alt-svc | h3=":443"; ma=86400 |
cf-cache-status | DYNAMIC |
cf-ray | a26e8fd1ee8569ae-BOM |
content-encoding | zstd |
content-type | text/html; charset=utf-8 |
date | Thu, 06 Aug 2026 13:59:23 GMT |
nel | {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800} |
priority | u=0,i |
report-to | {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=AX1D%2FdI5w80aRirqxxFtXFds%2F7nmigTIb9RFaQx5fc65vXWI6Mn45LSyBH8UP%2BTR77rKAPFqkn5ZRXrH%2FYoVQdMJJMaYadBtIRF6GtmgE1B8y43W8msDGeFPeDiGtB5OSZBB"}]} |
server | cloudflare |
server-timing | cfExtPri |
| URL | Type | Transfer Size | Content Size |
|---|---|---|---|
| https://skin.healnov...6d5cd556e/main.js | javascript | 9.6 KB | 20.1 KB |
| https://skin.healnova.ai/ | html | 6.2 KB | 23.5 KB |
| https://skin.healnov.../a26e8fd1ee8569ae | plain | 1.9 KB | 0 b |
| https://skin.healnova.ai/favicon.ico | json | 436 B | 22 B |
| https://skin.healnov...ripts/jsd/main.js | other | N/A | 0 b |
Transfer size17.8 KB
Content size43.6 KB
Requests3
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 6.2 KB | 23.5 KB | 1 |
| javascript | 0 b | 9.6 KB | 20.1 KB | 1 |
| plain | 0 b | 1.9 KB | 0 b | 1 |
| Total | 0 b | 17.8 KB | 43.6 KB | 3 |
| Domain | Total download time | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| skin.healnova.ai | 1.658 s | 18.2 KB | 43.6 KB | 5 |
| type | min | median | max |
|---|---|---|---|
| Expires | 0 seconds | 5 minutes | 4 hours |
Includes requests done after load event end.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 0 b | 0 |
| javascript | 9.6 KB | 1 |
| image | 0 b | 0 |
| font | 0 b | 0 |
| favicon | 0 b | 0 |
| plain | 1.9 KB | 1 |
| Total | 12.0 KB | 4 |
Includes requests done after DOM content loaded.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 0 b | 0 |
| javascript | 9.6 KB | 1 |
| image | 0 b | 0 |
| font | 0 b | 0 |
| favicon | 0 b | 0 |
| plain | 1.9 KB | 1 |
| Total | 12.0 KB | 4 |
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 .*healnova.* (use --firstParty to configure).
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 6.2 KB | 23.5 KB | 1 |
| css | 0 b | 0 b | 0 b | 0 |
| javascript | 0 b | 9.6 KB | 20.1 KB | 1 |
| image | 0 b | 0 b | 0 b | 0 |
| font | 0 b | 0 b | 0 b | 0 |
| favicon | 0 b | 0 b | 0 b | 0 |
| plain | 0 b | 1.9 KB | 0 b | 1 |
| Total | N/A | 18.2 KB | 43.6 KB | 5 |