ok.ru website review

27 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.9 s.

About 561 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.8 s faster on a phone.

cdn-vk.ru costs a phone 1.6 s of main-thread work and 4.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your mobile performance score is 40 (desktop: 36). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 5.1 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (cdn-vk.ru, Google Tag Manager and okcdn.ru and others), adding 6.0 MB and 2.4 s of main-thread time.

About 1.7 MB of JavaScript is downloaded but never used on this page.

Google Tag Manager costs a phone 291 ms of main-thread work and 323 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

okcdn.ru costs a phone 129 ms of main-thread work and 364 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Yandex CDN costs a phone 91 ms of main-thread work and 301 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

25 KiB could be saved by minifying CSS.

15 long tasks block the main thread while loading, the longest for 180 ms. During a long task the page ignores taps.

9 files are served with short cache lifetimes, so returning visitors download them again (116 KiB).

Polyfills for old browsers add 49 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

The page becomes fully interactive after 40.9 s. Good is under 3.8 s.

The first text or image appears after 5.9 s on a phone. Good is under 1.8 s.

Visually, the page fills in at 9.9 s (Speed Index). Good is under 3.4 s.

Your largest element takes 6.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Мы используем cookie-файлы, чтобы улучшить сервисы для вас.…”.

Scripts block taps and scrolling for 803 ms in total while the page loads. Good is under 200 ms.

Real visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 328 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

For real visitors the layout shifts by 0.13 (75th percentile). Good is under 0.1.

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 3.9 s to 5.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 317 ms to 333 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.2 MB in 420 requests on a phone: scripts 4.6 MB (299), other files 769 KiB (80) and stylesheets 629 KiB (18). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 1.77 g of CO₂e: 212.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 87 characters, so Google will cut it off around 60: “OK social network. Communication with friends on OK. Your meeting place with classmates”.

Your meta description is 198 characters; Google truncates after about 160, so the end of your pitch is cut.

No XML sitemap at https://ok.ru/sitemap-index-game.xml.gz, so Google discovers your pages only by following links.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 36 pages on ok.ru and 24 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://ok.ru/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

Your homepage links to https://ok.ru/null and https://ok.ru/dk, which answer with an error. Visitors hit a dead end and search engines drop them.

https://ok.ru/cookiepolicy, https://ok.ru/agreementpage and https://ok.ru/rtterms are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/ and https://ok.ru/video all use the title “OK social network. Communication with friends on OK. Your meeting pla…”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://ok.ru/cookiepolicy, https://ok.ru/agreementpage and https://ok.ru/rtterms have no meta description, so Google writes the search snippet from whatever text it finds.

https://ok.ru/gifts/catalog/all and https://ok.ru/gifts use the same meta description. A description written for each page earns more clicks.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://ok.ru/video, whose canonical is https://ok.ru/video/showcase. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://ok.ru/discovery, https://ok.ru/cookiepolicy, https://ok.ru/groups, https://ok.ru/games, https://ok.ru/agreementpage and https://ok.ru/rtterms have no <h1> headline, so visitors and search engines get no clear main topic.

https://ok.ru/games has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

https://ok.ru/help, https://ok.ru/ok and https://ok.ru/agreementpage took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage and read each the way a search engine does.

1 image failed to load on a phone, for example https://r.mradx.net/imgs/18/5b/9600c4780c869935.png.

2 of 5 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 44 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Yandex Metrica (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 21 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.