Website review, no card needed
iaa.edu.jo website review
Visit site (opens in a new tab)Reviewed 31 October 202633 issues · 78 checks
This review found 33 issues worth fixing on iaa.edu.jo, 9 of them high impact, across 78 checks. The most urgent: page weight: 13.1 MB in 70 requests. 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
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.2 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 124 ms |
| May 16, 2026 | 126 ms |
| May 23, 2026 | 125 ms |
| May 30, 2026 | 127 ms |
| Jun 6, 2026 | 128 ms |
| Jun 13, 2026 | 128 ms |
| Jun 20, 2026 | 129 ms |
| Jun 27, 2026 | 129 ms |
| Jul 4, 2026 | 132 ms |
| Jul 11, 2026 | 132 ms |
| Jul 18, 2026 | 135 ms |
| Jul 25, 2026 | 135 ms |
| Aug 1, 2026 | 135 ms |
| Aug 8, 2026 | 134 ms |
| Aug 15, 2026 | 134 ms |
| Aug 22, 2026 | 136 ms |
| Aug 29, 2026 | 139 ms |
| Sep 5, 2026 | 143 ms |
| Sep 12, 2026 | 144 ms |
| Sep 19, 2026 | 144 ms |
| Sep 26, 2026 | 135 ms |
| Oct 3, 2026 | 134 ms |
| Oct 10, 2026 | 126 ms |
| Oct 17, 2026 | 127 ms |
| Oct 24, 2026 | 144 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
Use efficient cache lifetimes
12.6 MB21 files are served with short cache lifetimes, so returning visitors download them again (12.6 MB).
Improve image delivery
6.5 MB4 images could be 6.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 71
71/100Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
450 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 55 ms. During a long task the page ignores taps.
Reduce unused JavaScript
26 KiBAbout 26 KiB of JavaScript is downloaded but never used on this page.
Legacy JavaScript
14 KiBPolyfills for old browsers add 14 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.
2 checks passed
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 486 ms of it running JavaScript. That is comfortably low.
Server response: 113 ms
113 msYour server sent the HTML in 113 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.
Cumulative Layout Shift: 0.988
0.988The layout shifts by 0.988 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 980 ms
980 msReal visitors wait 980 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.2 s
5.2 sVisually, the page fills in at 5.2 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 124 ms to 144 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user LCP: 2.4 s
2.4 sReal visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 138 ms
138 msReal visitors wait 138 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Time to Interactive: 2.6 s
2.6 sThe page is fully interactive after 2.6 s.
First Contentful Paint: 0.9 s
0.9 sThe first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 0.9 s
0.9 sYour largest element renders in 0.9 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Authorised IB World School, Accredited by the New England A…”.
Total Blocking Time: 5 ms
5 msScripts block the page for only 5 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 13.1 MB in 70 requests
13.1 MBYour homepage downloads 13.1 MB in 70 requests on a phone: images 9.6 MB (24), media 3.1 MB (3) and scripts 269 KiB (17). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 6.1 MB together. On a phone connection a single image that size takes seconds.
2 images far larger than shown
5.6 MB2 images are downloaded at several times the size a phone draws them, for example HanaHome.webp at 2,308 px wide, shown at 195 px. Resized copies would save about 5.6 MB.
About 3.7 g of CO₂ per visit
3.70 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.70 g of CO₂e: 444.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
11 buttons without a name
11 buttons have no accessible name, so screen readers announce just “button”.
9 tap targets too small
9 tap targets are too small or too close together to hit reliably with a finger.
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.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 26 images in the HTML carry an alt attribute.
37 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 37 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
4 H1 headlines
There are 4 <h1> headlines (“Welcome From the Director”, “IAA Highlights” and “Admissions”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (180 characters)
Your meta description is 180 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:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.iaa.edu.jo/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at iaa.edu.jo/robots.txt, the first file search crawlers ask for.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
27 internal links, 9 external
The homepage links to 27 pages on iaa.edu.jo and 9 external pages.
1 checks passed
Title: 60 characters
Your title is a healthy 60 characters: “The International Academy – Amman | Leading Education in Jor”.
AI search readiness
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://www.iaa.edu.jo/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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (217 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://www.iaa.edu.jo/Overview, which answers with an error. Visitors hit a dead end and search engines drop it.
13 pages share a title
/, https://www.iaa.edu.jo/our-community/Portals, https://www.iaa.edu.jo/calendar, https://www.iaa.edu.jo/admissions/Application-Form, https://www.iaa.edu.jo/contactus and https://www.iaa.edu.jo/aboutus/Welcome-From-the-Director and 7 others all use the title “The International Academy – Amman | Leading Education in Jor”. Search engines can't tell which page to show for a search, so each competes with the others.
12 pages share a meta description
https://www.iaa.edu.jo/our-community/Portals, https://www.iaa.edu.jo/calendar, https://www.iaa.edu.jo/admissions/Application-Form, https://www.iaa.edu.jo/contactus, https://www.iaa.edu.jo/aboutus/Welcome-From-the-Director and https://www.iaa.edu.jo/schools/Overview and 6 others use the same meta description. A description written for each page earns more clicks.
6 pages with very little text
https://www.iaa.edu.jo/our-community/Portals, https://www.iaa.edu.jo/calendar, https://www.iaa.edu.jo/contactus, https://www.iaa.edu.jo/our-community/Staff-Directory, https://www.iaa.edu.jo/admissions/Book-A-Tour and https://www.iaa.edu.jo/admissions/Inquire have 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.
2 pages slow to respond
https://www.iaa.edu.jo/facilities and https://www.iaa.edu.jo/schoollife/Sports- took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 17 found) and read each the way a search engine does.
5 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 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 14 pages that loaded have a <title>.
Best practices
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”.
2 checks passed
Tap targets are thumb-sized
18 of 22 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 202 words
The homepage has only about 202 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Apply Now” and “Contact Us”.
9 calls to action
The homepage has 9 calls to action, for example “Apply Now”, “Contact Us” and “Book a Tour”.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 iaa.edu.jo, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Hosting
- Contabo
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on iaa.edu.jo, including 9 speed issues, 7 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.