aws.amazon.com/amplify
https://aws.amazon.com/amplify
Data from Aug 22, 2026, 9:24 PM UTC 24h old
Web Hosts #11 · 3 measurements · since Aug 20, 2026
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.
Core Web Vitals field data, origin-level
Real Chrome users, 28-day window (2026-07-24 → 2026-08-20). This is what Google measures you on.
Scores
Filmstrip Lighthouse, mobile
How the page drew during the measured load, at 8 points across 5.63 s.
-
704 ms
-
1.41 s
-
2.11 s
-
2.82 s
-
3.52 s
-
4.23 s
-
4.93 s
-
5.63 s
Lab metrics Lighthouse, mobile
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| LCP Largest Contentful Paint | 45.87 s | 35.78 s | ↑ +10086 ms (+28.2%) significant | 35.78 s | 45.87 s | |
| CLS Cumulative Layout Shift | 0 | 0 | → no change | 0 | 0 | |
| TBT Total Blocking Time | 1.46 s | 1.89 s | ↓ -436 ms (-23%) | 1.46 s | 2.09 s | |
| FCP First Contentful Paint | 16.32 s | 14.79 s | ↑ +1528 ms (+10.3%) | 14.79 s | 16.32 s | |
| Speed Index | 20.86 s | 17.37 s | ↑ +3492 ms (+20.1%) | 15.75 s | 20.86 s | |
| TTFB Time to First Byte | 688 ms | 649 ms | ↑ +39 ms (+6%) | 632 ms | 688 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 45.87 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.
Field data Chrome UX Report, origin-level
Real Chrome users, 28-day trailing window (2026-07-24 → 2026-08-20). This is what Google measures you on.
| Metric | p75 | Rating | Distribution (good / needs work / poor) |
|---|---|---|---|
| LCP CWV | 3.98 s | needs-improvement | 50.9% good |
| INP CWV Interaction to Next Paint — field only, Lighthouse cannot measure this in a lab run | 316 ms | needs-improvement | 60.6% good |
| CLS CWV | 0 | good | 89.3% good |
| FCP | 3.65 s | poor | 38.6% good |
| TTFB | 1.29 s | needs-improvement | 49.2% good |
Lab vs field
Lab LCP 45.87 s · field p75 3.98 s · real users are 0.09× faster than the lab.
Field history 25 weeks
Weekly p75 from the CrUX History API, backfilled in a single request.
| Week ending | LCP | INP | CLS | FCP | TTFB |
|---|---|---|---|---|---|
| 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.59 MB | 11.45 MB | ↑ +134.5 kB (+1.2%) | 11.33 MB | 11.59 MB | |
| Requests | 155 | 156 | ↓ -1 (-0.6%) | 153 | 156 | |
| Third-party Weight | 10.33 MB | 10.18 MB | ↑ +145.6 kB (+1.5%) | 10.06 MB | 10.33 MB | |
| Third-party CPU | 573 ms | 684 ms | ↓ -111 ms (-16.3%) | 573 ms | 755 ms | |
| Unused JS | 2.35 MB | 2.22 MB | ↑ +127.6 kB (+5.9%) significant | 2.22 MB | 2.35 MB | |
| Unused CSS | 339 kB | 339 kB | ↓ -252 B (-0.1%) | 316 kB | 339 kB |
By resource type
Third parties 5 entities
10.33 MB transferred, 573 ms of main thread time. This is the number most likely to regress without anyone on your team shipping anything.
Page health
| Metric | Current | Previous | Change | Best | Worst | Trend |
|---|---|---|---|---|---|---|
| Main Thread Work | 8.91 s | 10.09 s | ↓ -1174 ms (-11.6%) | 8.91 s | 10.94 s | |
| Long Tasks | 20 | 20 | → no change | 20 | 20 | |
| DOM Elements | 2,378 | 2,391 | ↓ -13 (-0.5%) | 2,378 | 2,391 | |
| Axe Violations Violating nodes from a full axe run — stricter than Lighthouse's subset | 5 | 5 | → no change | 5 | 5 | |
| A11y Failures | 2 | 2 | → no change | 2 | 2 | |
| A11y Failing Nodes | 2 | 2 | → no change | 2 | 2 |
Main thread work
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 29 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.
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 | Perf | LCP | CLS | TBT | Weight | Runs | Spread | Bench | Took |
|---|---|---|---|---|---|---|---|---|---|
| Aug 22, 2026, 9:24 PM UTC | 30 | 45.87 s | 0 | 1.46 s | 11.59 MB | 3/3 | ±2 | 2,675 | 74.6s |
| Aug 21, 2026, 8:33 PM UTC | 28 | 35.78 s | 0 | 1.89 s | 11.45 MB | 3/3 | ±3 | 2,449 | 79.7s |
| 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 speedlify2-score.js component code into your site!
<speedlify2-score speedlify-url="https://www.speedlify.dev/" url="https://aws.amazon.com/amplify"></speedlify2-score>