Website review, no card needed
telekom.me website review
Visit site (opens in a new tab)Reviewed 20 November 202647 issues · 90 checks
This review found 47 issues worth fixing on telekom.me, 17 of them high impact, across 90 checks. The most urgent: use efficient cache lifetimes. 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
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.1 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.2 s |
| Jul 4, 2026 | 3.1 s |
| Jul 11, 2026 | 3.0 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 3.0 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.1 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.8 s |
| Oct 31, 2026 | 2.8 s |
| Nov 7, 2026 | 2.9 s |
| Nov 14, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 207 ms |
| Jun 6, 2026 | 210 ms |
| Jun 13, 2026 | 210 ms |
| Jun 20, 2026 | 213 ms |
| Jun 27, 2026 | 215 ms |
| Jul 4, 2026 | 214 ms |
| Jul 11, 2026 | 215 ms |
| Jul 18, 2026 | 214 ms |
| Jul 25, 2026 | 212 ms |
| Aug 1, 2026 | 211 ms |
| Aug 8, 2026 | 215 ms |
| Aug 15, 2026 | 220 ms |
| Aug 22, 2026 | 226 ms |
| Aug 29, 2026 | 234 ms |
| Sep 5, 2026 | 238 ms |
| Sep 12, 2026 | 243 ms |
| Sep 19, 2026 | 245 ms |
| Sep 26, 2026 | 242 ms |
| Oct 3, 2026 | 241 ms |
| Oct 10, 2026 | 241 ms |
| Oct 17, 2026 | 245 ms |
| Oct 24, 2026 | 250 ms |
| Oct 31, 2026 | 253 ms |
| Nov 7, 2026 | 253 ms |
| Nov 14, 2026 | 250 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
Use efficient cache lifetimes
7.5 s · 8.0 MB51 files are served with short cache lifetimes, so returning visitors download them again (8.0 MB).
Improve image delivery
4.7 s · 6.4 MB32 images could be 6.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.7 s faster on a phone.
Reduce unused JavaScript
8.0 s · 1.6 MBAbout 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.0 s faster on a phone.
Font display
1.8 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.8 s).
Main-thread work: 4.4 s
A phone's processor spends 4.4 s on main-thread work while loading, 2.4 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, Clarity and ContentSquare and others), adding 2.0 MB and 1.2 s of main-thread time.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 514 ms
514 msGoogle Tag Manager costs a phone 514 ms of main-thread work and 880 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.
sprinklr.com adds 91 ms
91 mssprinklr.com costs a phone 91 ms of main-thread work and 399 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.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 243 ms. During a long task the page ignores taps.
Legacy JavaScript
100 ms · 48 KiBPolyfills for old browsers add 48 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.
Reduce unused CSS
90 KiBAbout 90 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
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 567 ms
567 msYour server sent the HTML in 567 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.
Largest Contentful Paint: 48.8 s
48.8 sYour largest element takes 48.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 28.1 s
28.1 sVisually, the page fills in at 28.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 55.2 s
55.2 sThe page becomes fully interactive after 55.2 s. Good is under 3.8 s.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 244 ms
244 msReal visitors wait 244 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 207 ms to 250 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 429 ms
429 msScripts block taps and scrolling for 429 ms in total while the page loads. Good is under 200 ms.
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.1 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
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.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 687 ms
687 msReal visitors wait 687 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 12.2 MB in 211 requests
12.2 MBYour homepage downloads 12.2 MB in 211 requests on a phone: images 8.0 MB (66), scripts 3.6 MB (58) and fonts 442 KiB (8). Under 2 MB keeps phones on slow connections fast.
8 images in older formats
8 images (1.3 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.
7 images below the first screen load straight away
7 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
6 images far larger than shown
422 KiB6 images are downloaded at several times the size a phone draws them, for example 360 at 360 px wide, shown at 95 px. Resized copies would save about 422 KiB.
About 3.5 g of CO₂ per visit
3.46 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.46 g of CO₂e: 414.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
8 images without alt text
8 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (32 elements)
All page content should be contained by landmarks: 32 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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
14 links without text
14 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
40 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: 40 passed and 10 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.
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 short (18 characters)
Your meta description is only 18 characters: “Privatni korisnici”. 70 to 160 characters is enough to sell the click.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
71 internal links, 19 external
The homepage links to 71 pages on telekom.me and 19 external pages.
4 checks passed
Title: 39 characters
Your title is a healthy 39 characters: “Privatni korisnici - Crnogorski Telekom”.
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://telekom.me/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://telekom.me/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 (260 words), so crawlers that don't run JavaScript still read it.
Other pages
7 pages share 2 titles
/ and https://telekom.me/privatni-korisnici all use the title “Privatni korisnici - Crnogorski Telekom”, and 1 other title repeat too. 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://telekom.me/privatni-korisnici/korisnicka-zona/online-prijava-problema, https://telekom.me/privatni-korisnici/magentatv and https://telekom.me/o-kompaniji/kontakti have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages share a meta description
https://telekom.me/user/edit-profile, https://telekom.me/privatni-korisnici/magenta-tv-i-internet, https://telekom.me/shopping-cart, https://telekom.me/privatni-korisnici/praznicna-ponuda and https://telekom.me/privatni-korisnici/iphone-duo use the same meta description. A description written for each page earns more clicks.
6 pages without an H1
https://telekom.me/privatni-korisnici, https://telekom.me/user/edit-profile, https://telekom.me/privatni-korisnici/magenta-tv-i-internet, https://telekom.me/o-kompaniji/kontakti, https://telekom.me/shopping-cart and https://telekom.me/privatni-korisnici/iphone-duo have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://telekom.me/shopping-cart, https://telekom.me/privatni-korisnici/praznicna-ponuda and https://telekom.me/privatni-korisnici/iphone-duo took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 52 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Refused to set unsafe header "Cookie"”.
19 distorted images
19 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
37 of 39 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.
Thin social proof
Social proof on the homepage: 6 trust badges. 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 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 274 words of copy
The homepage carries about 274 words of visible text.
2 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 1 more (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.
19 cookies set on arrival
19Opening the homepage sets 19 cookies, 1 of them by other companies (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.
29 other companies contacted
Loading the homepage contacts 29 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.me, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Nuxt
- Analytics
- Microsoft Clarity
- Hosting
- Crnogorski Telekom a.d.Podgorica
Company
- Founded
- 1998
- Headquarters
- Podgorica
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 telekom.me, including 18 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.