Website review, no card needed

eldorado.ua logo

eldorado.ua website review

Visit site (opens in a new tab)Reviewed 28 October 202637 issues · 80 checks

This review found 37 issues worth fixing on eldorado.ua, 17 of them high impact, across 80 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.7 sMay 9Oct 242.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.9 s
May 16, 20262.9 s
May 23, 20262.9 s
May 30, 20263.0 s
Jun 6, 20263.0 s
Jun 13, 20263.0 s
Jun 20, 20263.0 s
Jun 27, 20263.0 s
Jul 4, 20263.0 s
Jul 11, 20263.0 s
Jul 18, 20263.0 s
Jul 25, 20262.9 s
Aug 1, 20262.9 s
Aug 8, 20263.0 s
Aug 15, 20263.0 s
Aug 22, 20263.0 s
Aug 29, 20263.0 s
Sep 5, 20262.9 s
Sep 12, 20262.9 s
Sep 19, 20262.9 s
Sep 26, 20262.8 s
Oct 3, 20262.8 s
Oct 10, 20262.8 s
Oct 17, 20262.8 s
Oct 24, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
838 ms611 msMay 9Oct 24637 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026792 ms
May 16, 2026788 ms
May 23, 2026789 ms
May 30, 2026798 ms
Jun 6, 2026805 ms
Jun 13, 2026812 ms
Jun 20, 2026799 ms
Jun 27, 2026803 ms
Jul 4, 2026807 ms
Jul 11, 2026770 ms
Jul 18, 2026751 ms
Jul 25, 2026729 ms
Aug 1, 2026687 ms
Aug 8, 2026720 ms
Aug 15, 2026742 ms
Aug 22, 2026738 ms
Aug 29, 2026757 ms
Sep 5, 2026749 ms
Sep 12, 2026750 ms
Sep 19, 2026752 ms
Sep 26, 2026736 ms
Oct 3, 2026719 ms
Oct 10, 2026680 ms
Oct 17, 2026670 ms
Oct 24, 2026637 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 eldorado.ua (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. eldorado.ua at 0.4 s0.4 s
  2. eldorado.ua at 0.9 s0.9 s
  3. eldorado.ua at 1.3 s1.3 s
  4. eldorado.ua at 1.8 s1.8 s
  5. eldorado.ua at 2.2 s2.2 s
  6. eldorado.ua at 2.7 s2.7 s
  7. eldorado.ua at 3.1 s3.1 s
  8. eldorado.ua at 3.5 s3.5 s

Speed

7 to fix24
  • Reduce unused JavaScript

    2.8 s · 702 KiB

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

  • Google Tag Manager adds 1.0 s

    1.0 s

    Google Tag Manager costs a phone 1.0 s of main-thread work and 1,017 KiB 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.

  • Mobile performance score: 24

    24/100

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, esputnik.com and Google Analytics and others), adding 1.2 MB and 1.2 s of main-thread time.

  • Render-blocking requests

    900 ms

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

  • 14 long tasks on the main thread

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

  • Main-thread work: 3.6 s

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

  • Reduce unused CSS

    150 ms · 50 KiB

    About 50 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Use efficient cache lifetimes

    34 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 61 but mobile only 24. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Improve image delivery

    5 KiB

    1 image could be 5 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

1 checks passed
  • Server response: 215 ms

    215 ms

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

Core Web Vitals

9 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: 589 ms

    589 ms

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

  • Real-user CLS: 0.86

    0.86

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

  • Largest Contentful Paint: 12.7 s

    12.7 s

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

  • Time to Interactive: 16.7 s

    16.7 s

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

  • Total Blocking Time: 1.3 s

    1.3 s

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

  • Cumulative Layout Shift: 0.446

    0.446

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

  • Speed Index: 6.7 s

    6.7 s

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

  • 26 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -6%

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

5 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 693 ms

    693 ms

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

  • Tap response (INP) got 17% faster for real visitors

    -17%

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

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

Images and page weight

2 to fix81
  • Page weight: 2.1 MB in 134 requests

    2.1 MB

    Your homepage downloads 2.1 MB in 134 requests on a phone: scripts 1.6 MB (19), fonts 176 KiB (7) and HTML 105 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    45189-1728924831.jpg 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).

  • About 0.6 g of CO₂ per visit

    0.60 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

8 to fixGoogle 7287
  • 9 buttons without a name

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

  • 2 text elements with low contrast

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

  • autocomplete attribute must be used correctly (1 element)

    autocomplete attribute must be used correctly: 1 element on the page fails this check, rated serious by axe-core.

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

    All page content should be contained by landmarks: 28 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.

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

    Alternative text of images should not be repeated as text: 18 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 link without text

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

2 checks passed
  • Every image has alt text

    All 17 images in the HTML carry an alt attribute.

  • 32 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 39 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 passed and 7 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 10083
  • No H1 headline

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

  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “Eldorado.ua — интернет-магазин бытовой техники и электроники в Украине”.

  • 32 internal links, 9 external

    The homepage links to 32 pages on eldorado.ua and 9 external pages.

6 checks passed
  • Meta description: 130 characters

    Your meta description is 130 characters: “Eldorado.ua — украинская сеть магазинов бытовой техники и электроники ☎ 0-800-217-600 ❗ Официальная гарантия ⚡ Широкий …”.

  • Canonical URL set

    The canonical URL is https://eldorado.ua/.

  • Structured data in place

    Structured data found: WebSite.

  • 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://eldorado.ua/sitemap/sitemap-list.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://eldorado.ua/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

2 to fix93
  • 4 pages share a meta description

    https://eldorado.ua/info/delivery, https://eldorado.ua/info/credit, https://eldorado.ua/info/service_centers and https://eldorado.ua/uk use the same meta description. A description written for each page earns more clicks.

  • 4 pages without an H1

    https://eldorado.ua/shops, https://eldorado.ua/info/credit, https://eldorado.ua/promotions and https://eldorado.ua/uk have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 pages with very little text

    https://eldorado.ua/shops, https://eldorado.ua/info/delivery, https://eldorado.ua/info/credit, https://eldorado.ua/info/service_centers, https://eldorado.ua/promotions and https://eldorado.ua/uk and 9 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.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

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

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'find')”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • 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: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 56 words

    The homepage has only about 56 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 0 email links.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.

  • 18 cookies set on arrival

    18

    Opening the homepage sets 18 cookies, 2 of them by other companies (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.

  • 16 other companies contacted

    Loading the homepage contacts 16 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 eldorado.ua, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
React
Analytics
Google Tag Manager
Hosting
AWS

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on eldorado.ua, including 16 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