Website review, no card needed
iteso.mx website review
Visit site (opens in a new tab)Reviewed 27 October 202659 issues · 97 checks
This review found 59 issues worth fixing on iteso.mx, 31 of them high impact, across 97 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
60DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.8 s |
| May 16, 2026 | 3.7 s |
| May 23, 2026 | 3.7 s |
| May 30, 2026 | 3.7 s |
| Jun 6, 2026 | 3.8 s |
| Jun 13, 2026 | 3.8 s |
| Jun 20, 2026 | 3.9 s |
| Jun 27, 2026 | 4.0 s |
| Jul 4, 2026 | 4.1 s |
| Jul 11, 2026 | 4.0 s |
| Jul 18, 2026 | 4.0 s |
| Jul 25, 2026 | 3.8 s |
| Aug 1, 2026 | 3.6 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.6 s |
| Aug 22, 2026 | 3.6 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.4 s |
| Sep 12, 2026 | 3.4 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.6 s |
| Oct 17, 2026 | 3.6 s |
| Oct 24, 2026 | 3.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 119 ms |
| May 16, 2026 | 114 ms |
| May 23, 2026 | 115 ms |
| May 30, 2026 | 110 ms |
| Jun 6, 2026 | 108 ms |
| Jun 13, 2026 | 111 ms |
| Jun 20, 2026 | 110 ms |
| Jun 27, 2026 | 113 ms |
| Jul 4, 2026 | 115 ms |
| Jul 11, 2026 | 115 ms |
| Jul 18, 2026 | 119 ms |
| Jul 25, 2026 | 123 ms |
| Aug 1, 2026 | 119 ms |
| Aug 8, 2026 | 126 ms |
| Aug 15, 2026 | 128 ms |
| Aug 22, 2026 | 127 ms |
| Aug 29, 2026 | 127 ms |
| Sep 5, 2026 | 128 ms |
| Sep 12, 2026 | 127 ms |
| Sep 19, 2026 | 127 ms |
| Sep 26, 2026 | 127 ms |
| Oct 3, 2026 | 127 ms |
| Oct 10, 2026 | 129 ms |
| Oct 17, 2026 | 130 ms |
| Oct 24, 2026 | 130 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Improve image delivery
14.1 s · 14.7 MB39 images could be 14.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 14.1 s faster on a phone.
Render-blocking requests
10.9 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 10.9 s.
Reduce unused CSS
8.0 s · 1.3 MBAbout 1.3 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 8.0 s faster on a phone.
Use efficient cache lifetimes
5.8 s · 1.4 MB17 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).
Reduce unused JavaScript
4.7 s · 1.6 MBAbout 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.7 s faster on a phone.
Minify CSS
1.1 s · 219 KiB219 KiB could be saved by minifying CSS.
Mobile performance score: 28
28/100Your mobile performance score is 28 (desktop: 16). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.0 s
A phone's processor spends 5.0 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, YouTube and Facebook and others), adding 1.8 MB and 1.6 s of main-thread time.
YouTube adds 615 ms
615 msYouTube costs a phone 615 ms of main-thread work and 994 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 adds 660 ms
660 msGoogle Tag Manager costs a phone 660 ms of main-thread work and 522 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.
Minify JavaScript
600 ms · 102 KiB102 KiB could be saved by minifying JavaScript.
Font display
500 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 500 ms).
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 260 ms. During a long task the page ignores taps.
2,243 HTML elements
The page has 2,243 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Document request latency
181 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
7 KiB7 KiB JavaScript is shipped twice across bundles.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 211 ms
211 msYour server sent the HTML in 211 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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-user LCP: 4.9 s
4.9 sReal visitors wait 4.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.55
0.55For real visitors the layout shifts by 0.55 (75th percentile). Good is under 0.1.
First Contentful Paint: 12.9 s
12.9 sThe first text or image appears after 12.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 44.6 s
44.6 sYour largest element takes 44.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Posgrados CONOCE MÁS”.
Speed Index: 20.1 s
20.1 sVisually, the page fills in at 20.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 75.9 s
75.9 sThe page becomes fully interactive after 75.9 s. Good is under 3.8 s.
Total Blocking Time: 850 ms
850 msScripts block taps and scrolling for 850 ms in total while the page loads. Good is under 200 ms.
Real-user FCP: 2.5 s
2.5 sReal visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.164
0.164The layout shifts by 0.164 while loading, so content jumps under the reader's thumb. Good is under 0.1.
6 images without width and height
6 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 119 ms to 130 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.8 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 130 ms
130 msReal visitors wait 130 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 716 ms
716 msReal visitors wait 716 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 25.5 MB in 184 requests
25.5 MBYour homepage downloads 25.5 MB in 184 requests on a phone: images 19.2 MB (68), scripts 3.4 MB (72) and stylesheets 1.3 MB (11). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 2.3 MB together. On a phone connection a single image that size takes seconds.
3 images far larger than shown
1.3 MB3 images are downloaded at several times the size a phone draws them, for example 26b_he_2560-x450px_lanza_ at 5,333 px wide, shown at 390 px. Resized copies would save about 1.3 MB.
9 images in older formats
9 images (3.1 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.
4 images below the first screen load straight away
4 images further down the page (280 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 7.2 g of CO₂ per visit
7.23 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.23 g of CO₂e: 867.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
17 buttons without a name
17 buttons have no accessible name, so screen readers announce just “button”.
16 tap targets too small
16 tap targets are too small or too close together to hit reliably with a finger.
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
15 links without text
15 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5, h1 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 9 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (5 characters)
Your title is only 5 characters: “ITESO”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
34 H1 headlines
There are 34 <h1> headlines (“NOTICIAS PRINCIPALES”, “ACTIVIDADES” and “PUBLICACIONES”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image (also missing: og:title), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
98 internal links, 135 external
The homepage links to 98 pages on iteso.mx and 135 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://www.iteso.mx/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://iteso.mx/sitemap.xml.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://iteso.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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (963 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://iteso.mx/c/portal/update_language, which answers with an error. Visitors hit a dead end and search engines drop it.
1 page without a title
https://iteso.mx/documents/d/publicaciones/convocatoria-para-dossier-n5-docx has no <title>, so Google invents the link text in results.
5 pages point its canonical at the homepage
https://iteso.mx/conocenos, https://iteso.mx/aspirantes, https://iteso.mx/familias, https://iteso.mx/contacto and https://iteso.mx/programas declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
9 pages share 2 titles
/, https://iteso.mx/conocenos, https://iteso.mx/aspirantes, https://iteso.mx/familias, https://iteso.mx/contacto and https://iteso.mx/programas all use the title “ITESO”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
13 pages without a meta description
https://iteso.mx/conocenos, https://iteso.mx/aspirantes, https://iteso.mx/web/internacional/visiting_students, https://iteso.mx/familias, https://iteso.mx/contacto and https://iteso.mx/programas and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://iteso.mx/web/iteso/acompanamiento and https://iteso.mx/documents/d/publicaciones/convocatoria-para-dossier-n5-docx have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://iteso.mx/web/radio has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 30 found) and read each the way a search engine does.
1 checks passed
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
19 small tap targets
19 of 38 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
4 distorted images
4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 620 words of copy
The homepage carries about 620 words of visible text.
3 checks passed
3 short forms
3 short forms (0 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
12 cookies set on arrival
12Opening the homepage sets 12 cookies, 1 of them by other companies (measured from a US location before any click).
No consent tool detected
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.
17 other companies contacted
Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at iteso.mx, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- React
- Analytics
- Google Tag Manager
- Hosting
- Iteso, A.C.
Company
- Employees
- 3,158
- Founded
- 1957
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 59 issues on iteso.mx, including 26 speed issues, 5 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.