Website review, no card needed
cumbresmexico.com website review
Visit site (opens in a new tab)Reviewed 21 October 202628 issues · 78 checks
This review found 28 issues worth fixing on cumbresmexico.com, 11 of them high impact, across 78 checks. The most urgent: reduce unused JavaScript. 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.1 s |
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.8 s |
| Aug 1, 2026 | 4.0 s |
| Aug 8, 2026 | 3.9 s |
| Aug 15, 2026 | 3.9 s |
| Aug 22, 2026 | 3.9 s |
| Aug 29, 2026 | 3.6 s |
| Sep 5, 2026 | 3.4 s |
| Sep 12, 2026 | 3.4 s |
| Sep 19, 2026 | 3.5 s |
| Sep 26, 2026 | 3.4 s |
| Oct 3, 2026 | 3.3 s |
| Oct 10, 2026 | 3.3 s |
| Oct 17, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 198 ms |
| May 9, 2026 | 236 ms |
| May 16, 2026 | 156 ms |
| May 23, 2026 | 304 ms |
| May 30, 2026 | 293 ms |
| Jun 6, 2026 | 287 ms |
| Jun 13, 2026 | 287 ms |
| Jun 20, 2026 | 278 ms |
| Jun 27, 2026 | 255 ms |
| Jul 4, 2026 | 223 ms |
| Jul 11, 2026 | 191 ms |
| Jul 18, 2026 | 129 ms |
| Jul 25, 2026 | 117 ms |
| Aug 1, 2026 | 115 ms |
| Aug 15, 2026 | 123 ms |
| Aug 22, 2026 | 121 ms |
| Aug 29, 2026 | 120 ms |
| Sep 5, 2026 | 108 ms |
| Sep 12, 2026 | 112 ms |
| Sep 19, 2026 | 112 ms |
| Sep 26, 2026 | 112 ms |
| Oct 3, 2026 | 112 ms |
| Oct 10, 2026 | 111 ms |
| Oct 17, 2026 | 102 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
How it loaded on a phone
0.6 s
1.3 s
1.9 s
2.6 s
3.2 s
3.8 s
4.5 s
5.1 s
Speed
Reduce unused JavaScript
5.0 s · 959 KiBAbout 959 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.0 s faster on a phone.
Render-blocking requests
1.9 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Use efficient cache lifetimes
900 ms · 192 KiB8 files are served with short cache lifetimes, so returning visitors download them again (192 KiB).
Mobile performance score: 56
56/100Your mobile performance score is 56 (desktop: 86). Pages that score under 90 lose visitors before the first paint.
Legacy JavaScript
150 ms · 13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 130 ms. During a long task the page ignores taps.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, Azure Web Services and Cloudflare CDN and others), adding 278 KiB and 65 ms of main-thread time.
Improve image delivery
16 KiB1 image could be 16 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Phones get a much slower page than desktops
Desktop scores 86 but mobile only 56. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 702 ms of it running JavaScript. That is comfortably low.
Server response: 33 ms
33 msYour server sent the HTML in 33 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.
First Contentful Paint: 8.7 s
8.7 sThe first text or image appears after 8.7 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 13.6 s
13.6 sYour largest element takes 13.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Usamos cookies para mejorar tu experiencia y medir el uso d…”.
Time to Interactive: 13.6 s
13.6 sThe page becomes fully interactive after 13.6 s. Good is under 3.8 s.
Speed Index: 8.7 s
8.7 sVisually, the page fills in at 8.7 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest content (LCP) got 41% slower for real visitors
+41%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
4 checks passed
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Tap response (INP) got 51% faster for real visitors
-51%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 198 ms to 102 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 116 ms
116 msScripts block the page for only 116 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.0 MB in 76 requests
2.0 MBYour homepage downloads 2.0 MB in 76 requests on a phone: scripts 1.5 MB (32), fonts 268 KiB (9) and images 89 KiB (7). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.58 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.58 g of CO₂e: 69.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
12 text elements with low contrast
12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
[role]s are not contained by their required parent element
[role]s are not contained by their required parent element (1 element).
All page content should be contained by landmarks (31 elements)
All page content should be contained by landmarks: 31 elements on the page fail this check, rated moderate by axe-core.
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.
2 checks passed
Every image has alt text
All 27 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 3 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
36 internal links, 12 external
The homepage links to 36 pages on cumbresmexico.com and 12 external pages.
8 checks passed
Meta description: 159 characters
Your meta description is 159 characters: “Somos un colegio privado en CDMX, parte de la Red de Colegios Semper Altius y nuestra misión es formar personas íntegra…”.
One H1 headline
Your main headline reads: “CELEBRAMOS LOS TALENTOS DE CADA ALUMNO”.
Title: 53 characters
Your title is a healthy 53 characters: “Colegio privado Cumbres International School México📚”.
Canonical URL set
The canonical URL is https://www.cumbresmexico.com/.
Structured data in place
Structured data found: EducationalOrganization, LocalBusiness and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://cumbresmexico.com/sitemap.xml.
AI search readiness
Parts of the site are closed to 4 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User), Perplexity (PerplexityBot) and Perplexity (Perplexity-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.
3 checks passed
Organization data: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (628 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.cumbresmexico.com/llms.txt (5 KiB, 21 links), a plain-text guide to the site for AI tools.
Other pages
4 pages share 2 titles
/ and https://www.cumbresmexico.com/en all use the title “Colegio privado Cumbres International School México📚”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://www.cumbresmexico.com/novedades and https://www.cumbresmexico.com/blog use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.cumbresmexico.com/blog, whose canonical is https://www.cumbresmexico.com/novedades. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.cumbresmexico.com/tour-virtual has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 small tap targets
3 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Missing source maps
Large scripts ship without source maps.
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.
Thin social proof
Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 592 words of copy
The homepage carries about 592 words of visible text.
4 checks passed
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 3 phone links and 3 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads 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.
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.
6 other companies contacted
Loading the homepage contacts 6 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 cumbresmexico.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- Google Tag Manager
- Hosting
- Netlify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on cumbresmexico.com, including 12 speed issues and 3 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.