Website review, no card needed

centpart.ru logo

centpart.ru website review

Visit site (opens in a new tab)Reviewed 18 October 202649 issues · 81 checks

This review found 49 issues worth fixing on centpart.ru, 22 of them high impact, across 81 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.0 s1.5 sMay 9Oct 102.8 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.4 s
May 16, 20262.4 s
May 23, 20262.2 s
Jul 4, 20262.1 s
Jul 18, 20262.3 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.7 s
Aug 15, 20262.0 s
Aug 22, 20261.6 s
Sep 5, 20261.9 s
Sep 12, 20262.1 s
Sep 19, 20262.2 s
Sep 26, 20262.5 s
Oct 3, 20262.6 s
Oct 10, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
271 ms121 msMay 9Oct 10254 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026138 ms
May 16, 2026154 ms
May 23, 2026189 ms
Jul 25, 2026227 ms
Aug 1, 2026222 ms
Aug 8, 2026208 ms
Aug 15, 2026232 ms
Aug 22, 2026194 ms
Sep 5, 2026184 ms
Sep 12, 2026188 ms
Sep 19, 2026189 ms
Sep 26, 2026205 ms
Oct 3, 2026201 ms
Oct 10, 2026254 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of centpart.ru (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. centpart.ru at 2.0 s2.0 s
  2. centpart.ru at 4.1 s4.1 s
  3. centpart.ru at 6.1 s6.1 s
  4. centpart.ru at 8.1 s8.1 s
  5. centpart.ru at 10.2 s10.2 s
  6. centpart.ru at 12.2 s12.2 s
  7. centpart.ru at 14.2 s14.2 s
  8. centpart.ru at 16.2 s16.2 s

Speed

8 to fix53
  • Use efficient cache lifetimes

    25.2 s · 6.7 MB

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

  • Improve image delivery

    24.3 s · 4.7 MB

    4 images could be 4.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 24.3 s faster on a phone.

  • Document request latency

    3.6 s

    The HTML itself could arrive about 3.6 s sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    3.6 s

    Reduce initial server response time. Google estimates savings of 3.6 s on a phone.

  • Server response: 3.7 s

    3.7 s

    Your server takes 3.7 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Mobile performance score: 53

    53/100

    Your mobile performance score is 53 (desktop: 67). Pages that score under 90 lose visitors before the first paint.

  • Font display

    950 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 950 ms).

  • Render-blocking requests

    350 ms

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.

  • Reduce unused JavaScript

    250 ms · 240 KiB

    About 240 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 250 ms faster on a phone.

  • 7 third-party services on the page

    7 third-party services load with your homepage (top100.ru, Yandex Metrica and mail.ru and others), adding 197 KiB and 171 ms of main-thread time.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 113 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    23 KiB

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

  • Reduce unused CSS

    11 KiB

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

  • Chained critical requests

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

  • Forced reflow

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

1 checks passed
  • Main-thread work: 1.2 s

    A phone's processor spends 1.2 s on main-thread work while loading, 605 ms of it running JavaScript. That is comfortably low.

Core Web Vitals

8 to fix50
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 30.1 s

    30.1 s

    Your largest element takes 30.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Это история о людях, которые решили сделать невозможное — с…”.

  • Speed Index: 23.6 s

    23.6 s

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

  • Time to Interactive: 30.1 s

    30.1 s

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

  • Real-user CLS: 0.16

    0.16

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

  • Tap response (INP) got 56% slower for real visitors

    +56%

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

  • First Contentful Paint: 2.7 s

    2.7 s

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

  • Cumulative Layout Shift: 0.169

    0.169

    The layout shifts by 0.169 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Largest content (LCP) got 11% slower for real visitors

    +11%

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

4 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Real-user TTFB: 628 ms

    628 ms

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

  • Total Blocking Time: 63 ms

    63 ms

    Scripts block the page for only 63 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix18
  • Page weight: 7.6 MB in 110 requests

    7.6 MB

    Your homepage downloads 7.6 MB in 110 requests on a phone: images 4.8 MB (16), media 1.8 MB (6) and scripts 691 KiB (40). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 4.7 MB together. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    3.3 MB

    4 images are downloaded at several times the size a phone draws them, for example 2026_10_14_12_38_30_marketing___gorokhova.ekaterina@centpart at 1,464 px wide, shown at 362 px. Resized copies would save about 3.3 MB.

  • 4 images in older formats

    4 images (4.8 MB) 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.

  • 3 images below the first screen load straight away

    3 images further down the page (2.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.1 g of CO₂ per visit

    2.15 g

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

Accessibility

6 to fix76
  • 5 buttons without a name

    5 buttons have no accessible name, so screen readers announce just “button”.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • 16 links without text

    16 visible links have no text or label, so screen readers cannot say where they go.

  • Elements use prohibited ARIA attributes

    Elements use prohibited ARIA attributes (1 element).

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

SEO

8 to fixGoogle 9249
  • No page title

    Your page has no <title>, so Google has to invent the blue link in search results.

  • No meta description

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

  • No H1 headline

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

  • No structured data

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

  • No canonical URL

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

  • No social preview image

    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

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

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

  • 19 internal links, 10 external

    The homepage links to 19 pages on centpart.ru and 10 external pages.

1 checks passed
  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix83
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://centpart.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.

1 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

Other pages

3 to fix71
  • 11 pages without a title

    https://centpart.ru/film/3235, https://centpart.ru/film/3192, https://centpart.ru/film/3180, https://centpart.ru/film/3225, https://centpart.ru/film/3245 and https://centpart.ru/item/3434 and 5 others have no <title>, so Google invents the link text in results.

  • 11 pages without a meta description

    https://centpart.ru/film/3235, https://centpart.ru/film/3192, https://centpart.ru/film/3180, https://centpart.ru/film/3225, https://centpart.ru/film/3245 and https://centpart.ru/item/3434 and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages without an H1

    https://centpart.ru/film/3235, https://centpart.ru/film/3192, https://centpart.ru/film/3180, https://centpart.ru/film/3225, https://centpart.ru/film/3245 and https://centpart.ru/item/3434 and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 11 pages with very little text

    https://centpart.ru/film/3235, https://centpart.ru/film/3192, https://centpart.ru/film/3180, https://centpart.ru/film/3225, https://centpart.ru/film/3245 and https://centpart.ru/item/3434 and 5 others 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.

  • 6 pages slow to respond

    https://centpart.ru/item/3434, https://centpart.ru/item/3432, https://centpart.ru/item/3429, https://centpart.ru/films, https://centpart.ru/about and https://centpart.ru/contacts took over 3 s to send their HTML from our server.

  • 13 internal pages checked

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

3 checks passed
  • Linked pages load

    11 pages of 13 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

3 to fixGoogle 9276
  • 1 broken image

    1 image failed to load on a phone, for example https://www.facebook.com/tr?id=643232433178099&ev=PageView&noscript=1.

  • 2 JavaScript errors while loading

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

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

    22 of 22 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix25
  • No call to action on the first screen

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

  • No calls to action

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

  • No social proof

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

  • No analytics detected

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

  • No direct contact details

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

  • Only about 29 words

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

  • No form on the homepage

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

  • No risk reducer

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Meta Pixel 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.

  • 10 cookies set on arrival

    10

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

  • No consent tool detected

    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.

  • 12 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at centpart.ru, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js

Company

Founded
1995
Headquarters
Moscow

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on centpart.ru, including 16 speed issues, 8 SEO issues and 6 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25