Page summary

https://stf.xelta.ai/llms.txt

Tested 2026-07-31 13:34:45 using Chrome 150.0.7871.186 (runtime settings)

SummaryWaterfallMetricsRenderingCoachPageXrayCPUThird party

This page is fast to paint, snappy to interact with and visually stable, but loose on best practices and weak on user privacy.

87 / 100
Coach overall
99 / 100
Performance
57 / 100
Best practice
82 / 100
Privacy

How it loaded →

0 → 201 ms · median run
Frame at 0 ms
start
Frame at 200 ms
Largest paint200 ms
Frame at 300 ms
Complete300 ms
201 ms
First Visual Change
201 ms
Speed Index
201 ms
Visual Complete 85%
201 ms
Last Visual Change
TTFB87 msLCP180 msTBT0 msCLS0.00

What to act on · top recommendations

Avoid extra requests by setting cache headers

90 / 100

The page has 1 request that are missing a cache time. Configure a cache time so the browser doesn't need to download them every time. It will save 697 B the next access.

Don't use private headers on static content

90 / 100

The page has 1 request with private headers. Make sure that the assets really should be private and only used by one user. Otherwise, make it cacheable for everyone.

Avoid missing and error requests

90 / 100

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

Google Web Vitals

min · median · mean · max of 1 run
MetricMinMedianMeanMax
Time To First Byte (TTFB)87 ms87 ms87 ms87 ms
Largest Contentful Paint (LCP)180 ms180 ms180 ms180 ms
Cumulative Layout Shift (CLS)0000

Visual Metrics

min · median · mean · max of 1 run
MetricMinMedianMeanMax
First visual change201 ms201 ms201 ms201 ms
Last visual change201 ms201 ms201 ms201 ms
Speed index201 ms201 ms201 ms201 ms
Visual readiness0 ms0 ms0 ms0 ms
Visual complete 85201 ms201 ms201 ms201 ms
Visual complete 95201 ms201 ms201 ms201 ms
Visual complete 99201 ms201 ms201 ms201 ms

CPU

min · median · mean · max of 1 run
MetricMinMedianMeanMax
Total Blocking Time0 ms0 ms0 ms0 ms
Max Potential FID0 ms0 ms0 ms0 ms
CPU long tasks 0000
CPU last long task happens at0 ms0 ms0 ms0 ms

More metrics

min · median · mean · max of 1 run
MetricMinMedianMeanMax
First paint180 ms180 ms180 ms180 ms
Load event end113 ms113 ms113 ms113 ms

Waterfall

Run 1 SpeedIndex median

First paintFCPLCPDOMContentLoadedDOM interactiveLoadRender-blockingRedirectError

Rendering

Run 1 · median
0.000 s
0s
Download video

Filmstrip

3 frames

Use --filmstrip.showAll to show all filmstrips.

Frame at 0 ms
0 ms
0 %
Frame at 200 ms
200 ms
0 %
Frame at 300 ms
300 ms
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 180 ms on a 87 ms first byte.

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

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

99
2 errors2 warnings1 info
warn(90)Avoid extra requests by setting cache headerscacheHeaders

The page has 1 request that are missing a cache time. Configure a cache time so the browser doesn't need to download them every time. It will save 697 B the next access.

The easiest way to make your page fast is to avoid doing requests to the server. Setting a cache header on your server response will tell the browser that it doesn't need to download the asset again during the configured cache time! Always try to set a cache time if the content doesn't change for every request.

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

The page has 1 request 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
error(90)Avoid missing and error requestsresponseOk

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

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
infoLong cache headers is goodcacheHeadersLong

The page has 1 request 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
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

57
4 warnings3 info
warn(0)Declare a doctype in your documentdoctype

The page is missing a doctype. Please use <!DOCTYPE html>.

The <!DOCTYPE> declaration is not an HTML tag; it is an instruction to the web browser about what version of HTML the page is written in.

warn(0)Declare the language code for your documentlanguage

The page is missing a language definition in the HTML tag. Define it with <html lang="YOUR_LANGUAGE_CODE">

According to the W3C recommendation you should declare the primary language for each Web page with the lang attribute inside the <html> tag https://www.w3.org/International/questions/qa-html-language-declarations#basics.

