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 ·

codersblock.com

https://codersblock.com/

84 96 100 100 –CWV 1AXE

Data from Aug 20, 2026, 7:34 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.

Netlify Hosted by Netlify

Scores

84
Performance
no change
96
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 3.31 s — — 3.31 s 3.31 s
CLS Cumulative Layout Shift 0.179 — — 0.179 0.179
TBT Total Blocking Time 71 ms — — 71 ms 71 ms
FCP First Contentful Paint 874 ms — — 874 ms 874 ms
Speed Index 1.17 s — — 1.17 s 1.17 s
TTFB Time to First Byte 710 ms — — 710 ms 710 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 154 ms
time to first byte 110 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 399.8 kB — — 399.8 kB 399.8 kB
Requests 12 — — 12 12
Third-party Weight 309.7 kB — — 309.7 kB 309.7 kB
Third-party CPU 81 ms — — 81 ms 81 ms
Unused JS 138.3 kB — — 138.3 kB 138.3 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 309.7 kB · 3 req
font 67.4 kB · 3 req
document 10.4 kB · 1 req
image 10.0 kB · 3 req
other 2.3 kB · 2 req
third party 309.7 kB · 3 req

Third parties 2 entities

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

Google Tag Manager 288.8 kB · 69 ms CPU
Google Analytics 20.9 kB · 12 ms CPU

Page health

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

Main thread work

script evaluation 297 ms
other 124 ms
script parse compile 88 ms
style layout 75 ms
paint composite render 22 ms
parse HTML 12 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 435 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.

  • serious link-in-text-block — Links must be distinguishable without relying on color 1 node

Accessibility failures 1 of 26 audits

Tracked as a count, not just the score — the weighted score is coarse enough that you can ship a broken component and barely move it.

  • link-in-text-block — Links rely on color to be distinguishable. 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:34 PM UTC 84 3.31 s 0.179 71 ms 399.8 kB 3/3 ±10 2,396 25.1s

Embed this score

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