Page summary

https://xelta.ai/ai-video-generator

Tested 2026-09-17 15:59:53 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.

79 / 100
Coach overall
82 / 100
Performance
90 / 100
Best practice
71 / 100
Privacy

How it loaded →

0 → 5.698 s · median run
Frame at 0 ms
start
Frame at 1000 ms
1.000 s
Frame at 1800 ms
Largest paint1.800 s
Frame at 2500 ms
2.500 s
Frame at 3300 ms
3.300 s
Frame at 5700 ms
Complete5.700 s
302 ms
First Visual Change
945 ms
Speed Index
1.207 s
Visual Complete 85%
5.698 s
Last Visual Change
TTFB105 msLCP1.220 sTBT306 msCLS0.00

What to act on · top recommendations

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 9 CPU long tasks with the total of 790 ms. The total blocking time is 306 ms and 1 long task before first contentful paint with total time of 84 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.

Avoid extra requests by setting cache headers

0 / 100

The page has 16 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 32.5 kB the next access.

Google Web Vitals

min · median · mean · max of 1 run
MetricMinMedianMeanMax
Time To First Byte (TTFB)105 ms105 ms105 ms105 ms
Largest Contentful Paint (LCP)1.220 s1.220 s1.220 s1.220 s
Cumulative Layout Shift (CLS)0.00320.00320.00320.0032

Visual Metrics

min · median · mean · max of 1 run
MetricMinMedianMeanMax
First visual change302 ms302 ms302 ms302 ms
Last visual change5.698 s5.698 s5.698 s5.698 s
Speed index945 ms945 ms945 ms945 ms
Visual readiness5.396 s5.396 s5.396 s5.396 s
Visual complete 851.207 s1.207 s1.207 s1.207 s
Visual complete 951.475 s1.475 s1.475 s1.475 s
Visual complete 992.715 s2.715 s2.715 s2.715 s

CPU

min · median · mean · max of 1 run
MetricMinMedianMeanMax
Total Blocking Time306 ms306 ms306 ms306 ms
Max Potential FID137 ms137 ms137 ms137 ms
CPU long tasks 9999
CPU last long task happens at2.031 s2.031 s2.031 s2.031 s

More metrics

min · median · mean · max of 1 run
MetricMinMedianMeanMax
First paint320 ms320 ms320 ms320 ms
Load event end439 ms439 ms439 ms439 ms

User Timing

