Website review, no card needed

ricerchemediche.it logo

ricerchemediche.it website review

Visit site (opens in a new tab)Reviewed 24 October 202640 issues · 85 checks

This review found 40 issues worth fixing on ricerchemediche.it, 19 of them high impact, across 85 checks. The most urgent: use efficient cache lifetimes. 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.9 s2.8 sMay 2Oct 172.9 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.9 s
May 9, 20262.9 s
May 16, 20262.9 s
May 23, 20262.8 s
May 30, 20262.8 s
Jun 6, 20262.9 s
Jun 13, 20262.9 s
Jun 20, 20262.9 s
Jun 27, 20262.9 s
Jul 4, 20262.8 s
Jul 11, 20262.8 s
Jul 18, 20262.9 s
Jul 25, 20262.8 s
Aug 1, 20262.8 s
Aug 8, 20262.8 s
Aug 15, 20262.8 s
Aug 22, 20262.9 s
Aug 29, 20262.9 s
Sep 5, 20262.9 s
Sep 12, 20262.9 s
Sep 19, 20262.9 s
Sep 26, 20262.9 s
Oct 3, 20262.9 s
Oct 10, 20262.9 s
Oct 17, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
159 ms106 msMay 2Oct 17143 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026116 ms
May 9, 2026115 ms
May 16, 2026113 ms
May 23, 2026112 ms
May 30, 2026114 ms
Jun 6, 2026117 ms
Jun 13, 2026116 ms
Jun 20, 2026117 ms
Jun 27, 2026115 ms
Jul 4, 2026114 ms
Jul 11, 2026113 ms
Jul 18, 2026113 ms
Jul 25, 2026113 ms
Aug 1, 2026117 ms
Aug 8, 2026127 ms
Aug 15, 2026135 ms
Aug 22, 2026147 ms
Aug 29, 2026153 ms
Sep 5, 2026150 ms
Sep 12, 2026147 ms
Sep 19, 2026145 ms
Sep 26, 2026144 ms
Oct 3, 2026144 ms
Oct 10, 2026143 ms
Oct 17, 2026143 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 ricerchemediche.it (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ricerchemediche.it at 0.5 s0.5 s
  2. ricerchemediche.it at 1.0 s1.0 s
  3. ricerchemediche.it at 1.5 s1.5 s
  4. ricerchemediche.it at 2.0 s2.0 s
  5. ricerchemediche.it at 2.5 s2.5 s
  6. ricerchemediche.it at 3.0 s3.0 s
  7. ricerchemediche.it at 3.5 s3.5 s
  8. ricerchemediche.it at 4.0 s4.0 s

Speed

13 to fix18
  • Use efficient cache lifetimes

    19.9 s · 4.3 MB

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

  • Render-blocking requests

    12.3 s

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

  • Reduce unused CSS

    5.4 s · 1.1 MB

    About 1.1 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 5.4 s faster on a phone.

  • Reduce unused JavaScript

    4.2 s · 788 KiB

    About 788 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.2 s faster on a phone.

  • Improve image delivery

    3.3 s · 768 KiB

    7 images could be 768 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.3 s faster on a phone.

  • Mobile performance score: 18

    18/100

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

  • Font display

    850 ms

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, FontAwesome CDN and Google Fonts and others), adding 969 KiB and 713 ms of main-thread time.

  • Google Tag Manager adds 713 ms

    713 ms

    Google Tag Manager costs a phone 713 ms of main-thread work and 847 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.

  • Legacy JavaScript

    300 ms · 57 KiB

    Polyfills for old browsers add 57 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

  • Minify CSS

    300 ms · 53 KiB

    53 KiB could be saved by minifying CSS.

  • Minify JavaScript

    300 ms · 26 KiB

    26 KiB could be saved by minifying JavaScript.

  • Main-thread work: 2.1 s

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

  • 8 long tasks on the main thread

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

  • Document request latency

    124 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Phones get a much slower page than desktops

    Desktop scores 47 but mobile only 18. 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.

