Run 1 summary

https://stf.xelta.ai/flow/cinematic-studio

Tested 2026-09-14 10:31:18 using Chrome 150.0.7871.46 (runtime settings)

SummaryWaterfallMetricsRenderingCoachPageXrayThird party

Summary

Google Web Vitals

345 msTTFB
1.792 sLargest Contentful Paint
0.000Cumulative Layout Shift
987 msTotal Blocking Time

Loading

1.252 sFirst Paint
8.891 sFully Loaded
372 msMax Potential FID

Page weight & requests

1.7 MBTotal transfer size
5.2 MBTotal content size
77Requests

CPU

11Long tasks
3.603 sLast long task at

Visual progress

1.000 sFirst Visual Change
1.477 sSpeed Index
1.800 sVisual Complete 85%
1.934 sVisual Complete 99%
5.400 sLast Visual Change
Screenshot
Run 1 · after page complete

Waterfall

First paintFCPLCPDOMContentLoadedDOM interactiveLoadRender-blockingRedirectError

Rendering

Run 1
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

47 frames

Use --filmstrip.showAll to show all filmstrips.

Frame at 0 ms
0 ms
0 %
Frame at 800 ms
800 ms
0 %
Frame at 1.000 s
1.000 s
17 %
Frame at 1.100 s
1.100 s
17 %
Frame at 1.200 s
1.200 s
17 %
Frame at 1.300 s
1.300 s
59 %
Frame at 1.400 s
1.400 s
59 %
Frame at 1.500 s
1.500 s
59 %
Frame at 1.600 s
1.600 s
59 %
Frame at 1.700 s
1.700 s
59 %
Frame at 1.800 s
1.800 s
98 %
Frame at 1.900 s
1.900 s
98 %
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 3.900 s
3.900 s
99 %
Frame at 4.000 s
4.000 s
99 %
Frame at 4.100 s
4.100 s
99 %
Frame at 4.200 s
4.200 s
99 %
Frame at 4.300 s
4.300 s
99 %
Frame at 4.400 s
4.400 s
99 %
Frame at 4.500 s
4.500 s
99 %
Frame at 4.600 s
4.600 s
99 %
Frame at 4.700 s
4.700 s
99 %
Frame at 4.800 s
4.800 s
99 %
Frame at 4.900 s
4.900 s
99 %
Frame at 5.000 s
5.000 s
99 %
Frame at 5.100 s
5.100 s
99 %
Frame at 5.200 s
5.200 s
99 %
Frame at 5.300 s
5.300 s
99 %
Frame at 5.400 s
5.400 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 1.252 s on a 345 ms first byte; the 2 render-blocking requests were done by 633 ms and the remaining ~619 ms is style, layout and web-font loading. The largest paint followed at 1.792 s. The LCP image itself was downloaded by 952 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 · 548.7 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
stf.xelta.ai · TTFB 345 ms
733 ms
15.9 KB730 ms
css · stf.xelta.ai
191 ms
4.4 KB191 ms
css · stf.xelta.ai
163 ms
86.2 KB163 ms
1ghsza2wgj0ob.jspotentially blocking
javascript · stf.xelta.ai
398 ms
44.0 KB398 ms
26--kr-ciax9i.jspotentially blocking
javascript · stf.xelta.ai
386 ms
42.8 KB386 ms
2fwxubudg7e2g.jspotentially blocking
javascript · stf.xelta.ai
380 ms
14.3 KB380 ms
3sy5ezjqwbusz.jspotentially blocking
javascript · stf.xelta.ai
379 ms
48.8 KB379 ms
00up96pc24a4e.jspotentially blocking
javascript · stf.xelta.ai
378 ms
10.4 KB378 ms
2qwl8sgb3v89v.jspotentially blocking
javascript · stf.xelta.ai
375 ms
19.7 KB375 ms
22 more requests
all done by 882 ms
278.0 KB
LCP resource
cinematic-studio.webp — downloaded by 894 ms, rendered at 1.792 s
87 ms
7.4 KB87 ms
web font · stf.xelta.ai
334 ms
37.0 KB334 ms
web font · stf.xelta.ai
330 ms
8.2 KB330 ms
web font · stf.xelta.ai
330 ms
35.5 KB330 ms
0448 ms896 msFCP 1.252 sLCP 1.792 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

