shopee.ph speed test — 20 Oct 2026

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

https://shopee.ph/

20 October 2026 at 12:42 UTC · Free test · report pt_c070db81ae19

Re-test this page Test your own site

Grade

80/100

Performance78/100

Structure83/100

13 audit(s) passed, 3 need work

First byte (TTFB)949 msmeasured from this server

Fully loaded1.93 sfirst byte + slowest asset

Requests26document + assets

Page weight410.6 KBcompressed transfer

HTML document28.6 KBgzip

ProtocolHTTP/3SGW

Third-party382.0 KBother hosts

Where the first byte went

DNS lookup 46 ms 5%
TCP connect 218 ms 23%
Server wait 685 ms 72%

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 byteslower than 83% of 4,999 pages tested here949 ms against a median of 448 ms

Page weightlighter than 64% of 4,999 pages tested here410.6 KB against a median of 650.5 KB

Fully loadedslower than 54% of 4,999 pages tested here1.93 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 took 949 ms. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
The page transfers 410.6 KB over 26 request(s). Javascript files are 92% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
The HTML itself arrives gzip-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
93% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
The largest element took 4.20 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.
Layout shift is 0.115 (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 2.47 s, so taps and scrolling wait while scripts run.

Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

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 shopee.ph — **Mobile** 390 × 844 · 6.5 KB · page is 2684 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 paint4.20 sgood is under 2.5 s

Cumulative layout shift0.115under 0.1 is stable

Total blocking time2.47 slong tasks during load

First contentful paint3.00 sfirst content on screen

Browser page weight3.55 MB232 request(s), scripts included

Failed requests8blocked or unreachable

Largest contentful paint4.20 s

Poorgood under 2.5 s, poor over 4 s

Cumulative layout shift0.115

Needs improvementgood under 0.1, poor over 0.25

Total blocking time2.47 s

Poorgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 23 requests

376.9 KB 92%

Css 1 request

5.1 KB 1%

Html 1 request

92 B 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 949 ms. Of that, 685 ms was the server thinking and 264 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.

Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.

Render-blocking resources

high impact

5 render-blocking resource(s) in the document head (4 script(s), 1 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.

Third-party weight

medium impact

2 third-party host(s) serve 382.0 KB 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.