Website review, no card needed

unl.edu.ec logo

unl.edu.ec website review

Visit site (opens in a new tab)Reviewed 24 October 202643 issues · 83 checks

This review found 43 issues worth fixing on unl.edu.ec, 17 of them high impact, across 83 checks. The most urgent: use efficient cache lifetimes. 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

Real-visitor load time (LCP)75th percentile, phones
1.8 s1.1 sMay 2Oct 171.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.5 s
May 9, 20261.6 s
May 16, 20261.5 s
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.3 s
Jun 13, 20261.2 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.4 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.6 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
243 ms128 msMay 2Oct 17203 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026213 ms
May 9, 2026188 ms
May 16, 2026163 ms
May 23, 2026161 ms
May 30, 2026158 ms
Jun 6, 2026147 ms
Jun 13, 2026143 ms
Jun 20, 2026141 ms
Jun 27, 2026141 ms
Jul 4, 2026157 ms
Jul 11, 2026170 ms
Jul 18, 2026178 ms
Jul 25, 2026188 ms
Aug 1, 2026196 ms
Aug 8, 2026207 ms
Aug 15, 2026222 ms
Aug 22, 2026227 ms
Aug 29, 2026225 ms
Sep 5, 2026224 ms
Sep 12, 2026223 ms
Sep 19, 2026222 ms
Sep 26, 2026228 ms
Oct 3, 2026230 ms
Oct 10, 2026214 ms
Oct 17, 2026203 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

Full-page screenshot of unl.edu.ec (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. unl.edu.ec at 0.5 s0.5 s
  2. unl.edu.ec at 1.0 s1.0 s
  3. unl.edu.ec at 1.5 s1.5 s
  4. unl.edu.ec at 2.0 s2.0 s
  5. unl.edu.ec at 2.4 s2.4 s
  6. unl.edu.ec at 2.9 s2.9 s
  7. unl.edu.ec at 3.4 s3.4 s
  8. unl.edu.ec at 3.9 s3.9 s

Speed

10 to fix56
  • Use efficient cache lifetimes

    5.1 s · 4.4 MB

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

  • Render-blocking requests

    4.6 s

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

  • Reduce unused CSS

    1.3 s · 359 KiB

    About 359 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.3 s faster on a phone.

  • Improve image delivery

    700 ms · 2.8 MB

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

  • Mobile performance score: 56

    56/100

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

  • Font display

    400 ms

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

  • Reduce unused JavaScript

    300 ms · 98 KiB

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

  • Minify JavaScript

    300 ms · 44 KiB

    44 KiB could be saved by minifying JavaScript.

  • Main-thread work: 2.8 s

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

  • 1,728 HTML elements

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and Google Analytics and others), adding 264 KiB and 242 ms of main-thread time.

  • 5 long tasks on the main thread

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

  • Minify CSS

    40 KiB

    40 KiB could be saved by minifying CSS.

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

    89 ms

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

Core Web Vitals

8 to fix67
  • 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: 11.3 s

    11.3 s

    Your largest element takes 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ADMISIONES Revisa aquí el proceso de admisión para los estu…”.

  • First Contentful Paint: 6.8 s

    6.8 s

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

  • Time to Interactive: 11.3 s

    11.3 s

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

  • Speed Index: 7.5 s

    7.5 s

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

  • Real-user INP: 247 ms

    247 ms

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

  • Real-user FCP: 2.0 s

    2.0 s

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

  • 7 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +4%

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

5 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user CLS: 0.03

    0.03

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

  • Real-user TTFB: 679 ms

    679 ms

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

  • Total Blocking Time: 170 ms

    170 ms

    Scripts block the page for only 170 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix26
  • Page weight: 4.7 MB in 120 requests

    4.7 MB

    Your homepage downloads 4.7 MB in 120 requests on a phone: images 3.7 MB (45), scripts 509 KiB (34) and stylesheets 437 KiB (34). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 2.2 MB together. On a phone connection a single image that size takes seconds.

  • 5 images far larger than shown

    1.8 MB

    5 images are downloaded at several times the size a phone draws them, for example b.jpg at 1,908 px wide, shown at 390 px. Resized copies would save about 1.8 MB.

  • 7 images in older formats

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

  • An image on the first screen is lazy-loaded

    b.jpg 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).

  • 2 images below the first screen load straight away

    2 images further down the page (82 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.3 g of CO₂ per visit

    1.33 g

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

Accessibility

4 to fix83
  • 8 images without alt text

    8 images have no alt text, which hurts accessibility and image search.

  • 7 links without text

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

  • 4 tap targets too small

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

  • 3 text elements with low contrast

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

  • No main landmark

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

SEO

5 to fixGoogle 8577
  • No H1 headline

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

  • No structured data

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

  • Meta description is long (415 characters)

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

  • No social preview image

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

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

  • 121 internal links, 242 external

    The homepage links to 121 pages on unl.edu.ec and 242 external pages.

4 checks passed
  • Title: 35 characters

    Your title is a healthy 35 characters: “Inicio Universidad Nacional de Loja”.

  • Canonical URL set

    The canonical URL is https://unl.edu.ec/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://unl.edu.ec/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://unl.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.

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 (844 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix64
  • 1 linked page is broken

    Your homepage links to https://unl.edu.ec/oferta, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 3 pages without a meta description

    https://unl.edu.ec/gaceta, https://unl.edu.ec/campus-unl and https://unl.edu.ec/unl-sostenible have no meta description, so Google writes the search snippet from whatever text it finds.

  • 5 pages share a meta description

    https://unl.edu.ec/autoridades, https://unl.edu.ec/normativa, https://unl.edu.ec/formatos, https://unl.edu.ec/preguntas-frecuentes and https://unl.edu.ec/admisiones use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://unl.edu.ec/gaceta and https://unl.edu.ec/contactenos have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

4 checks passed
  • Canonical URLs point to themselves

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

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 11 small tap targets

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

  • 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”.

  • 1 low-resolution image

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix50
  • 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.

  • No social proof

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

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

    The homepage carries about 290 words of visible text.

3 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 2 cookies set on arrival

    2

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

  • No consent tool detected

    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.

  • 7 other companies contacted

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

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 unl.edu.ec, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2025.

Stack

CMS
Drupal
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 43 issues on unl.edu.ec, including 18 speed issues, 5 SEO issues and 3 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