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 ·

craigerskine.com

https://craigerskine.com/

61 97 100 100 –CWV 5AXE

Data from Aug 20, 2026, 7:11 PM UTC — 24h old.

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

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 3.1.6 Built with Eleventy 3.1.6
Netlify Hosted by Netlify

Scores

61
Performance
no change
97
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 5.36 s — — 5.36 s 5.36 s
CLS Cumulative Layout Shift 0.221 — — 0.221 0.221
TBT Total Blocking Time 239 ms — — 239 ms 239 ms
FCP First Contentful Paint 2.63 s — — 2.63 s 2.63 s
Speed Index 2.63 s — — 2.63 s 2.63 s
TTFB Time to First Byte 620 ms — — 620 ms 620 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 252 ms
time to first byte 21 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 906.7 kB — — 906.7 kB 906.7 kB
Requests 38 — — 38 38
Third-party Weight 55.9 kB — — 55.9 kB 55.9 kB
Third-party CPU 0 ms — — 0 ms 0 ms
Unused JS 36.1 kB — — 36.1 kB 36.1 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

image 760.8 kB · 26 req
script 72.5 kB · 1 req
font 48.5 kB · 1 req
document 11.6 kB · 1 req
other 7.2 kB · 5 req
stylesheet 2.1 kB · 2 req
third party 55.9 kB · 6 req

Third parties 2 entities

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

Google Fonts 49.2 kB · 0 ms CPU
iconify.design 6.7 kB · 0 ms CPU

Page health

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

Main thread work

script evaluation 329 ms
other 314 ms
style layout 133 ms
paint composite render 46 ms
parse HTML 25 ms
script parse compile 16 ms
garbage collection 13 ms

Axe violations axe-core 4.13.0, full rule set

5 violating nodes across 1 rule, 436 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-name — Links must have discernible text 5 nodes

Accessibility failures 1 of 27 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-name — Links do not have a discernible name 5 nodes

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:11 PM UTC 61 5.36 s 0.221 239 ms 906.7 kB 3/3 ±8 2,963 25.6s

Embed this score

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