Tested 2026-10-03 06:21:50 using Chrome 150.0.7871.46 (runtime settings)
This page is fast to paint, snappy to interact with and visually stable, but loose on best practices and weak on user privacy.
Visual metrics
Google Web Vitals
The page has 1 CPU long task with the total of 54 ms. The total blocking time is 0 ms and 1 long task before first contentful paint with total time of 54 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 page has 1 request that are missing a cache time. Configure a cache time so the browser doesn't need to download them every time. It will save 447 B the next access.
The page has 1 misconfigured mime type.
Timings summary
| Metric | Min | Median | Mean | Max |
|---|---|---|---|---|
| First visual change | 233 ms | 233 ms | 233 ms | 233 ms |
| Last visual change | 233 ms | 233 ms | 233 ms | 233 ms |
| Speed index | 233 ms | 233 ms | 233 ms | 233 ms |
| Visual readiness | 0 ms | 0 ms | 0 ms | 0 ms |
| Visual complete 85 | 233 ms | 233 ms | 233 ms | 233 ms |
| Visual complete 95 | 233 ms | 233 ms | 233 ms | 233 ms |
| Visual complete 99 | 233 ms | 233 ms | 233 ms | 233 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 252 ms on a 85 ms first byte.
Want to see how much CSS style-recalculation work delayed FCP and LCP, plus CPU long tasks? Run with --cpu.
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 54 ms. The total blocking time is 0 ms and 1 long task before first contentful paint with total time of 54 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.
cacheHeadersThe page has 1 request that are missing a cache time. Configure a cache time so the browser doesn't need to download them every time. It will save 447 B 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.
mimeTypesThe page has 1 misconfigured mime type.
It's not a great idea to let browsers guess content types (content sniffing), in some cases it can actually be a security risk.
doctypeThe page is missing a doctype. Please use <!DOCTYPE html>.
The <!DOCTYPE> declaration is not an HTML tag; it is an instruction to the web browser about what version of HTML the page is written in.
languageThe page is missing a language definition in the HTML tag. Define it with <html lang="YOUR_LANGUAGE_CODE">
According to the W3C recommendation you should declare the primary language for each Web page with the lang attribute inside the <html> tag https://www.w3.org/International/questions/qa-html-language-declarations#basics.
metaDescriptionThe page is missing a meta description.
Use a page description to make the page more relevant to search engines.
pageTitleThe page is missing a title.
Use a title to make the page more relevant to search engines.
viewportThe page is missing a viewport meta tag. Add <meta name="viewport" content="width=device-width, initial-scale=1"> so the browser lays the page out at the device width.
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 3 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
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
contentSecurityPolicyHeaderThe policy allows 'unsafe-inline', which lets the browser execute inline scripts and styles directly from the page. Move to nonces or hashes plus 'strict-dynamic' so that inline injection cannot run.
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
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.
Storage and connection
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.2s0.3sWhen the page main content is rendered, collected via the Largest Contentful Paint API. Read more about Largest Contentful Paint.
body > pre
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 |
|---|---|---|
cfCacheStatus | 0 ms | DYNAMIC |
cfEdge | 8 ms | – |
cfOrigin | 26 ms | – |
There are no custom configured scripts.
There are no custom extra metrics from scripting.
How the page is built.
| Header | Value |
|---|---|
accept-ranges | bytes |
alt-svc | h3=":443"; ma=86400 |
cache-control | public, max-age=0 |
cf-cache-status | DYNAMIC |
cf-ray | a449d95efa3b59ea-DEL |
content-encoding | gzip |
content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https:; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com data:; img-src 'self' data: blob: https:; media-src 'self' https: blob:; connect-src 'self' https: wss: blob:; worker-src 'self' blob:; frame-src 'self' https:; frame-ancestors 'none'; object-src 'none'; base-uri 'self'; form-action 'self' https://www.facebook.com |
content-security-policy-report-only | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https:; style-src 'self' 'unsafe-inline' https:; img-src 'self' data: blob: https:; font-src 'self' data: https:; media-src 'self' data: blob: https:; connect-src 'self' https: wss: blob:; worker-src 'self' blob:; frame-src 'self' https:; object-src 'none'; base-uri 'self'; form-action 'self' https:; frame-ancestors 'self'; |
content-type | text/plain; charset=UTF-8 |
date | Sat, 03 Oct 2026 06:21:51 GMT |
etag | W/"1580-1a0f8b10590" |
expect-ct | max-age=86400, enforce |
last-modified | Thu, 01 Oct 2026 18:19:06 GMT |
nel | {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800} |
permissions-policy | camera=(), microphone=(self), geolocation=(), interest-cohort=() |
referrer-policy | same-origin strict-origin-when-cross-origin |
report-to | {"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=hksK%2BhN%2B%2FRtUSeHVWpX2R%2BVrQ1cp9Q2Ix2B9JgbOONTOa93z5hl4Y1fB46it83jSVR8YbcY3KAVObx1GqnIKehKwl2539ztLmIyHSb%2FwFqm354cQlRJu2LAq"}]} |
server | cloudflare |
server-timing | cfCacheStatus;desc="DYNAMIC" cfEdge;dur=8,cfOrigin;dur=26 |
speculation-rules | "/cdn-cgi/speculation" |
strict-transport-security | max-age=31536000; includeSubDomains; preload |
vary | Accept-Encoding |
x-content-type-options | nosniff |
x-frame-options | SAMEORIGIN |
x-xss-protection | 1; mode=block |
| URL | Type | Transfer Size | Content Size |
|---|---|---|---|
| https://xelta.ai/favicon.ico | favicon | 9.3 KB | 8.3 KB |
| https://xelta.ai/llms.txt | plain | 3.5 KB | 5.4 KB |
| https://xelta.ai/cdn-cgi/speculation | other | 447 B | 151 B |
Transfer size13.3 KB
Content size13.8 KB
Requests3
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| favicon | 0 b | 9.3 KB | 8.3 KB | 1 |
| plain | 0 b | 3.5 KB | 5.4 KB | 1 |
| other | 0 b | 447 B | 151 B | 1 |
| Total | 0 b | 13.3 KB | 13.8 KB | 3 |
| Domain | Total download time | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| xelta.ai | 205 ms | 13.3 KB | 13.8 KB | 3 |
| type | min | median | max |
|---|---|---|---|
| Expires | 0 seconds | 0 seconds | 1 year |
| Last modified | 2 days | 2 days | 2 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 | 0 b | 0 |
| font | 0 b | 0 |
| favicon | 9.3 KB | 1 |
| Total | 9.3 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 | 9.3 KB | 1 |
| Total | 9.3 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.
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 .*xelta.* (use --firstParty to configure).
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 0 b | 0 b | 0 |
| css | 0 b | 0 b | 0 b | 0 |
| javascript | 0 b | 0 b | 0 b | 0 |
| image | 0 b | 0 b | 0 b | 0 |
| font | 0 b | 0 b | 0 b | 0 |
| favicon | 0 b | 9.3 KB | 8.3 KB | 1 |
| plain | 0 b | 3.5 KB | 5.4 KB | 1 |
| other | 0 b | 447 B | 151 B | 1 |
| Total | N/A | 13.3 KB | 13.8 KB | 3 |