fansly.com speed test — 20 Oct 2026

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

https://fansly.com/

20 October 2026 at 14:29 UTC · Free test · report pt_57165ce5331b

Re-test this page Test your own site

Grade

86/100

Performance88/100

Structure83/100

12 audit(s) passed, 4 need work

First byte (TTFB)192 msmeasured from this server

Fully loaded1.58 sfirst byte + slowest asset

Requests26document + assets

Page weight2.26 MBcompressed transfer

HTML document6.5 KBbr

ProtocolHTTP/3Fansly CDN

Third-party322.2 KBother hosts

Where the first byte went

DNS lookup 53 ms 28%
TCP connect 33 ms 17%
Server wait 107 ms 56%

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

Page weightheavier than 84% of 4,999 pages tested here2.26 MB against a median of 650.3 KB

Fully loadedfaster than 65% of 4,999 pages tested here1.58 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 192 ms, which is fast: almost all of the wait is the page itself, not the host.
The page transfers 2.26 MB over 26 request(s). Javascript files are 82% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
The HTML itself arrives br-compressed.
It runs over HTTP/3, so the assets share a connection instead of opening one each.
The largest element painted at 1.74 s, inside the 2.5 s Google calls good.
Layout stayed still (CLS 0.032), so nothing jumps under the reader's cursor.
The main thread was blocked for 570 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.

Desktop screenshot of fansly.com — **Desktop** 1366 × 768 · 151.0 KB · page is 768 px tall

Mobile screenshot of fansly.com — **Mobile** 390 × 844 · 59.5 KB · page is 1211 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.74 sgood is under 2.5 s

Cumulative layout shift0.032under 0.1 is stable

Total blocking time570 mslong tasks during load

First contentful paint476 msfirst content on screen

Browser page weight2.45 MB73 request(s), scripts included

Failed requests3blocked or unreachable

Largest contentful paint1.74 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.032

Goodgood under 0.1, poor over 0.25

Total blocking time570 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 5 requests

1.85 MB 82%

Fonts 10 requests

281.1 KB 12%

Css 2 requests

68.8 KB 3%

Images 6 requests

59.1 KB 3%

Other 2 requests

680 B 0%

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

Top issues

Render-blocking resources

high impact

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

Total page weight

high impact

The page transfers 2.26 MB across 26 request(s), with the document itself at 6.5 KB.

Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.

Third-party weight

medium impact

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

JavaScript weight

medium impact

1 JavaScript file(s) over 200 KB: main.80ebad3c03385332.js (1.68 MB)

Fix: Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.