1c.ru speed test — 20 Oct 2026

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

https://1c.ru/

20 October 2026 at 12:57 UTC · Free test · report pt_eaa4a8669e6a

Re-test this page Test your own site

Grade

85/100

Performance85/100

Structure85/100

13 audit(s) passed, 3 need work

First byte (TTFB)686 msmeasured from this server

Fully loaded2.10 sfirst byte + slowest asset

Requests26document + assets

Page weight66.4 KBcompressed transfer

HTML document17.6 KBgzip

ProtocolHTTP/3ddos-guard

Third-party6.6 KBother hosts

Where the first byte went

DNS lookup 32 ms 5%
TCP connect 152 ms 22%
Server wait 501 ms 73%

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 69% of 4,999 pages tested here686 ms against a median of 448 ms

Page weightlighter than 90% of 4,999 pages tested here66.4 KB against a median of 650.5 KB

Fully loadedslower than 61% of 4,999 pages tested here2.10 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 686 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 66.4 KB over 26 request(s). Javascript files are 68% 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.
The largest element painted at 2.13 s, inside the 2.5 s Google calls good.
The main thread was blocked for 9 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 1c.ru — **Mobile** 390 × 844 · 84.8 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 paint2.13 sgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking time9 mslong tasks during load

First contentful paint1.84 sfirst content on screen

Browser page weight1.48 MB61 request(s), scripts included

Largest contentful paint2.13 s

Goodgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

Goodgood under 0.1, poor over 0.25

Total blocking time9 ms

Goodgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Javascript 3 requests

45.2 KB 68%

Html 19 requests

2.5 KB 4%

Images 2 requests

1.2 KB 2%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 686 ms. Of that, 501 ms was the server thinking and 184 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 (3 script(s), 1 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

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

Waterfall

Slowest requests

IMAGESstatic.1c.ru/images/logo_1C_small.svg

1.42 s

JAVASCRIPTstatic.1c.ru/lib/build/js/main.min.js

1.27 s

OTHERmc.yandex.ru/watch/22936357

1.27 s