telnor.com website review

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

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

About 946 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.

About 235 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

Google Tag Manager costs a phone 1.1 s of main-thread work and 1.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

A phone's processor spends 4.7 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 load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 1.7 MB and 1.6 s of main-thread time.

11 images could be 195 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

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

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

37 KiB could be saved by minifying CSS.

21 KiB could be saved by minifying JavaScript.

47 KiB JavaScript is shipped twice across bundles.

Polyfills for old browsers add 33 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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.

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

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

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

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

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

The layout shifts by 0.85 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

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

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

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

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

Your homepage downloads 4.3 MB in 224 requests on a phone: scripts 2.5 MB (98), images 981 KiB (61) and fonts 455 KiB (6). Under 2 MB keeps phones on slow connections fast.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

32 images have no alt text, which hurts accessibility and image search.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

All page content should be contained by landmarks: 8 elements on the page fail this check, rated moderate by axe-core.

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 on the page fails this check, rated moderate by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 link inside paragraphs relies on colour alone to stand out.

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

Your title is 74 characters, so Google will cut it off around 60: “Internet Infinitum y teléfono con llamadas ilimitadas para tu casa - Hogar”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There is no robots.txt at telnor.com/robots.txt, the first file search crawlers ask for.

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 95 pages on telnor.com and 25 external pages.

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.

There is no https://www.telnor.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.

/ and https://www.telnor.com/web/hogar all use the title “Internet Infinitum y teléfono con llamadas ilimitadas para tu casa - …”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.telnor.com/web/hogar/home, https://www.telnor.com/web/hogar/servicios-internet, https://www.telnor.com/web/hogar/paquetes-de-internet-con-netflix, https://www.telnor.com/web/hogar/internet-con-netflix, https://www.telnor.com/web/hogar/paquetes-de-internet-con-prime-video and https://www.telnor.com/web/hogar/internet-con-prime-video and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.telnor.com/web/buscador/lugares, https://www.telnor.com/web/hogar/home, https://www.telnor.com/web/hogar/servicios-internet, https://www.telnor.com/web/hogar/paquetes-de-internet-con-netflix, https://www.telnor.com/web/hogar/internet-con-netflix and https://www.telnor.com/web/hogar/paquetes-de-internet-con-prime-video and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.telnor.com/web/buscador/lugares, https://www.telnor.com/web/hogar/home, https://www.telnor.com/web/hogar/servicios-internet, https://www.telnor.com/web/hogar/paquetes-de-internet-con-netflix, https://www.telnor.com/web/hogar/internet-con-netflix and https://www.telnor.com/web/hogar/paquetes-de-internet-con-prime-video and 6 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.

We fetched 15 pages linked from your homepage (of 66 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://telmex.com/documents/23521/4627298/ID-error.png.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 78 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Opening the homepage sets 19 cookies, 5 of them by other companies (measured from a US location before any click).

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.

Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.