aws.amazon.com speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 13:37 UTC. Grade D (69/100), with the screenshots, the timings and the fixes that matter.

https://aws.amazon.com/

20 October 2026 at 13:37 UTC · Free test · report pt_979fb77f71f0

Re-test this page Test your own site

Grade

69/100

Performance71/100

Structure67/100

11 audit(s) passed, 5 need work

First byte (TTFB)363 msmeasured from this server

Fully loaded1.41 sfirst byte + slowest asset

Requests26document + assets

Page weight21.51 MBcompressed transfer

HTML document69.7 KBgzip

ProtocolHTTP/3Server

Third-party21.45 MBother hosts

Where the first byte went

DNS lookup 69 ms 19%
TCP connect 58 ms 16%
Server wait 236 ms 65%

Measured on the connection that fetched the HTML. Every other request on the page waits for the end of this bar before it can start.

How this page compares

First bytefaster than 62% of 4,999 pages tested here363 ms against a median of 449 ms

Page weightheavier than 99% of 4,999 pages tested here21.51 MB against a median of 650.3 KB

Fully loadedfaster than 77% of 4,999 pages tested here1.41 s against a median of 1.84 s

Requestssends more requests than 100% of 4,999 pages tested here26 against a median of 26

Every report published here is in this comparison, so it is a reference population of pages tested from one server - not a benchmark of the whole web.

What these numbers mean

The first byte arrived in 363 ms. That is workable, and the cheapest win left is caching or a warmer connection.
The page transfers 21.51 MB over 26 request(s). Images files are 100% of it, so resize and recompress the largest images before anything else.
The HTML itself arrives gzip-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
100% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
The largest element took 3.66 s to paint, past the 2.5 s threshold: usually a hero image that is too big or a render-blocking script in front of it.
The main thread was blocked for 1.17 s, so taps and scrolling wait while scripts run.

Fix first: Image delivery and format - Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

Read on one shared server, not a visitor's phone: use it to compare pages against each other, not as a promise about every connection. We fix what these tests find.

Screenshot

What the page looks like

Loaded in headless Chromium on this server. Click an image to open it full size.

Mobile screenshot of aws.amazon.com — **Mobile** 390 × 844 · 14.7 KB · page is 6000 px tall

Browser render

The same URL loaded in a real browser, so these are the readings curl cannot produce. The grade above is still built from the server measurements.

Largest contentful paint3.66 sgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking time1.17 slong tasks during load

First contentful paint1.18 sfirst content on screen

Browser page weight29.95 MB138 request(s), scripts included

Failed requests3blocked or unreachable

Largest contentful paint3.66 s

Needs improvementgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

Goodgood under 0.1, poor over 0.25

Total blocking time1.17 s

Poorgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 24 requests

21.43 MB 100%

Javascript 1 request

17.0 KB 0%

Transfer size, compressed as sent. 26 request(s) in total, 21.51 MB across all of them.

Top issues

Image delivery and format

high impact

19 image(s) over 200 KB and 21 large image(s) still served as JPEG or PNG.

Fix: Serve WebP or AVIF with a JPEG fallback, size images to the space they occupy, and lazy-load anything below the fold. Images are usually more than half of a slow page.

Render-blocking resources

high impact

14 render-blocking resource(s) in the document head (3 script(s), 11 stylesheet(s)). The page cannot paint until each one arrives.

Fix: Add defer or async to scripts that do not change the first paint, inline the critical CSS, and load the rest with media="print" plus an onload swap.

Total page weight

high impact

The page transfers 21.51 MB across 26 request(s), with the document itself at 69.7 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

Third-party weight

medium impact

2 third-party host(s) serve 21.45 MB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.

Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.

Avoid extra redirects

medium impact

2 redirect hop(s) before the page load started, each one a full round trip before the first byte.

Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.