Website review, no card needed

elko.ua logo

elko.ua website review

Visit site (opens in a new tab)Reviewed 24 October 202633 issues · 79 checks

This review found 33 issues worth fixing on elko.ua, 11 of them high impact, across 79 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
2.6 s1.9 sMay 2Oct 172.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.0 s
May 9, 20262.2 s
May 16, 20262.1 s
May 23, 20262.1 s
May 30, 20262.1 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20262.3 s
Jun 27, 20262.2 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.0 s
Jul 25, 20262.1 s
Aug 1, 20262.0 s
Aug 8, 20262.2 s
Aug 15, 20262.3 s
Aug 22, 20262.3 s
Aug 29, 20262.4 s
Sep 5, 20262.2 s
Sep 12, 20262.3 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.3 s
Oct 10, 20262.2 s
Oct 17, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
111 ms82 msMay 2Oct 1788 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026103 ms
May 9, 2026106 ms
May 16, 202695 ms
May 23, 202692 ms
May 30, 202691 ms
Jun 6, 202691 ms
Jun 13, 202689 ms
Jun 20, 202693 ms
Jun 27, 202696 ms
Jul 4, 202698 ms
Jul 11, 2026102 ms
Jul 18, 2026104 ms
Jul 25, 2026108 ms
Aug 1, 2026101 ms
Aug 8, 2026102 ms
Aug 15, 2026100 ms
Aug 22, 202695 ms
Aug 29, 202694 ms
Sep 5, 202689 ms
Sep 12, 202686 ms
Sep 19, 202686 ms
Sep 26, 202687 ms
Oct 3, 202685 ms
Oct 10, 202689 ms
Oct 17, 202688 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 elko.ua (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. elko.ua at 0.9 s0.9 s
  2. elko.ua at 1.8 s1.8 s
  3. elko.ua at 2.6 s2.6 s
  4. elko.ua at 3.5 s3.5 s
  5. elko.ua at 4.4 s4.4 s
  6. elko.ua at 5.3 s5.3 s
  7. elko.ua at 6.1 s6.1 s
  8. elko.ua at 7.0 s7.0 s

Speed

6 to fix79
  • Render-blocking requests

    1.0 s

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

  • Use efficient cache lifetimes

    800 ms · 779 KiB

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

  • Mobile performance score: 79

    79/100

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

  • Reduce unused CSS

    450 ms · 119 KiB

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

  • Reduce unused JavaScript

    150 ms · 365 KiB

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

  • Google CDN adds 106 ms

    106 ms

    Google CDN costs a phone 106 ms of main-thread work and 348 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.

  • 3 third-party services on the page

    3 third-party services load with your homepage (Cookiebot, Google CDN and Other Google APIs/SDKs), adding 513 KiB and 228 ms of main-thread time.

  • Improve image delivery

    147 KiB

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

  • 2 long tasks on the main thread

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

  • Legacy JavaScript

    34 KiB

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

  • Duplicated JavaScript

    26 KiB

    26 KiB JavaScript is shipped twice across bundles.

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

2 checks passed
  • Main-thread work: 1.2 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

8 to fix67
  • 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 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: 8.4 s

    8.4 s

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

  • Time to Interactive: 10.6 s

    10.6 s

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

  • Real-user LCP: 3.2 s

    3.2 s

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • Largest Contentful Paint: 3.6 s

    3.6 s

    Your largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ELKO Ukraine – дистриб’ютор широкого асортименту IT продукт…”. Most of its time is element render delay (4.4 s).

  • First Contentful Paint: 2.5 s

    2.5 s

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

  • Largest content (LCP) held steady for real visitors

    +2%

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

5 checks passed
  • Real-user INP: 94 ms

    94 ms

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

  • Real-user CLS: 0.00

    0.00

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

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

    -15%

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

  • Cumulative Layout Shift: 0.007

    0.007

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

  • Total Blocking Time: 47 ms

    47 ms

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

Images and page weight

100
  • 3 images in older formats

    3 images (230 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.

  • 1 image below the first screen load straight away

    1 image further down the page (57 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.5 g of CO₂ per visit

    0.45 g

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

2 checks passed
  • Page weight: 1.6 MB in 45 requests

    1.6 MB

    Your homepage downloads 1.6 MB in 45 requests on a phone: scripts 853 KiB (21), images 346 KiB (7) and fonts 276 KiB (5). That is a lean page.

  • Images are sized for phones

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

Accessibility

5 to fixGoogle 8692
  • 7 buttons without a name

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

  • 6 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 8 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

4 to fixGoogle 10075
  • No H1 headline

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

  • Title is short (19 characters)

    Your title is only 19 characters: “Home | ELKO Ukraine”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (315 characters)

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

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 116 internal links, 8 external

    The homepage links to 116 pages on elko.ua and 8 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.elko.ua/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • 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://www.elko.ua/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

Other pages

5 to fix76
  • 2 pages share a title

    https://www.elko.ua/%d1%80%d1%96%d1%88%d0%b5%d0%bd%d0%bd%d1%8f and https://www.elko.ua/rishennya all use the title “Всі Рішення | ELKO Ukraine”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 3 pages without a meta description

    https://www.elko.ua/produkty/manufacturers-portfolio, https://www.elko.ua/stat-partnerom-new and https://www.elko.ua/produkty/smartwatches have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.elko.ua/%d1%80%d1%96%d1%88%d0%b5%d0%bd%d0%bd%d1%8f and https://www.elko.ua/rishennya use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.elko.ua/%d1%80%d1%96%d1%88%d0%b5%d0%bd%d0%bd%d1%8f, whose canonical is https://www.elko.ua/rishennya. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://www.elko.ua/catalog and https://www.elko.ua/produkty/manufacturers-portfolio have no <h1> headline, so visitors and search engines get no clear main topic.

  • 8 pages with very little text

    https://www.elko.ua/catalog, https://www.elko.ua/stat-partnerom-new, https://www.elko.ua/produkty, https://www.elko.ua/vyrobnyky, https://www.elko.ua/microsoft-esd and https://www.elko.ua/produkty/getac-products 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.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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 10093
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

    20 of 24 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 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 45 words

    The homepage has only about 45 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: 1 phone link and 0 email links.

Privacy and tracking

  • 4 other companies contacted

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

2 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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

Upkeep, stack and company

Stack

CMS
WordPress
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on elko.ua, including 14 speed issues, 4 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