infoMeta descriptionmetaDescription

The page is missing a meta description.

Use a page description to make the page more relevant to search engines.

warn(0)Page titlepageTitle

The page is missing a title.

Use a title to make the page more relevant to search engines.

warn(0)Set a sensible viewport meta tagviewport

The page is missing a viewport meta tag. Add <meta name="viewport" content="width=device-width, initial-scale=1"> so the browser lays the page out at the device width.

The viewport meta tag tells the browser how to lay out the page on small screens. Without it (or without width=device-width) the page is rendered at a desktop fallback width and scaled down, which makes text unreadable on mobile. Disabling zoom (user-scalable=no, maximum-scale<=1) is also an accessibility regression. https://developer.mozilla.org/en-US/docs/Web/HTML/Viewport_meta_tag

infoDeclare a charset in your documentcharset

You are not using charset UTF-8?

The Unicode Standard (UTF-8) covers (almost) all the characters, punctuations, and symbols in the world. Please use that.

infoAvoid unnecessary headersunnecessaryHeaders

There are 3 responses that sets a server header.

Do not send headers that you don't need. We look for p3p, cache-control and max-age, pragma, server and x-frame-options headers. Have a look at Andrew Betts - Headers for Hackers talk as a guide https://www.youtube.com/watch?v=k92ZbrY815c or read https://www.fastly.com/blog/headers-we-dont-want.

Offenders

Privacy advice

82
4 warnings2 info
warn(0)Declare a referrer policy on the documentreferrerPolicy

No <meta name="referrer"> tag was found on the page. Set a Referrer-Policy response header (preferred) or add a meta tag, for example <meta name="referrer" content="strict-origin-when-cross-origin">.

Without an explicit referrer policy the browser falls back to the user-agent default and may leak the full URL of the previous page (including query strings) to every cross-origin request. Set a Referrer-Policy response header (preferred) or a <meta name="referrer"> tag in the document. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Referrer-Policy

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

Set a Content-Security-Policy header to mitigate cross-site scripting attacks. You can start with a Content-Security-Policy-Report-Only header, which only reports violations rather than blocking them.

A Content-Security-Policy response header tells the browser which sources of script, style, and other content are allowed. The most effective form is a strict CSP using nonces or hashes together with strict-dynamic; the worst is a missing header, with unsafe-inline and unsafe-eval close behind. https://web.dev/articles/strict-csp

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)Set a Permissions-Policy header to control which browser features the page can use.permissionsPolicyHeader

Set a Permissions-Policy header to control which browser features the page can use.

The Permissions-Policy response header (the successor to Feature-Policy) lets a site explicitly opt in or out of powerful browser features such as camera, microphone, geolocation, payment and clipboard. Setting a strict policy reduces the attack surface and limits what embedded third parties can do. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Permissions-Policy

Offenders

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.

TitleThe document title, shown in the browser tab and used by search results.
Layout viewport1350 × 971 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 elements5Total HTML elements. Fewer means less for the browser to style, lay out and paint.
Avg DOM depth2How deeply elements are nested on average.
Max DOM depth3The deepest nesting on the page. Deep branches cost more style recalculation.
Iframes0No embedded documents on this page.
Script tags0Number 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 storage0 bData the page saved in localStorage, kept across visits.
Session storage0 bData kept in sessionStorage for this tab session only.
Connection type4GWhat the Network Information API reported for the test connection.

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

3 technologies

Data from run 1

Visual Metrics

Visual milestones

all times from navigation start
Speed Index0.20 show quickly the page looked done
First Visual Change0.20 sfirst paint reaches the screen
Last Visual Change0.20 sscreen stops changing
nothing painted yet
First Visual Change · Visual Complete 85% · Visual Complete 95% · Visual Complete 99% · Last Visual Change0.20 s
00.1 s
Content milestones
Perception index
Visual progress
Visual progress at 0 s0.0s
Visual progress at 0.2 s0.2s
Visual progress at 0.3 s0.3s
FCP0.18s
LCP0.18s
VC850.20s
0.0s0.1s0.1s0.2s0.2s0.3s

