Page summary

https://xelta.ai/ai-tool

Tested 2026-09-22 14:46:07 using Chrome 150.0.7871.46 (runtime settings)

SummaryWaterfallMetricsRenderingCoachPageXrayCPUThird party

This page is fast to paint, visually stable and follows best practices, but a little janky to interact with and weak on user privacy.

77 / 100
Coach overall
78 / 100
Performance
91 / 100
Best practice
71 / 100
Privacy

How it loaded →

0 → 4.300 s · median run
Frame at 0 ms
start
Frame at 1000 ms
Largest paint1.000 s
Frame at 1700 ms
1.700 s
Frame at 2500 ms
2.500 s
Frame at 3200 ms
3.200 s
Frame at 4300 ms
Complete4.300 s
467 ms
First Visual Change
799 ms
Speed Index
1.067 s
Visual Complete 85%
4.300 s
Last Visual Change
TTFB171 msLCP864 msTBT266 msCLS0.00

What to act on · top recommendations

Don't scale images in the browser

0 / 100

The page has 11 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.

Avoid using Google Tag Manager.

0 / 100

The page is using Google Tag Manager, this is a performance risk since non-tech users can add JavaScript to your page.

Avoid CPU Long Tasks

0 / 100

The page has 8 CPU long tasks with the total of 689 ms. The total blocking time is 266 ms and 1 long task before first contentful paint with total time of 73 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.

Google Web Vitals

min · median · mean · max of 1 run
MetricMinMedianMeanMax
Time To First Byte (TTFB)171 ms171 ms171 ms171 ms
Largest Contentful Paint (LCP)864 ms864 ms864 ms864 ms
Cumulative Layout Shift (CLS)0000

Visual Metrics

min · median · mean · max of 1 run
MetricMinMedianMeanMax
First visual change467 ms467 ms467 ms467 ms
Last visual change4.300 s4.300 s4.300 s4.300 s
Speed index799 ms799 ms799 ms799 ms
Visual readiness3.833 s3.833 s3.833 s3.833 s
Visual complete 851.067 s1.067 s1.067 s1.067 s
Visual complete 951.067 s1.067 s1.067 s1.067 s
Visual complete 991.300 s1.300 s1.300 s1.300 s

CPU

min · median · mean · max of 1 run
MetricMinMedianMeanMax
Total Blocking Time266 ms266 ms266 ms266 ms
Max Potential FID149 ms149 ms149 ms149 ms
CPU long tasks 8888
CPU last long task happens at1.402 s1.402 s1.402 s1.402 s

More metrics

min · median · mean · max of 1 run
MetricMinMedianMeanMax
First paint468 ms468 ms468 ms468 ms
Load event end571 ms571 ms571 ms571 ms

User Timing

min · median · mean · max of 1 run
MetricMinMedianMeanMax
GTM-G-CPG3NLBKHP:150 ms0 ms0 ms0 ms
GTM-G-CPG3NLBKHP:171.003 s1.003 s1.003 s1.003 s
GTM-G-CPG3NLBKHP:41.329 s1.329 s1.329 s1.329 s
GTM-G-CPG3NLBKHP:81.339 s1.339 s1.339 s1.339 s
GTM-G-CPG3NLBKHP:31.340 s1.340 s1.340 s1.340 s
GTM-G-CPG3NLBKHP:21.341 s1.341 s1.341 s1.341 s
GTM-G-CPG3NLBKHP:71.341 s1.341 s1.341 s1.341 s
GTM-G-CPG3NLBKHP:1:131.342 s1.342 s1.342 s1.342 s
GTM-G-CPG3NLBKHP:1:111.343 s1.343 s1.343 s1.343 s
GTM-G-CPG3NLBKHP:1:101.347 s1.347 s1.347 s1.347 s
GTM-G-CPG3NLBKHP:1:121.347 s1.347 s1.347 s1.347 s
GTM-G-CPG3NLBKHP:2:131.347 s1.347 s1.347 s1.347 s
GTM-G-CPG3NLBKHP:2:111.347 s1.347 s1.347 s1.347 s
GTM-G-CPG3NLBKHP:2:101.348 s1.348 s1.348 s1.348 s
GTM-G-CPG3NLBKHP:2:121.348 s1.348 s1.348 s1.348 s
GTM-G-CPG3NLBKHP:2:10:221.349 s1.349 s1.349 s1.349 s
GTM-G-CPG3NLBKHP:2:10:211.350 s1.350 s1.350 s1.350 s
GTM-G-CPG3NLBKHP:2:12:221.350 s1.350 s1.350 s1.350 s
GTM-G-CPG3NLBKHP:2:12:211.353 s1.353 s1.353 s1.353 s
GTM-G-CPG3NLBKHP:2:26:221.353 s1.353 s1.353 s1.353 s
GTM-G-CPG3NLBKHP:2:26:211.353 s1.353 s1.353 s1.353 s
GTM-G-CPG3NLBKHP:2:25:221.353 s1.353 s1.353 s1.353 s
GTM-G-CPG3NLBKHP:2:25:211.353 s1.353 s1.353 s1.353 s
GTM-G-CPG3NLBKHP:2:24:221.353 s1.353 s1.353 s1.353 s
GTM-G-CPG3NLBKHP:2:24:211.354 s1.354 s1.354 s1.354 s
GTM-G-CPG3NLBKHP:2:23:221.354 s1.354 s1.354 s1.354 s
GTM-G-CPG3NLBKHP:2:23:211.355 s1.355 s1.355 s1.355 s
GTM-G-CPG3NLBKHP:2:22:221.355 s1.355 s1.355 s1.355 s
GTM-G-CPG3NLBKHP:2:22:211.356 s1.356 s1.356 s1.356 s
GTM-G-CPG3NLBKHP:2:21:221.357 s1.357 s1.357 s1.357 s
GTM-G-CPG3NLBKHP:2:21:211.357 s1.357 s1.357 s1.357 s
GTM-G-CPG3NLBKHP:2:20:221.357 s1.357 s1.357 s1.357 s
GTM-G-CPG3NLBKHP:2:20:211.358 s1.358 s1.358 s1.358 s
GTM-G-CPG3NLBKHP:2:19:221.358 s1.358 s1.358 s1.358 s
GTM-G-CPG3NLBKHP:2:19:211.359 s1.359 s1.359 s1.359 s
GTM-G-CPG3NLBKHP:2:18:221.359 s1.359 s1.359 s1.359 s
GTM-G-CPG3NLBKHP:2:18:211.359 s1.359 s1.359 s1.359 s
GTM-G-CPG3NLBKHP:2:17:221.359 s1.359 s1.359 s1.359 s
GTM-G-CPG3NLBKHP:2:17:211.360 s1.360 s1.360 s1.360 s
GTM-G-CPG3NLBKHP:2:16:221.360 s1.360 s1.360 s1.360 s
GTM-G-CPG3NLBKHP:2:16:211.360 s1.360 s1.360 s1.360 s
GTM-G-CPG3NLBKHP:2:15:221.361 s1.361 s1.361 s1.361 s
GTM-G-CPG3NLBKHP:2:15:211.361 s1.361 s1.361 s1.361 s
GTM-G-CPG3NLBKHP:2:14:221.361 s1.361 s1.361 s1.361 s
GTM-G-CPG3NLBKHP:2:14:211.361 s1.361 s1.361 s1.361 s
GTM-G-CPG3NLBKHP:2:13:221.361 s1.361 s1.361 s1.361 s
GTM-G-CPG3NLBKHP:2:13:211.361 s1.361 s1.361 s1.361 s
GTM-G-CPG3NLBKHP:3:131.362 s1.362 s1.362 s1.362 s
GTM-G-CPG3NLBKHP:3:111.362 s1.362 s1.362 s1.362 s
GTM-G-CPG3NLBKHP:3:101.362 s1.362 s1.362 s1.362 s
GTM-G-CPG3NLBKHP:3:121.362 s1.362 s1.362 s1.362 s
GTM-G-CPG3NLBKHP:3:8:221.362 s1.362 s1.362 s1.362 s
GTM-G-CPG3NLBKHP:3:8:211.363 s1.363 s1.363 s1.363 s
GTM-G-CPG3NLBKHP:11:131.363 s1.363 s1.363 s1.363 s
GTM-G-CPG3NLBKHP:12:141.390 s1.390 s1.390 s1.390 s
GTM-G-CPG3NLBKHP:51.390 s1.390 s1.390 s1.390 s
GTM-G-CPG3NLBKHP:13:131.391 s1.391 s1.391 s1.391 s
GTM-G-CPG3NLBKHP:13:111.391 s1.391 s1.391 s1.391 s
GTM-G-CPG3NLBKHP:13:101.392 s1.392 s1.392 s1.392 s
GTM-G-CPG3NLBKHP:13:121.392 s1.392 s1.392 s1.392 s
GTM-G-CPG3NLBKHP:14:131.392 s1.392 s1.392 s1.392 s
GTM-G-CPG3NLBKHP:14:111.393 s1.393 s1.393 s1.393 s
GTM-G-CPG3NLBKHP:14:101.393 s1.393 s1.393 s1.393 s
GTM-G-CPG3NLBKHP:14:121.393 s1.393 s1.393 s1.393 s
GTM-G-CPG3NLBKHP:1:91.394 s1.394 s1.394 s1.394 s
GTM-G-CPG3NLBKHP:2:10:201.394 s1.394 s1.394 s1.394 s
GTM-G-CPG3NLBKHP:2:12:201.395 s1.395 s1.395 s1.395 s
GTM-G-CPG3NLBKHP:2:26:201.395 s1.395 s1.395 s1.395 s
GTM-G-CPG3NLBKHP:2:25:201.396 s1.396 s1.396 s1.396 s
GTM-G-CPG3NLBKHP:2:24:201.396 s1.396 s1.396 s1.396 s
GTM-G-CPG3NLBKHP:2:23:201.396 s1.396 s1.396 s1.396 s
GTM-G-CPG3NLBKHP:2:22:201.396 s1.396 s1.396 s1.396 s
GTM-G-CPG3NLBKHP:2:21:201.396 s1.396 s1.396 s1.396 s
GTM-G-CPG3NLBKHP:2:20:201.397 s1.397 s1.397 s1.397 s
GTM-G-CPG3NLBKHP:2:19:201.397 s1.397 s1.397 s1.397 s
GTM-G-CPG3NLBKHP:2:18:201.397 s1.397 s1.397 s1.397 s
GTM-G-CPG3NLBKHP:2:17:201.398 s1.398 s1.398 s1.398 s
GTM-G-CPG3NLBKHP:2:16:201.398 s1.398 s1.398 s1.398 s
GTM-G-CPG3NLBKHP:2:15:201.398 s1.398 s1.398 s1.398 s
GTM-G-CPG3NLBKHP:2:14:201.398 s1.398 s1.398 s1.398 s
GTM-G-CPG3NLBKHP:2:13:201.399 s1.399 s1.399 s1.399 s
GTM-G-CPG3NLBKHP:3:8:201.399 s1.399 s1.399 s1.399 s
GTM-G-CPG3NLBKHP:13:91.399 s1.399 s1.399 s1.399 s
GTM-G-CPG3NLBKHP:14:91.399 s1.399 s1.399 s1.399 s
GTM-G-CPG3NLBKHP:61.399 s1.399 s1.399 s1.399 s
GTM-G-CPG3NLBKHP:2:91.402 s1.402 s1.402 s1.402 s
GTM-G-CPG3NLBKHP:3:91.402 s1.402 s1.402 s1.402 s

