mtqmexico.com website review

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

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

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

22 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

6 third-party services load with your homepage (YouTube, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.2 MB and 994 ms of main-thread time.

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

YouTube costs a phone 756 ms of main-thread work and 959 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.

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

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

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

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

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.

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

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

Your largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Maximizamos el valor de tus proyectos”. Most of its time is element render delay (6.0 s).

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 12.0 MB in 60 requests on a phone: media 7.5 MB (1), images 3.0 MB (25) and scripts 1.1 MB (15). Under 2 MB keeps phones on slow connections fast.

12 images (3.2 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.

11 images further down the page (3.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

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

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

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

ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.

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

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 13 characters: “MTQ de México”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

There are 3 <h1> headlines (“Maximizamos el valor de tus proyectos”, “SERVICIOS” and “PROYECTOS”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No XML sitemap at https://mtqmexico.com/sitemap.xml, so Google discovers your pages only by following links.

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

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

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

The homepage links to 28 pages on mtqmexico.com and 4 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://mtqmexico.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.

/, https://mtqmexico.com/nosotros, https://mtqmexico.com/servicios, https://mtqmexico.com/proyectos, https://mtqmexico.com/rse and https://mtqmexico.com/carrera and 10 others all use the title “MTQ de México”. Search engines can't tell which page to show for a search, so each competes with the others.

https://mtqmexico.com/nosotros, https://mtqmexico.com/servicios, https://mtqmexico.com/proyectos, https://mtqmexico.com/rse, https://mtqmexico.com/carrera and https://mtqmexico.com/contacto and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://mtqmexico.com/contacto and https://mtqmexico.com/blog have no <h1> headline, so visitors and search engines get no clear main topic.

https://mtqmexico.com/blog and https://mtqmexico.com/proyectos/jabil took over 3 s to send their HTML from our server.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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.

Your longest form asks for 13 fields (7 required). Every extra field lowers completion.

The homepage has only about 238 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 and Google Tag Manager (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 3 cookies, 1 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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.