itam.mx website review

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

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

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

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

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

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

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

137 KiB could be saved by minifying JavaScript.

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

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

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

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

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

Polyfills for old browsers add 26 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

25 KiB could be saved by minifying CSS.

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

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.

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

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

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

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

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

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

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

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

8 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 138 ms to 163 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 3.5 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 16.4 MB in 178 requests on a phone: images 14.1 MB (33), scripts 1.8 MB (73) and stylesheets 319 KiB (49). Under 2 MB keeps phones on slow connections fast.

2 images weigh 3.0 MB together. On a phone connection a single image that size takes seconds.

9 images (4.4 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.

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

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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.

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

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

Your title is only 24 characters: “Bienvenido a ITAM | ITAM”. 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 6 <h1> headlines (“El ITAM es”, “Su misión es” and “Investigación, docencia y extensión”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 184 pages on itam.mx and 350 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.itam.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.

/ and https://www.itam.mx/es all use the title “Bienvenido a ITAM | ITAM”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.itam.mx/es/1/contenido/rio-hondo, https://www.itam.mx/es/1/contenido/santa-teresa, https://www.itam.mx/es/comunicados-oficiales, https://www.itam.mx/en, https://www.itam.mx/es and https://www.itam.mx/es/1/paginas/rectoria and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://www.itam.mx/en, whose canonical is https://www.itam.mx/en/node. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.itam.mx/es/1/contenido/rio-hondo, https://www.itam.mx/es/1/contenido/santa-teresa, https://www.itam.mx/es/alumnos-de-nuevo-ingreso-itam, https://www.itam.mx/es/comunicados-oficiales, https://www.itam.mx/es/medidas-del-itam-ante-el-covid-19 and https://www.itam.mx/es/preguntas-frecuentes and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

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

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 14 cookies (measured from a US location before any click).

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