Website review, no card needed

telekom.sk logo

telekom.sk website review

Visit site (opens in a new tab)Reviewed 1 November 202631 issues · 81 checks

This review found 31 issues worth fixing on telekom.sk, 10 of them high impact, across 81 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.0 s1.5 sMay 9Oct 241.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.9 s
May 16, 20261.8 s
May 23, 20261.8 s
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.8 s
Jun 27, 20261.8 s
Jul 4, 20261.9 s
Jul 11, 20261.9 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.8 s
Sep 19, 20261.8 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
996 ms156 msMay 9Oct 24253 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026595 ms
May 16, 2026604 ms
May 23, 2026606 ms
May 30, 2026630 ms
Jun 6, 2026704 ms
Jun 13, 2026758 ms
Jun 20, 2026806 ms
Jun 27, 2026803 ms
Jul 4, 2026797 ms
Jul 11, 2026800 ms
Jul 18, 2026802 ms
Jul 25, 2026820 ms
Aug 1, 2026846 ms
Aug 8, 2026899 ms
Aug 15, 2026823 ms
Aug 22, 2026478 ms
Aug 29, 2026345 ms
Sep 5, 2026288 ms
Sep 12, 2026263 ms
Sep 19, 2026259 ms
Sep 26, 2026262 ms
Oct 3, 2026263 ms
Oct 10, 2026260 ms
Oct 17, 2026261 ms
Oct 24, 2026253 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 telekom.sk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. telekom.sk at 1.1 s1.1 s
  2. telekom.sk at 2.2 s2.2 s
  3. telekom.sk at 3.2 s3.2 s
  4. telekom.sk at 4.3 s4.3 s
  5. telekom.sk at 5.4 s5.4 s
  6. telekom.sk at 6.5 s6.5 s
  7. telekom.sk at 7.6 s7.6 s
  8. telekom.sk at 8.6 s8.6 s

Speed

9 to fix38
  • Render-blocking requests

    1.8 s

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

  • Mobile performance score: 38

    38/100

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

  • Reduce unused JavaScript

    150 ms · 998 KiB

    About 998 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.

  • Use efficient cache lifetimes

    882 KiB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and Google Analytics and others), adding 1.0 MB and 714 ms of main-thread time.

  • Google Tag Manager adds 714 ms

    714 ms

    Google Tag Manager costs a phone 714 ms of main-thread work and 1.0 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.

  • Reduce unused CSS

    300 ms · 258 KiB

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

  • 13 long tasks on the main thread

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

  • Main-thread work: 3.4 s

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

  • Improve image delivery

    54 KiB

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

  • Legacy JavaScript

    11 KiB

    Polyfills for old browsers add 11 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: 349 ms

    349 ms

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

Core Web Vitals

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

  • Time to Interactive: 22.6 s

    22.6 s

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

  • Speed Index: 11.1 s

    11.1 s

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

  • Largest Contentful Paint: 6.2 s

    6.2 s

    Your largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Dva mobilné telefóny s plávajúcimi lampiónmi na ružovom poz…”.

  • Total Blocking Time: 1.4 s

    1.4 s

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

  • Real-user INP: 245 ms

    245 ms

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

  • First Contentful Paint: 2.9 s

    2.9 s

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

7 checks passed
  • Real-user LCP: 0.9 s

    0.9 s

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 325 ms

    325 ms

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

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

    -57%

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

  • 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.9 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.006

    0.006

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

Images and page weight

1 to fix85
  • Page weight: 3.4 MB in 131 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 131 requests on a phone: scripts 2.0 MB (81), fonts 571 KiB (4) and stylesheets 411 KiB (14). Under 2 MB keeps phones on slow connections fast.

  • 2 images below the first screen load straight away

    2 images further down the page (57 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.0 g of CO₂ per visit

    0.98 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.98 g of CO₂e: 117.2 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

2 to fixGoogle 10097
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 52 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

2 to fixGoogle 9293
  • 7 H1 headlines

    There are 7 <h1> headlines (“Vianoce v Telekome.V spojení s rodinou aj vďaka d…”, “Každý deň nový dôvod otvoriť Telekom aplikáciu” and “Každý deň nový dôvod otvoriť Telekom aplikáciu”). One clear main headline is easier for people and search engines.

  • 3 links crawlers can't follow

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

  • 75 internal links, 37 external

    The homepage links to 75 pages on telekom.sk and 37 external pages.

7 checks passed
  • Meta description: 131 characters

    Your meta description is 131 characters: “Rýchly optický internet, výhodné paušály, TV balíky a mobily pre domácnosti aj firmy. Objavte kompletnú ponuku služieb …”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “Paušály, Internet a Magio Televízia, mobilné telefóny | Telekom”.

  • Canonical URL set

    The canonical URL is https://www.telekom.sk/.

  • Structured data in place

    Structured data found: 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://www.telekom.sk/sitemap-sb.xml.

AI search readiness

100
4 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: 6 of 6 facts

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

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,308 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.telekom.sk/llms.txt (9 KiB, 35 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 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.telekom.sk/pomoc-a-podpora, whose canonical is https://www.telekom.sk/podpora. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.telekom.sk/internet-televizia/zariadenia has no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages slow to respond

    https://www.telekom.sk/internet-televizia/zariadenia/samsung-galaxy-a57-5g-plus-samsung-galaxy-a27-5g, https://www.telekom.sk/internet-televizia, https://www.telekom.sk/wiki/ostatne/pripojenie-produktov-a-sluzieb-do-telekom-aplikacie, https://www.telekom.sk/volania/easy and https://www.telekom.sk/internet-televizia/zariadenia took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 50 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.

  • 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 8197
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix43
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. 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.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 864 words of copy

    The homepage carries about 864 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

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.

  • 5 cookies set on arrival

    5

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

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

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 telekom.sk, 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 Tag Manager
Hosting
Slovak Telekom T-Mobile CZ

Company

Employees
2,999
Founded
1999
Headquarters
Bratislava

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 telekom.sk, including 16 speed issues, 2 SEO issues and 6 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