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 ·

atom-editor.cc

https://atom-editor.cc/

99 90 100 83 CWV 15AXE

Data from Aug 20, 2026, 4:30 PM UTC — 26h old.

Built Awesome · 1 measurement · since Aug 20, 2026 · last attempt 26h

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-22 → 2026-08-18). This is what Google measures you on.

LCP 1.81 s good
INP 95 ms good
CLS 0 good

Scores

99
Performance
no change
90
Accessibility
no change
100
Best Practices
no change
83
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 1.92 s 1.92 s 1.92 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 1.55 s 1.55 s 1.55 s
Speed Index 1.55 s 1.55 s 1.55 s
TTFB Time to First Byte 625 ms 625 ms 625 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 48 ms
resource load duration 48 ms
element render delay 42 ms
time to first byte 12 ms

Field data Chrome UX Report, url-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.81 s good 85.5% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 95 ms good 93.9% good
CLS CWV 0 good 95.5% good
FCP 1.50 s good 81% good
TTFB 974 ms needs-improvement 67.5% good

Lab vs field

Lab LCP 1.92 s · field p75 1.81 s · real users are 0.94× 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 1.81 s 91 ms 0 1.50 s 978 ms
2026-08-08 1.81 s 93 ms 0 1.50 s 960 ms
2026-08-01 1.75 s 99 ms 0 1.43 s 941 ms
2026-07-25 1.80 s 99 ms 0 1.48 s 942 ms
2026-07-18 1.84 s 102 ms 0 1.48 s 971 ms
2026-07-11 1.85 s 105 ms 0 1.50 s 945 ms
2026-07-04 1.92 s 97 ms 0 1.54 s 945 ms
2026-06-27 1.86 s 94 ms 0 1.52 s 870 ms
2026-06-20 1.76 s 94 ms 0 1.43 s 791 ms
2026-06-13 1.74 s 94 ms 0 1.38 s 791 ms
2026-06-06 1.67 s 94 ms 0 1.36 s 770 ms
2026-05-30 1.67 s 93 ms 0 1.36 s 800 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 278.2 kB 278.2 kB 278.2 kB
Requests 24 24 24
Third-party Weight 11.5 kB 11.5 kB 11.5 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

image 238.7 kB · 18 req
font 18.1 kB · 1 req
script 11.5 kB · 1 req
document 4.2 kB · 1 req
other 488 B · 1 req
third party 11.5 kB · 1 req

Third parties 1 entities

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

Cloudflare 11.5 kB · 3 ms CPU

Page health

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

Main thread work

other 266 ms
style layout 102 ms
script evaluation 43 ms
paint composite render 29 ms
parse HTML 21 ms
script parse compile 1 ms

Axe violations axe-core 4.13.0, full rule set

15 violating nodes across 4 rules, 310 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 9 nodes
  • critical image-alt — Images must have alternative text 4 nodes
  • moderate heading-order — Heading levels should only increase by one 1 node
  • moderate landmark-one-main — Document should have one main landmark 1 node

Accessibility failures 3 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.

  • image-alt — Image elements do not have `[alt]` attributes 3 nodes
  • heading-order — Heading elements are not in a sequentially-descending order 1 node
  • 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 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, 4:30 PM UTC 99 1.92 s 0 0 ms 278.2 kB 3/3 ±0 2,452 22.8s

Embed this score

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