Google Web Vitals

from run 1

Largest Contentful Paint

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

180 msLCP render time

Phase breakdown

  • TTFB87 ms
  • Resource load delay0 ms
  • Resource load duration0 ms
  • Element render delay93 ms

Element

Element type
<pre>
Size (w × h)
793956
Load time
0 ms

DOM path

body > pre
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.

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

4 entries
NameDurationDescription
cfCacheStatus0 msDYNAMIC
cfEdge10 ms
cfOrigin24 ms
cfExtPri0 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 versionH3
Total requests3
Total domains1
Transfer size22.2 KB
Content size116.4 KB
Missing compression0

Main document

status 200 · 0 redirects

https://stf.xelta.ai/llms.txt

HeaderValue
alt-svch3=":443"; ma=86400
cf-cache-statusDYNAMIC
cf-raya23cfb82de574221-BOM
content-encodingzstd
content-typetext/plain
dateFri, 31 Jul 2026 13:34:46 GMT
expect-ctmax-age=86400, enforce
nel{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
priorityu=0,i
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=jAIkFIE4MhUolQxEVBU%2BtrJ1a%2FTJhvnY6TF2Nqpjs6qj45eRvKup5ekfbulkXzEbTsVMYnX5qndi09YpB3a3sIBsQprEH1Yv2jjxcqR9dw1klmNNfMJEtkWcQAj5Gfk%3D"}]}
servercloudflare
server-timingcfCacheStatus;desc="DYNAMIC" cfEdge;dur=10,cfOrigin;dur=24 cfExtPri
speculation-rules"/cdn-cgi/speculation"
strict-transport-securitymax-age=31536000; includeSubDomains; preload
varyrsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch
x-content-type-optionsnosniff
x-frame-optionsSAMEORIGIN
x-xss-protection1; mode=block

Response codes

200
266.7%
404
133.3%

Largest assets on the page (by transfer size)

3 assets
URLTypeTransfer SizeContent Size
https://stf.xelta.ai/favicon.icohtml19.3 KB113.2 KB
https://stf.xelta.ai/llms.txtplain2.1 KB3.0 KB
https://stf.xelta.ai/cdn-cgi/speculationother697 B151 B

Requests and sizes per content type

2 types

Transfer size2.8 KB

  • plain75.9%
  • other24.1%

Content size3.2 KB

  • plain95.4%
  • other4.6%

Requests2

  • plain50.0%
  • other50.0%
ContentHeader SizeTransfer SizeContent SizeRequests
plain0 b2.1 KB3.0 KB1
other0 b697 B151 B1
Total0 b2.8 KB3.2 KB2

Data per domain

1 domain
DomainTotal download timeTransfer SizeContent SizeRequests
stf.xelta.ai122 ms22.2 KB116.4 KB3

Expires & last-modified statistics

typeminmedianmax
Expires0 seconds0 seconds4 weeks

Requests loaded after onLoad event

1 request

Includes requests done after load event end.

ContentTransfer SizeRequests
html0 b0
css0 b0
javascript0 b0
image0 b0
font0 b0
favicon0 b0
Total19.3 KB1

Requests loaded after onContentLoad

1 request

Includes requests done after DOM content loaded.

ContentTransfer SizeRequests
html0 b0
css0 b0
javascript0 b0
image0 b0
font0 b0
favicon0 b0
Total19.3 KB1

CPU

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.

✓ No long tasks observed during this run.

Third party

Third party requests categorised by Third party web version 0.29.2.

No third-party requests detected

Every request on this page resolved to a first-party domain. There are no entries in Third party web to attribute, no third-party tools to enumerate, and no third-party cookies set. If you expected to see entries here you can fine-tune the first-party domain list with --firstParty.

First party requests and sizes per content type

3 requests

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

ContentHeader SizeTransfer SizeContent SizeRequests
html0 b0 b0 b0
css0 b0 b0 b0
javascript0 b0 b0 b0
image0 b0 b0 b0
font0 b0 b0 b0
favicon0 b0 b0 b0
plain0 b2.1 KB3.0 KB1
other0 b697 B151 B1
TotalN/A22.2 KB116.4 KB3