83
1 error8 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 11 CPU long tasks with the total of 1.849 s. The total blocking time is 987 ms and 3 long tasks before first contentful paint with total time of 462 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
  • self
  • unknown
  • self
  • self
  • self
  • self
  • self
  • self
  • self
  • self
  • self
infoAvoid too many fontsfewFonts
warn(0)Total JavaScript size shouldn't be too bigjavascriptSize

The total JavaScript transfer size is 1.4 MB and the uncompressed size is 4.3 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://stf.xelta.ai/_next/static/chunks/0_cis5bf89bk3.js3.7 KB9.3 KB
https://stf.xelta.ai/_next/static/chunks/3ur639cpt-7ui.js11.3 KB38.9 KB
https://stf.xelta.ai/_next/static/chunks/3dlul65aa-nvq.js73.3 KB232.0 KB
https://stf.xelta.ai/_next/static/chunks/3sy5ezjqwbusz.js48.8 KB171.2 KB
https://stf.xelta.ai/_next/static/chunks/turbopack-24c8re3t_hr9w.js6.6 KB18.4 KB
https://stf.xelta.ai/_next/static/chunks/0inxmj29ffnqy.js6.4 KB20.3 KB
https://stf.xelta.ai/_next/static/chunks/17d1-bwqhg7yp.js9.6 KB27.2 KB
https://stf.xelta.ai/_next/static/chunks/1umv1owun4cfl.js8.6 KB33.7 KB
https://stf.xelta.ai/_next/static/chunks/2uoulaw6kucli.js10.1 KB26.2 KB
https://stf.xelta.ai/_next/static/chunks/36h4r9duhyjke.js11.1 KB37.2 KB
https://stf.xelta.ai/_next/static/chunks/2f2i__v854m6r.js9.2 KB30.0 KB
https://stf.xelta.ai/_next/static/chunks/1ytwdotu3mdq4.js10.3 KB27.8 KB
https://stf.xelta.ai/_next/static/chunks/00up96pc24a4e.js10.4 KB25.8 KB
https://stf.xelta.ai/_next/static/chunks/2699mm_b_frg_.js8.0 KB21.0 KB
https://stf.xelta.ai/_next/static/chunks/2rlqhawoa2-1z.js24.1 KB77.8 KB
https://stf.xelta.ai/_next/static/chunks/0qj250lktf-9_.js12.8 KB34.0 KB
https://stf.xelta.ai/_next/static/chunks/1ghsza2wgj0ob.js44.0 KB140.5 KB
https://stf.xelta.ai/_next/static/chunks/0v-y_275lo0v3.js10.8 KB29.1 KB
https://stf.xelta.ai/_next/static/chunks/2qwl8sgb3v89v.js19.7 KB62.0 KB
https://stf.xelta.ai/_next/static/chunks/1j2emy2xhevk5.js6.7 KB15.0 KB
https://stf.xelta.ai/_next/static/chunks/3scmkth2l2ag2.js15.3 KB43.9 KB
https://stf.xelta.ai/_next/static/chunks/08f3iux3oyyat.js12.5 KB34.1 KB
https://stf.xelta.ai/_next/static/chunks/26--kr-ciax9i.js42.8 KB141.9 KB
https://stf.xelta.ai/_next/static/chunks/28l2j31ow31z4.js17.9 KB49.0 KB
https://stf.xelta.ai/_next/static/chunks/3_rq1zce56v9d.js7.1 KB20.2 KB
https://stf.xelta.ai/_next/static/chunks/2fwxubudg7e2g.js14.3 KB60.2 KB
https://stf.xelta.ai/_next/static/chunks/21qxs2_9klwty.js1.8 KB1.4 KB
https://stf.xelta.ai/_next/static/chunks/1yoy6xy7rnaz0.js2.1 KB2.2 KB
https://stf.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://stf.xelta.ai/_next/static/chunks/0ga4rs1yp22vv.js2.4 KB3.0 KB
https://stf.xelta.ai/_next/static/chunks/31gmcbixca3pb.js1.3 KB312 B
https://stf.xelta.ai/_next/static/chunks/3r6i7ud2kx9-k.js10.6 KB33.7 KB
https://www.googletagmanager.com/gtm.js?id=GTM-5XNS5NQ2115.0 KB324.1 KB
https://www.googletagmanager.com/gtag/js?id=G-CPG3NLBKHP186.6 KB567.5 KB
https://connect.facebook.net/en_US/fbevents.js110.4 KB410.0 KB
https://stf.xelta.ai/_next/static/chunks/3f1tw02kuplod.js3.3 KB6.2 KB
https://stf.xelta.ai/_next/static/chunks/2k5vpzc_p9jpq.js35.3 KB106.7 KB
https://connect.facebook.net/signals/config/1123404090023729.../1123404090023729137.0 KB485.1 KB
https://www.googletagmanager.com/gtag/js?id=G-CPG3NLBKHP&cx=c&gtm=4e6992186.6 KB567.5 KB
https://stf.xelta.ai/_next/static/chunks/3m9-oomc-qdle.js1.4 KB455 B
https://stf.xelta.ai/_next/static/chunks/34zqwff648hvy.js10.7 KB33.9 KB
https://stf.xelta.ai/_next/static/chunks/0_ierrc7whc8i.js10.5 KB31.3 KB
https://stf.xelta.ai/_next/static/chunks/3dh4veiardltk.js47.0 KB206.7 KB
warn(50)Avoid extra requests by setting cache headerscacheHeaders

