iper.it website review

About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.0 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Gigya, Google Tag Manager and Accessibe Accessibility Overlay and others), adding 2.4 MB and 1.6 s of main-thread time.

Gigya costs a phone 689 ms of main-thread work and 846 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.

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

13 images could be 334 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.

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

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.

4 KiB could be saved by minifying CSS.

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.

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

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

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

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

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

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

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

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

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

Your homepage downloads 5.5 MB in 228 requests on a phone: images 2.4 MB (116), scripts 2.2 MB (61) and fonts 360 KiB (12). Under 2 MB keeps phones on slow connections fast.

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

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

19 buttons have no accessible name, so screen readers announce just “button”.

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

2 elements have a tabindex above 0, which scrambles the keyboard order.

Some lists contain elements other than list items, which screen readers announce wrongly.

Some list items are not inside a list.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

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

Elements use prohibited ARIA attributes (1 element).

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your meta description is 174 characters; Google truncates after about 160, so the end of your pitch is cut.

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 at https://www.iper.it/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at iper.it/robots.txt, the first file search crawlers ask for.

8 links have no real href, so search engines can't follow them.

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

The homepage links to 118 pages on iper.it and 19 external pages.

There is no /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.

/iper-mag has no <title>, so Google invents the link text in results.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example /servizi/salute, whose canonical is /servizi/salute/page-1. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/carta-vantaggi, /servizi/animali/pet-food-store, /punti-vendita, /le-nostre-produzioni, /i-nostri-ristoranti and /mangiare-da-iper and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images failed to load on a phone, for example https://www.iper.it/.

37 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Requests the geolocation permission on page load.

Chrome logged issues while loading the page (“Cookie”).

2 links from your homepage to your own site are broken, for example https://www.iper.it/servizi/iperdrive/spendi-e-riprendi/ (404).

1 link to other sites is dead, for example https://www.ilviaggiatorgoloso.it/wp-content/themes/ilviaggiatorgoloso/pdf/VG_Catalogo-Natale-24_DiarioDiViaggio.pdf (404).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

1 link go through two or more redirects, for example https://itunes.apple.com/it/app/iper-la-grande-i/id1086027077?l=en&mt=8&utm_medium=referral.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

iper.it has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 942 words of visible text.

DMARC is set to p=none, so mail pretending to be iper.it is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 2 cookies, 1 of them by other companies (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.