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 ·

mikeritteronline.com

https://www.mikeritteronline.com/

78 84 100 91 CWV 4AXE

Data from Aug 21, 2026, 6:36 PM UTC — 37m old.

Built Awesome · 2 measurements · since Aug 21, 2026 · last attempt 37m

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

78
Performance
no change
84
Accessibility
no change
100
Best Practices
no change
91
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 5.93 s 5.93 s 5.93 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 0 ms 0 ms 0 ms
FCP First Contentful Paint 1.50 s 1.50 s 1.50 s
Speed Index 1.50 s 1.50 s 1.50 s
TTFB Time to First Byte 605 ms 605 ms 605 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 62 ms
resource load duration 33 ms
resource load delay 10 ms
time to first byte 7 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.02 MB 1.02 MB 1.02 MB
Requests 6 6 6
Third-party Weight 0 B 0 B 0 B
Third-party CPU 0 ms 0 ms 0 ms
Unused JS 30.7 kB 30.7 kB 30.7 kB
Unused CSS 30.7 kB 30.7 kB 30.7 kB

By resource type

image 852.3 kB · 1 req
font 91.9 kB · 1 req
script 41.9 kB · 1 req
stylesheet 32.2 kB · 1 req
document 2.6 kB · 1 req

Page health

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

Main thread work

other 168 ms
style layout 51 ms
parse HTML 26 ms
script parse compile 21 ms
script evaluation 17 ms
paint composite render 9 ms

Axe violations axe-core 4.13.0, full rule set

4 violating nodes across 4 rules, 203 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 1 node
  • critical image-alt — Images must have alternative text 1 node
  • serious label-title-only — Form elements should have a visible label 1 node
  • critical label — Form elements must have labels 1 node

Accessibility failures 3 of 21 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. 1 node
  • image-alt — Image elements do not have `[alt]` attributes 1 node
  • label — Form elements do not have associated labels 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:36 PM UTC 78 5.93 s 0 0 ms 1.02 MB 3/3 ±1 2,328 22.4s
Aug 21, 2026, 11:31 AM UTC TRACING_ALREADY_STARTED: An internal Chrome error occurred. Please restart Chrome and try re-running Lighthouse. 19.2s

Embed this score

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