Website review, no card needed

enaip.piemonte.it logo

enaip.piemonte.it website review

Visit site (opens in a new tab)Reviewed 28 October 202640 issues · 76 checks

This review found 40 issues worth fixing on enaip.piemonte.it, 18 of them high impact, across 76 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.5 s2.0 sMay 9Oct 242.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.2 s
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.2 s
Jun 6, 20262.2 s
Jun 13, 20262.2 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.2 s
Sep 19, 20262.3 s
Sep 26, 20262.4 s
Oct 3, 20262.4 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Oct 24, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
128 ms105 msMay 9Oct 24123 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026108 ms
May 16, 2026108 ms
May 23, 2026109 ms
May 30, 2026110 ms
Jun 6, 2026111 ms
Jun 13, 2026112 ms
Jun 20, 2026112 ms
Jun 27, 2026112 ms
Jul 4, 2026111 ms
Jul 11, 2026111 ms
Jul 18, 2026112 ms
Jul 25, 2026113 ms
Aug 1, 2026116 ms
Aug 8, 2026118 ms
Aug 15, 2026120 ms
Aug 22, 2026121 ms
Aug 29, 2026119 ms
Sep 5, 2026121 ms
Sep 12, 2026122 ms
Sep 19, 2026123 ms
Sep 26, 2026125 ms
Oct 3, 2026124 ms
Oct 10, 2026124 ms
Oct 17, 2026124 ms
Oct 24, 2026123 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

Full-page screenshot of enaip.piemonte.it (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. enaip.piemonte.it at 1.6 s1.6 s
  2. enaip.piemonte.it at 3.3 s3.3 s
  3. enaip.piemonte.it at 4.9 s4.9 s
  4. enaip.piemonte.it at 6.5 s6.5 s
  5. enaip.piemonte.it at 8.1 s8.1 s
  6. enaip.piemonte.it at 9.8 s9.8 s
  7. enaip.piemonte.it at 11.4 s11.4 s
  8. enaip.piemonte.it at 13.0 s13.0 s

Speed

10 to fix22
  • Improve image delivery

    4.0 s · 5.3 MB

    9 images could be 5.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.0 s faster on a phone.

  • Use efficient cache lifetimes

    1.9 s · 1.3 MB

    46 files are served with short cache lifetimes, so returning visitors download them again (1.3 MB).

  • Render-blocking requests

    3.1 s

    24 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.1 s.

  • Mobile performance score: 22

    22/100

    Your mobile performance score is 22 (desktop: 63). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.7 s

    A phone's processor spends 4.7 s on main-thread work while loading, 922 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 10 long tasks on the main thread

    10 long tasks block the main thread while loading, the longest for 1.5 s. During a long task the page ignores taps.

  • Reduce unused CSS

    750 ms · 124 KiB

    About 124 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Font display

    800 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 800 ms).

  • Reduce unused JavaScript

    600 ms · 124 KiB

    About 124 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • openfreemap.org adds 0 ms

    0 ms

    openfreemap.org costs a phone 0 ms of main-thread work and 339 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.

  • 3 third-party services on the page

    3 third-party services load with your homepage (JSDelivr CDN, Google Fonts and openfreemap.org), adding 409 KiB and 17 ms of main-thread time.

  • Legacy JavaScript

    16 KiB

    Polyfills for old browsers add 16 KiB JavaScript that modern phones do not need.

  • Phones get a much slower page than desktops

    Desktop scores 63 but mobile only 22. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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: 110 ms

    110 ms

    Your server sent the HTML in 110 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix100
  • 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.

  • Largest Contentful Paint: 18.0 s

    18.0 s

    Your largest element takes 18.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Immagine Scegli di essere te”. Most of its time is resource load duration (7.3 s).

  • Speed Index: 20.0 s

    20.0 s

    Visually, the page fills in at 20.0 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 18.6 s

    18.6 s

    The page becomes fully interactive after 18.6 s. Good is under 3.8 s.

  • Total Blocking Time: 1.4 s

    1.4 s

    Scripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.

  • First Contentful Paint: 3.2 s

    3.2 s

    The first text or image appears after 3.2 s on a phone. Good is under 1.8 s.

  • Real-user FCP: 2.2 s

    2.2 s

    Real visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.3 s

    1.3 s

    Real visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.24

    0.24

    The layout shifts by 0.24 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 14 images without width and height

    14 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) got 14% slower for real visitors

    +14%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 108 ms to 123 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-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).

3 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

    Real visitors wait 2.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 123 ms

    123 ms

    Real visitors wait 123 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

Images and page weight

5 to fix18
  • Page weight: 17.0 MB in 101 requests

    17.0 MB

    Your homepage downloads 17.0 MB in 101 requests on a phone: images 14.2 MB (35), other files 1.3 MB (15) and fonts 853 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 8 images over 500 KB

    8 images weigh 9.8 MB together. On a phone connection a single image that size takes seconds.

  • 7 images far larger than shown

    3.1 MB

    7 images are downloaded at several times the size a phone draws them, for example 126B_notiziehomecoope.jpg at 1,920 px wide, shown at 366 px. Resized copies would save about 3.1 MB.

  • 29 images in older formats

    29 images (14.2 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.

  • 5 images below the first screen load straight away

    5 images further down the page (4.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 4.8 g of CO₂ per visit

    4.81 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.81 g of CO₂e: 576.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

4 to fixGoogle 9495
  • 21 tap targets too small

    21 tap targets are too small or too close together to hit reliably with a finger.

  • All page content should be contained by landmarks (56 elements)

    All page content should be contained by landmarks: 56 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.

  • 5 links without text

    5 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

    Headings skip levels (h1 → h4, h1 → h3 and h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 35 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

6 to fixGoogle 10073
  • Title is short (22 characters)

    Your title is only 22 characters: “En.A.I.P. Piemonte ETS”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 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 (“Questo sito web utilizza i cookie”, “Scegli di essere te” and “Riscrivi il tuo futuro”). 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.

  • 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.enaip.piemonte.it/sitemap.xml, so Google discovers your pages only by following links.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 207 internal links, 24 external

    The homepage links to 207 pages on enaip.piemonte.it and 24 external pages.

2 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Corsi gratuiti per entrare nel mondo del lavoro. Corsi serali di aggiornamento. Stage, tirocini, mobilità all’estero. S…”.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • 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.enaip.piemonte.it/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.

  • Opted out of AI training for 1 crawler

    robots.txt blocks ClaudeBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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,371 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 95 found) and read each the way a search engine does.

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

Google 100100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    25 of 26 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix42
  • 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 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.

  • 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 430 words of copy

    The homepage carries about 430 words of visible text.

2 checks passed
  • 4 short forms

    4 short forms (7 fields at most) are right on the homepage, asking for an email.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie (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.

  • 5 other companies contacted

    Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

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 enaip.piemonte.it, 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 © 2023.

Stack

Framework
jQuery
Hosting
Azure

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on enaip.piemonte.it, including 20 speed issues, 6 SEO issues and 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25