Waterfall

Run 1 SpeedIndex median

First paintFCPLCPDOMContentLoadedDOM interactiveLoadRender-blockingRedirectError

Rendering

Run 1 · median
0.000 s
0s1s2s3s4s

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 video

Filmstrip

37 frames

Use --filmstrip.showAll to show all filmstrips.

Frame at 0 ms
0 ms
0 %
Frame at 400 ms
400 ms
0 %
Frame at 500 ms
500 ms
40 %
Frame at 600 ms
600 ms
40 %
Frame at 700 ms
700 ms
40 %
Frame at 800 ms
800 ms
40 %
Frame at 900 ms
900 ms
71 %
Frame at 1.000 s
1.000 s
72 %
Frame at 1.100 s
1.100 s
97 %
Frame at 1.200 s
1.200 s
98 %
Frame at 1.300 s
1.300 s
99 %
Frame at 1.400 s
1.400 s
99 %
Frame at 1.500 s
1.500 s
99 %
Frame at 1.600 s
1.600 s
99 %
Frame at 1.700 s
1.700 s
99 %
Frame at 1.800 s
1.800 s
99 %
Frame at 1.900 s
1.900 s
99 %
Frame at 2.000 s
2.000 s
99 %
Frame at 2.100 s
2.100 s
99 %
Frame at 2.200 s
2.200 s
99 %
Frame at 2.300 s
2.300 s
99 %
Frame at 2.400 s
2.400 s
99 %
Frame at 2.500 s
2.500 s
99 %
Frame at 2.600 s
2.600 s
99 %
Frame at 2.700 s
2.700 s
99 %
Frame at 2.800 s
2.800 s
99 %
Frame at 2.900 s
2.900 s
99 %
Frame at 3.000 s
3.000 s
99 %
Frame at 3.100 s
3.100 s
99 %
Frame at 3.200 s
3.200 s
99 %
Frame at 3.300 s
3.300 s
99 %
Frame at 3.400 s
3.400 s
99 %
Frame at 3.500 s
3.500 s
99 %
Frame at 3.600 s
3.600 s
99 %
Frame at 3.700 s
3.700 s
99 %
Frame at 3.800 s
3.800 s
99 %
Frame at 4.300 s
4.300 s
100 %

Click a frame to seek the video to that moment. The dot marks frames where the page changed visually.

Why was rendering delayed?

Rendering was not meaningfully delayed. First paint landed at 468 ms on a 171 ms first byte; the 2 render-blocking requests were done by 348 ms and the remaining ~120 ms is style and layout work. The largest paint followed at 864 ms.

Want to see how much CSS style-recalculation work delayed FCP and LCP, plus CPU long tasks? Run with --cpu.

Render blocking requests

25 requests · 469.0 KB

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.

