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 ·

aws.amazon.com/amplify

https://aws.amazon.com/amplify

27 91 92 92 ✗CWV 5AXE

Data from Aug 20, 2026, 4:37 PM UTC — 26h old.

Web Hosts · 1 measurement · since Aug 20, 2026 · last attempt 26h

This URL redirects to https://aws.amazon.com/amplify/.

A trailing slash only, so both forms are treated as one site rather than two — one history, measured once. Lighthouse follows the redirect, so the numbers below describe the canonical page; the only cost is an extra hop on each run.

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.

Se Hosted by Server

Core Web Vitals field data, origin-level

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

LCP 3.96 s needs-improvement
INP 314 ms needs-improvement
CLS 0 good

Scores

27
Performance
no change
91
Accessibility
no change
92
Best Practices
no change
92
SEO
no change

Lab metrics Lighthouse, mobile

Metric Current Previous Change Best Worst Trend
LCP Largest Contentful Paint 36.05 s — — 36.05 s 36.05 s
CLS Cumulative Layout Shift 0 — — 0 0
TBT Total Blocking Time 2.09 s — — 2.09 s 2.09 s
FCP First Contentful Paint 15.35 s — — 15.35 s 15.35 s
Speed Index 15.75 s — — 15.75 s 15.75 s
TTFB Time to First Byte 632 ms — — 632 ms 632 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 1.03 s
resource load delay 156 ms
resource load duration 70 ms
time to first byte 68 ms

Field data Chrome UX Report, origin-level

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

Metric p75 Rating Distribution (good / needs work / poor)
LCP CWV 3.96 s needs-improvement 50.9% good
INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run 314 ms needs-improvement 60.5% good
CLS CWV 0 good 89.7% good
FCP 3.63 s poor 39.2% good
TTFB 1.28 s needs-improvement 49.7% good

Lab vs field

Lab LCP 36.05 s · field p75 3.96 s · real users are 0.11× faster than the lab.

Field history 25 weeks

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

Week ending LCPINPCLSFCPTTFB
2026-08-15 3.91 s 311 ms 0 3.60 s 1.27 s
2026-08-08 3.84 s 304 ms 0 3.58 s 1.25 s
2026-08-01 3.81 s 300 ms 0 3.58 s 1.24 s
2026-07-25 3.79 s 297 ms 0 3.58 s 1.25 s
2026-07-18 3.82 s 292 ms 0 3.63 s 1.28 s
2026-07-11 3.85 s 292 ms 0 3.65 s 1.31 s
2026-07-04 3.88 s 293 ms 0 3.69 s 1.35 s
2026-06-27 3.90 s 291 ms 0 3.71 s 1.39 s
2026-06-20 3.90 s 293 ms 0 3.70 s 1.42 s
2026-06-13 3.88 s 289 ms 0 3.67 s 1.43 s
2026-06-06 3.78 s 280 ms 0 3.58 s 1.40 s
2026-05-30 3.67 s 274 ms 0 3.48 s 1.35 s

Page weight

Metric Current Previous Change Best Worst Trend
Page Weight 11.33 MB — — 11.33 MB 11.33 MB
Requests 153 — — 153 153
Third-party Weight 10.06 MB — — 10.06 MB 10.06 MB
Third-party CPU 755 ms — — 755 ms 755 ms
Unused JS 2.22 MB — — 2.22 MB 2.22 MB
Unused CSS 315.7 kB — — 315.7 kB 315.7 kB

By resource type

script 6.24 MB · 54 req
image 4.16 MB · 31 req
stylesheet 322.8 kB · 15 req
font 268.8 kB · 5 req
document 114.4 kB · 2 req
media 48.4 kB · 1 req
other 34.5 kB · 38 req
third party 11.19 MB · 146 req

Third parties 5 entities

10.06 MB transferred, 755 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.

awsstatic.com 8.60 MB · 444 ms CPU
aws.dev 1.46 MB · 311 ms CPU
Adobe Experience Cloud 3.1 kB · 0 ms CPU
api.aws 957 B · 0 ms CPU
clrt.ai 198 B · 0 ms CPU

Page health

Metric Current Previous Change Best Worst Trend
Main Thread Work 10.94 s — — 10.94 s 10.94 s
Long Tasks 20 — — 20 20
DOM Elements 2,391 — — 2,391 2,391
Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset 5 — — 5 5
A11y Failures 2 — — 2 2
A11y Failing Nodes 2 — — 2 2

Main thread work

script evaluation 5.29 s
other 3.11 s
style layout 856 ms
script parse compile 770 ms
paint composite render 566 ms
parse HTML 200 ms
garbage collection 152 ms

Axe violations axe-core 4.13.0, full rule set

5 violating nodes across 4 rules, 1869 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 2 nodes
  • minor aria-allowed-role — ARIA role should be appropriate for the element 1 node
  • serious link-name — Links must have discernible text 1 node
  • serious list — <ul> and <ol> must only directly contain <li>, <script> or <template> elements 1 node

Accessibility failures 2 of 30 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.

  • button-name — Buttons do not have an accessible name 1 node
  • link-name — Links do not have a discernible name 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:37 PM UTC 27 36.05 s 0 2.09 s 11.33 MB 3/3 ±1 2,435 82.9s

Embed this score

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