min · median · mean · max of 1 run
MetricMinMedianMeanMax
GTM-G-CPG3NLBKHP:150 ms0 ms0 ms0 ms
GTM-G-CPG3NLBKHP:17631 ms631 ms631 ms631 ms
GTM-G-CPG3NLBKHP:41.717 s1.717 s1.717 s1.717 s
GTM-G-CPG3NLBKHP:81.731 s1.731 s1.731 s1.731 s
GTM-G-CPG3NLBKHP:31.733 s1.733 s1.733 s1.733 s
GTM-G-CPG3NLBKHP:21.736 s1.736 s1.736 s1.736 s
GTM-G-CPG3NLBKHP:71.736 s1.736 s1.736 s1.736 s
GTM-G-CPG3NLBKHP:1:131.737 s1.737 s1.737 s1.737 s
GTM-G-CPG3NLBKHP:1:111.737 s1.737 s1.737 s1.737 s
GTM-G-CPG3NLBKHP:1:101.740 s1.740 s1.740 s1.740 s
GTM-G-CPG3NLBKHP:1:121.741 s1.741 s1.741 s1.741 s
GTM-G-CPG3NLBKHP:2:131.741 s1.741 s1.741 s1.741 s
GTM-G-CPG3NLBKHP:2:111.741 s1.741 s1.741 s1.741 s
GTM-G-CPG3NLBKHP:2:101.742 s1.742 s1.742 s1.742 s
GTM-G-CPG3NLBKHP:2:121.742 s1.742 s1.742 s1.742 s
GTM-G-CPG3NLBKHP:2:10:221.743 s1.743 s1.743 s1.743 s
GTM-G-CPG3NLBKHP:2:10:211.743 s1.743 s1.743 s1.743 s
GTM-G-CPG3NLBKHP:2:12:221.744 s1.744 s1.744 s1.744 s
GTM-G-CPG3NLBKHP:2:12:211.745 s1.745 s1.745 s1.745 s
GTM-G-CPG3NLBKHP:2:26:221.745 s1.745 s1.745 s1.745 s
GTM-G-CPG3NLBKHP:2:26:211.745 s1.745 s1.745 s1.745 s
GTM-G-CPG3NLBKHP:2:25:221.745 s1.745 s1.745 s1.745 s
GTM-G-CPG3NLBKHP:2:25:211.745 s1.745 s1.745 s1.745 s
GTM-G-CPG3NLBKHP:2:24:221.745 s1.745 s1.745 s1.745 s
GTM-G-CPG3NLBKHP:2:24:211.747 s1.747 s1.747 s1.747 s
GTM-G-CPG3NLBKHP:2:23:221.747 s1.747 s1.747 s1.747 s
GTM-G-CPG3NLBKHP:2:23:211.749 s1.749 s1.749 s1.749 s
GTM-G-CPG3NLBKHP:2:22:221.749 s1.749 s1.749 s1.749 s
GTM-G-CPG3NLBKHP:2:22:211.750 s1.750 s1.750 s1.750 s
GTM-G-CPG3NLBKHP:2:21:221.751 s1.751 s1.751 s1.751 s
GTM-G-CPG3NLBKHP:2:21:211.751 s1.751 s1.751 s1.751 s
GTM-G-CPG3NLBKHP:2:20:221.752 s1.752 s1.752 s1.752 s
GTM-G-CPG3NLBKHP:2:20:211.752 s1.752 s1.752 s1.752 s
GTM-G-CPG3NLBKHP:2:19:221.753 s1.753 s1.753 s1.753 s
GTM-G-CPG3NLBKHP:2:19:211.753 s1.753 s1.753 s1.753 s
GTM-G-CPG3NLBKHP:2:18:221.753 s1.753 s1.753 s1.753 s
GTM-G-CPG3NLBKHP:2:18:211.754 s1.754 s1.754 s1.754 s
GTM-G-CPG3NLBKHP:2:17:221.754 s1.754 s1.754 s1.754 s
GTM-G-CPG3NLBKHP:2:17:211.754 s1.754 s1.754 s1.754 s
GTM-G-CPG3NLBKHP:2:16:221.755 s1.755 s1.755 s1.755 s
GTM-G-CPG3NLBKHP:2:16:211.755 s1.755 s1.755 s1.755 s
GTM-G-CPG3NLBKHP:2:15:221.755 s1.755 s1.755 s1.755 s
GTM-G-CPG3NLBKHP:2:15:211.755 s1.755 s1.755 s1.755 s
GTM-G-CPG3NLBKHP:2:14:221.755 s1.755 s1.755 s1.755 s
GTM-G-CPG3NLBKHP:2:14:211.756 s1.756 s1.756 s1.756 s
GTM-G-CPG3NLBKHP:2:13:221.756 s1.756 s1.756 s1.756 s
GTM-G-CPG3NLBKHP:2:13:211.756 s1.756 s1.756 s1.756 s
GTM-G-CPG3NLBKHP:3:131.756 s1.756 s1.756 s1.756 s
GTM-G-CPG3NLBKHP:3:111.756 s1.756 s1.756 s1.756 s
GTM-G-CPG3NLBKHP:3:101.757 s1.757 s1.757 s1.757 s
GTM-G-CPG3NLBKHP:3:121.757 s1.757 s1.757 s1.757 s
GTM-G-CPG3NLBKHP:3:8:221.757 s1.757 s1.757 s1.757 s
GTM-G-CPG3NLBKHP:3:8:211.758 s1.758 s1.758 s1.758 s
GTM-G-CPG3NLBKHP:4:131.758 s1.758 s1.758 s1.758 s
GTM-G-CPG3NLBKHP:5:141.785 s1.785 s1.785 s1.785 s
GTM-G-CPG3NLBKHP:6:131.785 s1.785 s1.785 s1.785 s
GTM-G-CPG3NLBKHP:6:111.785 s1.785 s1.785 s1.785 s
GTM-G-CPG3NLBKHP:6:101.786 s1.786 s1.786 s1.786 s
GTM-G-CPG3NLBKHP:6:121.786 s1.786 s1.786 s1.786 s
GTM-G-CPG3NLBKHP:7:131.786 s1.786 s1.786 s1.786 s
GTM-G-CPG3NLBKHP:7:111.787 s1.787 s1.787 s1.787 s
GTM-G-CPG3NLBKHP:7:101.788 s1.788 s1.788 s1.788 s
GTM-G-CPG3NLBKHP:7:121.788 s1.788 s1.788 s1.788 s
GTM-G-CPG3NLBKHP:51.788 s1.788 s1.788 s1.788 s
GTM-G-CPG3NLBKHP:1:91.790 s1.790 s1.790 s1.790 s
GTM-G-CPG3NLBKHP:2:10:201.790 s1.790 s1.790 s1.790 s
GTM-G-CPG3NLBKHP:2:12:201.790 s1.790 s1.790 s1.790 s
GTM-G-CPG3NLBKHP:2:26:201.791 s1.791 s1.791 s1.791 s
GTM-G-CPG3NLBKHP:2:25:201.791 s1.791 s1.791 s1.791 s
GTM-G-CPG3NLBKHP:2:24:201.791 s1.791 s1.791 s1.791 s
GTM-G-CPG3NLBKHP:2:23:201.791 s1.791 s1.791 s1.791 s
GTM-G-CPG3NLBKHP:2:22:201.791 s1.791 s1.791 s1.791 s
GTM-G-CPG3NLBKHP:2:21:201.791 s1.791 s1.791 s1.791 s
GTM-G-CPG3NLBKHP:2:20:201.792 s1.792 s1.792 s1.792 s
GTM-G-CPG3NLBKHP:2:19:201.793 s1.793 s1.793 s1.793 s
GTM-G-CPG3NLBKHP:2:18:201.793 s1.793 s1.793 s1.793 s
GTM-G-CPG3NLBKHP:2:17:201.793 s1.793 s1.793 s1.793 s
GTM-G-CPG3NLBKHP:2:16:201.793 s1.793 s1.793 s1.793 s
GTM-G-CPG3NLBKHP:2:15:201.794 s1.794 s1.794 s1.794 s
GTM-G-CPG3NLBKHP:2:14:201.794 s1.794 s1.794 s1.794 s
GTM-G-CPG3NLBKHP:2:13:201.796 s1.796 s1.796 s1.796 s
GTM-G-CPG3NLBKHP:3:8:201.797 s1.797 s1.797 s1.797 s
GTM-G-CPG3NLBKHP:6:91.797 s1.797 s1.797 s1.797 s
GTM-G-CPG3NLBKHP:7:91.797 s1.797 s1.797 s1.797 s
GTM-G-CPG3NLBKHP:61.797 s1.797 s1.797 s1.797 s
GTM-G-CPG3NLBKHP:2:91.802 s1.802 s1.802 s1.802 s
GTM-G-CPG3NLBKHP:3:91.803 s1.803 s1.803 s1.803 s

Waterfall

Run 1 SpeedIndex median

First paintFCPLCPDOMContentLoadedDOM interactiveLoadRender-blockingRedirectError

Rendering

Run 1 · median
0.000 s
0s1s2s3s4s5s

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

