lumen.com.mx website review

Google Tag Manager costs a phone 1.8 s of main-thread work and 569 KiB 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 12. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

The page has 6,269 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 1.4 MB and 3.3 s of main-thread time.

23 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 578 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

Facebook costs a phone 770 ms of main-thread work and 314 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.

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

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

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

Polyfills for old browsers add 21 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

3 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

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

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

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

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

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

Your homepage downloads 8.0 MB in 161 requests on a phone: images 5.2 MB (58), scripts 1.5 MB (27) and fonts 978 KiB (12). Under 2 MB keeps phones on slow connections fast.

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

226 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

14 links inside paragraphs rely on colour alone to stand out.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

161 visible links have no text or label, so screen readers cannot say where they go.

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

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

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

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

Elements with visible text labels do not have matching accessible names. (1 element).

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.

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

The homepage links to 367 pages on lumen.com.mx and 11 external pages.

There is no https://lumen.com.mx/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.

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

10 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=187230435&tm=gtm002&Ver=2&mid=4bf2f4df-c618-4d85-aa7d-3414e0d3320d&bo=1&sid=0962dbc0d3bd11f1819bdbe8a82046b0&vid=0962f8e0d3bd11f1b6e9f304f31a559a&vids=1&msclkid=N&gtm_.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 413 ()”.

15 images are displayed at the wrong aspect ratio, so they look 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.

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

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

The homepage carries about 3,317 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 3 mores (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.

Opening the homepage sets 18 cookies (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 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.