Website review, no card needed
volia.com website review
Visit site (opens in a new tab)Reviewed 29 October 202647 issues · 84 checks
This review found 47 issues worth fixing on volia.com, 20 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
71CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.3 s |
| May 16, 2026 | 4.5 s |
| May 23, 2026 | 4.8 s |
| May 30, 2026 | 4.3 s |
| Jun 6, 2026 | 3.7 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.0 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 3.3 s |
| Aug 8, 2026 | 4.2 s |
| Aug 15, 2026 | 4.2 s |
| Aug 22, 2026 | 4.0 s |
| Aug 29, 2026 | 3.7 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 182 ms |
| May 16, 2026 | 182 ms |
| May 23, 2026 | 179 ms |
| May 30, 2026 | 175 ms |
| Jun 6, 2026 | 174 ms |
| Jun 13, 2026 | 172 ms |
| Jun 20, 2026 | 173 ms |
| Jun 27, 2026 | 176 ms |
| Jul 4, 2026 | 176 ms |
| Jul 11, 2026 | 174 ms |
| Jul 18, 2026 | 173 ms |
| Jul 25, 2026 | 171 ms |
| Aug 1, 2026 | 171 ms |
| Aug 8, 2026 | 172 ms |
| Aug 15, 2026 | 171 ms |
| Aug 22, 2026 | 172 ms |
| Aug 29, 2026 | 171 ms |
| Sep 5, 2026 | 170 ms |
| Sep 12, 2026 | 169 ms |
| Sep 19, 2026 | 169 ms |
| Sep 26, 2026 | 168 ms |
| Oct 3, 2026 | 169 ms |
| Oct 10, 2026 | 169 ms |
| Oct 17, 2026 | 166 ms |
| Oct 24, 2026 | 164 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
Speed
Reduce unused JavaScript
8.1 s · 1.0 MBAbout 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.1 s faster on a phone.
Mobile performance score: 33
33/100Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.1 s
A phone's processor spends 5.1 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and sender.mobi and others), adding 2.4 MB and 1.8 s of main-thread time.
Google Tag Manager adds 767 ms
767 msGoogle Tag Manager costs a phone 767 ms of main-thread work and 696 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.
Reduce unused CSS
750 ms · 61 KiBAbout 61 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Render-blocking requests
750 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Google CDN adds 635 ms
635 msGoogle CDN costs a phone 635 ms of main-thread work and 1.1 MB 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.
Use efficient cache lifetimes
500 ms · 187 KiB59 files are served with short cache lifetimes, so returning visitors download them again (187 KiB).
Improve image delivery
350 KiB5 images could be 350 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 270 ms. During a long task the page ignores taps.
sender.mobi adds 169 ms
169 mssender.mobi costs a phone 169 ms of main-thread work and 381 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.
Legacy JavaScript
24 KiBPolyfills for old browsers add 24 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: 59 ms
59 msYour server sent the HTML in 59 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 22.2 s
22.2 sYour largest element takes 22.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Інтернет”.
First Contentful Paint: 7.6 s
7.6 sThe first text or image appears after 7.6 s on a phone. Good is under 1.8 s.
Speed Index: 13.9 s
13.9 sVisually, the page fills in at 13.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 22.4 s
22.4 sThe page becomes fully interactive after 22.4 s. Good is under 3.8 s.
Total Blocking Time: 1.0 s
1.0 sScripts block taps and scrolling for 1.0 s in total while the page loads. Good is under 200 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 182 ms to 164 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 160 ms
160 msReal visitors wait 160 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 581 ms
581 msReal visitors wait 581 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 53% faster for real visitors
-53%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.3 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.7 MB in 162 requests
4.7 MBYour homepage downloads 4.7 MB in 162 requests on a phone: scripts 2.5 MB (50), images 1.1 MB (27) and other files 802 KiB (65). Under 2 MB keeps phones on slow connections fast.
5 images in older formats
5 images (530 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.
2 images below the first screen load straight away
2 images further down the page (198 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.3 g of CO₂ per visit
1.34 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.34 g of CO₂e: 161.2 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
9 buttons without a name
9 buttons have no accessible name, so screen readers announce just “button”.
36 text elements with low contrast
36 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
6 elements hidden from screen readers can still receive keyboard focus.
ARIA progressbar nodes must have an accessible name (1 element)
ARIA progressbar nodes must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
<html> element must have a valid value for the lang attribute (1 element)
<html> element must have a valid value for the lang attribute: 1 element on the page fails this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
All page content should be contained by landmarks (51 elements)
All page content should be contained by landmarks: 51 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (2 elements)
Heading levels should only increase by one: 2 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
2 form fields without a label
2 form fields have 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.
Alternative text of images should not be repeated as text (6 elements)
Alternative text of images should not be repeated as text: 6 elements on the page fail this check, rated minor by axe-core.
Page language is “uk_UA”
The page declares lang=“uk_UA”, which is not a usable language code, so screen readers and translation tools guess.
1 checks passed
35 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: 35 passed and 12 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (82 characters)
Your title is 82 characters, so Google will cut it off around 60: “Провайдер ВОЛЯ - підключити послуги ТБ та Інтернет у Києві | Лідер цифрових розваг”.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
7 links crawlers can't follow
7 links have no real href, so search engines can't follow them.
Invalid hreflang
Your hreflang tags are invalid, so Google may show the wrong language version.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
6 checks passed
Meta description: 135 characters
Your meta description is 135 characters: “Інтернет-провайдер Київ - Volia✅Швидке підключення та налаштування⭐Користуйтесь телекомунікаційними послугами провайдер…”.
Canonical URL set
The canonical URL is https://volia.com/.
Structured data in place
Structured data found: Organization 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://volia.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://volia.com/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 1 crawler
robots.txt blocks 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.
Best practices
5 small tap targets
5 of 23 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Framing 'https://www.google.com/' violates the following report-only Content Security Policy directive: "frame-ancestor…”.
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
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 74 words
The homepage has only about 74 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 Tag Manager and Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before 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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
17 other companies contacted
Loading the homepage contacts 17 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 volia.com, 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
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Akamai
Company
- Employees
- 87,544
- Founded
- 2002
- Headquarters
- Kyiv
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 volia.com, 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.