40 frames

Use --filmstrip.showAll to show all filmstrips.

Frame at 0 ms
0 ms
0 %
Frame at 300 ms
300 ms
0 %
Frame at 400 ms
400 ms
29 %
Frame at 500 ms
500 ms
29 %
Frame at 600 ms
600 ms
28 %
Frame at 700 ms
700 ms
28 %
Frame at 800 ms
800 ms
28 %
Frame at 900 ms
900 ms
49 %
Frame at 1.000 s
1.000 s
49 %
Frame at 1.100 s
1.100 s
49 %
Frame at 1.200 s
1.200 s
49 %
Frame at 1.300 s
1.300 s
95 %
Frame at 1.400 s
1.400 s
94 %
Frame at 1.500 s
1.500 s
95 %
Frame at 1.600 s
1.600 s
95 %
Frame at 1.700 s
1.700 s
97 %
Frame at 1.800 s
1.800 s
97 %
Frame at 1.900 s
1.900 s
97 %
Frame at 2.000 s
2.000 s
98 %
Frame at 2.100 s
2.100 s
98 %
Frame at 2.200 s
2.200 s
98 %
Frame at 2.300 s
2.300 s
98 %
Frame at 2.400 s
2.400 s
98 %
Frame at 2.500 s
2.500 s
98 %
Frame at 2.600 s
2.600 s
98 %
Frame at 2.700 s
2.700 s
98 %
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.800 s
3.800 s
99 %
Frame at 3.900 s
3.900 s
99 %
Frame at 5.300 s
5.300 s
99 %
Frame at 5.400 s
5.400 s
99 %
Frame at 5.500 s
5.500 s
99 %
Frame at 5.600 s
5.600 s
99 %
Frame at 5.700 s
5.700 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 320 ms on a 105 ms first byte; the 2 render-blocking requests were done by 199 ms and the remaining ~121 ms is style and layout work. The largest paint followed at 1.220 s. The LCP image itself was downloaded by 773 ms; the wait was render work, not the network.

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

Render blocking requests

30 requests · 512.1 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 105 ms
140 ms
36.9 KB138 ms
css · xelta.ai
85 ms
87.6 KB85 ms
css · xelta.ai
22 ms
3.7 KB22 ms
3-w1slqtx4wge.jspotentially blocking
javascript · xelta.ai
168 ms
73.3 KB168 ms
2qwl8sgb3v89v.jspotentially blocking
javascript · xelta.ai
155 ms
19.7 KB155 ms
1rttzs2jjmcrm.jspotentially blocking
javascript · xelta.ai
155 ms
44.0 KB155 ms
25ym4jnna99b5.jspotentially blocking
javascript · xelta.ai
153 ms
48.8 KB153 ms
120g0hpahlx34.jspotentially blocking
javascript · xelta.ai
152 ms
23.2 KB152 ms
3wmj0jv19y0e5.jspotentially blocking
javascript · xelta.ai
150 ms
15.0 KB150 ms
22 more requests
all done by 291 ms
196.7 KB
LCP resource
1788248207394-01214218a2305019.webp — downloaded by 700 ms, rendered at 1.220 s
70 ms
229.1 KB70 ms
web font · xelta.ai · finished after first paint
269 ms
8.6 KB269 ms
web font · xelta.ai · finished after first paint
285 ms
65.6 KB285 ms
web font · xelta.ai · finished after first paint
274 ms
8.8 KB274 ms
0610 ms915 msFCP 320 msLCP 1.220 s

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.

What to fix first

Performance advice

82
2 errors7 warnings3 info
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 9 CPU long tasks with the total of 790 ms. The total blocking time is 306 ms and 1 long task before first contentful paint with total time of 84 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
  • unknown
  • self
  • self
  • self
  • self
  • self
  • self
  • self
warn(0)Avoid extra requests by setting cache headerscacheHeaders
warn(0)Total JavaScript size shouldn't be too bigjavascriptSize

