Website review, no card needed

evo.company logo

evo.company website review

Visit site (opens in a new tab)Reviewed 30 October 202631 issues · 79 checks

This review found 31 issues worth fixing on evo.company, 11 of them high impact, across 79 checks. The most urgent: improve image delivery. 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
1.3 s896 msMay 9Oct 24941 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.1 s
May 16, 20261.1 s
May 23, 20261.1 s
May 30, 2026980 ms
Jun 6, 20261.0 s
Jun 13, 20261.1 s
Jun 20, 20261.0 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.1 s
Aug 22, 2026966 ms
Aug 29, 2026992 ms
Sep 5, 2026976 ms
Sep 12, 20261.0 s
Sep 19, 20261.1 s
Sep 26, 20261.0 s
Oct 3, 2026962 ms
Oct 10, 2026988 ms
Oct 17, 2026948 ms
Oct 24, 2026941 ms
Real-visitor tap response (INP)75th percentile, phones
94 ms78 msMay 9Oct 2482 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202687 ms
May 16, 202684 ms
May 23, 202683 ms
May 30, 202680 ms
Jun 6, 202682 ms
Jun 13, 202683 ms
Jun 20, 202686 ms
Jun 27, 202691 ms
Jul 4, 202687 ms
Jul 11, 202688 ms
Jul 18, 202688 ms
Jul 25, 202690 ms
Aug 1, 202692 ms
Aug 8, 202687 ms
Aug 15, 202687 ms
Aug 22, 202686 ms
Aug 29, 202687 ms
Sep 5, 202687 ms
Sep 12, 202687 ms
Sep 19, 202686 ms
Sep 26, 202687 ms
Oct 3, 202687 ms
Oct 10, 202686 ms
Oct 17, 202689 ms
Oct 24, 202682 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 evo.company (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. evo.company at 0.7 s0.7 s
  2. evo.company at 1.3 s1.3 s
  3. evo.company at 2.0 s2.0 s
  4. evo.company at 2.6 s2.6 s
  5. evo.company at 3.3 s3.3 s
  6. evo.company at 3.9 s3.9 s
  7. evo.company at 4.6 s4.6 s
  8. evo.company at 5.2 s5.2 s

Speed

6 to fix71
  • Improve image delivery

    5.5 s · 2.0 MB

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

  • Use efficient cache lifetimes

    5.0 s · 1.9 MB

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

  • Font display

    1.3 s

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

  • Mobile performance score: 71

    71/100

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

  • Render-blocking requests

    650 ms

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

  • Reduce unused JavaScript

    310 ms · 74 KiB

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 179 KiB and 86 ms of main-thread time.

  • 1 long task on the main thread

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

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 0.5 s

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

  • Server response: 2 ms

    2 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 11.1 s

    11.1 s

    Your largest element takes 11.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “EVO”.

  • Time to Interactive: 11.1 s

    11.1 s

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

  • Speed Index: 5.1 s

    5.1 s

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

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    0%

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

10 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • 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 INP: 89 ms

    89 ms

    Real visitors wait 89 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.

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 691 ms

    691 ms

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

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

    -12%

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0.018

    0.018

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

  • Total Blocking Time: 1 ms

    1 ms

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

Images and page weight

6 to fix33
  • 1 image over 500 KB

    our-values-illustration.png weighs 692 KiB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    492 KiB

    1 image is downloaded at several times the size a phone draws it, for example our-values-illustration.png at 2,401 px wide, shown at 430 px. Resized copies would save about 492 KiB.

  • Page weight: 3.0 MB in 39 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 39 requests on a phone: images 2.4 MB (29), fonts 360 KiB (1) and scripts 227 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 7 images in older formats

    7 images (2.2 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.

  • An image on the first screen is lazy-loaded

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

  • 4 images below the first screen load straight away

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

  • About 0.8 g of CO₂ per visit

    0.85 g

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

Accessibility

3 to fixGoogle 9095
  • Malformed lists

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

  • Orphan list items

    Some list items are not inside a list.

  • 6 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 26 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

2 to fixGoogle 9290
  • Title is short (13 characters)

    Your title is only 13 characters: “Головна - EVO”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 17 links crawlers can't follow

    17 links have no real href, so search engines can't follow them.

  • 30 internal links, 14 external

    The homepage links to 30 pages on evo.company and 14 external pages.

7 checks passed
  • Meta description: 129 characters

    Your meta description is 129 characters: “EVO – українська продуктова IT-компанія. Робимо маркетплейси для онлайн-шопінгу та замовлення послуг Prom, Bigl, Shafa,…”.

  • One H1 headline

    Your main headline reads: “EVO – українська продуктова IT-компанія”.

  • Canonical URL set

    The canonical URL is https://evo.company/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and 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://evo.company/sitemap_index.xml.

AI search readiness

1 to fix83
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

1 to fix95
  • 11 pages without a meta description

    https://evo.company/projects/prom, https://evo.company/projects/rozetkapay, https://evo.company/projects/shafa, https://evo.company/projects/bigl, https://evo.company/projects/satu and https://evo.company/projects/kabanchik and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 pages with very little text

    https://evo.company/projects/prom, https://evo.company/projects/rozetkapay, https://evo.company/projects/shafa, https://evo.company/projects/bigl, https://evo.company/projects/satu and https://evo.company/projects/kabanchik 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.

  • 11 internal pages checked

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

6 checks passed
  • Linked pages load

    All 11 pages we checked loaded without an error.

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

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

2 to fixGoogle 9687
  • 9 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix42
  • 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.

  • 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 52 words

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

1 checks passed
  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 3 cookies set on arrival

    3

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

  • 2 other companies contacted

    Loading the homepage contacts 2 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 evo.company, 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
Framework
jQuery
Analytics
Google Analytics
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on evo.company, including 10 speed issues, 2 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