Website review, no card needed
aip.edu.pa website review
Visit site (opens in a new tab)Reviewed 18 October 202641 issues · 90 checks
This review found 41 issues worth fixing on aip.edu.pa, 18 of them high impact, across 90 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
69DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 3.0 s |
| May 2, 2026 | 2.9 s |
| May 9, 2026 | 3.0 s |
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.8 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 3.1 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 3.2 s |
| Jul 25, 2026 | 2.9 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 2.9 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 3.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 118 ms |
| May 2, 2026 | 118 ms |
| May 9, 2026 | 119 ms |
| May 16, 2026 | 117 ms |
| May 23, 2026 | 115 ms |
| May 30, 2026 | 104 ms |
| Jun 6, 2026 | 103 ms |
| Jun 13, 2026 | 110 ms |
| Jun 20, 2026 | 105 ms |
| Jun 27, 2026 | 120 ms |
| Jul 4, 2026 | 119 ms |
| Jul 11, 2026 | 120 ms |
| Jul 18, 2026 | 120 ms |
| Jul 25, 2026 | 112 ms |
| Aug 1, 2026 | 111 ms |
| Aug 8, 2026 | 100 ms |
| Aug 15, 2026 | 94 ms |
| Aug 22, 2026 | 103 ms |
| Aug 29, 2026 | 111 ms |
| Sep 5, 2026 | 116 ms |
| Sep 12, 2026 | 128 ms |
| Sep 19, 2026 | 125 ms |
| Sep 26, 2026 | 117 ms |
| Oct 3, 2026 | 120 ms |
| Oct 10, 2026 | 112 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
Speed
Reduce unused JavaScript
5.3 s · 752 KiBAbout 752 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.3 s faster on a phone.
Improve image delivery
3.5 s · 1.4 MB7 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.5 s faster on a phone.
Render-blocking requests
4.5 s46 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.5 s.
Reduce unused CSS
1.4 s · 239 KiBAbout 239 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Main-thread work: 4.3 s
A phone's processor spends 4.3 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 50
50/100Your mobile performance score is 50 (desktop: 48). Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
800 ms · 183 KiB6 files are served with short cache lifetimes, so returning visitors download them again (183 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Google Tag Manager and Google Maps and others), adding 1.2 MB and 751 ms of main-thread time.
Google CDN adds 444 ms
444 msGoogle CDN costs a phone 444 ms of main-thread work and 742 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.
2,047 HTML elements
The page has 2,047 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 27 KiBPolyfills for old browsers add 27 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify CSS
150 ms · 23 KiB23 KiB could be saved by minifying CSS.
Minify JavaScript
160 ms · 10 KiB10 KiB could be saved by minifying JavaScript.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 150 ms. During a long task the page ignores taps.
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: 20 ms
20 msYour server sent the HTML in 20 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Real-user LCP: 4.6 s
4.6 sReal visitors wait 4.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
First Contentful Paint: 12.0 s
12.0 sThe first text or image appears after 12.0 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 52.1 s
52.1 sYour largest element takes 52.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 19.2 s
19.2 sVisually, the page fills in at 19.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 52.7 s
52.7 sThe page becomes fully interactive after 52.7 s. Good is under 3.8 s.
Real-user CLS: 0.24
0.24For real visitors the layout shifts by 0.24 (75th percentile). Good is under 0.1.
Total Blocking Time: 273 ms
273 msScripts block taps and scrolling for 273 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 118 ms to 112 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 3.0 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 131 ms
131 msReal visitors wait 131 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 784 ms
784 msReal visitors wait 784 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 15.6 MB in 212 requests
15.6 MBYour homepage downloads 15.6 MB in 212 requests on a phone: images 12.6 MB (65), scripts 1.8 MB (77) and other files 481 KiB (16). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 4.4 MB together. On a phone connection a single image that size takes seconds.
10 images in older formats
10 images (6.0 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.
4 images below the first screen load straight away
4 images further down the page (190 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 4.4 g of CO₂ per visit
4.42 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.42 g of CO₂e: 530.0 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
27 text elements with low contrast
27 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
22 tap targets too small
22 tap targets are too small or too close together to hit reliably with a finger.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
All page content should be contained by landmarks (80 elements)
All page content should be contained by landmarks: 80 elements on the page fail this check, rated moderate by axe-core.
No main landmark
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)
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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
3 links without text
3 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.
Headings skip levels
Headings skip levels (h2 → h6 and h2 → h6), which makes the page harder to scan with a screen reader.
<td> elements in a large <table> do not have table headers.
<td> elements in a large <table> do not have table headers. (1 element).
2 checks passed
Every image has alt text
All 97 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
101 internal links, 22 external
The homepage links to 101 pages on aip.edu.pa and 22 external pages.
8 checks passed
Meta description: 140 characters
Your meta description is 140 characters: “La AIP es un colegio bilingüe que prepara a sus alumnos, en un ambiente de respeto y apoyo, para que logren el más alto…”.
One H1 headline
Your main headline reads: “Responsabilidad · Respeto · Integridad · Excelencia · Cuidado”.
Title: 42 characters
Your title is a healthy 42 characters: “Inicio - Academia Interamericana de Panamá”.
Canonical URL set
The canonical URL is https://aip.edu.pa/.
Structured data in place
Structured data found: BreadcrumbList, 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://aip.edu.pa/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://aip.edu.pa/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.
3 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (933 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://aip.edu.pa/admisiones-2 and https://aip.edu.pa/admisiones all use the title “Admisiones - Academia Interamericana de Panamá”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages without a meta description
https://aip.edu.pa/acreditaciones-y-membresias, https://aip.edu.pa/aip-bistro and https://aip.edu.pa/nuevos-portales-2 have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages share a meta description
https://aip.edu.pa/admisiones-2, https://aip.edu.pa/costos-academicos and https://aip.edu.pa/admisiones 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://aip.edu.pa/admisiones, whose canonical is https://aip.edu.pa/admisiones-2. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
3 pages without an H1
https://aip.edu.pa/clases-extracurriculares-2, https://aip.edu.pa/contactenos and https://aip.edu.pa/contactenos/forme-parte-de-nuestro-equipo have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://aip.edu.pa/contactenos 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 39 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
34 small tap targets
34 of 47 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: the server responded with a status of 404 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 265 words of copy
The homepage carries about 265 words of visible text.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “start slideshow”.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Meta Pixel (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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
10 other companies contacted
Loading the homepage contacts 10 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 aip.edu.pa, 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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on aip.edu.pa, including 18 speed issues, 1 SEO issue and 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.