The total JavaScript transfer size is 1.5 MB and the uncompressed size is 4.9 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/3ur639cpt-7ui.js11.3 KB38.9 KB
https://xelta.ai/_next/static/chunks/3-w1slqtx4wge.js73.3 KB232.0 KB
https://xelta.ai/_next/static/chunks/25ym4jnna99b5.js48.8 KB171.2 KB
https://xelta.ai/_next/static/chunks/turbopack-0qliv_on3yvhn.js6.6 KB18.4 KB
https://xelta.ai/_next/static/chunks/40ecen_51u8zc.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/1s0vi8ebq1ha0.js11.3 KB31.2 KB
https://xelta.ai/_next/static/chunks/1vr-_-ai-9wxy.js8.0 KB21.0 KB
https://xelta.ai/_next/static/chunks/1321f5pb3peoq.js8.4 KB33.9 KB
https://xelta.ai/_next/static/chunks/00up96pc24a4e.js10.4 KB25.8 KB
https://xelta.ai/_next/static/chunks/3wmj0jv19y0e5.js15.0 KB45.5 KB
https://xelta.ai/_next/static/chunks/2qwl8sgb3v89v.js19.7 KB62.0 KB
https://xelta.ai/_next/static/chunks/0v-y_275lo0v3.js10.8 KB29.1 KB
https://xelta.ai/_next/static/chunks/2_mphrdu04vzv.js13.8 KB39.3 KB
https://xelta.ai/_next/static/chunks/1spzo3397ba2t.js6.5 KB14.5 KB
https://xelta.ai/_next/static/chunks/1rttzs2jjmcrm.js44.0 KB140.6 KB
https://xelta.ai/_next/static/chunks/17jp2fut2e48l.js18.1 KB54.6 KB
https://xelta.ai/_next/static/chunks/120g0hpahlx34.js23.2 KB66.2 KB
https://xelta.ai/_next/static/chunks/2f2i__v854m6r.js9.2 KB30.0 KB
https://xelta.ai/_next/static/chunks/21qxs2_9klwty.js1.8 KB1.4 KB
https://xelta.ai/_next/static/chunks/1yoy6xy7rnaz0.js2.1 KB2.2 KB
https://xelta.ai/_next/static/chunks/0r_-zfn80zo41.js2.3 KB2.7 KB
https://xelta.ai/_next/static/chunks/2ukl1_ne4iayb.js9.1 KB31.2 KB
https://xelta.ai/_next/static/chunks/30mdphmb0fhq7.js11.7 KB33.0 KB
https://xelta.ai/_next/static/chunks/36h4r9duhyjke.js11.1 KB37.2 KB
https://xelta.ai/_next/static/chunks/1p5m9ok22zrix.js11.7 KB28.8 KB
https://xelta.ai/_next/static/chunks/2l1phaqus8pmv.js2.6 KB3.0 KB
https://xelta.ai/_next/static/chunks/0i__pnr9dvq_3.js10.6 KB33.6 KB
https://xelta.ai/_next/static/chunks/18jbr26yqz8qq.js8.5 KB36.8 KB
https://xelta.ai/_next/static/chunks/26lmpfa86gk6a.js15.6 KB55.0 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/2oue1a6qt5s20.js1.4 KB493 B
https://xelta.ai/_next/static/chunks/2qqm7elam7bva.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.2 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/16orvb4qnjgm7.js41.8 KB139.5 KB
https://xelta.ai/_next/static/chunks/3f1tw02kuplod.js3.2 KB6.2 KB
https://xelta.ai/_next/static/chunks/2k5vpzc_p9jpq.js35.3 KB106.7 KB
https://connect.facebook.net/en_US/fbevents.js110.7 KB411.7 KB
https://www.googletagmanager.com/gtm.js?id=GTM-5XNS5NQ2115.0 KB324.6 KB
https://xelta.ai/_next/static/chunks/0g_2av48rckam.js1.2 KB254 B
https://xelta.ai/_next/static/chunks/2beid2e0bl3pr.js16.2 KB51.2 KB
https://xelta.ai/_next/static/chunks/3jkkw0mf2fi3y.js10.1 KB32.2 KB
https://connect.facebook.net/signals/config/1123404090023729.../1123404090023729139.3 KB496.7 KB
https://xelta.ai/_next/static/chunks/2vomlz6p1jols.js1.2 KB254 B
https://xelta.ai/_next/static/chunks/2xo2_vsacczb4.js12.0 KB37.0 KB
https://www.googletagmanager.com/gtag/js?id=G-CPG3NLBKHP&cx=c&gtm=4e69f3h1187.3 KB569.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/3dh4veiardltk.js47.0 KB206.7 KB
warn(50)Total CSS size shouldn't be too bigcssSize

The total CSS transfer size is 93.5 kB and uncompressed size is 692 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/18ag8ln2hb3l6.css87.6 KB646.8 KB
https://xelta.ai/_next/static/chunks/1eteo4yyc63ev.css3.7 KB28.9 KB
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
infoLong cache headers is goodcacheHeadersLong

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

Offenders
infoMake each CSS response smalloptimalCssSize

https://xelta.ai/_next/static/chunks/18ag8ln2hb3l6.css size is 89.7 kB (89689) 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/18ag8ln2hb3l6.css87.6 KB646.8 KB
error(90)Avoid missing and error requestsresponseOk

The page has 1 error response. The page has 1 response with code 401.

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.

Offenders
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

90
1 warning3 info
infoAvoid unnecessary headersunnecessaryHeaders

There are 1 response that sets a p3p header. There are 5 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 118 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 13% requests to third party domains (15 requests and 769.4 kB). First party is 105 requests and 1.6 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/_ne...ta.ai/_next/image has a header content-security-policy-report-only that is 805 characters long. https://xelta.ai/_ne...ta.ai/_next/image 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://xelta.ai/api...io_generation/all has a header content-security-policy-report-only that is 805 characters long. https://xelta.ai/api...io_generation/all has a header report-to that is 609 characters long. https://xelta.ai/api...eo_generation/all has a header content-security-policy-report-only that is 805 characters long. https://xelta.ai/api...eo_generation/all has a header report-to that is 607 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. https://xelta.ai/_ne...ta.ai/_next/image has a header content-security-policy-report-only that is 804 characters long. https://xelta.ai/_ne...ta.ai/_next/image has a header report-to that is 606 characters long.

Do not send response headers that are too long.

Offenders
infoAvoid use too many response headersmanyHeaders

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.https://xelta.ai/api...io_generation/all has 31 headers.https://xelta.ai/api...eo_generation/all has 31 headers.https://xelta.ai/api...nts/active-banner has 33 headers.https://xelta.ai/api...cms/announcements has 33 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 5 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 9% requests that are 3rd party (11 requests with a size of 768.8 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 2 utility requests and uses 2 utility tools. The page do 4 tag-manager requests and uses 1 tag-manager tool. The page do 10 survelliance requests and uses 5 survelliance tools. The page do 10 surveillance requests and uses 5 surveillance tools. 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 Video Generator | XeltaThe document title, shown in the browser tab and used by search results.
Layout viewport1350 × 10208 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 elements3,096Very 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 depth19The deepest nesting on the page. Deep branches cost more style recalculation.
Iframes1Embedded documents. Each is a separate page the browser loads and renders.
Script tags69Number 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 storage1.0 KBData 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

2 hints
dns-prefetch
  • https://media.xelta.ai/
preconnect
  • 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

16 tools

Data collected using Third Party Web version 0.29.2.

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

Data from run 1

Visual Metrics

Visual milestones

