retepas.com website review

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

The page has 3,053 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Your mobile performance score is 68 (desktop: 94). Pages that score under 90 lose visitors before the first paint.

7 third-party services load with your homepage (Google Tag Manager, iubenda and trustindex.io and others), adding 1.4 MB and 461 ms of main-thread time.

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

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

rocketcdn.me costs a phone 4 ms of main-thread work and 757 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.

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

About 193 KiB of JavaScript is downloaded but never used on this page.

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

About 26 KiB of CSS is downloaded but never applied on this page.

1 image could be 11 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “referti di Rete PAS entrano nel Fascicolo Sanitario Elettro…”.

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

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

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

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

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

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

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

Certain ARIA roles must contain particular children: 3 elements on the page fail this check, rated critical by axe-core.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

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

The homepage links to 253 pages on retepas.com and 10 external pages.

https://retepas.com/aree-sanitarie-e-diagnostiche/fisioterapia has no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “LiveChatWidget is not defined”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,461 words of visible text.

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

Opening the homepage sets 4 cookies (measured from a US location before any click).

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