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 ·

andeers.com

https://andeers.com/

100 93 100 100 CWV 2AXE

Data from Aug 20, 2026, 3:41 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.

Eleventy 2.0.1 Built with Eleventy 2.0.1
Netlify Hosted by Netlify

Scores

100
Performance
no change
93
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 1.03 s 1.03 s 1.03 s
CLS Cumulative Layout Shift 0.052 0.052 0.052
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 1.03 s 1.03 s 1.03 s
Speed Index 1.03 s 1.03 s 1.03 s
TTFB Time to First Byte 734 ms 734 ms 734 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 176 ms
time to first byte 53 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 47.1 kB 47.1 kB 47.1 kB
Requests 7 7 7
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 0 B 0 B 0 B

By resource type

font 26.2 kB · 1 req
script 10.6 kB · 1 req
document 5.1 kB · 1 req
stylesheet 3.9 kB · 1 req
image 823 B · 1 req
other 218 B · 1 req

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 184 ms 184 ms 184 ms
Long Tasks 0 0 0
DOM Elements 90 90 90
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 2 2 2
A11y Failures 2 2 2
A11y Failing Nodes 2 2 2

Main thread work

other 91 ms
style layout 46 ms
script evaluation 21 ms
paint composite render 10 ms
script parse compile 9 ms
parse HTML 7 ms

Axe violations axe-core 4.13.0, full rule set

2 violating nodes across 2 rules, 130 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 heading-order — Heading levels should only increase by one 1 node
  • serious list — <ul> and <ol> must only directly contain <li>, <script> or <template> elements 1 node

Accessibility failures 2 of 18 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
  • list — Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`). 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:41 PM UTC 100 1.03 s 0.052 0 ms 47.1 kB 3/3 ±0 2,330 20.4s

Embed this score

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