Tested 2026-08-06 13:58:18 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 896 ms on a 247 ms first byte; the 2 render-blocking requests were done by 366 ms and the remaining ~530 ms is style, layout and web-font loading.
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. Web fonts are context, not blockers: text renders invisible or in a fallback face while they load, so a font finishing after a paint is the classic reason text changed late.
| Request | When it loaded | Transfer | Download |
|---|---|---|---|
document | 231 ms | 14.9 KB | 230 ms |
0hecr_h8x653t.cssblocking | 71 ms | 17.6 KB | 71 ms |
1ee6gn1j-oy_o.cssblocking | 64 ms | 2.0 KB | 64 ms |
1upe53-127sm4.jspotentially blocking | 168 ms | 69.9 KB | 168 ms |
153tbw49q_1m9.jspotentially blocking | 138 ms | 13.1 KB | 138 ms |
2-5nk792mwq2y.jspotentially blocking | 134 ms | 40.1 KB | 134 ms |
0hoxp74tur_f3.jspotentially blocking | 123 ms | 8.0 KB | 123 ms |
2tv33b4-abenc.jspotentially blocking | 112 ms | 15.9 KB | 112 ms |
27jktro2p5rq9.jspotentially blocking | 88 ms | 9.5 KB | 88 ms |
| 1 more request | all done by 415 ms | 4.6 KB | |
99 ms | 38.5 KB | 99 ms | |
100 ms | 23.1 KB | 100 ms | |
110 ms | 24.5 KB | 110 ms | |
0224 ms448 msFCP · LCP 896 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.
lazyLoadingImagesThe page has 4 below-the-fold images without loading="lazy". Add loading="lazy" so the browser defers downloading and decoding them until the user scrolls them into view.
Adding loading="lazy" to an <img> tells the browser not to download or decode it until it is close to the viewport. For images that the user may never see (deep in the page, behind a tab, in a footer carousel), this saves bandwidth and main-thread time during initial render. The LCP image and any image in the initial viewport should NOT be lazy-loaded — that delays the first paint. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img#loading
longTasksThe page has 5 CPU long tasks with the total of 950 ms. The total blocking time is 501 ms and 2 long tasks before first contentful paint with total time of 299 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.
modernImageFormatsThe page ships 7 images (out of 7) 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 10 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 46.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.
responseOkThe page has 11 error responses. The page has 11 responses with code 403.
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.
avoidScalingImagesThe page has 8 images 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.
decodingAsyncThe page has 7 images (out of 9) 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
fewFontsThe page has 4 font requests. Do you really need them? What value does the fonts give the user?
How many fonts do you need on a page for the user to get the message? Fonts can slow down the rendering of content, try to avoid loading too many of them because worst case it can make the text invisible until they are loaded (FOIT—flash of invisible text), best case they will flicker the text content when they arrive.
compressAssetsThe page has 2 requests 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://healnova.ai/cdn-cgi/challenge-platform/h/b/scripts/jsd/8eb6d5cd556e/main.js? | 9.7 KB | 20.2 KB |
| https://healnova.ai/videos/hero-video.mp4 | N/A | 5.6 KB |
cacheHeadersLongThe page has 17 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.
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.
inlineCssThe page uses HTTP/3 and loads 2 CSS requests in head. Inline the critical CSS to avoid render-blocking on the first byte and lazy load the rest.
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.
pageTitleThe title is too long by 20 characters. The recommended max is 60
Use a title to make the page more relevant to search engines.
unnecessaryHeadersThere are 44 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://healnova.ai/.../a26e8e4cde44d163 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.0s1.0s1.5s1.8s2.1s2.4s2.8s3.1sWhen the page main content is rendered, collected via the Largest Contentful Paint API. Read more about Largest Contentful Paint.
body > div:eq(1) > main > section:eq(0) > div:eq(1) > 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 |
cache-control | s-maxage=31536000 |
cf-cache-status | DYNAMIC |
cf-ray | a26e8e4cde44d163-BOM |
content-encoding | zstd |
content-type | text/html; charset=utf-8 |
date | Thu, 06 Aug 2026 13:58:20 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=rQR%2BaxltuSeUpMGzAFWJ%2BV9b%2BLfYpHMP2%2FUl9RwvZ7DqQxm8VbyTlZOcZwr1hAkCvfUXv3QX7jh2BV6K%2FIIvBx%2Fw0eVpos3GNiMJBUQGKFoEyfZaItLBWuMpHzipow%3D%3D"}]} |
server | cloudflare |
server-timing | cfExtPri |
vary | rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding |
x-nextjs-cache | HIT |
x-nextjs-prerender | 1 1 |
x-nextjs-stale-time | 300 |
x-powered-by | Next.js |
Transfer size753.3 KB
Content size7.3 MB
Requests32
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 14.9 KB | 75.3 KB | 1 |
| css | 0 b | 19.6 KB | 110.0 KB | 2 |
| javascript | 0 b | 178.5 KB | 612.1 KB | 9 |
| image | 0 b | 339.7 KB | 334.2 KB | 11 |
| font | 0 b | 124.1 KB | 122.1 KB | 4 |
| video | 0 b | 74.6 KB | 6.1 MB | 4 |
| plain | 0 b | 1.9 KB | 0 b | 1 |
| Total | 0 b | 753.3 KB | 7.3 MB | 32 |
| Domain | Total download time | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| healnova.ai | 5.187 s | 804.0 KB | 7.4 MB | 44 |
| type | min | median | max |
|---|---|---|---|
| Expires | 0 seconds | 4 hours | 1 year |
| Last modified | 0 seconds | 6 days | 6 days |
Includes requests done after load event end.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 0 b | 0 |
| javascript | 0 b | 0 |
| image | 30.2 KB | 3 |
| font | 0 b | 0 |
| favicon | 0 b | 0 |
| Total | 80.9 KB | 14 |
Includes requests done after DOM content loaded.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 0 b | 0 |
| javascript | 9.7 KB | 1 |
| image | 30.2 KB | 3 |
| font | 0 b | 0 |
| favicon | 0 b | 0 |
| plain | 1.9 KB | 1 |
| Total | 92.5 KB | 17 |
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 | 14.9 KB | 75.3 KB | 1 |
| css | 0 b | 19.6 KB | 110.0 KB | 2 |
| javascript | 0 b | 178.5 KB | 612.1 KB | 9 |
| image | 0 b | 339.7 KB | 334.2 KB | 11 |
| font | 0 b | 124.1 KB | 122.1 KB | 4 |
| favicon | 0 b | 0 b | 0 b | 0 |
| video | 0 b | 74.6 KB | 6.1 MB | 4 |
| plain | 0 b | 1.9 KB | 0 b | 1 |
| Total | N/A | 804.0 KB | 7.4 MB | 44 |