all times from navigation start
Speed Index0.94 show quickly the page looked done
First Visual Change0.30 sfirst paint reaches the screen
Last Visual Change5.70 sscreen stops changing · 5.40 s after first
≥95% rendered
≥99%
0.30 sFirst Visual Change
1.21 sVisual Complete 85%
1.48 sVisual Complete 95%
2.71 sVisual Complete 99%
Last Visual Change5.70 s
Visual Readiness5.40 s· first to last change
01.0 s2.0 s3.0 s4.0 s5.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.9 s1.9s
Visual progress at 2.4 s2.4s
Visual progress at 3 s3.0s
Visual progress at 3.8 s3.8s
Visual progress at 5.7 s5.7s
FCP0.32s
LCP1.22s
VC851.21s
Long tasks
0.0s1.1s2.3s3.4s4.6s5.7s

Google Web Vitals

from run 1
105 msTTFB
Good
306 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.

1.220 sLCP render time

Phase breakdown

  • TTFB105 ms
  • Resource load delay531 ms
  • Resource load duration74 ms
  • Element render delay511 ms

Element

Size (w × h)
757350
URL
https://media.xelta....4218a2305019.webp
Load time
773 ms
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.003cumulative 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.003<div class="flex-1 w-full bg-transparent pr-2 flex flex-col gap-2"></div>
    body > div#app-root > div > div > div > div:eq(1) > div > div > div > div:eq(1) > div > div:eq(0) > div:eq(0) > div:eq(1)
  • #20.000<button disabled="" aria-label="Generate" title="Generate" class="h-[32px] xl:h-[36px] flex items-center justify-center gap-1.5 px-3 xl:px-5 rounded-[52px] transition-all transform shadow-lg text-[13px] font-medium bg-[#FF7B4F] text-white opacity-60 cursor-not-allowed"></button>,<svg class="w-3.5 h-3.5 flex-shrink-0" fill="none" stroke="currentColor" viewBox="0 0 24 24"></svg>
    body > div#app-root > div > div > div > div:eq(1) > div > div > div > div:eq(1) > div > div:eq(1) > div:eq(1) > button,body > div#app-root > div > div > div > div:eq(1) > div > div > div > div:eq(1) > div > div:eq(1) > div:eq(0) > button:eq(0) > svg
  • #30.000<div class="hidden lg:flex items-center flex-shrink-0 ml-auto"></div>
    body > div#app-root > header > div > div:eq(2)
  • #40.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:17631 ms
