www.ptgaming.ph speed test — 20 Oct 2026

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

https://www.ptgaming.ph/

20 October 2026 at 12:51 UTC · Free test · report pt_d6b26e026baa
Grade
B
83/100
Performance84/100
Structure82/100

11 audit(s) passed, 5 need work

First byte (TTFB)800 msmeasured from this server
Fully loaded1.51 sfirst byte + slowest asset
Requests7document + assets
Page weight200.2 KBcompressed transfer
HTML document5.3 KBgzip
ProtocolHTTP/3cloudflare
Third-party152.9 KBother hosts

Where the first byte went

  • DNS lookup 51 ms 6%
  • TCP connect 42 ms 5%
  • Server wait 706 ms 88%

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 76% of 4,999 pages tested here800 ms against a median of 448 ms
Page weightlighter than 79% of 4,999 pages tested here200.2 KB against a median of 650.5 KB
Fully loadedfaster than 69% of 4,999 pages tested here1.51 s against a median of 1.84 s
Requestssends fewer requests than 91% of 4,999 pages tested here7 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 800 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 200.2 KB over 7 request(s), which is lean. Images files are 95% 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.
  • 76% 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.00 s, inside the 2.5 s Google calls good.

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.

Desktop screenshot of www.ptgaming.ph
Desktop 1366 × 768 · 4.7 KB · page is 768 px tall
Mobile screenshot of www.ptgaming.ph
Mobile 390 × 844 · 33.6 KB · page is 844 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.00 sgood is under 2.5 s
Cumulative layout shift0.000under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paint984 msfirst content on screen
Browser page weight75.4 KB17 request(s), scripts included
Failed requests1blocked or unreachable
Largest contentful paint1.00 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.000
Goodgood under 0.1, poor over 0.25
Total blocking timenone over 50 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 2 requests
190.1 KB 95%
Javascript 2 requests
3.0 KB 1%
Css 1 request
1.8 KB 1%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 800 ms. Of that, 706 ms was the server thinking and 93 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

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

Image delivery and format

medium impact

0 image(s) over 200 KB and 1 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.

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.

Waterfall

Slowest requests

JAVASCRIPTwww.ptgaming.ph/md5.7a5c1.js
711 ms
OTHERwww.ptgaming.ph/${img.src}
708 ms
CSSwww.ptgaming.ph/style-mobile.2b70d.css
693 ms
IMAGESstatic.ptgaming.ph/seo/logo/777.png
679 ms
IMAGESwww.ptgaming.ph/launchscreen1.ada12.jpg
652 ms
JAVASCRIPTwww.ptgaming.ph/auth.8e1d0.js
593 ms

Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party

RequestTypeStatusTimeSize
https://www.ptgaming.ph/md5.7a5c1.jsjavascript200711 ms2.0 KB
https://www.ptgaming.ph/${img.src}other403708 ms0 B
https://www.ptgaming.ph/style-mobile.2b70d.csscss200693 ms1.8 KB
https://static.ptgaming.ph/seo/logo/777.png 3rd partyimages200679 ms152.9 KB
https://www.ptgaming.ph/launchscreen1.ada12.jpgimages200652 ms37.2 KB
https://www.ptgaming.ph/auth.8e1d0.jsjavascript200593 ms992 B
Report this page

The page is removed when the owner agrees. Sending this removes nothing by itself.

Run this test on your own site

The same engine, free, with the screenshots and the fixes. No account needed.