sharechat.com speed test — 20 Oct 2026

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

https://sharechat.com/

20 October 2026 at 16:18 UTC · Free test · report pt_da2ea8453b67
Grade
B
84/100
Performance86/100
Structure80/100

11 audit(s) passed, 5 need work

First byte (TTFB)557 msmeasured from this server
Fully loaded2.76 sfirst byte + slowest asset
Requests14document + assets
Page weight295.3 KBcompressed transfer
HTML document5.9 KBbr
ProtocolHTTP/3server not sent
Third-party236.4 KBother hosts

Where the first byte went

  • DNS lookup 64 ms 11%
  • TCP connect 57 ms 10%
  • Server wait 437 ms 78%

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 60% of 4,999 pages tested here557 ms against a median of 448 ms
Page weightlighter than 72% of 4,999 pages tested here295.3 KB against a median of 650.5 KB
Fully loadedslower than 79% of 4,999 pages tested here2.76 s against a median of 1.84 s
Requestssends fewer requests than 84% of 4,999 pages tested here14 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 557 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 295.3 KB over 14 request(s), which is lean. Javascript files are 49% 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.
  • 80% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
  • The largest element took 3.65 s to paint, past the 2.5 s threshold: usually a hero image that is too big or a render-blocking script in front of it.
  • Layout shift is 0.105 (good is under 0.1): something without a reserved size is loading late - an image, an ad, or a font swap.
  • The main thread was blocked for 79 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.

Mobile screenshot of sharechat.com
Mobile 390 × 844 · 161.9 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 paint3.65 sgood is under 2.5 s
Cumulative layout shift0.105under 0.1 is stable
Total blocking time79 mslong tasks during load
First contentful paint848 msfirst content on screen
Browser page weight20.63 MB206 request(s), scripts included
Failed requests10blocked or unreachable
Largest contentful paint3.65 s
Needs improvementgood under 2.5 s, poor over 4 s
Cumulative layout shift0.105
Needs improvementgood under 0.1, poor over 0.25
Total blocking time79 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 1 request
145.3 KB 49%
Images 6 requests
101.5 KB 34%
Html 2 requests
30.3 KB 10%
Css 4 requests
12.3 KB 4%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 557 ms. Of that, 437 ms was the server thinking and 121 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.

Compress text responses

high impact

1 text response(s) of 10 KB or more are sent uncompressed, and the document itself is not compressed. That is 30.2 KB of compressible text.

Fix: Turn on brotli (preferred) or gzip for text/css, javascript and text/html in the web server. This is the cheapest win available on almost any site.

Render-blocking resources

high impact

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

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

CSSsharechat.com/_app/immutable/assets/2.D5GFg2JA.css
2.21 s
CSSsharechat.com/_app/immutable/assets/drawer.CtYY5W8U.css
1.91 s
HTMLsharechat.com/
1.57 s
IMAGESsharechat.com/assets/icons/favicon-96x96.png
1.54 s
IMAGESsharechat.com/assets/icons/favicon-16x16.png
1.48 s
CSSsharechat.com/_app/immutable/assets/0.PElOMCSm.css
1.47 s
IMAGESsharechat.com/assets/icons/favicon-32x32.png
1.46 s
CSSsharechat.com/_app/immutable/assets/string-utils.Dy7…
885 ms
HTMLwww.googletagmanager.com/ns.html
667 ms
JAVASCRIPTwww.googletagmanager.com/gtag/js
634 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://sharechat.com/_app/immutable/assets/2.D5GFg2JA.csscss2002.21 s315 B
https://sharechat.com/_app/immutable/assets/drawer.CtYY5W8U.csscss2001.91 s455 B
https://sharechat.com/html2001.57 s30.2 KB
https://sharechat.com/assets/icons/favicon-96x96.pngimages2001.54 s6.6 KB
https://sharechat.com/assets/icons/favicon-16x16.pngimages2001.48 s1.4 KB
https://sharechat.com/_app/immutable/assets/0.PElOMCSm.csscss2001.47 s11.3 KB
https://sharechat.com/assets/icons/favicon-32x32.pngimages2001.46 s2.5 KB
https://sharechat.com/_app/immutable/assets/string-utils.Dy7shebE.csscss200885 ms225 B
https://www.googletagmanager.com/ns.html?id=$GTM-NRK367D 3rd partyhtml200667 ms92 B
https://www.googletagmanager.com/gtag/js?id=AW-18409256789/yAZICN69xeccENXum8pE 3rd partyjavascript200634 ms145.3 KB
https://cdn-sc-g.sharechat.com/33d5318_1c8/tools/24b337d_1789039131726_sc.webp 3rd partyimages200593 ms33.1 KB
https://cdn-sc-g.sharechat.com/33d5318_1c8/tools/38e44a7_1789038889595_sc.webp 3rd partyimages200592 ms31.9 KB
https://cdn4.sharechat.com/33d5318_1c8/tools/e7e57ba_1715942283598_sc.webp 3rd partyimages200589 ms26.0 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.