Tested 2026-08-08 06:34:43 using Chrome 150.0.7871.46 (runtime settings)
This page is snappy to interact with, visually stable and follows best practices, but slow to paint and weak on user privacy.
Visual metrics
Google Web Vitals
The main document gets redirected 1 time(s). Remove those redirect and make the page faster!
The total JavaScript transfer size is 503.6 kB and the uncompressed size is 1.8 MB. This is totally crazy! There is really room for improvement here.
The page has 8 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 14.4 kB the next access.
Timings summary
| Metric | Min | Median | Mean | Max | Runs agree? |
|---|---|---|---|---|---|
| First visual change | 720 ms | 745 ms | 822 ms | 1.000 s | runs disagree ±19% |
| Last visual change | 2.365 s | 3.167 s | 3.030 s | 3.559 s | runs disagree ±19% |
| Speed index | 2.184 s | 2.961 s | 2.809 s | 3.281 s | runs disagree ±19% |
| Visual readiness | 1.645 s | 2.167 s | 2.209 s | 2.814 s | runs disagree ±27% |
| Visual complete 85 | 2.297 s | 3.134 s | 2.951 s | 3.423 s | runs disagree ±18% |
| Visual complete 95 | 2.297 s | 3.134 s | 2.951 s | 3.423 s | runs disagree ±18% |
| Visual complete 99 | 2.365 s | 3.167 s | 3.030 s | 3.559 s | runs disagree ±19% |
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.
The server dominated the wait. The first byte took 890 ms (89 % of the time to First Contentful Paint). Nothing can render before it arrives, and Google Web Vitals considers a TTFB over 800 ms in need of improvement. See the request timing on the Waterfall tab. First paint landed at 1.004 s; the 1 render-blocking request was done by 955 ms. The largest paint followed at 2.952 s.
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. 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 | 646 ms | 851 B | 645 ms |
efb0a5289ab5b833.cssblocking | 46 ms | 20.0 KB | 46 ms |
66 ms | 48.0 KB | 66 ms | |
0738 ms1.476 s2.214 sFCP 1.004 sLCP 2.952 s |
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.
documentRedirectThe main document gets redirected 1 time(s). Remove those redirect and make the page faster!
You should never ever redirect the main document, because it will make the page load slower for the user. Well, you should redirect the user if the user tries to use HTTP and there's an HTTPS version of the page. The coach checks for that. :)
javascriptSizeThe total JavaScript transfer size is 503.6 kB and the uncompressed size is 1.8 MB. This is totally crazy! There is really room for improvement here.
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?
cacheHeadersThe page has 8 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 14.4 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.
longTasksThe page has 2 CPU long tasks with the total of 179 ms. The total blocking time is 79 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.
largestContentfulPaintLargest contentful paint can be improved 2.952 s. It is in the Google Web Vitals needs improvement range, slower than 2.5 seconds.
Largest contentful paint is one of Google Web Vitals and reports the render time of the largest image or text block visible within the viewport, relative to when the page first started loading. To be fast according to Google, it needs to render before 2.5 seconds and results over 4 seconds is poor performance.
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://xeltacut.xelta.ai/projects | 8.5 KB | 35.8 KB |
responseOkThe page has 1 error response. The page has 1 response with code 402.
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 6 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.
mimeTypesThe page has 6 misconfigured mime types.
It's not a great idea to let browsers guess content types (content sniffing), in some cases it can actually be a security risk.
inlineCssThe page has both inline CSS and CSS requests even though it uses a HTTP/2-ish connection. If you have many users on slow connections, it can be better to only inline the CSS. Run your own tests and check the waterfall graph to see what happens.
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.
thirdPartyThe page do 13% requests to third party domains (4 requests and 25.9 kB). First party is 27 requests and 1.8 MB. The regex .*xelta.* was used to calculate first/third party requests.
Do not load most of your content from third party URLs.
unnecessaryHeadersThere are 31 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
thirdPartyPrivacyThe page has 3% requests that are 3rd party (1 requests with a size of 11.6 kB). The page do 1 utility request and uses 1 utility tool.
Using third party requests shares user information with that third party. Please avoid that! The project https://github.com/patrickhulce/third-party-web is used to categorize first/third party requests.
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.0s1.2s1.6s1.9s2.2s2.5s2.9s3.2sWhen 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) > 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 |
|---|---|---|
cfCacheStatus | 0 ms | DYNAMIC |
cfEdge | 14 ms | – |
cfOrigin | 0 ms | – |
cfWorker | 191 ms | – |
There are no custom configured scripts.
There are no custom extra metrics from scripting.
How the page is built.
https://xeltacut.xelta.ai/projects
| Header | Value |
|---|---|
alt-svc | h3=":443"; ma=86400 |
cache-control | s-maxage=31536000 |
cf-cache-status | DYNAMIC |
cf-ray | a27c7f35bf8059a8-DEL |
content-type | text/html; charset=utf-8 |
date | Sat, 08 Aug 2026 06:34:44 GMT |
expect-ct | max-age=86400, enforce |
location | /projects |
nel | {"report_to":"cf-nel","success_fraction":0.0,"max_age":604800} |
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=Sft1wwzhnArCg9Id9Oczm4rKkTvFYgkH9fv5QbavuUvJx5%2Fh5QmTEwRE2G35VXd8UiYt1ZE2eQmCXHZ9OUIre%2Bm4LTvGNL4O%2F5gzBHZr%2Bx2eVJCC80ecuJxnY7Cbn59bOL%2Fh"}]} |
server | cloudflare |
server-timing | cfCacheStatus;desc="DYNAMIC" cfEdge;dur=10,cfOrigin;dur=0,cfWorker;dur=558 |
speculation-rules | "/cdn-cgi/speculation" |
strict-transport-security | max-age=31536000; includeSubDomains; preload |
vary | rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding |
x-content-type-options | nosniff |
x-edge-served-by | AP |
x-frame-options | SAMEORIGIN |
x-nextjs-cache | HIT |
x-nextjs-prerender | 1, 1 |
x-nextjs-stale-time | 300 |
x-xss-protection | 1; mode=block |
Transfer size1.8 MB
Content size6.2 MB
Requests29
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 8.5 KB | 35.8 KB | 1 |
| css | 0 b | 20.0 KB | 116.7 KB | 1 |
| javascript | 0 b | 491.8 KB | 1.7 MB | 13 |
| image | 0 b | 8.6 KB | 6.5 KB | 3 |
| font | 0 b | 48.0 KB | 47.3 KB | 1 |
| favicon | 0 b | 4.9 KB | 9.6 KB | 1 |
| other | 0 b | 1.2 MB | 4.2 MB | 7 |
| json | 0 b | 1011 B | 896 B | 1 |
| plain | 0 b | 590 B | 0 b | 1 |
| Total | 0 b | 1.8 MB | 6.2 MB | 29 |
| Domain | Total download time | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| xeltacut.xelta.ai | 5.553 s | 1.7 MB | 6.1 MB | 27 |
| cdn.databuddy.cc | 298 ms | 13.1 KB | 36.6 KB | 1 |
| static.cloudflareinsights.com | 79 ms | 11.3 KB | 30.9 KB | 1 |
| basket.databuddy.cc | 1.560 s | 898 B | 289 B | 2 |
| type | min | median | max |
|---|---|---|---|
| Expires | 0 seconds | 4 weeks | 1 year |
| Last modified | 2 weeks | 2 weeks | 7 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 | 8.6 KB | 3 |
| font | 0 b | 0 |
| favicon | 4.9 KB | 1 |
| plain | 590 B | 1 |
| other | 1.2 MB | 6 |
| Total | 1.2 MB | 12 |
Includes requests done after DOM content loaded.
| Content | Transfer Size | Requests |
|---|---|---|
| html | 0 b | 0 |
| css | 0 b | 0 |
| javascript | 0 b | 0 |
| image | 8.6 KB | 3 |
| font | 0 b | 0 |
| favicon | 4.9 KB | 1 |
| plain | 590 B | 1 |
| other | 1.2 MB | 6 |
| Total | 1.2 MB | 12 |
--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 |
|---|---|---|---|---|---|
| b284e8c90acb9c8e.js | 1 | 105.9 ms | 55.9 ms | – | script tag |
| eb93a8df11b8a9c8.js | 2 | 105.9 ms | 21.6 ms | 0.7 ms | script tag, 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.
2 more long frames 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.
Requests by category1
Domains that didn't match any tool in Third party web. If you are sure they are third party domains, please do a PR to that project. You can also fine tune the list using --firstParty.
Transfer size1.8 MB
Content size6.2 MB
Requests31
Calculated using .*xelta.* (use --firstParty to configure).
| Content | Header Size | Transfer Size | Content Size | Requests |
|---|---|---|---|---|
| html | 0 b | 8.5 KB | 35.8 KB | 1 |
| css | 0 b | 20.0 KB | 116.7 KB | 1 |
| javascript | 0 b | 467.4 KB | 1.7 MB | 11 |
| image | 0 b | 8.6 KB | 6.5 KB | 3 |
| font | 0 b | 48.0 KB | 47.3 KB | 1 |
| favicon | 0 b | 4.9 KB | 9.6 KB | 1 |
| other | 0 b | 1.2 MB | 4.2 MB | 6 |
| json | 0 b | 1011 B | 896 B | 1 |
| plain | 0 b | 590 B | 0 b | 1 |
| Total | N/A | 1.7 MB | 6.1 MB | 27 |
| 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 | 24.4 KB | 67.4 KB | 2 |
| image | 0 b | 0 b | 0 b | 0 |
| font | 0 b | 0 b | 0 b | 0 |
| favicon | 0 b | 0 b | 0 b | 0 |
| other | 0 b | 0 b | 0 b | 1 |
| Total | N/A | 25.3 KB | 67.7 KB | 4 |