GTM-G-CPG3NLBKHP:41.717 s
GTM-G-CPG3NLBKHP:81.731 s
GTM-G-CPG3NLBKHP:31.733 s
GTM-G-CPG3NLBKHP:21.736 s
GTM-G-CPG3NLBKHP:71.736 s
GTM-G-CPG3NLBKHP:1:131.737 s
GTM-G-CPG3NLBKHP:1:111.737 s
GTM-G-CPG3NLBKHP:1:101.740 s
GTM-G-CPG3NLBKHP:1:121.741 s
GTM-G-CPG3NLBKHP:2:131.741 s
GTM-G-CPG3NLBKHP:2:111.741 s
GTM-G-CPG3NLBKHP:2:101.742 s
GTM-G-CPG3NLBKHP:2:121.742 s
GTM-G-CPG3NLBKHP:2:10:221.743 s
GTM-G-CPG3NLBKHP:2:10:211.743 s
GTM-G-CPG3NLBKHP:2:12:221.744 s
GTM-G-CPG3NLBKHP:2:12:211.745 s
GTM-G-CPG3NLBKHP:2:26:221.745 s
GTM-G-CPG3NLBKHP:2:26:211.745 s
GTM-G-CPG3NLBKHP:2:25:221.745 s
GTM-G-CPG3NLBKHP:2:25:211.745 s
GTM-G-CPG3NLBKHP:2:24:221.745 s
GTM-G-CPG3NLBKHP:2:24:211.747 s
GTM-G-CPG3NLBKHP:2:23:221.747 s
GTM-G-CPG3NLBKHP:2:23:211.749 s
GTM-G-CPG3NLBKHP:2:22:221.749 s
GTM-G-CPG3NLBKHP:2:22:211.750 s
GTM-G-CPG3NLBKHP:2:21:221.751 s
GTM-G-CPG3NLBKHP:2:21:211.751 s
GTM-G-CPG3NLBKHP:2:20:221.752 s
GTM-G-CPG3NLBKHP:2:20:211.752 s
GTM-G-CPG3NLBKHP:2:19:221.753 s
GTM-G-CPG3NLBKHP:2:19:211.753 s
GTM-G-CPG3NLBKHP:2:18:221.753 s
GTM-G-CPG3NLBKHP:2:18:211.754 s
GTM-G-CPG3NLBKHP:2:17:221.754 s
GTM-G-CPG3NLBKHP:2:17:211.754 s
GTM-G-CPG3NLBKHP:2:16:221.755 s
GTM-G-CPG3NLBKHP:2:16:211.755 s
GTM-G-CPG3NLBKHP:2:15:221.755 s
GTM-G-CPG3NLBKHP:2:15:211.755 s
GTM-G-CPG3NLBKHP:2:14:221.755 s
GTM-G-CPG3NLBKHP:2:14:211.756 s
GTM-G-CPG3NLBKHP:2:13:221.756 s
GTM-G-CPG3NLBKHP:2:13:211.756 s
GTM-G-CPG3NLBKHP:3:131.756 s
GTM-G-CPG3NLBKHP:3:111.756 s
GTM-G-CPG3NLBKHP:3:101.757 s
GTM-G-CPG3NLBKHP:3:121.757 s
GTM-G-CPG3NLBKHP:3:8:221.757 s
GTM-G-CPG3NLBKHP:3:8:211.758 s
GTM-G-CPG3NLBKHP:4:131.758 s
GTM-G-CPG3NLBKHP:5:141.785 s
GTM-G-CPG3NLBKHP:6:131.785 s
GTM-G-CPG3NLBKHP:6:111.785 s
GTM-G-CPG3NLBKHP:6:101.786 s
GTM-G-CPG3NLBKHP:6:121.786 s
GTM-G-CPG3NLBKHP:7:131.786 s
GTM-G-CPG3NLBKHP:7:111.787 s
GTM-G-CPG3NLBKHP:7:101.788 s
GTM-G-CPG3NLBKHP:7:121.788 s
GTM-G-CPG3NLBKHP:51.788 s
GTM-G-CPG3NLBKHP:1:91.790 s
GTM-G-CPG3NLBKHP:2:10:201.790 s
GTM-G-CPG3NLBKHP:2:12:201.790 s
GTM-G-CPG3NLBKHP:2:26:201.791 s
GTM-G-CPG3NLBKHP:2:25:201.791 s
GTM-G-CPG3NLBKHP:2:24:201.791 s
GTM-G-CPG3NLBKHP:2:23:201.791 s
GTM-G-CPG3NLBKHP:2:22:201.791 s
GTM-G-CPG3NLBKHP:2:21:201.791 s
GTM-G-CPG3NLBKHP:2:20:201.792 s
GTM-G-CPG3NLBKHP:2:19:201.793 s
GTM-G-CPG3NLBKHP:2:18:201.793 s
GTM-G-CPG3NLBKHP:2:17:201.793 s
GTM-G-CPG3NLBKHP:2:16:201.793 s
GTM-G-CPG3NLBKHP:2:15:201.794 s
GTM-G-CPG3NLBKHP:2:14:201.794 s
GTM-G-CPG3NLBKHP:2:13:201.796 s
GTM-G-CPG3NLBKHP:3:8:201.797 s
GTM-G-CPG3NLBKHP:6:91.797 s
GTM-G-CPG3NLBKHP:7:91.797 s
GTM-G-CPG3NLBKHP:61.797 s
GTM-G-CPG3NLBKHP:2:91.802 s
GTM-G-CPG3NLBKHP:3:91.803 s
User Timing measures
GTM-G-CPG3NLBKHP:15:170 msduration 631 ms
GTM-G-CPG3NLBKHP:5:17:14631 msduration 1.154 s
GTM-G-CPG3NLBKHP:4:31.717 sduration 16 ms
GTM-G-CPG3NLBKHP:8:71.731 sduration 5 ms
GTM-G-CPG3NLBKHP:2:51.736 sduration 52 ms
GTM-G-CPG3NLBKHP:2:61.736 sduration 61 ms
GTM-G-CPG3NLBKHP:1:13:121.737 sduration 4 ms
GTM-G-CPG3NLBKHP:1:13:91.737 sduration 53 ms
GTM-G-CPG3NLBKHP:1:11:101.737 sduration 3 ms
GTM-G-CPG3NLBKHP:2:13:121.741 sduration 1 ms
GTM-G-CPG3NLBKHP:2:13:91.741 sduration 61 ms
GTM-G-CPG3NLBKHP:2:11:101.741 sduration 1 ms
GTM-G-CPG3NLBKHP:2:10:22:211.743 sduration 1 ms
GTM-G-CPG3NLBKHP:2:10:22:201.743 sduration 47 ms
GTM-G-CPG3NLBKHP:2:12:22:211.744 sduration 1 ms
GTM-G-CPG3NLBKHP:2:12:22:201.744 sduration 47 ms
GTM-G-CPG3NLBKHP:2:26:22:211.745 sduration 0 ms
GTM-G-CPG3NLBKHP:2:26:22:201.745 sduration 46 ms
GTM-G-CPG3NLBKHP:2:25:22:211.745 sduration 0 ms
GTM-G-CPG3NLBKHP:2:25:22:201.745 sduration 46 ms
GTM-G-CPG3NLBKHP:2:24:22:211.745 sduration 1 ms
GTM-G-CPG3NLBKHP:2:24:22:201.745 sduration 45 ms
GTM-G-CPG3NLBKHP:2:23:22:211.747 sduration 2 ms
GTM-G-CPG3NLBKHP:2:23:22:201.747 sduration 44 ms
GTM-G-CPG3NLBKHP:2:22:22:211.749 sduration 2 ms
GTM-G-CPG3NLBKHP:2:22:22:201.749 sduration 42 ms
GTM-G-CPG3NLBKHP:2:21:22:211.751 sduration 1 ms
GTM-G-CPG3NLBKHP:2:21:22:201.751 sduration 41 ms
GTM-G-CPG3NLBKHP:2:20:22:211.752 sduration 1 ms
GTM-G-CPG3NLBKHP:2:20:22:201.752 sduration 40 ms
GTM-G-CPG3NLBKHP:2:19:22:211.753 sduration 1 ms
GTM-G-CPG3NLBKHP:2:19:22:201.753 sduration 40 ms
GTM-G-CPG3NLBKHP:2:18:22:211.753 sduration 0 ms
GTM-G-CPG3NLBKHP:2:18:22:201.753 sduration 39 ms
GTM-G-CPG3NLBKHP:2:17:22:211.754 sduration 1 ms
GTM-G-CPG3NLBKHP:2:17:22:201.754 sduration 40 ms
GTM-G-CPG3NLBKHP:2:16:22:211.755 sduration 0 ms
GTM-G-CPG3NLBKHP:2:16:22:201.755 sduration 39 ms
GTM-G-CPG3NLBKHP:2:15:22:211.755 sduration 0 ms
GTM-G-CPG3NLBKHP:2:15:22:201.755 sduration 39 ms
GTM-G-CPG3NLBKHP:2:14:22:211.755 sduration 0 ms
GTM-G-CPG3NLBKHP:2:14:22:201.755 sduration 39 ms
GTM-G-CPG3NLBKHP:2:13:22:211.756 sduration 0 ms
GTM-G-CPG3NLBKHP:2:13:22:201.756 sduration 41 ms
GTM-G-CPG3NLBKHP:3:13:121.756 sduration 1 ms
GTM-G-CPG3NLBKHP:3:13:91.756 sduration 47 ms
GTM-G-CPG3NLBKHP:3:11:101.756 sduration 0 ms
GTM-G-CPG3NLBKHP:3:8:22:211.757 sduration 1 ms
GTM-G-CPG3NLBKHP:3:8:22:201.757 sduration 40 ms
GTM-G-CPG3NLBKHP:6:13:121.785 sduration 1 ms
GTM-G-CPG3NLBKHP:6:13:91.785 sduration 12 ms
GTM-G-CPG3NLBKHP:6:11:101.785 sduration 1 ms
GTM-G-CPG3NLBKHP:7:13:121.786 sduration 1 ms
GTM-G-CPG3NLBKHP:7:13:91.786 sduration 11 ms
GTM-G-CPG3NLBKHP:7:11:101.787 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
cfEdge11 ms–
cfOrigin49 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 requests120
Total domains12
Transfer size2.2 MB
Content size6.3 MB
Missing compression0
Cookies41 third-party

