Website review, no card needed
jaitalia.org website review
Visit site (opens in a new tab)Reviewed 19 October 202624 issues · 82 checks
This review found 24 issues worth fixing on jaitalia.org, 11 of them high impact, across 82 checks. The most urgent: render-blocking 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
83BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 1.8 s |
| May 2, 2026 | 1.7 s |
| May 9, 2026 | 1.6 s |
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 116 ms |
| May 2, 2026 | 109 ms |
| May 9, 2026 | 112 ms |
| May 16, 2026 | 107 ms |
| May 23, 2026 | 112 ms |
| May 30, 2026 | 113 ms |
| Jun 6, 2026 | 110 ms |
| Jun 13, 2026 | 111 ms |
| Jun 20, 2026 | 118 ms |
| Jun 27, 2026 | 115 ms |
| Jul 4, 2026 | 120 ms |
| Jul 11, 2026 | 118 ms |
| Jul 18, 2026 | 116 ms |
| Jul 25, 2026 | 117 ms |
| Aug 1, 2026 | 118 ms |
| Aug 8, 2026 | 124 ms |
| Aug 15, 2026 | 126 ms |
| Aug 22, 2026 | 134 ms |
| Aug 29, 2026 | 126 ms |
| Sep 5, 2026 | 128 ms |
| Sep 12, 2026 | 121 ms |
| Sep 19, 2026 | 117 ms |
| Sep 26, 2026 | 128 ms |
| Oct 3, 2026 | 126 ms |
| Oct 10, 2026 | 127 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
6.9 s42 files block the first paint until they finish downloading. Deferring or inlining them could save about 6.9 s.
Reduce unused JavaScript
1.4 s · 268 KiBAbout 268 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Improve image delivery
1.3 MB11 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 56
56/100Your mobile performance score is 56 (desktop: 82). Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 224 ms
224 msGoogle Tag Manager costs a phone 224 ms of main-thread work and 337 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.
1,587 HTML elements
The page has 1,587 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, iubenda and JSDelivr CDN and others), adding 490 KiB and 304 ms of main-thread time.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 121 ms. During a long task the page ignores taps.
Legacy JavaScript
24 KiBPolyfills for old browsers add 24 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 82 but mobile only 56. A gap that wide usually means heavy scripts and images that hit phones hardest.
Reduce unused CSS
10 KiBAbout 10 KiB of CSS is downloaded but never applied on this page.
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.
Use efficient cache lifetimes
4 KiB3 files are served with short cache lifetimes, so returning visitors download them again (4 KiB).
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 714 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 9.5 s
9.5 sThe first text or image appears after 9.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 19.8 s
19.8 sYour largest element takes 19.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Il futuro è Junior Siamo la più vasta organizzazione non pr…”.
Time to Interactive: 20.5 s
20.5 sThe page becomes fully interactive after 20.5 s. Good is under 3.8 s.
Speed Index: 9.5 s
9.5 sVisually, the page fills in at 9.5 s (Speed Index). Good is under 3.4 s.
20 images without width and height
20 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 116 ms to 127 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 111 ms
111 msReal visitors wait 111 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 427 ms
427 msReal visitors wait 427 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).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.9 MB in 130 requests
4.9 MBYour homepage downloads 4.9 MB in 130 requests on a phone: images 3.2 MB (42), fonts 861 KiB (7) and scripts 793 KiB (36). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (332 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.
1 image below the first screen load straight away
1 image further down the page (38 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.40 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.40 g of CO₂e: 167.5 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
23 text elements with low contrast
23 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (6 elements)
ARIA role should be appropriate for the element: 6 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (6 elements).
2 checks passed
Every image has alt text
All 36 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
53 internal links, 21 external
The homepage links to 53 pages on jaitalia.org and 21 external pages.
8 checks passed
Meta description: 138 characters
Your meta description is 138 characters: “Junior Achievement è la più vasta organizzazione non profit al mondo dedicata all’educazione imprenditoriale ed economi…”.
One H1 headline
Your main headline reads: “JUNIOR ACHIEVEMENT ITALIA”.
Title: 52 characters
Your title is a healthy 52 characters: “JA Italia | Educazione Imprenditoriale per i giovani”.
Canonical URL set
The canonical URL is https://www.jaitalia.org/.
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.jaitalia.org/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.jaitalia.org/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 (954 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages hidden from search
https://www.jaitalia.org/prehome and https://www.jaitalia.org/download-ricerca are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
4 pages without a meta description
https://www.jaitalia.org/registrati, https://www.jaitalia.org/prehome, https://www.jaitalia.org/pubblicazioni and https://www.jaitalia.org/download-ricerca have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://www.jaitalia.org/registrati, https://www.jaitalia.org/ja-italia-ja-worldwide-nominata-per-il-premio-nobel-per-la-pace, https://www.jaitalia.org/teacher-of-the-year and https://www.jaitalia.org/download-ricerca have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.jaitalia.org/registrati 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 24 found) and read each the way a search engine does.
4 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 a title
All 15 pages that loaded have a <title>.
Best practices
7 small tap targets
7 of 22 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 844 words of copy
The homepage carries about 844 words of visible text.
2 checks passed
Social proof on the page
Social proof on the homepage: 5 customer or partner logos and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: iubenda
A consent management tool (iubenda) 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 jaitalia.org, 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 Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 24 issues on jaitalia.org, including 11 speed 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.