1 checks passed
  • Server response: 264 ms

    264 ms

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

Core Web Vitals

13 to fix33
  • 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 CLS: 0.80

    0.80

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

  • First Contentful Paint: 11.8 s

    11.8 s

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

  • Largest Contentful Paint: 30.3 s

    30.3 s

    Your largest element takes 30.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 30.4 s

    30.4 s

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

  • Speed Index: 12.4 s

    12.4 s

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

  • Cumulative Layout Shift: 0.795

    0.795

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

  • Real-user LCP: 3.6 s

    3.6 s

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

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

    +24%

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • Total Blocking Time: 547 ms

    547 ms

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

  • 12 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

1 checks passed
  • Real-user INP: 138 ms

    138 ms

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

Images and page weight

3 to fix50
  • Page weight: 5.4 MB in 148 requests

    5.4 MB

    Your homepage downloads 5.4 MB in 148 requests on a phone: images 1.8 MB (26), scripts 1.8 MB (57) and stylesheets 1.2 MB (52). Under 2 MB keeps phones on slow connections fast.

  • 4 images in older formats

    4 images (743 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

    119 KiB

    1 image is downloaded at several times the size a phone draws it, for example Logo-Newsletter.png at 1,800 px wide, shown at 100 px. Resized copies would save about 119 KiB.

  • 4 images below the first screen load straight away

    4 images further down the page (203 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.5 g of CO₂ per visit

    1.53 g

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

Accessibility

5 to fixGoogle 8491
  • 13 text elements with low contrast

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

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

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

    All page content should be contained by landmarks: 14 elements on the page fail this check, rated moderate by axe-core.

  • 10 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 25 images in the HTML carry an alt attribute.

  • 40 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: 40 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 8598
  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 70 internal links, 15 external

    The homepage links to 70 pages on ricerchemediche.it and 15 external pages.

8 checks passed
  • Meta description: 155 characters

    Your meta description is 155 characters: “IRM Indagini Ricerche Mediche è un moderno poliambulatorio privato accreditato che si avvale di un qualificato team di …”.

  • One H1 headline

    Your main headline reads: “Prestazioni e servizi”.

  • Title: 41 characters

    Your title is a healthy 41 characters: “Home Page - IRM Indagini Ricerche Mediche”.

  • Canonical URL set

    The canonical URL is https://www.ricerchemediche.it/.

  • Structured data in place

    Structured data found: BreadcrumbList, 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.ricerchemediche.it/sitemap.xml.

AI search readiness

100
4 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: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,638 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.ricerchemediche.it/llms.txt (121 KiB, 731 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

1 to fix98
  • 2 pages share a meta description

    https://www.ricerchemediche.it/irm-pianezza and https://www.ricerchemediche.it/irm-san-donato use the same meta description. A description written for each page earns more clicks.

  • 7 pages slow to respond

    https://www.ricerchemediche.it/tipo_prestazione_ambulatoriale/reparto-odontoiatrico, https://www.ricerchemediche.it/tipo_prestazione_ambulatoriale/diagnostica-per-immagine, https://www.ricerchemediche.it/tipo_prestazione_ambulatoriale/fisioterapia-e-riabilitazione, https://www.ricerchemediche.it/tipo_prestazione_ambulatoriale/laboratorio-analisi, https://www.ricerchemediche.it/tipo_prestazione_ambulatoriale/visite-specialistiche and https://www.ricerchemediche.it/card-salute and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

    17 of 20 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix58
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • A 11-field form

    Your longest form asks for 11 fields (0 required). Every extra field lowers completion.

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

    The homepage carries about 488 words of visible text.

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Start search”.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Meta Pixel.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, 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.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 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.

  • 6 other companies contacted

    Loading the homepage contacts 6 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 ricerchemediche.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
E-commerce
WooCommerce
Analytics
Google 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 40 issues on ricerchemediche.it, including 26 speed issues, 1 SEO issue 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

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