www.americanas.com.br speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 16:07 UTC. Grade B (86/100), with the screenshots, the timings and the fixes that matter.

https://www.americanas.com.br/

20 October 2026 at 16:07 UTC · Free test · report pt_9e5c143b91df

Re-test this page Test your own site

Grade

86/100

Performance86/100

Structure86/100

13 audit(s) passed, 3 need work

First byte (TTFB)148 msmeasured from this server

Fully loaded5.20 sfirst byte + slowest asset

Requests26document + assets

Page weight136.2 KBcompressed transfer

HTML document34.3 KBgzip

ProtocolHTTP/3CloudFront

Third-party88.9 KBother hosts

Where the first byte went

DNS lookup 85 ms 57%
TCP connect 6 ms 4%
Server wait 56 ms 38%

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 98% of 4,999 pages tested here148 ms against a median of 449 ms

Page weightlighter than 84% of 4,999 pages tested here136.2 KB against a median of 650.5 KB

Fully loadedslower than 90% of 4,999 pages tested here5.20 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 server answered in 148 ms, which is fast: almost all of the wait is the page itself, not the host.
The page transfers 136.2 KB over 26 request(s). Images files are 75% 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.
65% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
The largest element painted at 1.24 s, inside the 2.5 s Google calls good.
Layout shift is 0.279 (good is under 0.1): something without a reserved size is loading late - an image, an ad, or a font swap.
The main thread was blocked for 375 ms, so taps and scrolling wait while scripts run.

Fix first: Render-blocking resources - 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.

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 www.americanas.com.br — **Mobile** 390 × 844 · 103.2 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 paint1.24 sgood is under 2.5 s

Cumulative layout shift0.279under 0.1 is stable

Total blocking time375 mslong tasks during load

First contentful paint780 msfirst content on screen

Browser page weight3.85 MB295 request(s), scripts included

Failed requests6blocked or unreachable

Largest contentful paint1.24 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.279

Poorgood under 0.1, poor over 0.25

Total blocking time375 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 25 requests

101.9 KB 75%

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

Top issues

Render-blocking resources

high impact

12 render-blocking resource(s) in the document head (3 script(s), 9 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.

Avoid extra redirects

medium impact

1 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.

Strict-Transport-Security

low impact

HSTS is not set, so the first visit on a hostile network can still be downgraded to HTTP.

Fix: Send Strict-Transport-Security with a max-age of at least six months. Add includeSubDomains once every subdomain is HTTPS.