speedlify2

Lighthouse lab metrics and Chrome UX Report field data for a list of sites, recorded on every run and compared over time — measured continuously.

Measurement runs · Embed a score ·

superawesomeshit.com

https://www.superawesomeshit.com/

82 95 77 100 34AXE –CWV

Data from Aug 22, 2026, 9:26 AM UTC 37h old

Built Awesome #1,031 · 4 measurements · since Aug 21, 2026

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

Scores

82
Performance
no change
95
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.21 s — — 4.21 s 4.21 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 218 ms — — 218 ms 218 ms
FCP First Contentful Paint 1.54 s — — 1.54 s 1.54 s
Speed Index 1.54 s — — 1.54 s 1.54 s
TTFB Time to First Byte 614 ms — — 614 ms 614 ms

What LCP is made of observed, unthrottled

A flat LCP number tells you something regressed. The subparts tell you whether it was the server, resource discovery, the download, or rendering.

Measured on the trace before throttling is modelled, so these are real durations that will not sum to the 4.21 s above — that figure is a simulation of the same load on a slow phone and connection. Read these for the proportions: which phase dominates.

time to first byte 282 ms
element render delay 78 ms
resource load delay 57 ms
resource load duration 24 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 675 kB — — 675 kB 675 kB
Requests 27 — — 27 27
Third-party Weight 258 kB — — 258 kB 258 kB
Third-party CPU 118 ms — — 118 ms 118 ms
Unused JS 70.5 kB — — 70.5 kB 70.5 kB
Unused CSS 21.3 kB — — 21.3 kB 21.3 kB

By resource type

image 398 kB · 15 req
script 259 kB · 6 req
document 7.0 kB · 1 req
stylesheet 4.7 kB · 2 req
other 755 B · 2 req
third party 258 kB · 9 req

Third parties 4 entities

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

Google Tag Manager 164 kB · 55 ms CPU
Netlify 55.0 kB · 32 ms CPU
Clarity 27.0 kB · 27 ms CPU
Cloudflare 11.5 kB · 4 ms CPU

Page health

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

Main thread work

script evaluation 501 ms
other 258 ms
script parse compile 85 ms
style layout 58 ms
paint composite render 24 ms
parse HTML 19 ms

Axe violations axe-core 4.13.0, full rule set

34 violating nodes across 3 rules, 662 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 22 nodes
  • minor image-redundant-alt — Alternative text of images should not be repeated as text 11 nodes
  • moderate region — All page content should be contained by landmarks 1 node

Accessibility failures 1 of 22 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. 22 nodes

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 22, 2026, 9:26 AM UTC 82 4.21 s 0 218 ms 675 kB 3/3 ±27 2,331 34.9s
Aug 22, 2026, 2:53 AM UTC CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. 16.4s
Aug 21, 2026, 7:25 PM UTC CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. 16.7s
Aug 21, 2026, 12:46 PM UTC CHROME_INTERSTITIAL_ERROR: Chrome prevented page load with an interstitial. Make sure you are testing the correct URL and that the server is properly responding to all requests. 16.9s

Embed this score

Live below, then the markup that produces it. Drop that on any page to show superawesomeshit.com's scores, updated whenever this instance re-measures — more about the component. Don’t forget to bundle the speedlify2-score.js component code into your site! 

<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://www.superawesomeshit.com/"></speedlify2-score>