tecnolite.mx website review

8 images could be 382 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

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

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

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

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 750 ms.

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

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

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

Hotjar costs a phone 335 ms of main-thread work and 290 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.

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

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

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

39 KiB could be saved by minifying JavaScript.

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.

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 10.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 5.2 MB in 203 requests on a phone: scripts 3.7 MB (72), images 760 KiB (71) and fonts 416 KiB (8). Under 2 MB keeps phones on slow connections fast.

B2B-Octubre-Mobile-450x450.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

2 images (231 KiB) 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.

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

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

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

2 tap targets are too small or too close together to hit reliably with a finger.

Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

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

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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

1 element has a tabindex above 0, which scrambles the keyboard order.

Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

Your meta description is 254 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 206 pages on tecnolite.mx and 15 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.

https://tecnolite.mx/c/MARCAS_Tecnolite_connect, https://tecnolite.mx/c/focos, https://tecnolite.mx/c/focos-inteligentes, https://tecnolite.mx/c/focos-repelente-de-insectos and https://tecnolite.mx/c/lamparas-colgantes-para-exteriores all use the title “Tecnolite”. Search engines can't tell which page to show for a search, so each competes with the others.

https://tecnolite.mx/c/MARCAS_Tecnolite_connect, https://tecnolite.mx/c/focos, https://tecnolite.mx/c/focos-inteligentes, https://tecnolite.mx/c/focos-repelente-de-insectos and https://tecnolite.mx/c/lamparas-colgantes-para-exteriores have no meta description, so Google writes the search snippet from whatever text it finds.

https://tecnolite.mx/comocomprar, https://tecnolite.mx/c/MARCAS_Tecnolite, https://tecnolite.mx/c/MARCAS_Tecnolite_connect, https://tecnolite.mx/c/focos, https://tecnolite.mx/c/focos-inteligentes and https://tecnolite.mx/c/focos-repelente-de-insectos and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://tecnolite.mx/c/MARCAS_Tecnolite, https://tecnolite.mx/c/MARCAS_Tecnolite_connect, https://tecnolite.mx/c/focos, https://tecnolite.mx/c/focos-inteligentes and https://tecnolite.mx/c/lamparas-colgantes-para-exteriores took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “TypeError: Cannot read properties of null (reading 'addEventListener')”.

1 image is served at too low a resolution for sharp phone screens.

Large scripts ship without source maps.

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: 13 trust badges. 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.

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

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 380 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight 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 11 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 25 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.