stocrm.ru speed test — 20 Oct 2026

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

https://stocrm.ru/

20 October 2026 at 15:00 UTC · Free test · report pt_e39333b2b810
Grade
C
73/100
Performance74/100
Structure71/100

11 audit(s) passed, 5 need work

First byte (TTFB)949 msmeasured from this server
Fully loaded3.07 sfirst byte + slowest asset
Requests26document + assets
Page weight921.6 KBcompressed transfer
HTML document33.8 KBgzip
ProtocolHTTP/3nginx/1.31.3
Third-party43 Bother hosts

Where the first byte went

  • DNS lookup 230 ms 24%
  • TCP connect 208 ms 22%
  • Server wait 510 ms 54%

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 83% of 4,999 pages tested here949 ms against a median of 448 ms
Page weightheavier than 60% of 4,999 pages tested here921.6 KB against a median of 650.3 KB
Fully loadedslower than 83% of 4,999 pages tested here3.07 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 949 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 921.6 KB over 26 request(s). Images files are 96% 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.
  • The largest element took 4.24 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 stayed still (CLS 0.001), so nothing jumps under the reader's cursor.
  • The main thread was blocked for 116 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 stocrm.ru
Mobile 390 × 844 · 120.6 KB · page is 6000 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 paint4.24 sgood is under 2.5 s
Cumulative layout shift0.001under 0.1 is stable
Total blocking time116 mslong tasks during load
First contentful paint1.91 sfirst content on screen
Browser page weight2.70 MB66 request(s), scripts included
Largest contentful paint4.24 s
Poorgood under 2.5 s, poor over 4 s
Cumulative layout shift0.001
Goodgood under 0.1, poor over 0.25
Total blocking time116 ms
Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Images 21 requests
887.8 KB 96%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 949 ms. Of that, 510 ms was the server thinking and 438 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 1 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.

Total page weight

medium impact

The page transfers 921.6 KB across 26 request(s), with the document itself at 33.8 KB.

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

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

IMAGESstocrm.ru/img/badges/b7.webp
2.12 s
IMAGESstocrm.ru/img/logos/АвтоРусь.webp
1.84 s
IMAGEStop-fwz1.mail.ru/tracker
1.51 s
OTHERmc.yandex.ru/watch/49528453
1.48 s
IMAGESstocrm.ru/img/logos/CallTouch.webp
1.46 s
IMAGESstocrm.ru/img/logos/Билайн.webp
1.41 s
OTHERmc.yandex.ru/pixel/966991329191516669
1.41 s
IMAGESstocrm.ru/img/logos/ПартКом.webp
1.40 s
IMAGESstocrm.ru/img/logos/JivoSite.webp
1.39 s
IMAGESstocrm.ru/img/logos/ABCP.webp
1.36 s

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://stocrm.ru/img/badges/b7.webpimages2002.12 s1004 B
https://stocrm.ru/img/logos/АвтоРусь.webpimages2001.84 s2.6 KB
https://top-fwz1.mail.ru/tracker?id=3162273;e=RG%3A/trg-pixel-8418007-1582031409332;_=1 3rd partyimages2001.51 s43 B
https://mc.yandex.ru/watch/49528453 3rd partyother3021.48 s0 B
https://stocrm.ru/img/logos/CallTouch.webpimages2001.46 s3.7 KB
https://stocrm.ru/img/logos/Билайн.webpimages2001.41 s2.0 KB
https://mc.yandex.ru/pixel/966991329191516669?rnd=1 3rd partyother3021.41 s0 B
https://stocrm.ru/img/logos/ПартКом.webpimages2001.40 s3.0 KB
https://stocrm.ru/img/logos/JivoSite.webpimages2001.39 s3.1 KB
https://stocrm.ru/img/logos/ABCP.webpimages2001.36 s3.0 KB
https://stocrm.ru/img/logos/ZZap.webpimages2001.31 s2.2 KB
https://stocrm.ru/img/logos/Мегафон.webpimages2001.30 s3.0 KB
https://stocrm.ru/img/logos/Qwep.webpimages2001.30 s4.2 KB
https://stocrm.ru/img/badges/b3.webpimages2001.30 s914 B
https://stocrm.ru/img/hero-stocrm-transparent.pngimages2001.30 s845.8 KB
https://stocrm.ru/img/logos/VINPIN.webpimages2001.30 s2.5 KB
https://stocrm.ru/img/badges/b4.webpimages2001.30 s978 B
https://stocrm.ru/img/logos/LIFE_PAY.webpimages2001.29 s1.7 KB
https://stocrm.ru/img/logos/Marquiz.webpimages2001.28 s4.6 KB
https://stocrm.ru/img/badges/b6.webpimages2001.28 s740 B
https://stocrm.ru/img/badges/b2.webpimages2001.28 s706 B
https://stocrm.ru/img/badges/b1.webpimages2001.27 s1.1 KB
https://stocrm.ru/img/badges/b5.webpimages2001.26 s870 B
https://vk.com/rtrg?p=VK-RTRG-456790-h6sIT 3rd partyother4181.25 s0 B
https://top-fwz1.mail.ru/counter?id=3405686;js=na 3rd partyother3021.25 s0 B
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.