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 ·

jamesdoc.com

https://jamesdoc.com/

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

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

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

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 819 ms — — 819 ms 819 ms
CLS Cumulative Layout Shift 0.002 — — 0.002 0.002
TBT Total Blocking Time 0 ms — — 0 ms 0 ms
FCP First Contentful Paint 819 ms — — 819 ms 819 ms
Speed Index 819 ms — — 819 ms 819 ms
TTFB Time to First Byte 651 ms — — 651 ms 651 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.

resource load delay 71 ms
time to first byte 53 ms
resource load duration 53 ms
element render delay 23 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 67.0 kB — — 67.0 kB 67.0 kB
Requests 12 — — 12 12
Third-party Weight 1.4 kB — — 1.4 kB 1.4 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

font 42.2 kB · 2 req
image 12.3 kB · 4 req
stylesheet 6.3 kB · 1 req
script 4.1 kB · 2 req
document 1.3 kB · 1 req
other 895 B · 2 req
third party 1.4 kB · 2 req

Third parties 1 entities

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

tinylytics.app 1.4 kB · 3 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 191 ms — — 191 ms 191 ms
Long Tasks 0 — — 0 0
DOM Elements 34 — — 34 34
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 111 ms
style layout 32 ms
script evaluation 30 ms
paint composite render 9 ms
parse HTML 7 ms
script parse compile 3 ms

Axe violations axe-core 4.13.0, full rule set

0 violating nodes across 0 rules, 91 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, 1:16 AM UTC 100 819 ms 0.002 0 ms 67.0 kB 3/3 ±3 2,452 22.7s

Embed this score

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