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 ·

swelldiary.com

https://swelldiary.com/

80 88 77 100 CWV 156AXE

Data from Aug 21, 2026, 4:34 PM UTC — 2h old.

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

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
Amazon S3 Hosted by Amazon S3

Scores

80
Performance
no change
88
Accessibility
no change
77
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 4.22 s 4.22 s 4.22 s
CLS Cumulative Layout Shift 0.013 0.013 0.013
TBT Total Blocking Time 128 ms 128 ms 128 ms
FCP First Contentful Paint 2.90 s 2.90 s 2.90 s
Speed Index 2.90 s 2.90 s 2.90 s
TTFB Time to First Byte 603 ms 603 ms 603 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 95 ms
element render delay 46 ms
resource load duration 20 ms
time to first byte 4 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 668.0 kB 668.0 kB 668.0 kB
Requests 25 25 25
Third-party Weight 655.3 kB 655.3 kB 655.3 kB
Third-party CPU 101 ms 101 ms 101 ms
Unused JS 72.5 kB 72.5 kB 72.5 kB
Unused CSS 32.1 kB 32.1 kB 32.1 kB

By resource type

image 302.5 kB · 12 req
script 221.0 kB · 4 req
font 97.2 kB · 2 req
stylesheet 37.7 kB · 3 req
document 7.5 kB · 1 req
other 2.1 kB · 3 req
third party 655.3 kB · 21 req

Third parties 5 entities

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

YouTube 302.5 kB · 0 ms CPU
Google Tag Manager 169.6 kB · 62 ms CPU
Google Fonts 97.9 kB · 0 ms CPU
JSDelivr CDN 58.3 kB · 3 ms CPU
Clarity 26.9 kB · 36 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 899 ms 899 ms 899 ms
Long Tasks 4 4 4
DOM Elements 1,108 1,108 1,108
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 156 156 156
A11y Failures 3 3 3
A11y Failing Nodes 214 214 214

Main thread work

script evaluation 412 ms
other 180 ms
style layout 180 ms
script parse compile 72 ms
paint composite render 31 ms
parse HTML 24 ms

Axe violations axe-core 4.13.0, full rule set

156 violating nodes across 3 rules, 2302 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 154 nodes
  • moderate heading-order — Heading levels should only increase by one 1 node
  • moderate region — All page content should be contained by landmarks 1 node

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

  • color-contrast — Background and foreground colors do not have a sufficient contrast ratio. 154 nodes
  • target-size — Touch targets do not have sufficient size or spacing. 59 nodes
  • heading-order — Heading elements are not in a sequentially-descending order 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 21, 2026, 4:34 PM UTC 80 4.22 s 0.013 128 ms 668.0 kB 3/3 ±11 2,464 33.9s

Embed this score

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