Website review, no card needed

aiep.cl logo

aiep.cl website review

Visit site (opens in a new tab)Reviewed 18 October 202646 issues · 89 checks

This review found 46 issues worth fixing on aiep.cl, 23 of them high impact, across 89 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
3.1 s2.1 sApr 25Oct 102.9 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.2 s
May 2, 20262.2 s
May 9, 20262.2 s
May 16, 20262.4 s
May 23, 20262.5 s
May 30, 20262.7 s
Jun 6, 20262.8 s
Jun 13, 20262.8 s
Jun 20, 20262.9 s
Jun 27, 20262.9 s
Jul 4, 20262.9 s
Jul 11, 20262.8 s
Jul 18, 20262.7 s
Jul 25, 20262.7 s
Aug 1, 20262.7 s
Aug 8, 20262.7 s
Aug 15, 20262.8 s
Aug 22, 20262.7 s
Aug 29, 20262.6 s
Sep 5, 20262.5 s
Sep 12, 20262.4 s
Sep 19, 20262.4 s
Sep 26, 20262.6 s
Oct 3, 20262.8 s
Oct 10, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
453 ms313 msApr 25Oct 10437 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026349 ms
May 2, 2026339 ms
May 9, 2026330 ms
May 16, 2026329 ms
May 23, 2026338 ms
May 30, 2026351 ms
Jun 6, 2026363 ms
Jun 13, 2026373 ms
Jun 20, 2026375 ms
Jun 27, 2026378 ms
Jul 4, 2026377 ms
Jul 11, 2026374 ms
Jul 18, 2026375 ms
Jul 25, 2026378 ms
Aug 1, 2026386 ms
Aug 8, 2026387 ms
Aug 15, 2026389 ms
Aug 22, 2026387 ms
Aug 29, 2026382 ms
Sep 5, 2026381 ms
Sep 12, 2026385 ms
Sep 19, 2026395 ms
Sep 26, 2026411 ms
Oct 3, 2026427 ms
Oct 10, 2026437 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 aiep.cl (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. aiep.cl at 0.8 s0.8 s
  2. aiep.cl at 1.5 s1.5 s
  3. aiep.cl at 2.3 s2.3 s
  4. aiep.cl at 3.1 s3.1 s
  5. aiep.cl at 3.9 s3.9 s
  6. aiep.cl at 4.6 s4.6 s
  7. aiep.cl at 5.4 s5.4 s
  8. aiep.cl at 6.2 s6.2 s

Speed

14 to fix35
  • Use efficient cache lifetimes

    7.6 s · 4.4 MB

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

  • Reduce unused JavaScript

    3.3 s · 1.9 MB

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

  • Improve image delivery

    1.8 s · 2.2 MB

    13 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.8 s faster on a phone.

  • Render-blocking requests

    3.3 s

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

  • Google Tag Manager adds 1.7 s

    1.7 s

    Google Tag Manager costs a phone 1.7 s of main-thread work and 2.2 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.

  • Mobile performance score: 35

    35/100

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

  • Main-thread work: 6.2 s

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

  • 5,047 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, TikTok and Google CDN and others), adding 4.0 MB and 3.0 s of main-thread time.

  • Reduce unused CSS

    600 ms · 127 KiB

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

  • TikTok adds 365 ms

    365 ms

    TikTok costs a phone 365 ms of main-thread work and 405 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.

  • Google CDN adds 257 ms

    257 ms

    Google CDN costs a phone 257 ms of main-thread work and 730 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.

  • Facebook adds 253 ms

    253 ms

    Facebook costs a phone 253 ms of main-thread work and 234 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.

  • VWO adds 41 ms

    41 ms

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

  • 20 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    40 KiB

    Polyfills for old browsers add 40 KiB JavaScript that modern phones do not need.

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

    303 ms

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

Core Web Vitals

10 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: 18.3 s

    18.3 s

    Your largest element takes 18.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Admisión 2027 Más de 90 carreras. Distintas formas de estud…”.

  • Time to Interactive: 39.0 s

    39.0 s

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

  • Total Blocking Time: 1.5 s

    1.5 s

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

  • Speed Index: 8.1 s

    8.1 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • Real-user INP: 307 ms

    307 ms

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

  • Tap response (INP) got 26% slower for real visitors

    +26%

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

  • Largest content (LCP) got 31% slower for real visitors

    +31%

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

  • 27 images without width and height

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

5 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 466 ms

    466 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix53
  • Page weight: 10.6 MB in 214 requests

    10.6 MB

    Your homepage downloads 10.6 MB in 214 requests on a phone: images 5.6 MB (69), scripts 4.0 MB (68) and other files 651 KiB (61). Under 2 MB keeps phones on slow connections fast.

  • 8 images in older formats

    8 images (1.7 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.

  • 11 images below the first screen load straight away

    11 images further down the page (1.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.0 g of CO₂ per visit

    2.99 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

8 to fixGoogle 8390
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • Orphan list items

    Some list items are not inside a list.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Page should contain a level-one heading (1 element)

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

  • All page content should be contained by landmarks (1 element)

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

  • 8 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • ARIA role should be appropriate for the element (8 elements)

    ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 42 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 8 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 10090
  • No H1 headline

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

  • 639 internal links, 18 external

    The homepage links to 639 pages on aiep.cl and 18 external pages.

7 checks passed
  • Meta description: 126 characters

    Your meta description is 126 characters: “Estudia de forma flexible en AIEP, en donde podrás elegir entre carreras online, híbridas y presenciales. Matrículas ab…”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Matrículas 2027 | AIEP | Carreras Técnicas y Profesionales”.

  • Canonical URL set

    The canonical URL is https://www.aiep.cl/.

  • Structured data in place

    Structured data found: Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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.aiep.cl/sitemap_index.xml.

AI search readiness

1 to fix83
  • Parts of the site are closed to 3 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

3 checks passed
  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (3,538 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.aiep.cl/llms.txt (2 KiB, 0 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix86
  • 2 pages share a title

    https://www.aiep.cl/admision/por-que-aiep and https://www.aiep.cl/por-que-aiep all use the title “¿Por qué estudiar en AIEP? | Admisión 2027”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages share a meta description

    https://www.aiep.cl/admision/por-que-aiep and https://www.aiep.cl/por-que-aiep use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.aiep.cl/por-que-aiep, whose canonical is https://www.aiep.cl/admision/por-que-aiep. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

3 to fixGoogle 9271
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=355037375&Ver=2&mid=9012466e-c616-4ed0-83dd-38de991f618e&bo=1&sid=8e024540caa811f18820f701a50d22c2&vid=8e0257e0caa811f191886f372a827535&vids=1&msclkid=N&pi=918639831&l.

  • 23 small tap targets

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

  • 3 JavaScript errors while loading

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

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 731 words of copy

    The homepage carries about 731 words of visible text.

3 checks passed
  • 2 short forms

    2 short forms (3 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Hotjar and HubSpot.

  • Direct contact links

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

Privacy and tracking

  • 11 trackers load before any consent

    11

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and HubSpot and 6 mores (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.

  • 35 cookies set on arrival

    35

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

  • 45 other companies contacted

    Loading the homepage contacts 45 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 aiep.cl, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager | Hotjar

Company

Founded
1960

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on aiep.cl, including 24 speed issues, 1 SEO issue 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