Website review, no card needed
santannainstitute.com website review
Visit site (opens in a new tab)Reviewed 18 October 202638 issues · 84 checks
This review found 38 issues worth fixing on santannainstitute.com, 17 of them high impact, across 84 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
62D- #117,983 of 123,001 reviewed websitesbeats 3%
- #68,223 of 69,377 online storesbeats 1%
- #2,751 of 2,868 WooCommerce storesbeats 3%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 4.5 s |
| May 2, 2026 | 4.3 s |
| May 9, 2026 | 3.9 s |
| May 16, 2026 | 3.7 s |
| May 23, 2026 | 3.8 s |
| May 30, 2026 | 3.8 s |
| Jun 6, 2026 | 3.9 s |
| Jun 13, 2026 | 4.2 s |
| Jun 20, 2026 | 4.2 s |
| Jun 27, 2026 | 4.1 s |
| Jul 4, 2026 | 3.7 s |
| Jul 11, 2026 | 4.0 s |
| Jul 18, 2026 | 4.0 s |
| Jul 25, 2026 | 4.0 s |
| Aug 1, 2026 | 4.3 s |
| Aug 8, 2026 | 4.0 s |
| Aug 15, 2026 | 4.2 s |
| Aug 22, 2026 | 4.8 s |
| Aug 29, 2026 | 4.7 s |
| Sep 5, 2026 | 4.5 s |
| Sep 12, 2026 | 4.5 s |
| Sep 19, 2026 | 4.4 s |
| Sep 26, 2026 | 4.4 s |
| Oct 3, 2026 | 4.8 s |
| Oct 10, 2026 | 4.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 80 ms |
| May 2, 2026 | 91 ms |
| May 9, 2026 | 92 ms |
| May 16, 2026 | 91 ms |
| May 23, 2026 | 95 ms |
| May 30, 2026 | 87 ms |
| Jun 6, 2026 | 80 ms |
| Jun 13, 2026 | 80 ms |
| Jun 20, 2026 | 75 ms |
| Jun 27, 2026 | 79 ms |
| Jul 4, 2026 | 80 ms |
| Jul 11, 2026 | 83 ms |
| Jul 18, 2026 | 81 ms |
| Jul 25, 2026 | 87 ms |
| Aug 1, 2026 | 85 ms |
| Aug 8, 2026 | 87 ms |
| Aug 15, 2026 | 88 ms |
| Aug 22, 2026 | 88 ms |
| Aug 29, 2026 | 91 ms |
| Sep 5, 2026 | 88 ms |
| Sep 12, 2026 | 88 ms |
| Sep 19, 2026 | 85 ms |
| Sep 26, 2026 | 85 ms |
| Oct 3, 2026 | 82 ms |
| Oct 10, 2026 | 83 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
How it loaded on a phone
1.3 s
2.7 s
4.0 s
5.4 s
6.7 s
8.0 s
9.4 s
10.7 s
Speed
Use efficient cache lifetimes
32.8 s · 11.4 MB106 files are served with short cache lifetimes, so returning visitors download them again (11.4 MB).
Reduce unused JavaScript
9.3 s · 1.7 MBAbout 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 9.3 s faster on a phone.
Improve image delivery
5.0 s · 1.4 MB9 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 5.0 s faster on a phone.
Render-blocking requests
3.1 s30 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.1 s.
Reduce unused CSS
1.1 s · 177 KiBAbout 177 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: 24
24/100Your mobile performance score is 24 (desktop: 39). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Document request latency
850 msThe HTML itself could arrive about 850 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
826 msReduce initial server response time. Google estimates savings of 826 ms on a phone.
4 third-party services on the page
4 third-party services load with your homepage (Facebook, Google Tag Manager and Vimeo and others), adding 1.7 MB and 536 ms of main-thread time.
Font display
450 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 450 ms).
Legacy JavaScript
300 ms · 22 KiBPolyfills for old browsers add 22 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Vimeo adds 114 ms
114 msVimeo costs a phone 114 ms of main-thread work and 1.1 MB 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.
Server response: 926 ms
926 msYour server takes 926 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 208 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 45 KiB45 KiB could be saved by minifying JavaScript.
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.
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: 5.4 s
5.4 sReal visitors wait 5.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.81
0.81For real visitors the layout shifts by 0.81 (75th percentile). Good is under 0.1.
Real-user FCP: 3.6 s
3.6 sReal visitors see the first content after 3.6 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 43.2 s
43.2 sYour largest element takes 43.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Applications for Spring 2027 are open! Learn More”.
Speed Index: 19.3 s
19.3 sVisually, the page fills in at 19.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 43.2 s
43.2 sThe page becomes fully interactive after 43.2 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.708
0.708The layout shifts by 0.708 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 3.5 s
3.5 sThe first text or image appears after 3.5 s on a phone. Good is under 1.8 s.
Total Blocking Time: 440 ms
440 msScripts block taps and scrolling for 440 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image 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-10, real Chrome visitors' tap response (inp) went from 80 ms to 83 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-10, real Chrome visitors' largest content (lcp) went from 4.5 s to 4.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 12.8 MB in 122 requests
12.8 MBYour homepage downloads 12.8 MB in 122 requests on a phone: images 9.1 MB (21), scripts 2.9 MB (58) and fonts 418 KiB (4). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (37 KiB) is 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.
1 image below the first screen load straight away
1 image further down the page (24 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 3.6 g of CO₂ per visit
3.62 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.62 g of CO₂e: 434.7 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
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
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.
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.
11 links without text
11 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 (h1 → h5, h2 → h4 and h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 7 images in the HTML carry an alt attribute.
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 41 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
101 internal links, 8 external
The homepage links to 101 pages on santannainstitute.com and 8 external pages.
8 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Sant'Anna Institute Sorrento study abroad in Italy. JU credit in Sorrento, best abroad programs. Contact us (+39) 081 8…”.
One H1 headline
Your main headline reads: “Blog”.
Title: 53 characters
Your title is a healthy 53 characters: “Sant'Anna Institute | Study abroad in Sorrento, Italy”.
Canonical URL set
The canonical URL is https://www.santannainstitute.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, 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.santannainstitute.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.santannainstitute.com/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 (835 words), so crawlers that don't run JavaScript still read it.
Other pages
14 pages without a meta description
https://www.santannainstitute.com/about-us, https://www.santannainstitute.com/our-campus, https://www.santannainstitute.com/affiliates, https://www.santannainstitute.com/partnerships-memberships, https://www.santannainstitute.com/our-team and https://www.santannainstitute.com/news-events and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
9 pages slow to respond
https://www.santannainstitute.com/our-campus, https://www.santannainstitute.com/affiliates, https://www.santannainstitute.com/partnerships-memberships, https://www.santannainstitute.com/our-team, https://www.santannainstitute.com/news-events and https://www.santannainstitute.com/blog and 3 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 43 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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.
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 small tap targets
3 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “$search_button.live is not a function”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 24 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 599 words of copy
The homepage carries about 599 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn More”.
10 calls to action
The homepage has 10 calls to action, for example “Contact us”, “Apply Now” and “Learn More”.
2 short forms
2 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics and Meta Pixel.
Direct contact links
Visitors can reach you directly: 3 phone links and 2 email links.
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.
14 cookies set on arrival
14Opening the homepage sets 14 cookies, 2 of them by other companies (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.
9 other companies contacted
Loading the homepage contacts 9 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 santannainstitute.com, 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
- E-commerce
- WooCommerce
- 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 38 issues on santannainstitute.com, including 25 speed issues, 1 SEO issue 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.