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 ·

jordanjohnson.pt

https://jordanjohnson.pt/

99 100 100 100 CWV 1AXE

Data from Aug 21, 2026, 1:21 AM UTC — 17h old.

Built Awesome · 1 measurement · since Aug 21, 2026 · last attempt 17h

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

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-19 → 2026-08-15). From the backfilled CrUX history rather than this measurement, which predates the API key. This is what Google measures you on.

LCP no data
INP no data
CLS no data

Scores

99
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 2.08 s 2.08 s 2.08 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 5 ms 5 ms 5 ms
FCP First Contentful Paint 822 ms 822 ms 822 ms
Speed Index 822 ms 822 ms 822 ms
TTFB Time to First Byte 474 ms 474 ms 474 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 44 ms
resource load delay 42 ms
resource load duration 24 ms
time to first byte 8 ms

Field history 25 weeks

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

Week ending LCPINPCLSFCPTTFB
2026-08-15
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
2026-05-30

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 225.4 kB 225.4 kB 225.4 kB
Requests 20 20 20
Third-party Weight 17.7 kB 17.7 kB 17.7 kB
Third-party CPU 25 ms 25 ms 25 ms
Unused JS 0 B 0 B 0 B
Unused CSS 0 B 0 B 0 B

By resource type

image 163.8 kB · 11 req
other 32.7 kB · 5 req
script 17.6 kB · 2 req
document 8.7 kB · 1 req
third party 17.7 kB · 4 req

Third parties 2 entities

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

SpeedCurve RUM 12.7 kB · 11 ms CPU
simpleanalyticscdn.com 5.0 kB · 14 ms CPU

Page health

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

Main thread work

other 143 ms
script evaluation 113 ms
style layout 49 ms
parse HTML 16 ms
paint composite render 15 ms
script parse compile 10 ms

Axe violations axe-core 4.13.0, full rule set

1 violating node across 1 rule, 253 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 landmark-unique — Landmarks should have a unique role or role/label/title (i.e. accessible name) combination 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, 1:21 AM UTC 99 2.08 s 0 5 ms 225.4 kB 3/3 ±1 2,485 22.7s

Embed this score

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