Website review, no card needed
aiglon.ch website review
Visit site (opens in a new tab)Reviewed 20 October 202643 issues · 87 checks
This review found 43 issues worth fixing on aiglon.ch, 19 of them high impact, across 87 checks. The most urgent: use efficient cache lifetimes. 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
62DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.9 s |
| May 9, 2026 | 2.8 s |
| May 16, 2026 | 2.9 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 3.0 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.0 s |
| Jun 20, 2026 | 3.0 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 3.1 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 3.0 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 3.0 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 3.1 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 3.1 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 3.1 s |
| Oct 17, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 203 ms |
| May 9, 2026 | 190 ms |
| May 16, 2026 | 197 ms |
| May 23, 2026 | 208 ms |
| May 30, 2026 | 207 ms |
| Jun 6, 2026 | 200 ms |
| Jun 13, 2026 | 184 ms |
| Jun 20, 2026 | 173 ms |
| Jun 27, 2026 | 173 ms |
| Jul 4, 2026 | 175 ms |
| Jul 11, 2026 | 177 ms |
| Jul 18, 2026 | 183 ms |
| Jul 25, 2026 | 190 ms |
| Aug 1, 2026 | 202 ms |
| Aug 8, 2026 | 221 ms |
| Aug 15, 2026 | 242 ms |
| Aug 22, 2026 | 235 ms |
| Aug 29, 2026 | 226 ms |
| Sep 5, 2026 | 215 ms |
| Sep 12, 2026 | 207 ms |
| Sep 19, 2026 | 206 ms |
| Sep 26, 2026 | 205 ms |
| Oct 3, 2026 | 220 ms |
| Oct 10, 2026 | 236 ms |
| Oct 17, 2026 | 242 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
6.8 s · 1.5 MB30 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).
Render-blocking requests
7.0 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 7.0 s.
Reduce unused JavaScript
5.0 s · 993 KiBAbout 993 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.0 s faster on a phone.
audioeye-services.com adds 1.6 s
1.6 saudioeye-services.com costs a phone 1.6 s of main-thread work and 319 KiB 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.
Reduce unused CSS
1.1 s · 134 KiBAbout 134 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 13
13/100Your mobile performance score is 13 (desktop: 14). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.9 s
A phone's processor spends 5.9 s on main-thread work while loading, 3.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (audioeye-services.com, Google Tag Manager and weglot.com and others), adding 928 KiB and 2.3 s of main-thread time.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 512 ms. During a long task the page ignores taps.
Google Tag Manager adds 447 ms
447 msGoogle Tag Manager costs a phone 447 ms of main-thread work and 312 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,310 HTML elements
The page has 2,310 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
150 ms · 180 KiB8 images could be 180 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
Legacy JavaScript
150 ms · 44 KiBPolyfills for old browsers add 44 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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: 7 ms
7 msYour server sent the HTML in 7 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.8 s
4.8 sReal visitors wait 4.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.68
0.68For real visitors the layout shifts by 0.68 (75th percentile). Good is under 0.1.
First Contentful Paint: 8.2 s
8.2 sThe first text or image appears after 8.2 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 18.7 s
18.7 sYour largest element takes 18.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 19.0 s
19.0 sThe page becomes fully interactive after 19.0 s. Good is under 3.8 s.
Speed Index: 9.6 s
9.6 sVisually, the page fills in at 9.6 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.512
0.512The layout shifts by 0.512 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 969 ms
969 msScripts block taps and scrolling for 969 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 271 ms
271 msReal visitors wait 271 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 203 ms to 242 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.9 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 3.8 MB in 110 requests
3.8 MBYour homepage downloads 3.8 MB in 110 requests on a phone: images 2.1 MB (64), scripts 1.5 MB (19) and stylesheets 166 KiB (11). Under 2 MB keeps phones on slow connections fast.
5 images far larger than shown
316 KiB5 images are downloaded at several times the size a phone draws them, for example Louise-Thomas-091_lr.jpg at 512 px wide, shown at 1 px. Resized copies would save about 316 KiB.
3 images in older formats
3 images (133 KiB) 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.
About 1.1 g of CO₂ per visit
1.08 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.08 g of CO₂e: 129.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
Interactive controls must not be nested (5 elements)
Interactive controls must not be nested: 5 elements on the page fail this check, rated serious by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
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.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
ARIA role should be appropriate for the element (2 elements)
ARIA role should be appropriate for the element: 2 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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 6 failed. 5 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.
No XML sitemap
No XML sitemap at https://www.aiglon.ch/sitemap.xml, so Google discovers your pages only by following links.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
294 internal links, 11 external
The homepage links to 294 pages on aiglon.ch and 11 external pages.
6 checks passed
Meta description: 160 characters
Your meta description is 160 characters: “Aiglon College is a private, non-profit international boarding school in Switzerland offering a distinctive, world-clas…”.
One H1 headline
Your main headline reads: “Home”.
Title: 61 characters
Your title is a healthy 61 characters: “Aiglon College | International Boarding School in Switzerland”.
Canonical URL set
The canonical URL is https://www.aiglon.ch/.
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.
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.aiglon.ch/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 (2,381 words), so crawlers that don't run JavaScript still read it.
Other pages
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.aiglon.ch/fs/pages/531, whose canonical is https://www.aiglon.ch/admissions/begin-the-journey. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.aiglon.ch/fs/pages/466 has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.aiglon.ch/fs/pages/466 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.
2 pages slow to respond
https://www.aiglon.ch/about/founder-history and https://www.aiglon.ch/about/governance took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 94 found) and read each the way a search engine does.
5 checks passed
Linked pages load
13 pages of 15 loaded without an error (the rest turned automated requests away).
Every page has a meta description
All 13 pages that loaded have a meta description.
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 13 pages that loaded have a <title>.
Best practices
15 small tap targets
15 of 22 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'productConfig')”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
About 1,515 words of copy
The homepage carries about 1,515 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more”.
16 calls to action
The homepage has 16 calls to action, for example “ENQUIRE”, “School Shop” and “Learn More”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
2 trackers load before any consent
2Before 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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
12 other companies contacted
Loading the homepage contacts 12 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 aiglon.ch, 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
- Framework
- Bootstrap
- Analytics
- Google Tag Manager
Company
- Founded
- 1949
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 aiglon.ch, including 24 speed issues, 3 SEO issues and 1 conversion gap. 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.