speedlify2

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

Measurement runs · Embed a score ·

cam.macfar.land

https://cam.macfar.land/

82 94 77 100 14AXE CWV

Data from Aug 20, 2026, 7:34 PM UTC 3d old

Built Awesome #1,032 · 1 measurement · since Aug 20, 2026

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
Vercel Hosted by Vercel

Scores

82
Performance
no change
94
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 3.80 s 3.80 s 3.80 s
CLS Cumulative Layout Shift 0.013 0.013 0.013
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 3.35 s 3.35 s 3.35 s
Speed Index 3.35 s 3.35 s 3.35 s
TTFB Time to First Byte 617 ms 617 ms 617 ms

What LCP is made of observed, unthrottled

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

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 3.80 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

element render delay 106 ms
resource load delay 50 ms
time to first byte 14 ms
resource load duration 3 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 592 kB 592 kB 592 kB
Requests 32 32 32
Third-party Weight 569 kB 569 kB 569 kB
Third-party CPU 7 ms 7 ms 7 ms
Unused JS 0 B 0 B 0 B
Unused CSS 0 B 0 B 0 B

By resource type

image 362 kB · 4 req
font 194 kB · 3 req
script 13.5 kB · 6 req
stylesheet 11.4 kB · 4 req
document 8.4 kB · 1 req
other 1.7 kB · 3 req
third party 570 kB · 12 req

Third parties 5 entities

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

unsplash.com 362 kB · 0 ms CPU
Google Fonts 197 kB · 0 ms CPU
JSDelivr CDN 7.2 kB · 6 ms CPU
codepenassets.com 3.2 kB · 0 ms CPU
codepen.io 0 B · 1 ms CPU

Page health

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

Main thread work

script evaluation 290 ms
other 156 ms
style layout 80 ms
paint composite render 20 ms
parse HTML 17 ms
script parse compile 9 ms

Axe violations axe-core 4.13.0, full rule set

14 violating nodes across 3 rules, 432 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 color-contrast — Elements must meet minimum color contrast ratio thresholds 12 nodes
  • moderate heading-order — Heading levels should only increase by one 1 node
  • moderate landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 1 node

Accessibility failures 2 of 23 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.

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 12 nodes
  • heading-order — Heading elements are not in a sequentially-descending order 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 82 3.80 s 0.013 0 ms 592 kB 3/3 ±0 2,435 24.1s

Embed this score

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

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://cam.macfar.land/"></speedlify2-score>