speedlify2

Lighthouse lab metrics, Axe, and Chrome UX Report field data for a list of sites recorded and compared over time.

Measurement runs Embed a score

emberjs.com

https://emberjs.com/

71 93 100 100 AXE CWV

Data from Aug 27, 2026, 6:58 PM UTC old

Overall #1,250 Developer Tooling #39 Frameworks and Libraries #9 · 1 measurement · since Aug 27, 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

Core Web Vitals field data, url-level

Real Chrome users, 28-day window (2026-07-29 → 2026-08-25). This is what Google measures you on.

LCP 1.82 s good
INP 112 ms good
CLS 0 good

Scores

71
Performance
no change
93
Accessibility
no change
100
Best Practices
no change
100
SEO
no change

Filmstrip Lighthouse, mobile

How the page drew during the measured load, at 8 points across 3.00 s.

  1. 375 ms
  2. 750 ms
  3. 1.13 s
  4. 1.50 s
  5. 1.88 s
  6. 2.25 s
  7. 2.63 s
  8. 3.00 s

Without JavaScript

The same load, photographed twice at 412×823: once with scripts disabled, once as rendered.

Scripts disabled
As rendered

0% of pixels differ — they are identical. A shifted layout counts as difference, so a <noscript> banner alone can account for a large figure.

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 6.18 s 6.18 s 6.18 s
CLS Cumulative Layout Shift 0 0 0
TBT Total Blocking Time 324 ms 324 ms 324 ms
FCP First Contentful Paint 1.05 s 1.05 s 1.05 s
Speed Index 1.05 s 1.05 s 1.05 s
TTFB Time to First Byte 604 ms 604 ms 604 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 6.18 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 160 ms
resource load delay 93 ms
time to first byte 13 ms
resource load duration 5 ms

Field data Chrome UX Report, url-level

Real Chrome users, 28-day trailing window (2026-07-29 → 2026-08-25). This is what Google measures you on.

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 1.82 s good 87.4% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 112 ms good 94.1% good
CLS CWV 0 good 98.5% good
FCP 1.60 s good 80.8% good
TTFB 842 ms needs-improvement 72.6% good

Lab vs field LCP

Lab 6.18 s
Field p75 1.82 s

The lab LCP is 3.39× the field p75 — real users likely have above-average hardware or network connectivity.

Field history 25 weeks

Weekly p75 from the CrUX History API, backfilled in a single request.

Week ending LCPINPCLSFCPTTFB
2026-08-22 1.91 s 114 ms 0 1.59 s 853 ms
2026-08-15 1.91 s 113 ms 0 1.57 s 853 ms
2026-08-08 1.91 s 121 ms 0 1.59 s 857 ms
2026-08-01 1.84 s 106 ms 0 1.50 s 769 ms
2026-07-25 1.75 s 99 ms 0 1.48 s 666 ms
2026-07-18 1.63 s 99 ms 0 1.46 s 627 ms
2026-07-11 1.79 s 101 ms 0 1.56 s 683 ms
2026-07-04 1.76 s 102 ms 0 1.55 s 699 ms
2026-06-27 1.89 s 119 ms 0 1.61 s 820 ms
2026-06-20 1.76 s 115 ms 0 1.51 s 820 ms
2026-06-13 1.73 s 111 ms 0 1.45 s 817 ms
2026-06-06 1.75 s 109 ms 0 1.47 s 820 ms

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 1.19 MB 1.19 MB 1.19 MB
Requests 35 35 35
Third-party Weight 180 kB 180 kB 180 kB
Third-party CPU 43 ms 43 ms 43 ms
Unused JS 332 kB 332 kB 332 kB
Unused CSS 0 B 0 B 0 B

By resource type

script 585 kB · 11 req
image 333 kB · 15 req
font 225 kB · 1 req
document 35.7 kB · 1 req
stylesheet 13.1 kB · 2 req
other 1.4 kB · 3 req
third party 180 kB · 4 req

Third parties 2 entities

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

Google Tag Manager 158 kB · 30 ms CPU
Google Analytics 21.6 kB · 13 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 1.25 s 1.25 s 1.25 s
Long Tasks 5 5 5
DOM Elements 529 529 529
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 6 6 6

Main thread work

script evaluation 512 ms
other 284 ms
style layout 212 ms
script parse compile 156 ms
paint composite render 49 ms
parse HTML 33 ms

Axe violations axe-core 4.13.0, full rule set

6 violating nodes across 2 rules, 939 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 3 nodes
  • serious link-in-text-block — Links must be distinguishable without relying on color 3 nodes

Accessibility failures 2 of 27 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. 3 nodes
  • link-in-text-block — Links rely on color to be distinguishable. 3 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 27, 2026, 6:58 PM UTC 71 6.18 s 0 324 ms 1.19 MB 3/3 ±16 3,071 30.1s

Embed this score

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