umh.es website review

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

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

YouTube costs a phone 2.7 s of main-thread work and 18.4 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

3 third-party services load with your homepage (YouTube, Google Fonts and Google/Doubleclick Ads), adding 19.4 MB and 2.8 s of main-thread time.

35 images could be 3.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

12 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

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

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

9 KiB could be saved by minifying CSS.

The page has 2,472 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Google Fonts costs a phone 3 ms of main-thread work and 1.0 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.

4 KiB could be saved by minifying JavaScript.

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

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

Your largest element takes 177.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Agenda. Conoce los eventos de tu universidad”.

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

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

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

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

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

Your homepage downloads 272.5 MB in 752 requests on a phone: images 251.5 MB (530), scripts 15.8 MB (77) and stylesheets 1.9 MB (65). Under 2 MB keeps phones on slow connections fast.

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

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails 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.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

Your title is only 22 characters: “UMH - Página principal”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 37 characters: “Universidad Miguel Hernández de Elche”. 70 to 160 characters is enough to sell the click.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://www.umh.es/sitemap.xml, so Google discovers your pages only by following links.

11 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 132 pages on umh.es and 224 external pages.

Your robots.txt shuts out ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

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.

There is no https://www.umh.es/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.

robots.txt blocks GPTBot, ClaudeBot and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

https://www.umh.es/contenido/Estudios/:Grado/datos_es.html, https://www.umh.es/contenido/Estudios/:Master_Oficial/datos_es.html, https://www.umh.es/contenido/Estudios/:Doctorado/datos_es.html, https://www.umh.es/contenido/Estudios/:Escuela_Facultad/datos_es.html, https://www.umh.es/contenido/Estudios/:Otros_estudios/datos_es.html and https://www.umh.es/contenido/Estudios/:ServiciosEstudiantes/datos_es.html and 9 others all use the title “UMH - Universidad Miguel Hernández”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.umh.es/contenido/Estudios/:Grado/datos_es.html, https://www.umh.es/contenido/Estudios/:Master_Oficial/datos_es.html, https://www.umh.es/contenido/Estudios/:Doctorado/datos_es.html, https://www.umh.es/contenido/Estudios/:Escuela_Facultad/datos_es.html, https://www.umh.es/contenido/Estudios/:Otros_estudios/datos_es.html and https://www.umh.es/contenido/Estudios/:ServiciosEstudiantes/datos_es.html and 9 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 9 pages by a URL that isn't their canonical one, for example https://www.umh.es/contenido/Investigacion/:Instituto_Investigacion/datos_es.html, whose canonical is https://www.umh.es/contenido/Estudios/:Instituto_Investigacion/datos_es.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

14 of 32 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

Chrome logged issues while loading the page (“Cookie”).

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.

Social proof on the homepage: 7 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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 3 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.