speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time.

Measurement runs · Embed a score · Field data from the Chrome UX Report ·

cosmo-digital.at

https://cosmo-digital.at/

98 100 100 100 –CWV 1AXE

Data from Aug 20, 2026, 7:40 PM UTC — 23h old.

Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 23h

Stack

Detected on the same page load as the accessibility pass — the generator from <meta name="generator"> or the shape of the page, the host from response headers.

Eleventy Built with Eleventy
Amazon S3 Hosted by Amazon S3

Scores

98
Performance
no change
100
Accessibility
no change
100
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.11 s — — 2.11 s 2.11 s
CLS Cumulative Layout Shift 0.036 — — 0.036 0.036
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 1.64 s — — 1.64 s 1.64 s
Speed Index 1.64 s — — 1.64 s 1.64 s
TTFB Time to First Byte 608 ms — — 608 ms 608 ms

What LCP is made of

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

element render delay 44 ms
resource load duration 16 ms
resource load delay 8 ms
time to first byte 7 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 312.3 kB — — 312.3 kB 312.3 kB
Requests 50 — — 50 50
Third-party Weight 2.4 kB — — 2.4 kB 2.4 kB
Third-party CPU 2 ms — — 2 ms 2 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

image 155.9 kB · 30 req
font 113.1 kB · 6 req
stylesheet 11.2 kB · 4 req
document 8.7 kB · 1 req
script 6.4 kB · 6 req
other 1.5 kB · 2 req
third party 2.4 kB · 2 req

Third parties 1 entities

2.4 kB transferred, 2 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

Plausible 2.4 kB · 2 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 533 ms — — 533 ms 533 ms
Long Tasks 0 — — 0 0
DOM Elements 344 — — 344 344
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 1 — — 1 1
A11y Failures 0 — — 0 0
A11y Failing Nodes 0 — — 0 0

Main thread work

other 308 ms
style layout 127 ms
paint composite render 56 ms
script evaluation 29 ms
parse HTML 11 ms
script parse compile 3 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 698 passing. This is a standalone axe run, stricter than the subset Lighthouse folds into its score above — and it is the second tiebreaker in the ranking.

  • moderate region — All page content should be contained by landmarks 1 node

Hygiene

Changes rarely — which is exactly why a change is worth noticing.

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h2

Measurement log

Every stored run for this URL, newest first. Failures are kept as records — "this site was down on Tuesday" is data too.

When PerfLCPCLSTBTWeight RunsSpreadBenchTook
Aug 20, 2026, 7:40 PM UTC 98 2.11 s 0.036 0 ms 312.3 kB 3/3 ±14 4,260 27s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show cosmo-digital.at's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify-score.js component code into your site! 

<speedlify-score speedlify-url="https://zachleat.github.io/speedlify2/" url="https://cosmo-digital.at/"></speedlify-score>