Website review, no card needed

u-erre.mx logo

u-erre.mx website review

Visit site (opens in a new tab)Reviewed 2 November 202634 issues · 83 checks

This review found 34 issues worth fixing on u-erre.mx, 13 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of u-erre.mx (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. u-erre.mx at 0.4 s0.4 s
  2. u-erre.mx at 0.8 s0.8 s
  3. u-erre.mx at 1.1 s1.1 s
  4. u-erre.mx at 1.5 s1.5 s
  5. u-erre.mx at 1.9 s1.9 s
  6. u-erre.mx at 2.3 s2.3 s
  7. u-erre.mx at 2.6 s2.6 s
  8. u-erre.mx at 3.0 s3.0 s

Speed

13 to fix40
  • Reduce unused JavaScript

    5.9 s · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.9 s faster on a phone.

  • Render-blocking requests

    3.8 s

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

  • Use efficient cache lifetimes

    1.6 s · 500 KiB

    18 files are served with short cache lifetimes, so returning visitors download them again (500 KiB).

  • Mobile performance score: 40

    40/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (mypurecloud.com, Sentry and Google Tag Manager and others), adding 2.4 MB and 2.0 s of main-thread time.

  • Improve image delivery

    750 ms · 240 KiB

    5 images could be 240 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

  • mypurecloud.com adds 825 ms

    825 ms

    mypurecloud.com costs a phone 825 ms of main-thread work and 1.1 MB 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

    450 ms · 76 KiB

    76 KiB could be saved by minifying JavaScript.

  • Google Tag Manager adds 358 ms

    358 ms

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

  • Sentry adds 403 ms

    403 ms

    Sentry costs a phone 403 ms of main-thread work and 41 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.

  • Main-thread work: 3.8 s

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

  • Reduce unused CSS

    300 ms · 75 KiB

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

  • 15 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 26 KiB

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

  • 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: 3 ms

    3 ms

    Your server sent the HTML in 3 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix100
  • 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: 20.2 s

    20.2 s

    Your largest element takes 20.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Inscripciones abiertas: Primavera 2027 Prepa | Licenciatura…”.

  • Time to Interactive: 23.6 s

    23.6 s

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

  • First Contentful Paint: 6.3 s

    6.3 s

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

  • Speed Index: 6.7 s

    6.7 s

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

  • Total Blocking Time: 783 ms

    783 ms

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 859 ms

    859 ms

    Real visitors wait 859 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • 7 images without width and height

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

4 checks passed
  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user INP: 166 ms

    166 ms

    Real visitors wait 166 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.02

    0.02

    For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.

  • Cumulative Layout Shift: 0.015

    0.015

    The layout barely moves while loading (CLS 0.015, good is under 0.1).

Images and page weight

2 to fix75
  • Page weight: 3.7 MB in 134 requests

    3.7 MB

    Your homepage downloads 3.7 MB in 134 requests on a phone: scripts 2.6 MB (59), images 818 KiB (41) and fonts 227 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    46 KiB

    1 image is downloaded at several times the size a phone draws it, for example revalidacion-2027-thumb.webp at 1,200 px wide, shown at 113 px. Resized copies would save about 46 KiB.

  • About 1.1 g of CO₂ per visit

    1.06 g

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

2 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.

Accessibility

4 to fixGoogle 9394
  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (22 elements)

    All page content should be contained by landmarks: 22 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.

  • 4 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 110 images in the HTML carry an alt attribute.

  • 35 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 10097
  • No social preview image

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

  • 74 internal links, 32 external

    The homepage links to 74 pages on u-erre.mx and 32 external pages.

7 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “La U-ERRE es una de las universidades en Monterrey más importantes, con nuestros programas te formamos en líder del mañ…”.

  • One H1 headline

    Your main headline reads: “Impulsa tu futuro en U-ERRE, tu universidad en Monterrey: Conoce nuestra oferta educativa.”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “U-ERRE - Bienvenidos a la Universidad Regiomontana”.

  • Canonical URL set

    The canonical URL is https://www.u-erre.mx/.

  • Structured data in place

    Structured data found: CollegeOrUniversity.

  • 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://www.u-erre.mx/sitemap.xml.

AI search readiness

1 to fix88
  • 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://www.u-erre.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 (1,140 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

Google 96100
  • 1 low-resolution image

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

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    11 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix63
  • 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 street address 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: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 961 words of copy

    The homepage carries about 961 words of visible text.

4 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager, Hotjar and HubSpot.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 0 email links.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

  • 6 trackers load before any consent

    6

    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.

  • 14 cookies set on arrival

    14

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

  • 40 other companies contacted

    Loading the homepage contacts 40 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 u-erre.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
Webflow
Framework
jQuery
Analytics
Google Tag Manager | Hotjar
Hosting
Webflow

Company

Founded
1969

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on u-erre.mx, including 22 speed issues, 1 SEO issue 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25