passport.yandex-team.ru/pwl/auth?retpath=https%3A%2F%2Fyandex-team.ru%2F speed test — 20 Oct 2026

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

https://passport.yandex-team.ru/pwl/auth?retpath=https%3A%2F%2Fyandex-team.ru%2F

20 October 2026 at 14:39 UTC · Free test · report pt_72bbbcce1721

Re-test this page Test your own site

Grade

72/100

Performance70/100

Structure74/100

11 audit(s) passed, 5 need work

First byte (TTFB)1.18 smeasured from this server

Fully loaded2.53 sfirst byte + slowest asset

Requests19document + assets

Page weight497.8 KBcompressed transfer

HTML document8.2 KBgzip

ProtocolHTTP/2server not sent

Third-party415.9 KBother hosts

Where the first byte went

DNS lookup 249 ms 21%
TCP connect 193 ms 16%
Server wait 736 ms 62%

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

Page weightlighter than 58% of 4,999 pages tested here497.8 KB against a median of 650.5 KB

Fully loadedslower than 74% of 4,999 pages tested here2.53 s against a median of 1.84 s

Requestssends fewer requests than 80% of 4,999 pages tested here19 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.18 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 497.8 KB over 19 request(s). Fonts files are 47% of it, so subset the fonts and stop preloading the weights you do not render.
The HTML itself arrives gzip-compressed.
It runs over HTTP/2, so the assets share a connection instead of opening one each.
84% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
The largest element took 5.27 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.
The main thread was blocked for 431 ms, so taps and scrolling wait while scripts run.

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 passport.yandex-team.ru — **Mobile** 390 × 844 · 10.7 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 paint5.27 sgood is under 2.5 s

Cumulative layout shift0.000under 0.1 is stable

Total blocking time431 mslong tasks during load

First contentful paint1.94 sfirst content on screen

Browser page weight4.18 MB53 request(s), scripts included

Largest contentful paint5.27 s

Poorgood under 2.5 s, poor over 4 s

Cumulative layout shift0.000

Goodgood under 0.1, poor over 0.25

Total blocking time431 ms

Needs improvementgood under 200 ms, poor over 600 ms

Page weight by type

What the page is made of

Fonts 4 requests

234.2 KB 47%

Other 4 requests

173.8 KB 35%

Html 9 requests

73.8 KB 15%

Css 1 request

7.8 KB 2%

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

Top issues

Server response time (TTFB)

high impact

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

9 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

1 third-party host(s) serve 415.9 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.

Avoid extra redirects

medium impact

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