www.jiosaavn.com speed test — 20 Oct 2026

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

https://www.jiosaavn.com/

20 October 2026 at 14:26 UTC · Free test · report pt_ca0be5858165

Re-test this page Test your own site

Grade

66/100

Performance61/100

Structure73/100

10 audit(s) passed, 6 need work

First byte (TTFB)1.49 smeasured from this server

Fully loaded2.60 sfirst byte + slowest asset

Requests26document + assets

Page weight853.5 KBcompressed transfer

HTML document40.2 KBgzip

ProtocolHTTP/3server not sent

Third-party813.4 KBother hosts

Where the first byte went

DNS lookup 87 ms 6%
TCP connect 33 ms 2%
Server wait 1.37 s 92%

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 95% of 4,999 pages tested here1.49 s against a median of 448 ms

Page weightheavier than 58% of 4,999 pages tested here853.5 KB against a median of 650.3 KB

Fully loadedslower than 76% of 4,999 pages tested here2.60 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 1.49 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 853.5 KB over 26 request(s). Javascript files are 95% 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.
95% 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 248 ms, 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.

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 paint248 msgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking timenone over 50 mslong tasks during load

First contentful paint248 msfirst content on screen

Browser page weight562 B1 request(s), scripts included

Largest contentful paint248 ms

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

Javascript 24 requests

813.3 KB 95%

Images 1 request

43 B 0%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 1492 ms. Of that, 1372 ms was the server thinking and 120 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.

Cache static assets

medium impact

2 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.

Third-party weight

medium impact

3 third-party host(s) serve 813.4 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: shaka-player.js (250.0 KB)

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