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 ·

limoaugusta.com

https://www.limoaugusta.com/

92 96 100 100 CWV 27AXE

Data from Aug 21, 2026, 6:43 PM UTC — 29m old.

Build Awesome Starters, 11ty Emeritus · 1 measurement · since Aug 21, 2026 · last attempt 29m

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.

Jekyll 4.4.1 Built with Jekyll 4.4.1
Netlify Hosted by Netlify

Scores

92
Performance
no change
96
Accessibility
no change
100
Best Practices
no change
100
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 3.31 s 3.31 s 3.31 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 908 ms 908 ms 908 ms
Speed Index 908 ms 908 ms 908 ms
TTFB Time to First Byte 608 ms 608 ms 608 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 76 ms
time to first byte 9 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 669.5 kB 669.5 kB 669.5 kB
Requests 15 15 15
Third-party Weight 0 B 0 B 0 B
Third-party CPU 0 ms 0 ms 0 ms
Unused JS 0 B 0 B 0 B
Unused CSS 22.9 kB 22.9 kB 22.9 kB

By resource type

image 588.6 kB · 10 req
stylesheet 24.6 kB · 2 req
other 23.6 kB · 1 req
script 22.3 kB · 1 req
document 10.4 kB · 1 req

Page health

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

Main thread work

other 180 ms
style layout 59 ms
parse HTML 24 ms
script evaluation 19 ms
paint composite render 16 ms
script parse compile 10 ms

Axe violations axe-core 4.13.0, full rule set

27 violating nodes across 3 rules, 671 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 25 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 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.

  • 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
  • label-content-name-mismatch — Elements with visible text labels do not have matching accessible names. 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, 6:43 PM UTC 92 3.31 s 0 0 ms 669.5 kB 3/3 ±3 2,354 24.8s

Embed this score

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