Website review, no card needed

metro-cc.ru logo

metro-cc.ru website review

Visit site (opens in a new tab)Reviewed 2 November 202647 issues · 88 checks

This review found 47 issues worth fixing on metro-cc.ru, 20 of them high impact, across 88 checks. The most urgent: reduce unused JavaScript. 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.1 s2.4 sMay 16Oct 313.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.8 s
May 23, 20262.7 s
May 30, 20262.6 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.6 s
Jul 4, 20262.6 s
Jul 11, 20262.6 s
Jul 18, 20262.6 s
Jul 25, 20262.6 s
Aug 1, 20262.6 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.7 s
Sep 26, 20262.7 s
Oct 17, 20263.0 s
Oct 24, 20263.0 s
Oct 31, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
1.1 s362 msMay 16Oct 31746 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026467 ms
May 23, 2026458 ms
May 30, 2026445 ms
Jun 6, 2026445 ms
Jun 13, 2026466 ms
Jun 20, 2026468 ms
Jun 27, 2026479 ms
Jul 4, 2026546 ms
Jul 11, 2026625 ms
Jul 18, 2026784 ms
Jul 25, 2026974 ms
Aug 1, 2026997 ms
Aug 8, 2026928 ms
Aug 15, 2026836 ms
Aug 22, 2026797 ms
Aug 29, 2026818 ms
Sep 5, 2026862 ms
Sep 12, 2026838 ms
Sep 19, 2026790 ms
Sep 26, 2026718 ms
Oct 17, 2026733 ms
Oct 24, 2026734 ms
Oct 31, 2026746 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 metro-cc.ru (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. metro-cc.ru at 2.0 s2.0 s
  2. metro-cc.ru at 4.1 s4.1 s
  3. metro-cc.ru at 6.1 s6.1 s
  4. metro-cc.ru at 8.2 s8.2 s
  5. metro-cc.ru at 10.2 s10.2 s
  6. metro-cc.ru at 12.3 s12.3 s
  7. metro-cc.ru at 14.3 s14.3 s
  8. metro-cc.ru at 16.4 s16.4 s

Speed

9 to fix38
  • Reduce unused JavaScript

    1.1 s · 809 KiB

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

  • Mobile performance score: 38

    38/100

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

  • Main-thread work: 8.8 s

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

  • Use efficient cache lifetimes

    600 ms · 6.1 MB

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

  • Improve image delivery

    900 ms · 5.7 MB

    33 images could be 5.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

  • 16 long tasks on the main thread

    16 long tasks block the main thread while loading, the longest for 1.7 s. During a long task the page ignores taps.

  • 8 third-party services on the page

    8 third-party services load with your homepage (stellarlabs.ai, Yandex Metrica and Google Tag Manager and others), adding 1,008 KiB and 538 ms of main-thread time.

  • stellarlabs.ai adds 165 ms

    165 ms

    stellarlabs.ai costs a phone 165 ms of main-thread work and 546 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.

  • 1,904 HTML elements

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

  • Reduce unused CSS

    70 KiB

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

  • Legacy JavaScript

    45 KiB

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

  • 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
  • Server response: 275 ms

    275 ms

    Your server sent the HTML in 275 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 to fix33
  • 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.

  • Real-user INP: 2.5 s

    2.5 s

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

  • Real-user TTFB: 2.1 s

    2.1 s

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

  • Speed Index: 20.7 s

    20.7 s

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

  • Time to Interactive: 31.7 s

    31.7 s

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

  • Largest Contentful Paint: 7.6 s

    7.6 s

    Your largest element takes 7.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Берите не глядя 22.10-04.11”. Most of its time is resource load delay (5.5 s).

  • Total Blocking Time: 1.7 s

    1.7 s

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

  • Real-user LCP: 3.4 s

    3.4 s

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

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

    +60%

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

  • Real-user FCP: 2.5 s

    2.5 s

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

  • 14 images without width and height

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

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

    +11%

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

3 checks passed
  • Real-user CLS: 0.10

    0.10

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

  • First Contentful Paint: 1.7 s

    1.7 s

    The first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.065

    0.065

    The layout barely moves while loading (CLS 0.065, good is under 0.1).

Images and page weight

2 to fix64
  • Page weight: 10.2 MB in 129 requests

    10.2 MB

    Your homepage downloads 10.2 MB in 129 requests on a phone: images 7.4 MB (54), scripts 1.8 MB (27) and fonts 725 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    7717f082cdd0f0ba43f3e70af058ab87.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 2 images in older formats

    2 images (175 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.

  • About 2.9 g of CO₂ per visit

    2.89 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

11 to fixGoogle 6083
  • 10 buttons without a name

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

  • 21 tap targets too small

    21 tap targets are too small or too close together to hit reliably with a finger.

  • 16 text elements with low contrast

    16 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 (5 elements)

    Elements must only use permitted ARIA attributes: 5 elements on the page fail this check, rated serious by axe-core.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 21 images without alt text

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

  • All page content should be contained by landmarks (85 elements)

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

  • Zoom is disabled

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

  • 24 form fields without a label

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

  • 4 links without text

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 40 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 11 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9286
  • 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 X (Twitter) card tag

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

  • 36 internal links, 83 external

    The homepage links to 36 pages on metro-cc.ru and 83 external pages.

6 checks passed
  • Meta description: 78 characters

    Your meta description is 78 characters: “Оформите карту за 5 минут и получите доступ к 45 000 товаров по оптовым ценам.”.

  • Title: 33 characters

    Your title is a healthy 33 characters: “METRO | Для бизнеса и покупателей”.

  • Canonical URL set

    The canonical URL is https://metro-cc.ru/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://metro-cc.ru/sitemap.xml.

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://metro-cc.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 fix83
  • 4 pages share a title

    https://metro-cc.ru/blog/Pirog-s-terpugom-i-shpinatom, https://metro-cc.ru/blog/File-sazana-s-sousom-ber-blan, https://metro-cc.ru/blog/Terpug-Sever-vstrechaet-Don and https://metro-cc.ru/blog/File-terpuga-pod-ikornym-sousom-s-kartofelnym-gratenom all use the title “Metro”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 4 pages without a meta description

    https://metro-cc.ru/blog/Pirog-s-terpugom-i-shpinatom, https://metro-cc.ru/blog/File-sazana-s-sousom-ber-blan, https://metro-cc.ru/blog/Terpug-Sever-vstrechaet-Don and https://metro-cc.ru/blog/File-terpuga-pod-ikornym-sousom-s-kartofelnym-gratenom have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://metro-cc.ru/for-business, https://metro-cc.ru/sales and https://metro-cc.ru/fasol have no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages with very little text

    https://metro-cc.ru/catalogues, https://metro-cc.ru/blog, https://metro-cc.ru/blog/Pirog-s-terpugom-i-shpinatom, https://metro-cc.ru/blog/File-sazana-s-sousom-ber-blan, https://metro-cc.ru/blog/Terpug-Sever-vstrechaet-Don and https://metro-cc.ru/blog/File-terpuga-pod-ikornym-sousom-s-kartofelnym-gratenom and 2 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.

  • 1 page slow to respond

    https://metro-cc.ru/blog took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    11 pages of 15 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.

  • Every page has a title

    All 11 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7385
  • 24 small tap targets

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

  • 4 third-party cookies

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'after')”.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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.

  • Thin social proof

    Social proof on the homepage: 30 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 139 words

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

2 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    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.

  • 5 cookies set on arrival

    5

    Opening the homepage sets 5 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.

  • 10 other companies contacted

    Loading the homepage contacts 10 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 metro-cc.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
Nuxt
Analytics
Google Tag Manager
Hosting
EdgeCenter LLC

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 47 issues on metro-cc.ru, including 20 speed issues, 2 SEO issues and 4 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