RequestWhen it loadedTransferDownload
document
xelta.ai · TTFB 171 ms
185 ms
27.4 KB183 ms
css · xelta.ai
143 ms
89.3 KB143 ms
css · xelta.ai
77 ms
3.7 KB77 ms
2cc4dk9_-w4i-.jspotentially blocking
javascript · xelta.ai
170 ms
73.3 KB170 ms
25ym4jnna99b5.jspotentially blocking
javascript · xelta.ai
157 ms
48.8 KB157 ms
0r_-zfn80zo41.jspotentially blocking
javascript · xelta.ai
144 ms
2.3 KB144 ms
1vagg_skbh5uc.jspotentially blocking
javascript · xelta.ai
144 ms
2.0 KB144 ms
199dgixr4wd7s.jspotentially blocking
javascript · xelta.ai
144 ms
23.8 KB144 ms
2qwl8sgb3v89v.jspotentially blocking
javascript · xelta.ai
143 ms
19.7 KB143 ms
17 more requests
all done by 413 ms
206.1 KB
LCP resource
image — downloaded by 408 ms, rendered at 864 ms
166 ms
27.8 KB166 ms
web font · xelta.ai · finished after first paint
36 ms
65.5 KB36 ms
web font · xelta.ai · finished after first paint
29 ms
9.8 KB29 ms
web font · xelta.ai · finished after first paint
26 ms
8.8 KB26 ms
0216 ms648 msFCP 468 msLCP 864 ms

Coach

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.

Performance advice

78
2 errors9 warnings4 info
warn(0)Don't scale images in the browseravoidScalingImages

The page has 11 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.

Offenders
warn(0)Avoid using Google Tag Manager.googleTagManager

The page is using Google Tag Manager, this is a performance risk since non-tech users can add JavaScript to your page.

Google Tag Manager makes it possible for non tech users to add scripts to your page that will downgrade performance.

warn(0)Avoid CPU Long TaskslongTasks

The page has 8 CPU long tasks with the total of 689 ms. The total blocking time is 266 ms and 1 long task before first contentful paint with total time of 73 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.

Offenders
  • unknown
  • self
  • self
  • unknown
  • self
  • self
  • self
  • self
warn(0)Total JavaScript size shouldn't be too bigjavascriptSize

The total JavaScript transfer size is 1.2 MB and the uncompressed size is 4 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?

Offenders
URLTransferContent
https://xelta.ai/_next/static/chunks/0_cis5bf89bk3.js3.7 KB9.3 KB
https://xelta.ai/_next/static/chunks/3er0xpd5wsvv-.js11.3 KB38.9 KB
https://xelta.ai/_next/static/chunks/2cc4dk9_-w4i-.js73.3 KB232.0 KB
https://xelta.ai/_next/static/chunks/25ym4jnna99b5.js48.8 KB171.2 KB
https://xelta.ai/_next/static/chunks/turbopack-1vqwnc7wbbpm2.js6.6 KB18.4 KB
https://xelta.ai/_next/static/chunks/0wfygv4307v4j.js6.5 KB20.8 KB
https://xelta.ai/_next/static/chunks/2uoulaw6kucli.js10.1 KB26.2 KB
https://xelta.ai/_next/static/chunks/403qh4uu73dc5.js5.9 KB14.3 KB
https://xelta.ai/_next/static/chunks/444qa-9lnnm8j.js9.9 KB24.2 KB
https://xelta.ai/_next/static/chunks/26x6fmtag4t-4.js11.3 KB31.4 KB
https://xelta.ai/_next/static/chunks/00up96pc24a4e.js10.4 KB25.8 KB
https://xelta.ai/_next/static/chunks/3wuo8wdooey29.js8.4 KB34.0 KB
https://xelta.ai/_next/static/chunks/2juhx6ts-ps8o.js15.1 KB45.8 KB
https://xelta.ai/_next/static/chunks/2_mphrdu04vzv.js13.8 KB39.3 KB
https://xelta.ai/_next/static/chunks/1rttzs2jjmcrm.js44.0 KB140.6 KB
https://xelta.ai/_next/static/chunks/1d_v2ad2mjc3_.js10.9 KB29.7 KB
https://xelta.ai/_next/static/chunks/1spzo3397ba2t.js6.5 KB14.5 KB
https://xelta.ai/_next/static/chunks/3harezu8knhoz.js8.0 KB21.0 KB
https://xelta.ai/_next/static/chunks/15jgvcbmyanuo.js18.1 KB54.6 KB
https://xelta.ai/_next/static/chunks/2f2i__v854m6r.js9.2 KB30.0 KB
https://xelta.ai/_next/static/chunks/2qwl8sgb3v89v.js19.7 KB62.0 KB
https://xelta.ai/_next/static/chunks/199dgixr4wd7s.js23.8 KB67.5 KB
https://xelta.ai/_next/static/chunks/1vagg_skbh5uc.js2.0 KB1.7 KB
https://xelta.ai/_next/static/chunks/0r_-zfn80zo41.js2.3 KB2.7 KB
https://static.cloudflareinsights.com/beacon.min.js/v31edd6df95cf4e85bb4c19e7a9bdbcba178836298749510.1 KB29.6 KB
https://xelta.ai/_next/static/chunks/0ga4rs1yp22vv.js2.4 KB3.0 KB
https://xelta.ai/_next/static/chunks/2tldojfjwreij.js10.6 KB36.2 KB
https://xelta.ai/_next/static/chunks/2aamqngoqh57z.js6.1 KB16.1 KB
https://xelta.ai/_next/static/chunks/36h4r9duhyjke.js11.1 KB37.2 KB
https://xelta.ai/_next/static/chunks/2oue1a6qt5s20.js1.4 KB493 B
https://xelta.ai/_next/static/chunks/2axbiy1_jtyuw.js1.7 KB1.2 KB
https://xelta.ai/_next/static/chunks/3c9-jx0jhg1zb.js2.1 KB1.8 KB
https://xelta.ai/analytics/gtm.js1.6 KB403 B
https://www.googletagmanager.com/gtag/js?id=G-CPG3NLBKHP187.5 KB569.0 KB
https://xelta.ai/analytics/ga4.js1.4 KB144 B
https://xelta.ai/analytics/meta-pixel.js1.6 KB514 B
https://xelta.ai/_next/static/chunks/1ki4hltmjvw2d.js77.6 KB253.9 KB
https://xelta.ai/_next/static/chunks/3a5v007d95ttp.js41.8 KB139.5 KB
https://xelta.ai/_next/static/chunks/3f1tw02kuplod.js3.3 KB6.2 KB
https://xelta.ai/_next/static/chunks/2k5vpzc_p9jpq.js35.3 KB106.7 KB
https://www.googletagmanager.com/gtm.js?id=GTM-5XNS5NQ2114.9 KB324.3 KB
https://connect.facebook.net/en_US/fbevents.js110.8 KB411.9 KB
https://connect.facebook.net/signals/config/1123404090023729.../1123404090023729139.6 KB497.2 KB
https://xelta.ai/_next/static/chunks/28r3ari2she5h.js1.2 KB217 B
https://xelta.ai/_next/static/chunks/34zqwff648hvy.js10.7 KB33.9 KB
https://xelta.ai/_next/static/chunks/0ibqqj5n22681.js10.4 KB31.0 KB
https://xelta.ai/_next/static/chunks/38cqstpd1yycs.js47.0 KB206.7 KB
warn(10)Avoid extra requests by setting cache headerscacheHeaders

The page has 9 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 11.2 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.

Offenders
warn(50)Total CSS size shouldn't be too bigcssSize

The total CSS transfer size is 96.6 kB and uncompressed size is 707.8 kB. That is big and the CSS could most probably be smaller.

Delivering a massive amount of CSS to the browser is not the best thing you can do, because it means more work for the browser when parsing the CSS against the HTML and that makes the rendering slower. Try to send only the CSS that is used on that page. And make sure to remove CSS rules when they aren't used anymore.

