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 ·

alfieaward.com

https://www.alfieaward.com/

78 98 100 100 –CWV 31AXE

Data from Aug 21, 2026, 5:30 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.

Build Awesome 4.0.0 Built with Build Awesome 4.0.0
Netlify Hosted by Netlify

Scores

78
Performance
no change
98
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 4.91 s — — 4.91 s 4.91 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 2.62 s — — 2.62 s 2.62 s
Speed Index 2.62 s — — 2.62 s 2.62 s
TTFB Time to First Byte 466 ms — — 466 ms 466 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 2.18 s
time to first byte 19 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 599.1 kB — — 599.1 kB 599.1 kB
Requests 22 — — 22 22
Third-party Weight 59.9 kB — — 59.9 kB 59.9 kB
Third-party CPU 3 ms — — 3 ms 3 ms
Unused JS 0 B — — 0 B 0 B
Unused CSS 0 B — — 0 B 0 B

By resource type

other 497.1 kB · 3 req
font 46.2 kB · 2 req
script 27.4 kB · 3 req
stylesheet 14.9 kB · 2 req
document 9.5 kB · 1 req
image 4.0 kB · 1 req
third party 59.9 kB · 4 req

Third parties 2 entities

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

Google Fonts 48.4 kB · 0 ms CPU
Cloudflare 11.5 kB · 3 ms CPU

Page health

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

Main thread work

other 382 ms
style layout 277 ms
paint composite render 86 ms
script evaluation 78 ms
parse HTML 28 ms
script parse compile 10 ms

Axe violations axe-core 4.13.0, full rule set

31 violating nodes across 4 rules, 576 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 25 nodes
  • minor image-redundant-alt — Alternative text of images should not be repeated as text 3 nodes
  • minor empty-heading — Headings should not be empty 2 nodes
  • moderate landmark-one-main — Document should have one main landmark 1 node

Accessibility failures 1 of 28 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.

  • landmark-one-main — Document does not have a main landmark. 1 node

Hygiene

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

HTTPS HSTS CSP Clickjacking protection Origin isolation Trusted Types bfcache h3

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:30 PM UTC 78 4.91 s 0 0 ms 599.1 kB 3/3 ±6 2,458 30.6s

Embed this score

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