The page has 5 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 8.6 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 92.8 kB and uncompressed size is 688.9 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://stf.xelta.ai/_next/static/chunks/0l1q20e5y-c75.css86.2 KB636.6 KB
https://stf.xelta.ai/_next/static/chunks/0kldb6fnstui0.css4.4 KB36.2 KB
warn(60)Don't use private headers on static contentprivateAssets

The page has 5 requests with private headers. The main page has a private header. It could be right in some cases where the user can be logged in and served specific content. But if your asset is static it should never be private. 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(90)Always compress text contentcompressAssets

The page has 1 request that are served uncompressed. You could save a lot of bytes by sending them compressed instead.

In the early days of the Internet there were browsers that didn't support compressing (gzipping) text content. They do now. Make sure you compress HTML, JSON, JavaScript, CSS and SVG. It will save bytes for the user; making the page load faster and use less bandwith.

Offenders
URLTransferContent
https://cinematic.stg.xelta.ai/presets3.8 KB3.6 KB
infoMake each CSS response smalloptimalCssSize

https://stf.xelta.ai/_next/static/chunks/0l1q20e5y-c75.css size is 88.2 kB (88219) 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://stf.xelta.ai/_next/static/chunks/0l1q20e5y-c75.css86.2 KB636.6 KB
infoLong cache headers is goodcacheHeadersLong

The page has 7 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
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 5 responses that sets both a max-age and expires header. There are 4 responses that sets a pragma no-cache header (that is a request header). There are 75 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 18% requests to third party domains (14 requests and 764.9 kB). First party is 63 requests and 1.1 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://stf.xelta.ai.../cinematic-studio has a header link that is 1725 characters long. https://stf.xelta.ai...ta.ai/_next/image has a header content-security-policy-report-only that is 797 characters long. https://stf.xelta.ai...ta.ai/_next/image has a header report-to that is 615 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://stf.xelta.ai/api/cms/maintenance has 33 headers.https://stf.xelta.ai/api/geo has 32 headers.

Avoid send too many response headers.

Offenders

Privacy advice

