Website review, no card needed
uinter.mx website review
Visit site (opens in a new tab)Reviewed 25 October 202645 issues · 88 checks
This review found 45 issues worth fixing on uinter.mx, 19 of them high impact, across 88 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
56FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.6 s |
| May 9, 2026 | 2.6 s |
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.6 s |
| Aug 22, 2026 | 2.9 s |
| Sep 19, 2026 | 2.8 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 3.0 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 3.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 173 ms |
| Jun 6, 2026 | 142 ms |
| Jul 11, 2026 | 186 ms |
| Jul 25, 2026 | 183 ms |
| Aug 1, 2026 | 182 ms |
| Aug 8, 2026 | 190 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
16.9 s · 12.2 MB13 images could be 12.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 16.9 s faster on a phone.
Use efficient cache lifetimes
3.3 s · 2.9 MB92 files are served with short cache lifetimes, so returning visitors download them again (2.9 MB).
Render-blocking requests
2.6 s41 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.6 s.
Reduce unused JavaScript
1.5 s · 831 KiBAbout 831 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Mobile performance score: 31
31/100Your mobile performance score is 31 (desktop: 42). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.6 s
A phone's processor spends 6.6 s on main-thread work while loading, 3.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 (hsappstatic.net, Hubspot and Google Tag Manager and others), adding 2.0 MB and 2.4 s of main-thread time.
hsappstatic.net adds 844 ms
844 mshsappstatic.net costs a phone 844 ms of main-thread work and 713 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.
Hubspot adds 632 ms
632 msHubspot costs a phone 632 ms of main-thread work and 346 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 529 ms
529 msGoogle Tag Manager costs a phone 529 ms of main-thread work and 501 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 542 ms. During a long task the page ignores taps.
Facebook adds 382 ms
382 msFacebook costs a phone 382 ms of main-thread work and 252 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.
Reduce unused CSS
73 KiBAbout 73 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
26 KiBPolyfills for old browsers add 26 KiB JavaScript that modern phones do not need.
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.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 408 ms
408 msYour server sent the HTML in 408 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.
Largest Contentful Paint: 78.0 s
78.0 sYour largest element takes 78.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 82.9 s
82.9 sThe page becomes fully interactive after 82.9 s. Good is under 3.8 s.
Total Blocking Time: 2.1 s
2.1 sScripts block taps and scrolling for 2.1 s in total while the page loads. Good is under 200 ms.
Speed Index: 9.9 s
9.9 sVisually, the page fills in at 9.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.14
0.14For real visitors the layout shifts by 0.14 (75th percentile). Good is under 0.1.
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.6 s
1.6 sReal visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 173 ms to 190 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.6 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Cumulative Layout Shift: 0.097
0.097The layout barely moves while loading (CLS 0.097, good is under 0.1).
Images and page weight
6 images over 500 KB
6 images weigh 29.4 MB together. On a phone connection a single image that size takes seconds.
Page weight: 25.6 MB in 147 requests
25.6 MBYour homepage downloads 25.6 MB in 147 requests on a phone: images 23.2 MB (27), scripts 2.0 MB (54) and stylesheets 193 KiB (44). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
7.1 MB1 image is downloaded at several times the size a phone draws it, for example FINAL-OK-REALS-4.png at 3,375 px wide, shown at 342 px. Resized copies would save about 7.1 MB.
7 images in older formats
7 images (29.5 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.
5 images below the first screen load straight away
5 images further down the page (28.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 7.3 g of CO₂ per visit
7.25 gBy the Sustainable Web Design model, a visit to your homepage emits about 7.25 g of CO₂e: 870.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
8 text elements with low contrast
8 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 (59 elements)
All page content should be contained by landmarks: 59 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Headings skip levels
Headings skip levels (h1 → h3, h1 → h3 and h3 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 24 images in the HTML carry an alt attribute.
39 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: 39 passed and 5 failed. 3 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 long (82 characters)
Your title is 82 characters, so Google will cut it off around 60: “Universidad UINTER - Universidad Internacional del Liderazgo y Desarrollo | UINTER”.
2 H1 headlines
There are 2 <h1> headlines (“Formamos Profesionales Con Estándares Internacion…” and “Formamos Profesionales Con Estándares Internacion…”). One clear main headline is easier for people and search engines.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
63 internal links, 17 external
The homepage links to 63 pages on uinter.mx and 17 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://uinter.mx/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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://uinter.mx/sitemap_index.xml.
AI search readiness
4 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (978 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://uinter.mx/llms.txt (2 KiB, 22 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without a meta description
https://uinter.mx/quienes-somos, https://uinter.mx/politica-de-calidad, https://uinter.mx/preparatoria-uinter, https://uinter.mx/carreras-uinter, https://uinter.mx/mba-uinter and https://uinter.mx/educacion-continua and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://uinter.mx/contact, whose canonical is https://uinter.mx/contacto-uinter. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
4 pages slow to respond
https://uinter.mx/mba-uinter, https://uinter.mx/blog-uinter, https://uinter.mx/contact and https://uinter.mx/licenciatura-en-mercadotecnia-y-negocios-internacionales took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 18 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
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 12 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
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.
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.
Thin social proof
Social proof on the homepage: 4 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.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 720 words of copy
The homepage carries about 720 words of visible text.
2 checks passed
Analytics in place
Analytics detected: Google Analytics and HubSpot.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel (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.
9 cookies set on arrival
9Opening the homepage sets 9 cookies (measured from a US location before any click).
28 other companies contacted
Loading the homepage contacts 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) loads with the page.
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 uinter.mx, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on uinter.mx, including 23 speed issues, 4 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.