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 ·

antlersocial.com

https://antlersocial.com/

86 94 54 92 6AXE CWV

Data from Aug 20, 2026, 4:28 PM UTC 3d old

Built Awesome #1,071 · 1 measurement · since Aug 20, 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.

Netlify Hosted by Netlify

Scores

86
Performance
no change
94
Accessibility
no change
54
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 2.26 s 2.26 s 2.26 s
CLS Cumulative Layout Shift 0.001 0.001 0.001
TBT Total Blocking Time 449 ms 449 ms 449 ms
FCP First Contentful Paint 1.96 s 1.96 s 1.96 s
Speed Index 1.96 s 1.96 s 1.96 s
TTFB Time to First Byte 609 ms 609 ms 609 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 2.26 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.

element render delay 117 ms
time to first byte 7 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 801 kB 801 kB 801 kB
Requests 45 45 45
Third-party Weight 533 kB 533 kB 533 kB
Third-party CPU 218 ms 218 ms 218 ms
Unused JS 190 kB 190 kB 190 kB
Unused CSS 21.3 kB 21.3 kB 21.3 kB

By resource type

script 537 kB · 10 req
document 169 kB · 1 req
image 53.2 kB · 7 req
font 30.9 kB · 2 req
stylesheet 5.1 kB · 1 req
other 1.4 kB · 6 req
third party 533 kB · 12 req

Third parties 5 entities

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

Google Tag Manager 457 kB · 181 ms CPU
Netlify 55.3 kB · 25 ms CPU
Google Analytics 20.9 kB · 12 ms CPU
Other Google APIs/SDKs 105 B · 0 ms CPU
Google/Doubleclick Ads 60 B · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 2.51 s 2.51 s 2.51 s
Long Tasks 7 7 7
DOM Elements 573 573 573
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 6 6 6
A11y Failures 2 2 2
A11y Failing Nodes 8 8 8

Main thread work

script evaluation 1.07 s
other 587 ms
style layout 318 ms
paint composite render 192 ms
script parse compile 147 ms
parse HTML 129 ms
garbage collection 67 ms

Axe violations axe-core 4.13.0, full rule set

6 violating nodes across 2 rules, 712 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 5 nodes
  • moderate heading-order — Heading levels should only increase by one 1 node

Accessibility failures 2 of 24 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. 7 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 5 console errors

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:28 PM UTC 86 2.26 s 0.001 449 ms 801 kB 3/3 ±2 2,470 256.4s

Embed this score

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