72
5 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 14% requests that are 3rd party (11 requests with a size of 764.6 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 3 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 2 analytics requests 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(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 Cinematic Studio | Create Stunning AI Videos EasilyThe document title, shown in the browser tab and used by search results.
Layout viewport1365 × 620 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 elements352Total HTML elements. Fewer means less for the browser to style, lay out and paint.
Avg DOM depth5How deeply elements are nested on average.
Max DOM depth15The deepest nesting on the page. Deep branches cost more style recalculation.
Iframes1Embedded documents. Each is a separate page the browser loads and renders.
Script tags53Number 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 storage360 BData the page saved in localStorage, kept across visits.
Session storage188 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://media.xelta.ai/
  • https://fonts.googleapis.com/
  • https://fonts.gstatic.com/

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

5 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

Visual Metrics

Visual milestones

all times from navigation start
Speed Index1.48 show quickly the page looked done
First Visual Change1.00 sfirst paint reaches the screen
Last Visual Change5.40 sscreen stops changing · 4.40 s after first
nothing painted yet
≥99%
1.00 sFirst Visual Change
1.80 sVisual Complete 85% · Visual Complete 95%
1.93 sVisual Complete 99%
Last Visual Change5.40 s
Visual Readiness4.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 1.5 s1.5s
Visual progress at 2.1 s2.1s
Visual progress at 2.8 s2.8s
Visual progress at 3.4 s3.4s
Visual progress at 4.1 s4.1s
Visual progress at 4.7 s4.7s
Visual progress at 5.4 s5.4s
FCP1.25s
LCP1.79s
VC851.80s
Long tasks
0.0s1.1s2.2s3.2s4.3s5.4s

Google Web Vitals

Largest Contentful Paint

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

1.792 sLCP render time

Phase breakdown

  • TTFB345 ms
  • Resource load delay483 ms
  • Resource load duration89 ms
  • Element render delay876 ms

Element

Element type
<div>
Size (w × h)
360150
URL
https://stf.xelta.ai...matic-studio.webp
Load time
952 ms

DOM path

body > div#app-root > div > div > div > div:eq(1)
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

No layout shifts were detected on this page.

Browser Metrics

Navigation Timing
Extra timings

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
cfEdge4 ms–
cfOrigin243 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.

Chrome internal metrics (CDP)33
Audio handlers0
Audio worklet processors0
Documents2
Frames2
JS event listeners455
Layout objects149
Media key sessions0
Media keys0
Nodes659
Resources101
Context lifecycle state observers64
V8 per context datas3
Worker global scopes0
Uacss resources0
Rtc peer connections0
Resource fetchers2
Ad subframes0
Detached script states2
Array buffer contents0
Layout count6
Recalc style count14
Layout duration90
Recalc style duration79
Dev tools command duration26
Script duration1847
V8 compile duration7
Task duration3435
Task other duration1386
Thread time3
Process time7
JS heap used size16523732
JS heap total size25452544
First meaningful paint1250

PageXray

How the page is built.

HTTP versionHTTP/2.0
Total requests77
Total domains11
Transfer size1.7 MB
Content size5.2 MB
Missing compression1
Cookies41 third-party

Main document

status 200 · 0 redirects

https://stf.xelta.ai/flow/cinematic-studio

HeaderValue
alt-svch3=":443"; ma=86400
cache-controlprivate, no-cache, no-store, max-age=0, must-revalidate
cf-cache-statusDYNAMIC
cf-raya3aeb8b61a69f4fe-DEL
content-encodingbr
content-security-policydefault-src 'self'; script-src 'self' 'nonce-sn77kQ6C3tdAYbBZnRz+MA==' 'strict-dynamic' 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:; 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:; 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
dateMon, 14 Sep 2026 10:31:21 GMT
expect-ctmax-age=86400, enforce
link</_next/static/media/47fe1b7cd6e6ed85-s.p.3bh2vc0w-r-ll.woff2>; rel=preload; as="font"; crossorigin=""; nonce="sn77kQ6C3tdAYbBZnRz+MA=="; type="font/woff2", </_next/static/media/83afe278b6a6bb3c-s.p.2bn3s6zvc0dyp.woff2>; rel=preload; as="font"; crossorigin=""; nonce="sn77kQ6C3tdAYbBZnRz+MA=="; type="font/woff2", </_next/static/media/8dfd6563338cbf38-s.p.2uos8jt9rp249.woff2>; rel=preload; as="font"; crossorigin=""; nonce="sn77kQ6C3tdAYbBZnRz+MA=="; type="font/woff2", </_next/static/media/8e6fa89aa22d24ec-s.p.2o7m9ogm38dql.woff2>; rel=preload; as="font"; crossorigin=""; nonce="sn77kQ6C3tdAYbBZnRz+MA=="; type="font/woff2", </_next/static/media/9d0c71fa164043fa-s.p.2snziqcncuet5.woff2>; rel=preload; as="font"; crossorigin=""; nonce="sn77kQ6C3tdAYbBZnRz+MA=="; type="font/woff2", </_next/static/media/9e9f04e3c37952ab-s.p.0pan85mumqyf3.woff2>; rel=preload; as="font"; crossorigin=""; nonce="sn77kQ6C3tdAYbBZnRz+MA=="; type="font/woff2", </_next/static/media/a218039a3287bcfd-s.p.43zbiuwnnoiok.woff2>; rel=preload; as="font"; crossorigin=""; nonce="sn77kQ6C3tdAYbBZnRz+MA=="; type="font/woff2", </_next/static/media/c875c6f5d3e977ac-s.p.1h18_wedhzk4h.woff2>; rel=preload; as="font"; crossorigin=""; nonce="sn77kQ6C3tdAYbBZnRz+MA=="; type="font/woff2", </_next/static/media/ce62453a442c7f35-s.p.0a0h245ktd4x0.woff2>; rel=preload; as="font"; crossorigin=""; nonce="sn77kQ6C3tdAYbBZnRz+MA=="; type="font/woff2", </_next/static/media/e2334d715941921e-s.p.3o_v2fun1jzxk.woff2>; rel=preload; as="font"; crossorigin=""; nonce="sn77kQ6C3tdAYbBZnRz+MA=="; type="font/woff2", </_next/static/media/e8f2fbee2754df70-s.p.1dqa_6e_ad4sj.woff2>; rel=preload; as="font"; crossorigin=""; nonce="sn77kQ6C3tdAYbBZnRz+MA=="; type="font/woff2"
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=Pj64mObbKAkLXey7jLRCDlQouMhgh1UQy1%2F4Lsb%2BSue5VZ75r6l1RzivDw1saVJ1rO%2B96v1FTmiE19kuFn4zGr6bVKB17mSZDhNt%2Fuu8i5vm%2BPC72QIsQ7BrqT%2Bhzg%3D%3D"}]}
servercloudflare
server-timingcfCacheStatus;desc="DYNAMIC" cfEdge;dur=4,cfOrigin;dur=243
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-xss-protection1; mode=block

Response codes

200
7192.2%
202
11.3%
204
56.5%

Largest assets on the page (by transfer size)

Top 20 of 77

Requests and sizes per content type

9 types

Transfer size1.7 MB

  • javascript74.5%
  • font17.3%
  • css5.1%
  • image1.0%
  • html0.89%
  • favicon0.54%
  • json0.51%
  • plain0.08%
  • other0.03%

Content size5.2 MB

  • javascript79.6%
  • css12.6%
  • font5.7%
  • html1.5%
  • image0.23%
  • favicon0.16%
  • json0.09%
  • other0.00%
  • plain0.00%

Requests77

  • javascript57.1%
  • font14.3%
  • plain9.1%
  • image6.5%
  • json6.5%
  • css2.6%
  • html1.3%
  • favicon1.3%
  • other1.3%
ContentHeader SizeTransfer SizeContent SizeRequests
html0 b15.9 KB80.9 KB1
css0 b90.6 KB672.8 KB2
javascript0 b1.3 MB4.1 MB44
image0 b18.6 KB12.3 KB5
font0 b308.7 KB304.1 KB11
favicon0 b9.6 KB8.3 KB1
other0 b617 B151 B1
json0 b9.2 KB5.0 KB5
plain0 b1.4 KB2 B7
Total0 b1.7 MB5.2 MB77

Data per domain

11 domains
DomainTotal download timeTransfer SizeContent SizeRequests
stf.xelta.ai16.061 s1.0 MB2.9 MB62
static.cloudflareinsights.com155 ms10.1 KB29.6 KB1
www.googletagmanager.com1.634 s488.2 KB1.4 MB3
connect.facebook.net228 ms247.4 KB895.2 KB2
cinematic.stg.xelta.ai214 ms3.8 KB3.6 KB1
mpc-prod-27-s6uit34pua-uk.a.run.app550 msN/A0 b1
analytics.google.com378 msN/A0 b2
stats.g.doubleclick.net248 ms555 B0 b1
www.google.co.in172 ms408 B42 B1
telemetry.matchbestsoftware.online221 ms286 B2 B2
www.facebook.com210 msN/A0 b1

Expires & last-modified statistics

typeminmedianmax
Expires0 seconds1 year1 year
Last modified2 hours2 days2 weeks

Requests loaded after onLoad event

29 requests

Includes requests done after load event end.

ContentTransfer SizeRequests
html0 b0
css0 b0
javascript858.1 KB14
image8.5 KB3
font0 b0
favicon9.6 KB1
plain1.4 KB7
json7.2 KB4
Total884.9 KB29

Requests loaded after onContentLoad

29 requests

Includes requests done after DOM content loaded.

ContentTransfer SizeRequests
html0 b0
css0 b0
javascript858.1 KB14
image8.5 KB3
font0 b0
favicon9.6 KB1
plain1.4 KB7
json7.2 KB4
Total884.9 KB29

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-manager3 req · 1 tool14.3%
  • social3 req · 1 tool14.3%
  • utility2 req · 2 tools9.5%
  • analytics2 req · 1 tool9.5%
  • ad1 req · 1 tool4.8%

Third party requests and tools

6 categories
utilityCloudflareOther Google APIs/SDKs2 requests · 2 tools
tag-managerGoogle Tag Manager3 requests · 1 tool
survellianceGoogle Tag ManagerFacebookGoogle Analytics+ 2 more10 requests · 5 tools
socialFacebook3 requests · 1 tool
analyticsGoogle Analytics2 requests · 1 tool
adGoogle/Doubleclick Ads1 requests · 1 tool

Unmatched third party domains

2 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
  • telemetry.matchbestsoftware.online
Third party cookies1
.facebook.com1 cookie

First party vs third party

63 first · 14 third party

Transfer size1.7 MB

  • First party1.0 MB58.1%
  • Third party747.0 KB41.9%

Content size5.2 MB

  • First party2.9 MB55.2%
  • Third party2.3 MB44.8%

Requests77

  • First party6381.8%
  • Third party1418.2%

First party requests and sizes per content type

63 requests

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

ContentHeader SizeTransfer SizeContent SizeRequests
html0 b15.9 KB80.9 KB1
css0 b90.6 KB672.8 KB2
javascript0 b584.3 KB1.8 MB38
image0 b18.2 KB12.3 KB4
font0 b308.7 KB304.1 KB11
favicon0 b9.6 KB8.3 KB1
other0 b617 B151 B1
json0 b9.2 KB5.0 KB4
plain0 b586 B0 b1
TotalN/A1.0 MB2.9 MB63

Third party requests and sizes per content type

14 requests
ContentHeader SizeTransfer SizeContent SizeRequests
html0 b0 b0 b0
css0 b0 b0 b0
javascript0 b745.7 KB2.3 MB6
image0 b408 B42 B1
font0 b0 b0 b0
favicon0 b0 b0 b0
json0 b0 b0 b1
plain0 b841 B2 B6
TotalN/A747.0 KB2.3 MB14