masvision.mx website review

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

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

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

8 third-party services load with your homepage (productcustomizer.com, POWr and Google Tag Manager and others), adding 1.3 MB and 1.4 s of main-thread time.

Your mobile performance score is 56 (desktop: 89). Pages that score under 90 lose visitors before the first paint.

productcustomizer.com costs a phone 581 ms of main-thread work and 24 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.

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

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

POWr costs a phone 275 ms of main-thread work and 13 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.

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

Shopify costs a phone 112 ms of main-thread work and 852 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,528 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

Desktop scores 89 but mobile only 56. A gap that wide usually means heavy scripts and images that hit phones hardest.

9 KiB could be saved by minifying JavaScript.

1 image could be 6 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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.

Your largest element takes 13.1 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 13.7 s. Good is under 3.8 s.

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

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

2 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-24, real Chrome visitors' tap response (inp) went from 149 ms to 154 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 3.5 MB in 431 requests on a phone: other files 1.4 MB (246), scripts 1.1 MB (130) and images 763 KiB (23). Under 2 MB keeps phones on slow connections fast.

50_OFT_6f9457af-e465-4c57-b86a-c567bf430feb_550x.png 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 are downloaded at several times the size a phone draws them, for example X_RBMeta_LP_tile-2.jpg at 1,312 px wide, shown at 193 px. Resized copies would save about 294 KiB.

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

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.

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

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

The homepage links to 182 pages on masvision.mx and 18 external pages.

https://www.masvision.mx/customer_authentication/redirect has no <title>, so Google invents the link text in results.

https://www.masvision.mx/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.masvision.mx/customer_authentication/redirect, https://www.masvision.mx/collections/lentes-ray-ban-meta, https://www.masvision.mx/collections/probador-virtual-de-lentes-oftalmico and https://www.masvision.mx/collections/probador-virtual-de-lentes-solares have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.masvision.mx/customer_authentication/redirect, https://www.masvision.mx/collections/mujeres-oftalmicos, https://www.masvision.mx/collections/hombres-oftalmicos, https://www.masvision.mx/collections/ninos-oftalmicos, https://www.masvision.mx/collections/lentes-ray-ban-meta and https://www.masvision.mx/collections/todos-oftalmicos and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

6 errors were logged to the browser console while the page loaded, for example “Invalid or unexpected token”.

5 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Chrome logged issues while loading the page (“Cookie”).

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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

The homepage has only about 217 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.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 2 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 27 cookies, 3 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 42 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.