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 ·

cyberpunk.co.uk

https://www.cyberpunk.co.uk/

79 100 77 100 CWV 0AXE

Data from Aug 21, 2026, 5:35 PM UTC — 1h old.

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

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.

Netlify Hosted by Netlify

Scores

79
Performance
no change
100
Accessibility
no change
77
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.55 s 2.55 s 2.55 s
CLS Cumulative Layout Shift 0.238 0.238 0.238
TBT Total Blocking Time 282 ms 282 ms 282 ms
FCP First Contentful Paint 779 ms 779 ms 779 ms
Speed Index 2.07 s 2.07 s 2.07 s
TTFB Time to First Byte 604 ms 604 ms 604 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 48 ms
resource load delay 20 ms
resource load duration 11 ms
time to first byte 5 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.06 MB 1.06 MB 1.06 MB
Requests 40 40 40
Third-party Weight 644.7 kB 644.7 kB 644.7 kB
Third-party CPU 231 ms 231 ms 231 ms
Unused JS 316.5 kB 316.5 kB 316.5 kB
Unused CSS 0 B 0 B 0 B

By resource type

script 841.7 kB · 13 req
image 156.4 kB · 8 req
document 29.9 kB · 8 req
other 14.2 kB · 5 req
stylesheet 8.7 kB · 5 req
third party 892.1 kB · 34 req

Third parties 5 entities

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

Google Tag Manager 309.2 kB · 112 ms CPU
Google/Doubleclick Ads 290.2 kB · 93 ms CPU
adtrafficquality.google 21.2 kB · 7 ms CPU
Google Analytics 20.9 kB · 16 ms CPU
Fathom Analytics 3.2 kB · 3 ms CPU

Page health

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

Main thread work

script evaluation 1.21 s
other 279 ms
script parse compile 172 ms
style layout 54 ms
paint composite render 19 ms
parse HTML 9 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 127 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.

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 21, 2026, 5:35 PM UTC 79 2.55 s 0.238 282 ms 1.06 MB 3/3 ±1 2,474 35.5s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show cyberpunk.co.uk'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://www.cyberpunk.co.uk/"></speedlify-score>