Website review, no card needed
o2.sk website review
Visit site (opens in a new tab)Reviewed 4 November 202641 issues · 86 checks
This review found 41 issues worth fixing on o2.sk, 11 of them high impact, across 86 checks. The most urgent: render-blocking requests. 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
78CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 356 ms |
| May 23, 2026 | 355 ms |
| May 30, 2026 | 355 ms |
| Jun 6, 2026 | 355 ms |
| Jun 13, 2026 | 357 ms |
| Jun 20, 2026 | 361 ms |
| Jun 27, 2026 | 363 ms |
| Jul 4, 2026 | 368 ms |
| Jul 11, 2026 | 374 ms |
| Jul 18, 2026 | 377 ms |
| Jul 25, 2026 | 378 ms |
| Aug 1, 2026 | 379 ms |
| Aug 8, 2026 | 380 ms |
| Aug 15, 2026 | 386 ms |
| Aug 22, 2026 | 390 ms |
| Aug 29, 2026 | 393 ms |
| Sep 5, 2026 | 391 ms |
| Sep 12, 2026 | 388 ms |
| Sep 19, 2026 | 386 ms |
| Sep 26, 2026 | 383 ms |
| Oct 3, 2026 | 384 ms |
| Oct 10, 2026 | 386 ms |
| Oct 17, 2026 | 387 ms |
| Oct 24, 2026 | 392 ms |
| Oct 31, 2026 | 400 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
Render-blocking requests
2.4 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.
Use efficient cache lifetimes
2.4 MB40 files are served with short cache lifetimes, so returning visitors download them again (2.4 MB).
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, luigisbox.tech and JSDelivr CDN and others), adding 1.1 MB and 1.2 s of main-thread time.
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
300 ms · 504 KiBAbout 504 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.
Google Tag Manager adds 539 ms
539 msGoogle Tag Manager costs a phone 539 ms of main-thread work and 675 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.
luigisbox.tech adds 481 ms
481 msluigisbox.tech costs a phone 481 ms of main-thread work and 326 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.
Main-thread work: 3.6 s
A phone's processor spends 3.6 s on main-thread work while loading, 2.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
309 KiB8 images could be 309 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
1,513 HTML elements
The page has 1,513 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 151 ms. During a long task the page ignores taps.
Legacy JavaScript
34 KiBPolyfills for old browsers add 34 KiB JavaScript that modern phones do not need.
Reduce unused CSS
12 KiBAbout 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.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 372 ms
372 msYour server sent the HTML in 372 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Speed Index: 18.1 s
18.1 sVisually, the page fills in at 18.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 14.5 s
14.5 sThe page becomes fully interactive after 14.5 s. Good is under 3.8 s.
First Contentful Paint: 3.1 s
3.1 sThe first text or image appears after 3.1 s on a phone. Good is under 1.8 s.
Real-user INP: 354 ms
354 msReal visitors wait 354 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest Contentful Paint: 3.1 s
3.1 sYour largest element takes 3.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Podnikatelia a firmy”. Most of its time is element render delay (6.6 s).
Total Blocking Time: 288 ms
288 msScripts block taps and scrolling for 288 ms in total while the page loads. Good is under 200 ms.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 356 ms to 400 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 478 ms
478 msReal visitors wait 478 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.063
0.063The layout barely moves while loading (CLS 0.063, good is under 0.1).
Images and page weight
Page weight: 4.3 MB in 114 requests
4.3 MBYour homepage downloads 4.3 MB in 114 requests on a phone: images 3.0 MB (35), scripts 1.2 MB (30) and HTML 74 KiB (1). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
355 KiB1 image is downloaded at several times the size a phone draws it, for example 860fe3dd-64d8-2730-b28d-b8f866f2428b at 1,300 px wide, shown at 160 px. Resized copies would save about 355 KiB.
1 image below the first screen load straight away
1 image further down the page (411 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (411 KiB) is 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.
About 1.2 g of CO₂ per visit
1.21 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.21 g of CO₂e: 144.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
[role]s do not have all required [aria-*] attributes
[role]s do not have all required [aria-*] attributes (1 element).
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Main landmark should not be contained in another landmark (1 element)
Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one main landmark (1 element)
Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.
9 tap targets too small
9 tap targets are too small or too close together to hit reliably with a finger.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (5 elements).
2 checks passed
Every image has alt text
All 31 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 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
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 (214 characters)
Your meta description is 214 characters; Google truncates after about 160, so the end of your pitch is cut.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
130 internal links, 0 external
The homepage links to 130 pages on o2.sk and 0 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Sledujte hviezdy Ligy majstrov na O2 TV”.
Title: 50 characters
Your title is a healthy 50 characters: “O2 | Mobilné telefóny, internet a volacie programy”.
Canonical URL set
The canonical URL is https://www.o2.sk/.
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://www.o2.sk/sitemap.xml.
AI search readiness
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://www.o2.sk/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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,032 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages without a meta description
https://www.o2.sk/connect, https://www.o2.sk/ponuka/mobilne-sluzby/o2-maxx and https://www.o2.sk/o2-simka have no meta description, so Google writes the search snippet from whatever text it finds.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.o2.sk/o2-pausal, whose canonical is https://www.o2.sk/ponuka/mobilne-sluzby/novy-o2-pausal. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 93 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 15 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://www.o2static.sk/combo?browserId=other&minifierType=&themeId=o2Atomic_WAR_eportalli…”.
2 checks passed
Tap targets are thumb-sized
12 of 12 tappable elements near the top are at least 24 px.
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.
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.
About 343 words of copy
The homepage carries about 343 words of visible text.
2 checks passed
3 short forms
3 short forms (0 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
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.
11 other companies contacted
Loading the homepage contacts 11 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 o2.sk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2022.
Stack
- Framework
- Tailwind CSS
- Analytics
- Google Tag Manager
- Hosting
- O2 Czech Republic
Company
- Founded
- 2007
- Headquarters
- Bratislava
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on o2.sk, including 18 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.