thepiratebay.org/index.html speed test — 20 Oct 2026

Measured from the wfix.shop server on 20 October 2026 at 14:32 UTC. Grade C (78/100), with the screenshots, the timings and the fixes that matter.

https://thepiratebay.org/index.html

20 October 2026 at 14:32 UTC · Free test · report pt_5439b1b6208b
Grade
C
78/100
Performance77/100
Structure80/100

12 audit(s) passed, 4 need work

First byte (TTFB)1.04 smeasured from this server
Fully loaded1.60 sfirst byte + slowest asset
Requests6document + assets
Page weight31.8 KBcompressed transfer
HTML document1.8 KBzstd
ProtocolHTTP/3cloudflare
Third-party22.0 KBother hosts

Where the first byte went

  • DNS lookup 89 ms 9%
  • TCP connect 40 ms 4%
  • Server wait 910 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 87% of 4,999 pages tested here1.04 s against a median of 448 ms
Page weightlighter than 93% of 4,999 pages tested here31.8 KB against a median of 650.5 KB
Fully loadedfaster than 64% of 4,999 pages tested here1.60 s against a median of 1.84 s
Requestssends fewer requests than 92% of 4,999 pages tested here6 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 1.04 s. Everything else waits for that number, so the server is where to start: caching, a slow query, or an overloaded host.
  • The page transfers 31.8 KB over 6 request(s), which is lean. Images files are 59% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives zstd-compressed.
  • It runs over HTTP/3, so the assets share a connection instead of opening one each.
  • 69% 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.48 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.

Mobile screenshot of thepiratebay.org
Mobile 390 × 844 · 111.1 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.48 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 paint1.48 sfirst content on screen
Browser page weight45.4 KB8 request(s), scripts included
Largest contentful paint1.48 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 1 request
18.7 KB 59%
Javascript 2 requests
8.0 KB 25%
Css 2 requests
3.3 KB 10%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 1040 ms. Of that, 910 ms was the server thinking and 129 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

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

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.

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

JAVASCRIPTunhappyweakness.com/0c/e3/13/0ce3135c177b20043c5650228182a…
555 ms
JAVASCRIPTthepiratebay.org/static/main.js
372 ms
IMAGEStorrindex.net/images/tpb.jpg
227 ms
CSStorrindex.net/static/tpb.css
221 ms
CSStorrindex.net/static/normalize.css
217 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://unhappyweakness.com/0c/e3/13/0ce3135c177b20043c5650228182ad9a.js 3rd partyjavascript405555 ms0 B
https://thepiratebay.org/static/main.jsjavascript200372 ms8.0 KB
https://torrindex.net/images/tpb.jpg 3rd partyimages200227 ms18.7 KB
https://torrindex.net/static/tpb.css 3rd partycss200221 ms1.6 KB
https://torrindex.net/static/normalize.css 3rd partycss200217 ms1.7 KB
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.