Offenders
URLTransferContent
https://xelta.ai/_next/static/chunks/15zws3noqtpa8.css89.3 KB658.8 KB
https://xelta.ai/_next/static/chunks/1eteo4yyc63ev.css3.7 KB28.9 KB
https://fonts.googleapis.com/css2...ogleapis.com/css21.2 KB3.5 KB
infoThe favicon should be small and cacheablefavicon

The favicon size is 10.8 kB bytes. That's quite big, can you make it smaller?

It is easy to make the favicon big but please avoid doing that, because every browser will then perform an unnecessarily large download. And make sure the cache headers are set for a long time for the favicon. It is easy to miss since it's another content type.

Offenders
infoAvoid too many fontsfewFonts

The page has 5 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.

Offenders
warn(60)Don't use private headers on static contentprivateAssets

The page has 4 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.

Offenders
warn(70)Apply the right priority hints to the LCP imagelcpImageHints

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

Offenders
  • <img alt="Website Builder" loading="eager" width="550" height="280" decoding="async" data-nimg="1" class="rounded-xl sm:rounded-[32px] w-full aspect-[4/3] sm:aspect-auto sm:h-[240px] md:h-[280px] object-cover" sizes="(max-width: 640px) 50vw, (max-width: 1200px) 50vw, 550px" srcset="/_next/image?url=https%3A%2F%2Fmedia.xelta.ai%2Fuploads%2Finput%2Fdefault%2F1783407794358-4a3b2fe493c62c36.png&amp;w=384&amp;q=75 384w, /_next/image?url=https%3A%2F%2Fmedia.xelta.ai%2Fuploads%2Finput%2Fdefault%2F1783407794358-4a3b2fe493c62c36.png&amp;w=640&amp;q=75 640w, /_next/image?url=https%3A%2F%2Fmedia.xelta.ai%2Fuploads%2Finput%2Fdefault%2F1783407794358-4a3b2fe493c62c36.png&amp;w=750&amp;q=75 750w, /_next/image?url=https%3A%2F%2Fmedia.xelta.ai%2Fuploads%2Finput%2Fdefault%2F1783407794358-4a3b2fe493c62c36.png&amp;w=828&amp;q=75 828w, /_next/image?url=https%3A%2F%2Fmedia.xelta.ai%2Fuploads%2Finput%2Fdefault%2F1783407794358-4a3b2fe493c62c36.png&amp;w=1080&amp;q=75 1080w, /_next/image?url=https%3A%2F%2Fmedia.xelta.ai%2Fuploads%2Finput%2Fdefault%2F1783407794358-4a3b2fe493c62c36.png&amp;w=1200&amp;q=75 1200w, /_next/image?url=https%3A%2F%2Fmedia.xelta.ai%2Fuploads%2Finput%2Fdefault%2F1783407794358-4a3b2fe493c62c36.png&amp;w=1920&amp;q=75 1920w" src="https://xelta.ai/_next/image?url=https%3A%2F%2Fmedia.xelta.ai%2Fuploads%2Finput%2Fdefault%2F1783407794358-4a3b2fe493c62c36.png&amp;w=1920&amp;q=75" style="color: transparent;">
infoLong cache headers is goodcacheHeadersLong
error(90)Avoid Frontend single point of failuresspof

The page has 1 request inside of the head that can cause a SPOF (single point of failure). Load them asynchronously or move them outside of the document head.

A page can be stopped from loading in the browser if a single JavaScript, CSS, and in some cases a font, couldn't be fetched or is loading really slowly (the white screen of death). That is a scenario you really want to avoid. Never load 3rd-party components synchronously inside of the head tag.

Offenders
infoMake each CSS response smalloptimalCssSize

https://xelta.ai/_next/static/chunks/15zws3noqtpa8.css size is 91.5 kB (91494) and that is bigger than the limit of 25 kB. Try to keep each CSS response under 25 kB.

Render-blocking CSS holds up the first paint until it has fully downloaded, parsed and applied, so smaller CSS files mean a faster start. Split your CSS into a small critical bundle inlined or eagerly loaded, with the rest lazy-loaded.

Offenders
URLTransferContent
https://xelta.ai/_next/static/chunks/15zws3noqtpa8.css89.3 KB658.8 KB
warn(95)Inline CSS for faster first renderinlineCss

The 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.

error(99)Avoid using incorrect mime typesmimeTypes

The 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.

Offenders

Best practice advice

91
1 warning3 info
infoAvoid unnecessary headersunnecessaryHeaders

There are 1 response that sets a p3p header. There are 6 responses that sets both a max-age and expires header. There are 3 responses that sets a pragma no-cache header (that is a request header). There are 91 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.

Offenders
warn(50)Avoid too many third party requeststhirdParty

The page do 17% requests to third party domains (16 requests and 587.5 kB). First party is 77 requests and 1.2 MB. The regex .*xelta.* was used to calculate first/third party requests.

Do not load most of your content from third party URLs.

infoDo not send too long headerslongHeaders

https://xelta.ai/ai-tool has a header content-security-policy-report-only that is 805 characters long. https://xelta.ai/ai-tool has a header report-to that is 611 characters long. https://xelta.ai/_ne..._v2fun1jzxk.woff2 has a header content-security-policy-report-only that is 805 characters long. https://xelta.ai/_ne..._v2fun1jzxk.woff2 has a header report-to that is 607 characters long. https://xelta.ai/icons/favicon.ico has a header content-security-policy-report-only that is 805 characters long. https://xelta.ai/icons/favicon.ico has a header report-to that is 607 characters long. https://connect.face...en_US/fbevents.js has a header content-security-policy that is 1344 characters long. https://connect.face...en_US/fbevents.js has a header permissions-policy that is 874 characters long. https://connect.face.../1123404090023729 has a header content-security-policy that is 1344 characters long. https://connect.face.../1123404090023729 has a header permissions-policy that is 874 characters long.

Do not send response headers that are too long.

Offenders
infoAvoid use too many response headersmanyHeaders

https://xelta.ai/api...nts/active-banner has 33 headers.https://xelta.ai/api...cms/announcements has 33 headers.https://xelta.ai/api...nt/public/pricing has 33 headers.https://xelta.ai/api/cms/maintenance has 33 headers.https://xelta.ai/api/geo has 32 headers.

Avoid send too many response headers.

Offenders

Privacy advice

71
6 warnings2 info
warn(0)Avoid using Google Analyticsga

The page is using Google Analytics meaning you share your users private information with Google. You should use analytics that care about user privacy, something like https://matomo.org.

Google Analytics share private user information with Google that your user hasn't agreed on sharing.

warn(0)Avoid embedding services from surveillance capitalist companiessurveillance

The page embeds 4 resources from companies that profit from user surveillance. Consider privacy-respecting alternatives.

Embedding scripts or iframes from companies whose business model is surveillance capitalism (Google, Facebook, etc.) leaks detailed user data on every page view, often before the user has had a chance to consent. See https://en.wikipedia.org/wiki/Surveillance_capitalism for background. Prefer privacy-respecting alternatives where possible.

Offenders
infoSet a Cross-Origin-Embedder-Policy header so cross-origin subresources opt in to being embedded.crossOriginEmbedderPolicyHeader

Set 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

Offenders
warn(0)Set a Cross-Origin-Opener-Policy header to isolate the page from cross-origin windows.crossOriginOpenerPolicyHeader

Set 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

Offenders
infoSet a Cross-Origin-Resource-Policy header to limit who may embed the page.crossOriginResourcePolicyHeader

Set 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

Offenders
warn(0)Do not share user data with third parties.thirdPartyPrivacy