Main document

status 200 · 0 redirects

https://xelta.ai/ai-video-generator

HeaderValue
alt-svch3=":443"; ma=86400
cache-controls-maxage=31536000
cf-cache-statusDYNAMIC
cf-raya3c9522a18c0597d-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';
content-typetext/html; charset=utf-8
dateThu, 17 Sep 2026 15:59:56 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=CSWBg9ITofbgmbG8Wbe%2FyAIRLiwhZdwJ6JBf0TBFPvn84%2BknhVUkGS9%2FC%2FtX7IAwIdoQLeYqrmDngsmgEdBseeBrf0GgLTZm8Zk%2FTCnZro%2Bf0gIcUr7BWUij"}]}
servercloudflare
server-timingcfCacheStatus;desc="DYNAMIC" cfEdge;dur=11,cfOrigin;dur=49
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
11495.0%
202
10.8%
204
43.3%
401
10.8%

Largest assets on the page (by transfer size)

Top 20 of 120

Requests and sizes per content type

9 types

Transfer size2.2 MB

  • javascript65.7%
  • image20.8%
  • font6.1%
  • css4.0%
  • html1.6%
  • json1.4%
  • favicon0.42%
  • plain0.06%
  • other0.02%

Content size6.3 MB

  • javascript74.1%
  • css10.5%
  • image6.9%
  • html5.7%
  • font2.1%
  • json0.57%
  • favicon0.13%
  • other0.00%
  • plain0.00%

Requests119

  • javascript51.3%
  • image21.8%
  • json12.6%
  • plain5.0%
  • font4.2%
  • html1.7%
  • css1.7%
  • favicon0.84%
  • other0.84%
ContentHeader SizeTransfer SizeContent SizeRequests
html0 b36.9 KB366.0 KB2
css0 b91.3 KB675.8 KB2
javascript0 b1.5 MB4.7 MB61
image0 b476.8 KB446.9 KB26
font0 b140.0 KB134.9 KB5
favicon0 b9.6 KB8.3 KB1
other0 b452 B151 B1
json0 b31.5 KB36.5 KB15
plain0 b1.4 KB2 B6
Total0 b2.2 MB6.3 MB119

Data per domain

12 domains
DomainTotal download timeTransfer SizeContent SizeRequests
xelta.ai12.689 s1.3 MB3.7 MB104
static.cloudflareinsights.com65 ms10.1 KB29.6 KB1
www.googletagmanager.com1.780 s489.8 KB1.4 MB4
connect.facebook.net118 ms250.0 KB908.4 KB2
media.xelta.ai86 ms229.1 KB228.2 KB1
analytics.google.com737 msN/A0 b1
stats.g.doubleclick.net123 ms554 B0 b1
www.google.co.in456 ms409 B42 B1
mpc-prod-27-s6uit34pua-uk.a.run.app343 msN/A0 b1
us.i.posthog.com3.412 s286 B15 B1
telemetry.matchbestsoftware.online171 ms286 B2 B2
www.facebook.com40 msN/A0 b1

Expires & last-modified statistics

typeminmedianmax
Expires0 seconds1 year1 year
Last modified60 minutes17 hours2 weeks

Requests loaded after onLoad event

71 requests

Includes requests done after load event end.

ContentTransfer SizeRequests
html11 B1
css0 b0
javascript1.0 MB27
image360.4 KB17
font91.8 KB4
favicon9.6 KB1
plain1.4 KB6
json29.5 KB14
Total1.5 MB71

Requests loaded after onContentLoad

71 requests

Includes requests done after DOM content loaded.

ContentTransfer SizeRequests
html11 B1
css0 b0
javascript1.0 MB27
image360.4 KB17
font91.8 KB4
favicon9.6 KB1
plain1.4 KB6
json29.5 KB14
Total1.5 MB71

CPU

76 ms of 221 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.

