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 ·

atomic.financial

https://atomic.financial/

66 96 58 100 ✗CWV 4AXE

Data from Aug 20, 2026, 3:45 PM UTC — 27h old.

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

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.

Netlify Hosted by Netlify

Core Web Vitals field data, origin-level

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

LCP 2.61 s needs-improvement
INP 194 ms good
CLS 0 good

Scores

66
Performance
no change
96
Accessibility
no change
58
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 3.52 s — — 3.52 s 3.52 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 1.14 s — — 1.14 s 1.14 s
FCP First Contentful Paint 1.85 s — — 1.85 s 1.85 s
Speed Index 2.30 s — — 2.30 s 2.30 s
TTFB Time to First Byte 610 ms — — 610 ms 610 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 313 ms
time to first byte 13 ms

Field data Chrome UX Report, origin-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 2.61 s needs-improvement 73.3% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 194 ms good 77.1% good
CLS CWV 0 good 96.3% good
FCP 2.60 s needs-improvement 63.1% good
TTFB 681 ms good 82.2% good

Lab vs field

Lab LCP 3.52 s · field p75 2.61 s · real users are 0.74× 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 2.93 s — 0.030 2.82 s 626 ms
2026-08-08 2.93 s 253 ms 0.030 2.82 s 578 ms
2026-08-01 2.67 s 237 ms 0.030 2.67 s 611 ms
2026-07-25 2.78 s 227 ms 0.020 2.72 s 606 ms
2026-07-18 2.73 s 228 ms 0.020 2.76 s 591 ms
2026-07-11 2.73 s 219 ms 0.030 3.02 s 582 ms
2026-07-04 2.77 s 219 ms 0.030 3.02 s 559 ms
2026-06-27 2.62 s — 0.030 2.73 s 521 ms
2026-06-20 2.62 s — 0.020 2.62 s 506 ms
2026-06-13 2.67 s — 0.020 2.69 s 539 ms
2026-06-06 2.68 s 262 ms 0.010 2.71 s 530 ms
2026-05-30 2.77 s 260 ms 0.010 2.84 s 563 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 983.9 kB — — 983.9 kB 983.9 kB
Requests 43 — — 43 43
Third-party Weight 754.3 kB — — 754.3 kB 754.3 kB
Third-party CPU 328 ms — — 328 ms 328 ms
Unused JS 249.7 kB — — 249.7 kB 249.7 kB
Unused CSS 0 B — — 0 B 0 B

By resource type

script 815.2 kB · 20 req
document 107.0 kB · 1 req
font 31.2 kB · 2 req
stylesheet 21.2 kB · 1 req
other 6.9 kB · 14 req
image 1.2 kB · 4 req
third party 754.3 kB · 30 req

Third parties 8 entities

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

Google Tag Manager 483.6 kB · 188 ms CPU
Facebook 109.5 kB · 61 ms CPU
Hubspot 90.7 kB · 44 ms CPU
LinkedIn Ads 41.3 kB · 16 ms CPU
claydar.com 24.9 kB · 18 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 5.45 s — — 5.45 s 5.45 s
Long Tasks 17 — — 17 17
DOM Elements 5,802 — — 5,802 5,802
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 4 — — 4 4
A11y Failures 2 — — 2 2
A11y Failing Nodes 3 — — 3 3

Main thread work

script evaluation 1.89 s
other 1.74 s
style layout 1.10 s
script parse compile 276 ms
paint composite render 273 ms
parse HTML 130 ms
garbage collection 37 ms

Axe violations axe-core 4.13.0, full rule set

4 violating nodes across 3 rules, 2411 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.

  • serious color-contrast — Elements must meet minimum color contrast ratio thresholds 2 nodes
  • serious link-in-text-block — Links must be distinguishable without relying on color 1 node
  • moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 2 of 27 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.

  • label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 2 nodes
  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 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, 3:45 PM UTC 66 3.52 s 0 1.14 s 983.9 kB 3/3 ±1 2,374 41.8s

Embed this score

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