The page has 13% requests that are 3rd party (12 requests with a size of 586.9 kB). The page also have request to companies that harvest data from users and do not respect users privacy (see https://en.wikipedia.org/wiki/Surveillance_capitalism). The page do 11 survelliance requests and uses 6 survelliance tools. The page do 11 surveillance requests and uses 6 surveillance tools. The page do 2 utility requests and uses 2 utility tools. The page do 3 tag-manager requests and uses 1 tag-manager tool. The page do 3 social requests and uses 1 social tool. The page do 1 analytics request and uses 1 analytics tool. The page do 1 ad request and uses 1 ad 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.

Offenders
warn(60)Use a strict Content-Security-Policy header to mitigate cross-site scripting (XSS) attacks.contentSecurityPolicyHeader

The 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

warn(90)Avoid third party cookies that is used to track the user.thirdPartyCookies

The page sets 1 third party cookie.

Third party cookies are used to track the user. They are automatically blocked in Safari and Firefox.

Offenders
  • .facebook.com

Page info

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.

Page info

Document

What the page says it is and how large it rendered.

TitleAI Tools - Instant Ads, Background Remover & More | XeltaThe document title, shown in the browser tab and used by search results.
Layout viewport1350 × 1314 pxThe width the page laid out at, and the full height of the rendered document.

DOM structure

How much markup the browser has to build, style and lay out.

DOM elements1,446Very large, slows layout and styleTotal HTML elements. Fewer means less for the browser to style, lay out and paint.
Avg DOM depth11How deeply elements are nested on average.
Max DOM depth16The deepest nesting on the page. Deep branches cost more style recalculation.
Iframes1Embedded documents. Each is a separate page the browser loads and renders.
Script tags55Number of script elements. More scripts usually means more main-thread work.

Storage and connection

What the page stored on the client, and the network it was tested on.

Local storage844 BData the page saved in localStorage, kept across visits.
Session storage565 BData kept in sessionStorage for this tab session only.
Connection type4GWhat the Network Information API reported for the test connection.

Resource hints

4 hints
dns-prefetch
  • https://media.xelta.ai/
preconnect
  • https://fonts.googleapis.com/
  • https://fonts.gstatic.com/
  • https://media.xelta.ai/

Technologies used to build the page

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.

Detected technologies

6 technologies

Third-party tools

19 tools

Data collected using Third Party Web version 0.29.2.

Cdn
  • Google Fonts
Survelliance
  • Google Fonts
  • Google Tag Manager
  • Facebook
  • Google Analytics
  • Google/Doubleclick Ads
  • Other Google APIs/SDKs
Surveillance
  • Google Fonts
  • Google Tag Manager
  • Facebook
  • Google Analytics
  • Google/Doubleclick Ads
  • Other Google APIs/SDKs
Utility
  • Cloudflare
  • Other Google APIs/SDKs
Tag-manager
  • Google Tag Manager
Social
  • Facebook
Analytics
  • Google Analytics
Ad
  • Google/Doubleclick Ads

Data from run 1

Visual Metrics

Visual milestones

all times from navigation start
Speed Index0.80 show quickly the page looked done
First Visual Change0.47 sfirst paint reaches the screen
Last Visual Change4.30 sscreen stops changing · 3.83 s after first
≥99%
0.47 sFirst Visual Change
1.07 sVisual Complete 85% · Visual Complete 95%
1.30 sVisual Complete 99%
Last Visual Change4.30 s
Visual Readiness3.83 s· first to last change
01.0 s2.0 s3.0 s4.0 s
Content milestones
Perception index
Visual progress
Visual progress at 0 s0.0s
Visual progress at 0.8 s0.8s
Visual progress at 1.3 s1.3s
Visual progress at 1.8 s1.8s
Visual progress at 2.4 s2.4s
Visual progress at 2.9 s2.9s
Visual progress at 3.4 s3.4s
Visual progress at 4.3 s4.3s
FCP0.47s
LCP0.86s
VC851.07s
Long tasks
0.0s0.9s1.7s2.6s3.4s4.3s

Google Web Vitals

from run 1
171 msTTFB
Good
266 msTBT
Needs improvement

Largest Contentful Paint

When the page main content is rendered, collected via the Largest Contentful Paint API. Read more about Largest Contentful Paint.

864 msLCP render time

Phase breakdown

  • TTFB171 ms
  • Resource load delay29 ms
  • Resource load duration221 ms
  • Element render delay444 ms

Element

Element type
<img>
Size (w × h)
105520
URL
https://xelta.ai/_ne...ta.ai/_next/image
Load time
768 ms

DOM path

body > div#app-root > div:eq(1) > section > div:eq(1) > div > a:eq(0) > div > div:eq(0) > img
LCP

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:

LCP element

Cumulative Layout Shift

How much the page's content shifts as it loads, collected via the Cumulative Layout Shift API.

0.000cumulative layout shift score

Elements that shifted

Sorted by individual shift score (higher = bigger shift). The top entries usually account for most of the page's CLS.

  • #10.000<div class="hidden lg:flex items-center flex-shrink-0 ml-auto"></div>
    body > div#app-root > header > div > div:eq(2)
Layout shift

Elements that shifted by more than 0.01 are highlighted in the screenshot. If an element shifted outside the viewport, it won't appear here. Check the video or filmstrip to see the shift.

Browser Metrics

Navigation Timing
Extra timings
User Timing marks
GTM-G-CPG3NLBKHP:150 ms
GTM-G-CPG3NLBKHP:171.003 s
GTM-G-CPG3NLBKHP:41.329 s
GTM-G-CPG3NLBKHP:81.339 s
GTM-G-CPG3NLBKHP:31.340 s
GTM-G-CPG3NLBKHP:21.341 s
GTM-G-CPG3NLBKHP:71.341 s
GTM-G-CPG3NLBKHP:1:131.342 s
GTM-G-CPG3NLBKHP:1:111.343 s
GTM-G-CPG3NLBKHP:1:101.347 s
GTM-G-CPG3NLBKHP:1:121.347 s
GTM-G-CPG3NLBKHP:2:131.347 s
GTM-G-CPG3NLBKHP:2:111.347 s
GTM-G-CPG3NLBKHP:2:101.348 s
GTM-G-CPG3NLBKHP:2:121.348 s
GTM-G-CPG3NLBKHP:2:10:221.349 s
GTM-G-CPG3NLBKHP:2:10:211.350 s
GTM-G-CPG3NLBKHP:2:12:221.350 s
GTM-G-CPG3NLBKHP:2:12:211.353 s
GTM-G-CPG3NLBKHP:2:26:221.353 s
GTM-G-CPG3NLBKHP:2:26:211.353 s
GTM-G-CPG3NLBKHP:2:25:221.353 s
GTM-G-CPG3NLBKHP:2:25:211.353 s
GTM-G-CPG3NLBKHP:2:24:221.353 s
GTM-G-CPG3NLBKHP:2:24:211.354 s
GTM-G-CPG3NLBKHP:2:23:221.354 s
GTM-G-CPG3NLBKHP:2:23:211.355 s
GTM-G-CPG3NLBKHP:2:22:221.355 s
GTM-G-CPG3NLBKHP:2:22:211.356 s
GTM-G-CPG3NLBKHP:2:21:221.357 s
GTM-G-CPG3NLBKHP:2:21:211.357 s
GTM-G-CPG3NLBKHP:2:20:221.357 s
GTM-G-CPG3NLBKHP:2:20:211.358 s
GTM-G-CPG3NLBKHP:2:19:221.358 s
GTM-G-CPG3NLBKHP:2:19:211.359 s
GTM-G-CPG3NLBKHP:2:18:221.359 s
GTM-G-CPG3NLBKHP:2:18:211.359 s
GTM-G-CPG3NLBKHP:2:17:221.359 s
GTM-G-CPG3NLBKHP:2:17:211.360 s
GTM-G-CPG3NLBKHP:2:16:221.360 s
GTM-G-CPG3NLBKHP:2:16:211.360 s
GTM-G-CPG3NLBKHP:2:15:221.361 s
GTM-G-CPG3NLBKHP:2:15:211.361 s
GTM-G-CPG3NLBKHP:2:14:221.361 s
GTM-G-CPG3NLBKHP:2:14:211.361 s
GTM-G-CPG3NLBKHP:2:13:221.361 s
GTM-G-CPG3NLBKHP:2:13:211.361 s
GTM-G-CPG3NLBKHP:3:131.362 s
GTM-G-CPG3NLBKHP:3:111.362 s
GTM-G-CPG3NLBKHP:3:101.362 s
GTM-G-CPG3NLBKHP:3:121.362 s
GTM-G-CPG3NLBKHP:3:8:221.362 s
GTM-G-CPG3NLBKHP:3:8:211.363 s
GTM-G-CPG3NLBKHP:11:131.363 s
GTM-G-CPG3NLBKHP:12:141.390 s
GTM-G-CPG3NLBKHP:51.390 s
GTM-G-CPG3NLBKHP:13:131.391 s
GTM-G-CPG3NLBKHP:13:111.391 s
GTM-G-CPG3NLBKHP:13:101.392 s
GTM-G-CPG3NLBKHP:13:121.392 s
GTM-G-CPG3NLBKHP:14:131.392 s
GTM-G-CPG3NLBKHP:14:111.393 s
GTM-G-CPG3NLBKHP:14:101.393 s
GTM-G-CPG3NLBKHP:14:121.393 s
GTM-G-CPG3NLBKHP:1:91.394 s
GTM-G-CPG3NLBKHP:2:10:201.394 s
GTM-G-CPG3NLBKHP:2:12:201.395 s
GTM-G-CPG3NLBKHP:2:26:201.395 s
GTM-G-CPG3NLBKHP:2:25:201.396 s
GTM-G-CPG3NLBKHP:2:24:201.396 s
GTM-G-CPG3NLBKHP:2:23:201.396 s
GTM-G-CPG3NLBKHP:2:22:201.396 s
GTM-G-CPG3NLBKHP:2:21:201.396 s
GTM-G-CPG3NLBKHP:2:20:201.397 s
GTM-G-CPG3NLBKHP:2:19:201.397 s
GTM-G-CPG3NLBKHP:2:18:201.397 s
GTM-G-CPG3NLBKHP:2:17:201.398 s
GTM-G-CPG3NLBKHP:2:16:201.398 s
GTM-G-CPG3NLBKHP:2:15:201.398 s
GTM-G-CPG3NLBKHP:2:14:201.398 s
GTM-G-CPG3NLBKHP:2:13:201.399 s
GTM-G-CPG3NLBKHP:3:8:201.399 s
GTM-G-CPG3NLBKHP:13:91.399 s
GTM-G-CPG3NLBKHP:14:91.399 s
GTM-G-CPG3NLBKHP:61.399 s
GTM-G-CPG3NLBKHP:2:91.402 s
GTM-G-CPG3NLBKHP:3:91.402 s
User Timing measures
GTM-G-CPG3NLBKHP:15:170 msduration 1.003 s
GTM-G-CPG3NLBKHP:12:17:141.003 sduration 386 ms
GTM-G-CPG3NLBKHP:4:31.329 sduration 11 ms
GTM-G-CPG3NLBKHP:8:71.339 sduration 2 ms
GTM-G-CPG3NLBKHP:2:51.341 sduration 49 ms
GTM-G-CPG3NLBKHP:2:61.341 sduration 58 ms
GTM-G-CPG3NLBKHP:1:13:121.342 sduration 5 ms
GTM-G-CPG3NLBKHP:1:13:91.342 sduration 52 ms
GTM-G-CPG3NLBKHP:1:11:101.343 sduration 4 ms
GTM-G-CPG3NLBKHP:2:13:121.347 sduration 1 ms
GTM-G-CPG3NLBKHP:2:13:91.347 sduration 54 ms
GTM-G-CPG3NLBKHP:2:11:101.347 sduration 1 ms
GTM-G-CPG3NLBKHP:2:10:22:211.349 sduration 1 ms
GTM-G-CPG3NLBKHP:2:10:22:201.349 sduration 45 ms
GTM-G-CPG3NLBKHP:2:12:22:211.350 sduration 2 ms
GTM-G-CPG3NLBKHP:2:12:22:201.350 sduration 45 ms
GTM-G-CPG3NLBKHP:2:26:22:211.353 sduration 0 ms
GTM-G-CPG3NLBKHP:2:26:22:201.353 sduration 43 ms
GTM-G-CPG3NLBKHP:2:25:22:211.353 sduration 0 ms
GTM-G-CPG3NLBKHP:2:25:22:201.353 sduration 43 ms
GTM-G-CPG3NLBKHP:2:24:22:211.353 sduration 1 ms
GTM-G-CPG3NLBKHP:2:24:22:201.353 sduration 43 ms
GTM-G-CPG3NLBKHP:2:23:22:211.354 sduration 1 ms
GTM-G-CPG3NLBKHP:2:23:22:201.354 sduration 42 ms
GTM-G-CPG3NLBKHP:2:22:22:211.355 sduration 1 ms
GTM-G-CPG3NLBKHP:2:22:22:201.355 sduration 41 ms
GTM-G-CPG3NLBKHP:2:21:22:211.357 sduration 1 ms
GTM-G-CPG3NLBKHP:2:21:22:201.357 sduration 40 ms
GTM-G-CPG3NLBKHP:2:20:22:211.357 sduration 1 ms
GTM-G-CPG3NLBKHP:2:20:22:201.357 sduration 39 ms
GTM-G-CPG3NLBKHP:2:19:22:211.358 sduration 1 ms
GTM-G-CPG3NLBKHP:2:19:22:201.358 sduration 39 ms
GTM-G-CPG3NLBKHP:2:18:22:211.359 sduration 0 ms
GTM-G-CPG3NLBKHP:2:18:22:201.359 sduration 38 ms
GTM-G-CPG3NLBKHP:2:17:22:211.359 sduration 1 ms
GTM-G-CPG3NLBKHP:2:17:22:201.359 sduration 38 ms
GTM-G-CPG3NLBKHP:2:16:22:211.360 sduration 0 ms
GTM-G-CPG3NLBKHP:2:16:22:201.360 sduration 38 ms
GTM-G-CPG3NLBKHP:2:15:22:211.361 sduration 0 ms
GTM-G-CPG3NLBKHP:2:15:22:201.361 sduration 38 ms
GTM-G-CPG3NLBKHP:2:14:22:211.361 sduration 0 ms
GTM-G-CPG3NLBKHP:2:14:22:201.361 sduration 38 ms
GTM-G-CPG3NLBKHP:2:13:22:211.361 sduration 0 ms
GTM-G-CPG3NLBKHP:2:13:22:201.361 sduration 38 ms
GTM-G-CPG3NLBKHP:3:13:121.362 sduration 1 ms
GTM-G-CPG3NLBKHP:3:13:91.362 sduration 40 ms
GTM-G-CPG3NLBKHP:3:11:101.362 sduration 0 ms
GTM-G-CPG3NLBKHP:3:8:22:211.362 sduration 1 ms
GTM-G-CPG3NLBKHP:3:8:22:201.362 sduration 37 ms
GTM-G-CPG3NLBKHP:13:13:121.391 sduration 1 ms
GTM-G-CPG3NLBKHP:13:13:91.391 sduration 8 ms
GTM-G-CPG3NLBKHP:13:11:101.391 sduration 1 ms
GTM-G-CPG3NLBKHP:14:13:121.392 sduration 1 ms
GTM-G-CPG3NLBKHP:14:13:91.392 sduration 7 ms
GTM-G-CPG3NLBKHP:14:11:101.393 sduration 1 ms

Server timings

Timing data the server chose to expose through Server-Timing response headers on the main document — typically backend time, cache status or experiment flags.

Server timings

3 entries
NameDurationDescription
cfCacheStatus0 msDYNAMIC
cfEdge46 ms–
cfOrigin55 ms–

Custom metrics collected through JavaScript

There are no custom configured scripts.

Extra metrics collected using scripting

There are no custom extra metrics from scripting.

PageXray

How the page is built.

HTTP versionHTTP/2.0
Total requests93
Total domains13
Transfer size1.7 MB
Content size5.0 MB
Missing compression0
Cookies51 third-party

Main document

status 200 · 0 redirects

https://xelta.ai/ai-tool

HeaderValue
alt-svch3=":443"; ma=86400
cache-controls-maxage=31536000
cf-cache-statusDYNAMIC
cf-raya3f218f4b9725a26-DEL
content-encodingbr
content-security-policydefault-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'
content-security-policy-report-onlydefault-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'; script-src 'unsafe-inline' 'unsafe-eval'; connect-src 'none'; report-uri https://csp-reporting.cloudflare.com/cdn-cgi/script_monitor/report?m=y5yD0oVyd8Lbm.2H0MjvBy4sB3vtuE0jMZUmd8DlOuk-1790088369.3976142-1.0.1.1-TF0DlezA2T6E4mqcSSGcFdL9_6Tciz8V90e08LK2RWc_GOFRHshL7Xtrr3qVDtvFsIluiBEqDi_pDsJoyaq.Y9efsfBtYW0w4Pmd9_HKk0YOZ3E97Q_uD0lUOI8ZWnUYy8aHXrT03bCEt2kDXLt0n92fU6CIMZtkWWNtp4okrDM; report-to cf-csp-endpoint
content-typetext/html; charset=utf-8
dateTue, 22 Sep 2026 14:46:09 GMT
expect-ctmax-age=86400, enforce
nel{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
permissions-policycamera=(), microphone=(self), geolocation=(), interest-cohort=()
referrer-policysame-origin strict-origin-when-cross-origin
report-to{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=5Rq6bw%2BO8HMy7pKeMePDKf2Fm%2FrDKvFDktMz6Wqdhez5j6KMi%2BXtxghLZ3TeO4PsUlz3NNrll63q2Wi7ZqvoonGZwshnU7lLiZvKo%2FxHDdUGv2hVypSP%2BVld"}]} {"group":"cf-csp-endpoint","max_age":86400,"endpoints":[{"url":"https://csp-reporting.cloudflare.com/cdn-cgi/script_monitor/report?m=y5yD0oVyd8Lbm.2H0MjvBy4sB3vtuE0jMZUmd8DlOuk-1790088369.3976142-1.0.1.1-TF0DlezA2T6E4mqcSSGcFdL9_6Tciz8V90e08LK2RWc_GOFRHshL7Xtrr3qVDtvFsIluiBEqDi_pDsJoyaq.Y9efsfBtYW0w4Pmd9_HKk0YOZ3E97Q_uD0lUOI8ZWnUYy8aHXrT03bCEt2kDXLt0n92fU6CIMZtkWWNtp4okrDM"}]}
reporting-endpointscf-csp-endpoint="https://csp-reporting.cloudflare.com/cdn-cgi/script_monitor/report?m=y5yD0oVyd8Lbm.2H0MjvBy4sB3vtuE0jMZUmd8DlOuk-1790088369.3976142-1.0.1.1-TF0DlezA2T6E4mqcSSGcFdL9_6Tciz8V90e08LK2RWc_GOFRHshL7Xtrr3qVDtvFsIluiBEqDi_pDsJoyaq.Y9efsfBtYW0w4Pmd9_HKk0YOZ3E97Q_uD0lUOI8ZWnUYy8aHXrT03bCEt2kDXLt0n92fU6CIMZtkWWNtp4okrDM"
servercloudflare
server-timingcfCacheStatus;desc="DYNAMIC" cfEdge;dur=46,cfOrigin;dur=55
speculation-rules"/cdn-cgi/speculation"
strict-transport-securitymax-age=31536000; includeSubDomains; preload
varyrsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding
x-content-type-optionsnosniff
x-frame-optionsSAMEORIGIN
x-nextjs-cacheHIT
x-nextjs-prerender1 1
x-nextjs-stale-time300
x-xss-protection1; mode=block

Response codes

200
8894.6%
202
11.1%
204
44.3%

Largest assets on the page (by transfer size)

Top 20 of 93

Requests and sizes per content type

9 types

Transfer size1.7 MB

  • javascript71.0%
  • image12.1%
  • font8.2%
  • css5.5%
  • html1.6%
  • json0.71%
  • favicon0.62%
  • plain0.08%
  • other0.03%

Content size5.0 MB

  • javascript75.8%
  • css13.6%
  • html4.1%
  • image3.6%
  • font2.6%
  • favicon0.16%
  • json0.08%
  • other0.00%
  • plain0.00%

Requests93

  • javascript50.5%
  • image20.4%
  • json9.7%
  • plain6.5%
  • font5.4%
  • css3.2%
  • html2.2%
  • favicon1.1%
  • other1.1%
ContentHeader SizeTransfer SizeContent SizeRequests
html0 b27.5 KB208.4 KB2
css0 b94.3 KB691.3 KB3
javascript0 b1.2 MB3.8 MB47
image0 b206.5 KB185.9 KB19
font0 b140.4 KB134.9 KB5
favicon0 b10.5 KB8.3 KB1
other0 b469 B151 B1
json0 b12.1 KB4.0 KB9
plain0 b1.4 KB2 B6
Total0 b1.7 MB5.0 MB93

Data per domain

13 domains
DomainTotal download timeTransfer SizeContent SizeRequests
xelta.ai6.488 s1.1 MB3.2 MB77
fonts.googleapis.com204 ms1.2 KB3.5 KB1
static.cloudflareinsights.com66 ms10.1 KB29.6 KB1
fonts.gstatic.com15 ms8.1 KB7.6 KB1
www.googletagmanager.com722 ms302.5 KB893.3 KB3
connect.facebook.net101 ms250.4 KB909.1 KB2
analytics.google.com146 msN/A0 b1
stats.g.doubleclick.net112 ms553 B0 b1
www.google.co.in118 ms408 B42 B1
mpc-prod-27-s6uit34pua-uk.a.run.app347 msN/A0 b1
us.i.posthog.com935 ms286 B15 B1
telemetry.matchbestsoftware.online205 ms286 B2 B2
www.facebook.com56 msN/A0 b1

Expires & last-modified statistics

typeminmedianmax
Expires0 seconds1 year1 year
Last modified10 minutes2 days1 year

Requests loaded after onLoad event

51 requests

Includes requests done after load event end.

ContentTransfer SizeRequests
html59 B1
css0 b0
javascript820.1 KB22
image74.1 KB9
font92.2 KB4
favicon10.5 KB1
plain1.4 KB6
json10.2 KB8
Total1008.4 KB51

Requests loaded after onContentLoad

51 requests

Includes requests done after DOM content loaded.

ContentTransfer SizeRequests
html59 B1
css0 b0
javascript820.1 KB22
image74.1 KB9
font92.2 KB4
favicon10.5 KB1
plain1.4 KB6
json10.2 KB8
Total1008.4 KB51

CPU

https://xelta.ai/_next/static/chunks/2cc4dk9_-w4i-.js is responsible for 51% of blocking time
149 ms of 292 ms total. Defer it, replace it with a lighter alternative, or move its work off the main thread to recover most of your TBT.
Get deeper CPU insight with one extra run
Run with --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.

Long tasks

Tasks ≥ 50 ms blocking the main thread, collected via the Long Task API.

TBT266 ms
Max potential input delay149 ms
Total long tasks8
Total time689 ms
Last task at1.402 s
Before first paint73 ms1 task
Before FCP73 ms1 task
Before LCP356 ms4 tasks
After load556 ms6 tasks

Long Animation Frames

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.

Long animation frames9every frame ≥ 50 ms
Blocking time359.7 msacross all long frames — what hurts INP and TBT
Blocking before LCP223.8 msdelaying the largest paint — fix these first
Blocking after load305.9 msafter the load event — didn't delay page load
Input waiting1 framea real interaction was delayed (INP)

What to fix first

ScriptFramesTime runningBlocking (share by run time)Forced style & layoutTriggered by
2cc4dk9_-w4i-.js3201.6 ms149.1 ms–event handler
11234040900237293rd party1113.5 ms63.1 ms–script tag
fbevents.js3rd party199.6 ms49.6 ms–script tag
1ki4hltmjvw2d.js164.7 ms10.7 ms–script tag
0_cis5bf89bk3.js159.3 ms8.9 ms–script tag
js3rd party156.9 ms7.1 ms–script tag
2k5vpzc_p9jpq.js124.3 ms4 ms–script tag

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.

Long animation frame #1 · 220.3 msat 593.8 ms · before LCP
blocking 170 ms
  • Scripts & other work149.4 ms
  • Animation callbacks0.1 ms
  • Style & layout70.8 ms
  • Render0 ms
1 script ran during this frame
Ran for
149.1 ms
Started by
MessagePort.onmessage
How it started
event handler
Source function
z
Position in source
character 3191 into the file (locate it via DevTools → Performance → the Long Animation Frames track)
Long animation frame #2 · 115.4 msat 1.402 s · after load
blocking 64 ms
  • Scripts & other work115.1 ms
  • Animation callbacks0.1 ms
  • Style & layout0.2 ms
  • Render0 ms
1 script ran during this frame
Ran for
113.5 ms
How it started
script tag
Long animation frame #3 · 99.6 msat 1.142 s · after load
blocking 49.6 ms
  • Scripts & other work99.6 ms
  • Animation callbacks0 ms
  • Style & layout0 ms
  • Render0 ms
1 script ran during this frame
fbevents.js3rd party
Ran for
99.6 ms
How it started
script tag
Long animation frame #4 · 229.3 msat 216.9 ms · before LCP
blocking 43.1 ms
  • Scripts & other work159.1 ms
  • Animation callbacks0.1 ms
  • Style & layout70.1 ms
  • Render0 ms

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.

Long animation frame #5 · 92.7 msat 1.045 s · after load
blocking 15.2 ms
  • Scripts & other work92.3 ms
  • Animation callbacks0.3 ms
  • Style & layout0.1 ms
  • Render0 ms
2 scripts ran during this frame
Ran for
64.7 ms
How it started
script tag
Ran for
24.3 ms
How it started
script tag
Long animation frame #6 · 71.5 msat 491.3 ms · before LCP
blocking 10.7 ms
  • Scripts & other work71 ms
  • Animation callbacks0.5 ms
  • Style & layout0 ms
  • Render0 ms
1 script ran during this frame
Ran for
59.3 ms
How it started
script tag
Long animation frame #7 · 57.1 msat 1.284 s · after load
blocking 7.1 ms
  • Scripts & other work57.1 ms
  • Animation callbacks0 ms
  • Style & layout0 ms
  • Render0 ms
1 script ran during this frame
js3rd party
Ran for
56.9 ms
How it started
script tag

2 more long frames carried no blocking time (nothing ran past the 50 ms threshold) — long, but harmless to INP and TBT.

Blocking time per script (browser-reported)

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.

Top scripts blocking the main thread

7 of 7 scripts

Third party

Third party requests categorised by Third party web version 0.29.2.

Third-party requests23
Tools7
Categories7
Third-party cookies1

Categories

7 categories

Requests by category23

  • survelliance11 req · 6 tools47.8%
  • tag-manager3 req · 1 tool13.0%
  • social3 req · 1 tool13.0%
  • cdn2 req · 1 tool8.7%
  • utility2 req · 2 tools8.7%
  • analytics1 req · 1 tool4.3%
  • ad1 req · 1 tool4.3%

Third party requests and tools

7 categories
cdnGoogle Fonts2 requests · 1 tool
survellianceGoogle FontsGoogle Tag ManagerFacebook+ 3 more11 requests · 6 tools
utilityCloudflareOther Google APIs/SDKs2 requests · 2 tools
tag-managerGoogle Tag Manager3 requests · 1 tool
socialFacebook3 requests · 1 tool
analyticsGoogle Analytics1 requests · 1 tool
adGoogle/Doubleclick Ads1 requests · 1 tool

Unmatched third party domains

3 domains

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.

  • mpc-prod-27-s6uit34pua-uk.a.run.app
  • us.i.posthog.com
  • telemetry.matchbestsoftware.online
Third party cookies1
.facebook.com1 cookie

First party vs third party

77 first · 16 third party

Transfer size1.7 MB

  • First party1.1 MB66.3%
  • Third party573.7 KB33.7%

Content size5.0 MB

  • First party3.2 MB63.8%
  • Third party1.8 MB36.2%

Requests93

  • First party7782.8%
  • Third party1617.2%

First party requests and sizes per content type

77 requests

Calculated using .*xelta.* (use --firstParty to configure).

ContentHeader SizeTransfer SizeContent SizeRequests
html0 b27.4 KB208.4 KB1
css0 b93.1 KB687.7 KB2
javascript0 b647.0 KB2.0 MB42
image0 b206.1 KB185.9 KB18
font0 b132.3 KB127.3 KB4
favicon0 b10.5 KB8.3 KB1
other0 b469 B151 B1
json0 b11.8 KB4.0 KB7
plain0 b569 B0 b1
TotalN/A1.1 MB3.2 MB77

Third party requests and sizes per content type

16 requests
ContentHeader SizeTransfer SizeContent SizeRequests
html0 b59 B0 b1
css0 b1.2 KB3.5 KB1
javascript0 b562.9 KB1.8 MB5
image0 b408 B42 B1
font0 b8.1 KB7.6 KB1
favicon0 b0 b0 b0
plain0 b839 B2 B5
json0 b286 B15 B2
TotalN/A573.7 KB1.8 MB16