uabc.mx website review

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

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

12 images could be 621 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.

Your mobile performance score is 61 (desktop: 86). Pages that score under 90 lose visitors before the first paint.

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

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

About 55 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

6 KiB could be saved by minifying JavaScript.

Desktop scores 86 but mobile only 61. A gap that wide usually means heavy scripts and images that hit phones hardest.

1 third-party service load with your homepage (Google Fonts), adding 65 KiB and 0 ms of main-thread time.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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.

Your largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “UABC conmemora 50 años de egreso de la segunda generación d…”. Most of its time is resource load delay (4.9 s).

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

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

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

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

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

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

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

9 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-17, real Chrome visitors' tap response (inp) went from 271 ms to 270 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 images are downloaded at several times the size a phone draws them, for example 1-2.jpg at 1,600 px wide, shown at 370 px. Resized copies would save about 318 KiB.

5 images (509 KiB) 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.

1 image further down the page (53 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

7 elements hidden from screen readers can still receive keyboard focus.

2 elements have a tabindex above 0, which scrambles the keyboard order.

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your meta description is 852 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 121 pages on uabc.mx and 19 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

Your homepage links to https://www.uabc.mx/Egresados, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.uabc.mx/Admisiones, https://www.uabc.mx/PortalDelAlumno, https://www.uabc.mx/PortalAcademico, https://www.uabc.mx/ConsejoUniversitario, https://www.uabc.mx/PatronatoUniversitario and https://www.uabc.mx/TribunalUniversitario have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.uabc.mx/oferta-educativa-programas-de-posgrado, https://www.uabc.mx/historia-de-la-uabc, https://www.uabc.mx/mensaje-del-rector, https://www.uabc.mx/acerca-de-mision-y-vision, https://www.uabc.mx/acerca-de-rectoria and https://www.uabc.mx/acerca-de-unidades-academicas and 1 other use the same meta description. A description written for each page earns more clicks.

https://www.uabc.mx/oferta-educativa-programas-de-posgrado, https://www.uabc.mx/en/uabc-2, https://www.uabc.mx/historia-de-la-uabc, https://www.uabc.mx/mensaje-del-rector, https://www.uabc.mx/acerca-de-mision-y-vision and https://www.uabc.mx/acerca-de-rectoria and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.uabc.mx/TribunalUniversitario 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.

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

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

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

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

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.

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