Website review, no card needed

4lapy.ru logo

4lapy.ru website review

Visit site (opens in a new tab)Reviewed 18 November 202645 issues · 85 checks

This review found 45 issues worth fixing on 4lapy.ru, 15 of them high impact, across 85 checks. The most urgent: render-blocking requests. 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
6.7 s2.3 sMay 30Nov 142.8 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20266.0 s
Jun 6, 20266.0 s
Jun 13, 20266.1 s
Jun 20, 20266.1 s
Jun 27, 20266.2 s
Jul 4, 20266.2 s
Jul 11, 20266.2 s
Jul 18, 20266.2 s
Jul 25, 20266.2 s
Aug 1, 20266.1 s
Aug 8, 20266.1 s
Aug 15, 20266.1 s
Aug 22, 20266.1 s
Aug 29, 20265.9 s
Sep 5, 20265.5 s
Sep 12, 20264.8 s
Sep 19, 20263.8 s
Sep 26, 20263.4 s
Oct 3, 20263.4 s
Oct 10, 20263.4 s
Oct 17, 20263.3 s
Oct 24, 20263.2 s
Oct 31, 20263.0 s
Nov 7, 20262.9 s
Nov 14, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
551 ms242 msMay 30Nov 14515 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026278 ms
Jun 6, 2026304 ms
Jun 13, 2026330 ms
Jun 20, 2026353 ms
Jun 27, 2026356 ms
Jul 4, 2026348 ms
Jul 11, 2026348 ms
Jul 18, 2026350 ms
Jul 25, 2026349 ms
Aug 1, 2026363 ms
Aug 8, 2026376 ms
Aug 15, 2026384 ms
Aug 22, 2026395 ms
Aug 29, 2026402 ms
Sep 5, 2026406 ms
Sep 12, 2026413 ms
Sep 19, 2026423 ms
Sep 26, 2026437 ms
Oct 3, 2026465 ms
Oct 10, 2026490 ms
Oct 17, 2026504 ms
Oct 24, 2026513 ms
Oct 31, 2026507 ms
Nov 7, 2026507 ms
Nov 14, 2026515 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 4lapy.ru (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 4lapy.ru at 1.6 s1.6 s
  2. 4lapy.ru at 3.2 s3.2 s
  3. 4lapy.ru at 4.7 s4.7 s
  4. 4lapy.ru at 6.3 s6.3 s
  5. 4lapy.ru at 7.9 s7.9 s
  6. 4lapy.ru at 9.5 s9.5 s
  7. 4lapy.ru at 11.1 s11.1 s
  8. 4lapy.ru at 12.6 s12.6 s

Speed

8 to fix71
  • Render-blocking requests

    2.3 s

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

  • Main-thread work: 9.1 s

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

  • Use efficient cache lifetimes

    850 ms · 766 KiB

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

  • Mobile performance score: 71

    71/100

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

  • Reduce unused JavaScript

    300 ms · 604 KiB

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

  • Font display

    600 ms

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

  • 11 long tasks on the main thread

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

  • gravityfield.ai adds 33 ms

    33 ms

    gravityfield.ai costs a phone 33 ms of main-thread work and 345 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (diginetica.net, Yandex Metrica and mts.ru and others), adding 981 KiB and 390 ms of main-thread time.

  • Improve image delivery

    65 KiB

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

  • Legacy JavaScript

    33 KiB

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

  • Reduce unused CSS

    12 KiB

    About 12 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
  • Server response: 150 ms

    150 ms

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

Core Web Vitals

10 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: 710 ms

    710 ms

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

  • Real-user CLS: 0.57

    0.57

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

  • Time to Interactive: 17.5 s

    17.5 s

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

  • Speed Index: 11.0 s

    11.0 s

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

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

    +76%

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

  • Real-user TTFB: 801 ms

    801 ms

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Total Blocking Time: 414 ms

    414 ms

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

  • Largest Contentful Paint: 3.0 s

    3.0 s

    Your largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s.

4 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user FCP: 1.7 s

    1.7 s

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

  • Largest content (LCP) got 52% faster for real visitors

    -52%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 2.5 MB in 288 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 288 requests on a phone: scripts 1.5 MB (55), images 464 KiB (67) and other files 219 KiB (148). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.71 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

9 to fixGoogle 7385
  • 3 buttons without a name

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

  • 14 text elements with low contrast

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

  • Malformed lists

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

  • 15 images without alt text

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

  • Zoom is disabled

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

  • Page should contain a level-one heading (1 element)

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

  • 27 links without text

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

  • Alternative text of images should not be repeated as text (12 elements)

    Alternative text of images should not be repeated as text: 12 elements on the page fail this check, rated minor by axe-core.

  • 1 form field without a label

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

1 checks passed
  • 33 automated accessibility rules passed

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

SEO

5 to fixGoogle 8572
  • No H1 headline

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

  • Title is long (90 characters)

    Your title is 90 characters, so Google will cut it off around 60: “Зоомагазин Четыре Лапы — купить товары для животных с доставкой на дом в интернет-магазине”.

  • No structured data

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

  • Meta description is long (224 characters)

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

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

  • 120 internal links, 16 external

    The homepage links to 120 pages on 4lapy.ru and 16 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://4lapy.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.

  • XML sitemap found

    Your XML sitemap is reachable at https://4lapy.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://4lapy.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 fix75
  • 1 page without a title

    https://4lapy.ru/favourites has no <title>, so Google invents the link text in results.

  • 1 page without a meta description

    https://4lapy.ru/favourites has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://4lapy.ru/favourites has no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages with very little text

    https://4lapy.ru/favourites, https://4lapy.ru/vetcentr-and-grooming-appointment, https://4lapy.ru/landings/fashion, https://4lapy.ru/shares and https://4lapy.ru/catalog/koshki 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.

  • 2 pages slow to respond

    https://4lapy.ru/vetcentr-and-grooming-appointment and https://4lapy.ru/landings/fashion took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

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

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

2 to fixGoogle 9287
  • 18 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Uncaught Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full…”.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 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: 45 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • Only about 71 words

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

  • 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
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 11 cookies set on arrival

    11

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

  • 7 other companies contacted

    Loading the homepage contacts 7 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 4lapy.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
Hosting
Yandex.Cloud LLC

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 45 issues on 4lapy.ru, including 18 speed issues, 5 SEO issues and 5 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