uartes.edu.ec website review

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

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

About 1.5 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 9.2 s faster on a phone.

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

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

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

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

71 KiB could be saved by minifying CSS.

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

4 third-party services load with your homepage (Google Tag Manager, AddToAny and Google Fonts and others), adding 221 KiB and 144 ms of main-thread time.

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

11 KiB could be saved by minifying JavaScript.

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.

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

Your largest element takes 34.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 220 ms to 211 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.5 MB in 209 requests on a phone: scripts 2.4 MB (77), images 2.1 MB (43) and stylesheets 1.8 MB (81). Under 2 MB keeps phones on slow connections fast.

17 images (1.4 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.

2210-FACHADA-UARTES-400x147.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

4 tap targets are too small or too close together to hit reliably with a finger.

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

Contentinfo 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 contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

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

Your meta description is only 51 characters: “Universidad de las Artes - Universidad de las Artes”. 70 to 160 characters is enough to sell the click.

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

The homepage links to 137 pages on uartes.edu.ec and 30 external pages.

There is no https://www.uartes.edu.ec/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.

https://www.uartes.edu.ec/sitio/blog/category/noticias has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.uartes.edu.ec/sitio/blog/category/noticias has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.uartes.edu.ec/sitio/la-universidad/la-universidad/campus took over 3 s to send its HTML from our server.

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

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

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

Large scripts ship without source maps.

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: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The page uses urgency cues (a countdown or limited-time wording).

Before a visitor clicks anything, the page loads Google Analytics and 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.

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