primezone.ru website review

About 675 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.

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

Google CDN costs a phone 1.2 s of main-thread work and 1.1 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 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

25 files are served with short cache lifetimes, so returning visitors download them again (22.7 MB).

5 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and jQuery CDN and others), adding 1.5 MB and 1.6 s of main-thread time.

7 images could be 747 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

53 KiB could be saved by minifying JavaScript.

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

Other Google APIs/SDKs costs a phone 317 ms of main-thread work and 60 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.

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

9 KiB could be saved by minifying CSS.

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.

Your largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Мы Представляем Программы Корпоративных Привилегий и Корпор…”.

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

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

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

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

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

21 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-31, real Chrome visitors' tap response (inp) went from 120 ms to 127 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 24.9 MB in 50 requests on a phone: media 21.8 MB (3), scripts 1.2 MB (10) and images 881 KiB (20). Under 2 MB keeps phones on slow connections fast.

7 images are downloaded at several times the size a phone draws them, for example map-mobile.png at 1,202 px wide, shown at 390 px. Resized copies would save about 620 KiB.

7 images (789 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

7 images further down the page (789 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

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

18 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 9 characters: “PrimeZone”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 3 <h1> headlines (“Мы Представляем Программы Корпоративных Привилеги…”, “Благополучие сотрудников является нашим основным …” and “Наши глобальные лучшие практики в вашем распоряже…”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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

No XML sitemap at https://primezone.ru/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at primezone.ru/robots.txt, the first file search crawlers ask for.

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

The homepage links to 5 pages on primezone.ru and 7 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://primezone.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.

https://primezone.ru/ru, / and https://primezone.ru/en all use the title “PrimeZone”. Search engines can't tell which page to show for a search, so each competes with the others.

/, https://primezone.ru/en, https://primezone.ru/ru/agreement.html and https://primezone.ru/ru/details.html have no meta description, so Google writes the search snippet from whatever text it finds.

/, https://primezone.ru/ru/agreement.html and https://primezone.ru/ru/details.html have 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.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

Your longest form asks for 9 fields (9 required). Every extra field lowers completion.

The homepage has only about 61 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.

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 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.