www.bitrix24.tech speed test — 20 Oct 2026

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

https://www.bitrix24.tech/

20 October 2026 at 14:44 UTC · Free test · report pt_da77e4845ce4
Grade
B
87/100
Performance87/100
Structure88/100

12 audit(s) passed, 4 need work

First byte (TTFB)642 msmeasured from this server
Fully loaded1.71 sfirst byte + slowest asset
Requests10document + assets
Page weight339.0 KBcompressed transfer
HTML document8.4 KBbr
ProtocolHTTP/2QRATOR

Where the first byte went

  • DNS lookup 228 ms 36%
  • TCP connect 59 ms 9%
  • Server wait 355 ms 55%

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 66% of 4,999 pages tested here642 ms against a median of 448 ms
Page weightlighter than 69% of 4,999 pages tested here339.0 KB against a median of 650.5 KB
Fully loadedfaster than 57% of 4,999 pages tested here1.71 s against a median of 1.84 s
Requestssends fewer requests than 88% of 4,999 pages tested here10 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 642 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 339.0 KB over 10 request(s), which is lean. Images files are 81% of it, so resize and recompress the largest images before anything else.
  • The HTML itself arrives br-compressed.
  • It runs over HTTP/2, so the assets share a connection instead of opening one each.
  • The largest element painted at 1.98 s, inside the 2.5 s Google calls good.
  • Layout stayed still (CLS 0.029), so nothing jumps under the reader's cursor.

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 paint1.98 sgood is under 2.5 s
Cumulative layout shift0.029under 0.1 is stable
Total blocking timenone over 50 mslong tasks during load
First contentful paint1.08 sfirst content on screen
Browser page weight168.9 KB5 request(s), scripts included
Largest contentful paint1.98 s
Goodgood under 2.5 s, poor over 4 s
Cumulative layout shift0.029
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

Images 7 requests
274.9 KB 81%
Fonts 2 requests
55.7 KB 16%

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

Top issues

Server response time (TTFB)

high impact

The first byte arrived after 642 ms. Of that, 355 ms was the server thinking and 287 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.

Cache static assets

medium impact

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

Avoid extra redirects

medium impact

1 redirect hop(s) before the page load started, each one a full round trip before the first byte.

Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.

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

IMAGESwww.bitrix24.tech/assets/img/heart-3d.avif
1.07 s
IMAGESwww.bitrix24.tech/assets/img/cursor-3d.avif
1.07 s
FONTSwww.bitrix24.tech/assets/fonts/montserrat-var-latin.woff2
1.06 s
IMAGESwww.bitrix24.tech/favicon.ico
1.04 s
FONTSwww.bitrix24.tech/assets/fonts/montserrat-var-cyrillic.w…
1.03 s
IMAGESwww.bitrix24.tech/favicon.svg
976 ms
IMAGESwww.bitrix24.tech/apple-touch-icon.png
766 ms
IMAGESwww.bitrix24.tech/assets/img/heart-3d.webp
688 ms
IMAGESwww.bitrix24.tech/assets/img/cursor-3d.webp
688 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://www.bitrix24.tech/assets/img/heart-3d.avifimages2001.07 s79.3 KB
https://www.bitrix24.tech/assets/img/cursor-3d.avifimages2001.07 s25.5 KB
https://www.bitrix24.tech/assets/fonts/montserrat-var-latin.woff2fonts2001.06 s34.7 KB
https://www.bitrix24.tech/favicon.icoimages2001.04 s5.0 KB
https://www.bitrix24.tech/assets/fonts/montserrat-var-cyrillic.woff2fonts2001.03 s21.0 KB
https://www.bitrix24.tech/favicon.svgimages200976 ms460 B
https://www.bitrix24.tech/apple-touch-icon.pngimages200766 ms14.1 KB
https://www.bitrix24.tech/assets/img/heart-3d.webpimages200688 ms112.1 KB
https://www.bitrix24.tech/assets/img/cursor-3d.webpimages200688 ms38.5 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.