Website review, no card needed

oasigiovani.it logo

oasigiovani.it website review

Visit site (opens in a new tab)Reviewed 16 November 202628 issues · 72 checks

This review found 28 issues worth fixing on oasigiovani.it, 12 of them high impact, across 72 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
3.6 s1.7 sMay 30Sep 53.0 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.9 s
Jun 6, 20262.1 s
Jun 13, 20262.5 s
Jun 20, 20262.6 s
Jun 27, 20262.6 s
Jul 4, 20262.5 s
Jul 11, 20262.4 s
Jul 18, 20262.3 s
Jul 25, 20262.4 s
Aug 1, 20262.4 s
Aug 8, 20262.7 s
Aug 15, 20263.2 s
Aug 22, 20263.4 s
Aug 29, 20263.4 s
Sep 5, 20263.0 s
Real-visitor tap response (INP)75th percentile, phones
131 ms108 msMay 30Aug 29119 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026112 ms
Jun 6, 2026111 ms
Jun 13, 2026117 ms
Jun 20, 2026124 ms
Jun 27, 2026128 ms
Jul 4, 2026125 ms
Jul 11, 2026121 ms
Jul 18, 2026121 ms
Jul 25, 2026126 ms
Aug 1, 2026128 ms
Aug 8, 2026121 ms
Aug 15, 2026118 ms
Aug 22, 2026122 ms
Aug 29, 2026119 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 oasigiovani.it (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. oasigiovani.it at 0.6 s0.6 s
  2. oasigiovani.it at 1.2 s1.2 s
  3. oasigiovani.it at 1.8 s1.8 s
  4. oasigiovani.it at 2.4 s2.4 s
  5. oasigiovani.it at 3.1 s3.1 s
  6. oasigiovani.it at 3.7 s3.7 s
  7. oasigiovani.it at 4.3 s4.3 s
  8. oasigiovani.it at 4.9 s4.9 s

Speed

5 to fix63
  • Improve image delivery

    14.9 s · 4.2 MB

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

  • Render-blocking requests

    2.6 s

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

  • Use efficient cache lifetimes

    1.9 s · 544 KiB

    63 files are served with short cache lifetimes, so returning visitors download them again (544 KiB).

  • Mobile performance score: 63

    63/100

    Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    600 ms · 108 KiB

    About 108 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.

  • Font display

    200 ms

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

  • Reduce unused CSS

    150 ms · 39 KiB

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

  • 2 third-party services on the page

    2 third-party services load with your homepage (iubenda and Google Fonts), adding 162 KiB and 162 ms of main-thread time.

  • Minify JavaScript

    150 ms · 22 KiB

    22 KiB could be saved by minifying JavaScript.

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 77 ms. During a long task the page ignores taps.

  • 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.

  • Legacy JavaScript

    4 KiB

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

2 checks passed
  • Main-thread work: 1.0 s

    A phone's processor spends 1.0 s on main-thread work while loading, 493 ms of it running JavaScript. That is comfortably low.

  • Server response: 118 ms

    118 ms

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

Core Web Vitals

5 to fix66
  • Largest Contentful Paint: 23.6 s

    23.6 s

    Your largest element takes 23.6 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: 23.7 s

    23.7 s

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

  • Speed Index: 9.1 s

    9.1 s

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

  • Largest content (LCP) got 57% slower for real visitors

    +57%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.9 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • Tap response (INP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 112 ms to 119 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Cumulative Layout Shift: 0.055

    0.055

    The layout barely moves while loading (CLS 0.055, good is under 0.1).

  • Total Blocking Time: 33 ms

    33 ms

    Scripts block the page for only 33 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix50
  • Page weight: 5.3 MB in 69 requests

    5.3 MB

    Your homepage downloads 5.3 MB in 69 requests on a phone: images 4.6 MB (9), scripts 390 KiB (28) and fonts 158 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 4 images in older formats

    4 images (691 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 far larger than shown

    79 KiB

    1 image is downloaded at several times the size a phone draws it, for example [email protected] at 444 px wide, shown at 32 px. Resized copies would save about 79 KiB.

  • 1 image below the first screen load straight away

    1 image further down the page (21 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.5 g of CO₂ per visit

    1.51 g

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

Accessibility

4 to fixGoogle 8595
  • 16 text elements with low contrast

    16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 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.

  • 18 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 9 images in the HTML carry an alt attribute.

  • 41 automated accessibility rules passed

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

SEO

5 to fixGoogle 8571
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (25 characters)

    Your title is only 25 characters: “Oasi Giovani – Savigliano”. 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.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Home” and “CHI SIAMO”). One clear main headline is easier for people and search engines.

  • 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 X (Twitter) card tag

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

  • 89 internal links, 4 external

    The homepage links to 89 pages on oasigiovani.it and 4 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://oasigiovani.it/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://oasigiovani.it/sitemap.xml.

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://oasigiovani.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.

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

Other pages

1 to fix95
  • 15 pages without a meta description

    https://oasigiovani.it/chi-siamo/mission-e-vision, https://oasigiovani.it/chi-siamo/la-nostra-storia, https://oasigiovani.it/chi-siamo/statuto, https://oasigiovani.it/chi-siamo/governance-e-organigramma, https://oasigiovani.it/chi-siamo/trasparenza and https://oasigiovani.it/unoasi-per and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 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

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

    20 of 23 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 660 words of copy

    The homepage carries about 660 words of visible text.

2 checks passed
  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Direct contact links

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

Privacy and tracking

  • 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.

2 checks passed
  • Consent tool: iubenda

    A consent management tool (iubenda) loads with the page.

  • 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 oasigiovani.it, 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
Hosting
Netsons s.r.l.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on oasigiovani.it, including 10 speed issues, 5 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