TBT306 ms
Max potential input delay137 ms
Total long tasks9
Total time790 ms
Last task at2.031 s
Before first paint84 ms1 task
Before FCP84 ms1 task
Before LCP299 ms3 tasks
After load706 ms8 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 frames12showing the 10 with the most blocking time
Blocking time590.3 msacross all long frames — what hurts INP and TBT
Forced style & layout46 msscripts reading layout mid-frame
Blocking before LCP387.3 msdelaying the largest paint — fix these first
Blocking after load542.3 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
11234040900237293rd party1125.7 ms76.3 ms0.4 msscript tag
fbevents.js3rd party1110.6 ms60.4 ms–script tag
3-w1slqtx4wge.js2103.2 ms23.5 ms45.6 msevent handler
js3rd party171.4 ms21.3 ms–script tag
1ki4hltmjvw2d.js178.4 ms17.9 ms–script tag
js3rd party161.1 ms11.2 ms–script tag
2k5vpzc_p9jpq.js128.8 ms6.6 ms–script tag
16orvb4qnjgm7.js116.5 ms3.8 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 · 278.8 msat 921.3 ms · before LCP
blocking 228.1 ms
  • Scripts & other work1.2 ms
  • Animation callbacks277.6 ms
  • Style & layout0 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 #2 · 136 msat 632.4 ms · before LCP
blocking 85.3 ms
  • Scripts & other work2.1 ms
  • Animation callbacks0.1 ms
  • Style & layout133.8 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 #3 · 127.1 msat 1.805 s · after load
blocking 76.6 ms
  • Scripts & other work126.2 ms
  • Animation callbacks0.4 ms
  • Style & layout0.5 ms
  • Render0 ms
1 script ran during this frame · forced style & layout 0.4 ms
Ran for
125.7 ms
Forced style and layout
0.4 ms
How it started
script tag
Long animation frame #4 · 118.4 msat 1.419 s · after load
blocking 63.3 ms
  • Scripts & other work116 ms
  • Animation callbacks1.6 ms
  • Style & layout0.8 ms
  • Render0 ms
1 script ran during this frame
fbevents.js3rd party
Ran for
110.6 ms
How it started
script tag
Long animation frame #5 · 179.1 msat 124.1 ms · before LCP
blocking 45.2 ms
  • Scripts & other work98 ms
  • Animation callbacks0 ms
  • Style & layout81.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 #6 · 125.6 msat 783.6 ms · before LCP
blocking 28.7 ms
  • Scripts & other work125.5 ms
  • Animation callbacks0.1 ms
  • Style & layout0 ms
  • Render0 ms
3 scripts ran during this frame
Ran for
28.8 ms
How it started
script tag
Ran for
16.5 ms
How it started
script tag
Ran for
78.4 ms
How it started
script tag
Long animation frame #7 · 77.7 msat 1.657 s · after load
blocking 22.8 ms
  • Scripts & other work76.4 ms
  • Animation callbacks1.3 ms
  • Style & layout0 ms
  • Render0 ms
1 script ran during this frame
js3rd party
Ran for
71.4 ms
How it started
script tag
Long animation frame #8 · 79.3 msat 1.336 s · after load
input was waitingblocking 22.5 ms
  • Scripts & other work78.8 ms
  • Animation callbacks0.5 ms
  • Style & layout0 ms
  • Render0 ms
1 script ran during this frame · forced style & layout 45.6 ms
Ran for
71.9 ms
Forced style and layout
45.6 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 #9 · 65.7 msat 2.027 s · after load
blocking 11.9 ms
  • Scripts & other work65 ms
  • Animation callbacks0.1 ms
  • Style & layout0.6 ms
  • Render0 ms
1 script ran during this frame
js3rd party
Ran for
61.1 ms
How it started
script tag
Long animation frame #10 · 54.6 msat 1.961 s · after load
blocking 3.1 ms
  • Scripts & other work33 ms
  • Animation callbacks0.4 ms
  • Style & layout21.2 ms
  • Render0 ms
1 script ran during this frame
Ran for
31.3 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)

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.

Forced layout per script

Each long animation frame reports how much time each script spent forcing synchronous style and layout, i.e. JavaScript reading layout-triggering properties mid-execution. Same actionable answer as forced reflows above but measured directly by the browser instead of inferred from the trace.

Scripts forcing layout

1 of 2 scripts

Third party

Third party requests categorised by Third party web version 0.29.2.

Third-party requests21
Tools6
Categories6
Third-party cookies1

Categories

6 categories

Requests by category21

  • survelliance10 req · 5 tools47.6%
  • tag-manager4 req · 1 tool19.0%
  • social3 req · 1 tool14.3%
  • utility2 req · 2 tools9.5%
  • analytics1 req · 1 tool4.8%
  • ad1 req · 1 tool4.8%

Third party requests and tools

6 categories
utilityCloudflareOther Google APIs/SDKs2 requests · 2 tools
tag-managerGoogle Tag Manager4 requests · 1 tool
survellianceGoogle Tag ManagerFacebookGoogle Analytics+ 2 more10 requests · 5 tools
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

105 first · 15 third party

Transfer size2.2 MB

  • First party1.5 MB67.3%
  • Third party751.4 KB32.7%

Content size6.3 MB

  • First party3.9 MB62.7%
  • Third party2.3 MB37.3%

Requests120

  • First party10587.5%
  • Third party1512.5%

First party requests and sizes per content type

105 requests

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

ContentHeader SizeTransfer SizeContent SizeRequests
html0 b36.9 KB366.0 KB1
css0 b91.3 KB675.8 KB2
javascript0 b758.9 KB2.3 MB55
image0 b476.4 KB446.9 KB25
font0 b140.0 KB134.9 KB5
favicon0 b9.6 KB8.3 KB1
other0 b452 B151 B1
json0 b31.2 KB36.5 KB13
plain0 b578 B0 b1
TotalN/A1.5 MB3.9 MB105

Third party requests and sizes per content type

15 requests
ContentHeader SizeTransfer SizeContent SizeRequests
html0 b11 B0 b1
css0 b0 b0 b0
javascript0 b749.9 KB2.3 MB6
image0 b409 B42 B1
font0 b0 b0 b0
favicon0 b0 b0 b0
plain0 b840 B2 B5
json0 b286 B15 B2
TotalN/A751.4 KB2.3 MB15