kaspersky.ru website review

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

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

8 third-party services load with your homepage (kaspersky.de, solta.io and Yandex Metrica and others), adding 1.2 MB and 1.6 s of main-thread time.

Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.

kaspersky.de costs a phone 705 ms of main-thread work and 502 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.

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

About 568 KiB of JavaScript is downloaded but never used on this page.

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

solta.io costs a phone 351 ms of main-thread work and 108 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.

The page has 1,575 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

About 70 KiB of CSS is downloaded but never applied on this page.

52 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 45 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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 22.3 s. Good is under 3.8 s.

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

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

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

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.

13 images have no width and height attributes, so the layout jumps as each one loads.

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

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

Your homepage downloads 2.8 MB in 214 requests on a phone: scripts 1.9 MB (77), fonts 461 KiB (8) and HTML 164 KiB (5). Under 2 MB keeps phones on slow connections fast.

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

12 images have no alt text, which hurts accessibility and image search.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

1 button has no accessible name, so screen readers announce just “button”.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Some lists contain elements other than list items, which screen readers announce wrongly.

2 frames have no title, so screen-reader users cannot tell what they contain.

1 element hidden from screen readers can still receive keyboard focus.

Your title is 79 characters, so Google will cut it off around 60: “Защитные решения кибербезопасности для дома и бизнеса | Лаборатория Касперского”.

Structured data found (Organization, WebPage and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://www.kaspersky.com/)”.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 88 pages on kaspersky.ru and 123 external pages.

https://www.kaspersky.ru/premium, https://www.kaspersky.ru/plus, https://www.kaspersky.ru/standard, https://www.kaspersky.ru/safe-kids, https://www.kaspersky.ru/office-software and https://www.kaspersky.ru/renewal-center/home and 2 others took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 50 found) and read each the way a search engine does.

10 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 (Forbidden)”.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

The homepage carries about 349 words of visible text.

Before a visitor clicks anything, the page loads 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 8 cookies, 6 of them by other companies (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 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.