www.xpaja.net speed test — 20 Oct 2026

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

https://www.xpaja.net/

20 October 2026 at 12:52 UTC · Free test · report pt_2869f7a33e80
Grade
B
81/100
Performance86/100
Structure74/100

10 audit(s) passed, 6 need work

First byte (TTFB)681 msmeasured from this server
Fully loaded1.68 sfirst byte + slowest asset
Requests26document + assets
Page weight736.4 KBcompressed transfer
HTML document18.7 KBgzip
ProtocolHTTP/3nginx
Third-party164.7 KBother hosts

Where the first byte went

  • DNS lookup 70 ms 10%
  • TCP connect 89 ms 13%
  • Server wait 523 ms 77%

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 68% of 4,999 pages tested here681 ms against a median of 448 ms
Page weightheavier than 54% of 4,999 pages tested here736.4 KB against a median of 650.3 KB
Fully loadedfaster than 59% of 4,999 pages tested here1.68 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 681 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 736.4 KB over 26 request(s). Images files are 66% 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.
  • 22% 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.33 s, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.004), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 61 ms in total, which is not enough to feel.

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.xpaja.net
Desktop 1366 × 768 · 526.7 KB · page is 2589 px tall
Mobile screenshot of www.xpaja.net
Mobile 390 × 844 · 258.8 KB · page is 5733 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.33 sgood is under 2.5 s
Cumulative layout shift0.004under 0.1 is stable
Total blocking time61 mslong tasks during load
First contentful paint1.32 sfirst content on screen
Browser page weight1.63 MB59 request(s), scripts included
Largest contentful paint1.33 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.004
Goodgood under 0.1, poor over 0.25
Total blocking time61 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 17 requests
486.3 KB 66%
Javascript 8 requests
231.4 KB 31%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 681 ms. Of that, 523 ms was the server thinking and 159 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.

Image delivery and format

high impact

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

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

Cache static assets

medium impact

1 asset(s) answer without a Cache-Control max-age, so browsers revalidate them on every visit.

Fix: Version filenames on change and serve them with a long max-age plus immutable. That is what makes a returning visitor fast.

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.

Waterfall

Slowest requests

JAVASCRIPTwww.xpaja.net/views/jscontrollers/login.js
994 ms
JAVASCRIPTwww.xpaja.net/views/jscontrollers/GeneralFunctions.js
945 ms
JAVASCRIPTwww.xpaja.net/views/hammer.js
938 ms
JAVASCRIPTwww.xpaja.net/views/plugins/xp-carousel/xp-carousel.js
934 ms
IMAGESwww.xpaja.net/views/images/default_user.png
926 ms
JAVASCRIPTwww.xpaja.net/views/bootstrap/js/bootstrap.min.js
923 ms
IMAGESwww.xpaja.net/views/images/ads/shorts/exclusive-shor…
922 ms
IMAGESwww.xpaja.net/views/images/img-lazy.png
914 ms
IMAGESwww.xpaja.net/views/images/flag/us.webp
911 ms
IMAGESwww.xpaja.net/views/images/flaglang/en.png
909 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.xpaja.net/views/jscontrollers/login.jsjavascript200994 ms5.6 KB
https://www.xpaja.net/views/jscontrollers/GeneralFunctions.js?v=0.1.3javascript200945 ms7.3 KB
https://www.xpaja.net/views/hammer.jsjavascript200938 ms6.9 KB
https://www.xpaja.net/views/plugins/xp-carousel/xp-carousel.js?v=1.1.0javascript200934 ms7.1 KB
https://www.xpaja.net/views/images/default_user.pngimages200926 ms7.0 KB
https://www.xpaja.net/views/bootstrap/js/bootstrap.min.jsjavascript200923 ms10.1 KB
https://www.xpaja.net/views/images/ads/shorts/exclusive-shorts4.pngimages200922 ms67.5 KB
https://www.xpaja.net/views/images/img-lazy.pngimages200914 ms1.3 KB
https://www.xpaja.net/views/images/flag/us.webpimages200911 ms946 B
https://www.xpaja.net/views/images/flaglang/en.pngimages200909 ms1.7 KB
https://www.xpaja.net/views/jquery-3.7.1.min.jsjavascript200908 ms29.7 KB
https://www.xpaja.net/views/categories/14.jpgimages200905 ms23.7 KB
https://www.xpaja.net/views/images/ads/gif-stickerbar.gifimages200904 ms332.4 KB
https://www.xpaja.net/views/images/network/undress.pngimages200899 ms3.1 KB
https://www.xpaja.net/views/users/2022/12/2819.jpgimages200898 ms10.2 KB
https://www.xpaja.net/views/images/network/undressly.pngimages200893 ms3.1 KB
https://www.xpaja.net/views/images/logo.pngimages200891 ms4.9 KB
https://www.xpaja.net/views/images/network/stripchat.pngimages200887 ms1.8 KB
https://www.xpaja.net/views/images/network/chaturbate.pngimages200885 ms1.9 KB
https://www.xpaja.net/views/images/flaglang/es.pngimages200882 ms1.6 KB
https://www.xpaja.net/views/images/network/tpd24px.pngimages200877 ms2.3 KB
https://www.xpaja.net/views/images/network/chatmate.pngimages200868 ms18.7 KB
https://www.xpaja.net/views/images/network/onfirex.pngimages200862 ms4.0 KB
https://www.googletagmanager.com/gtag/js?id=G-G2T3WMVMQ7 3rd partyjavascript200846 ms163.1 KB
https://cdnjs.cloudflare.com/ajax/libs/jstimezonedetect/1.0.4/jstz.min.js 3rd partyjavascript200846 ms1.6 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.