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 ·

redfang.net

https://redfang.net/

Data from Aug 21, 2026, 6:45 AM UTC — 11h old.

11ty Emeritus · 1 measurement · since Aug 21, 2026 · last attempt 11h

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.

Astro 7.1.6 Built with Astro 7.1.6
Netlify Hosted by Netlify

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-23 → 2026-08-19). This is what Google measures you on.

LCP 593 ms good
INP 60 ms good
CLS 0 good

Scores

100
Performance
no change
100
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 793 ms 793 ms 793 ms
CLS Cumulative Layout Shift 0.006 0.006 0.006
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 793 ms 793 ms 793 ms
Speed Index 793 ms 793 ms 793 ms
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 25 ms
time to first byte 22 ms

Field data Chrome UX Report, url-level

Real Chrome users, 28-day trailing window (2026-07-23 → 2026-08-19). This is what Google measures you on.

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 593 ms good 98.3% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 60 ms good 100% good
CLS CWV 0 good 100% good
FCP 622 ms good 97.1% good

Lab vs field

Lab LCP 793 ms · field p75 593 ms · real users are 0.75× faster than the lab.

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-15 60 ms 0 640 ms
2026-08-08
2026-08-01
2026-07-25
2026-07-18
2026-07-11
2026-07-04
2026-06-27
2026-06-20
2026-06-13
2026-06-06 0 891 ms 793 ms
2026-05-30

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 101.3 kB 101.3 kB 101.3 kB
Requests 4 4 4
Third-party Weight 0 B 0 B 0 B
Third-party CPU 0 ms 0 ms 0 ms
Unused JS 0 B 0 B 0 B
Unused CSS 0 B 0 B 0 B

By resource type

image 75.2 kB · 1 req
font 19.7 kB · 1 req
document 5.7 kB · 1 req
other 689 B · 1 req

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 113 ms 113 ms 113 ms
Long Tasks 0 0 0
DOM Elements 45 45 45
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

other 74 ms
style layout 18 ms
script evaluation 9 ms
parse HTML 6 ms
paint composite render 5 ms
script parse compile 0 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 126 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, 6:45 AM UTC 100 793 ms 0.006 0 ms 101.3 kB 3/3 ±0 2,648 19.8s

Embed this score

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