interlem.it website review

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

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

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

About 229 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

YouTube costs a phone 1.1 s of main-thread work and 2.8 MB of downloads while your page loads. That alone is enough to make taps feel slow. 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 4.9 s on main-thread work while loading, 3.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

7 third-party services load with your homepage (YouTube, Google CDN and Google Tag Manager and others), adding 4.0 MB and 1.7 s of main-thread time.

10 images could be 764 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

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

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

Google CDN costs a phone 337 ms of main-thread work and 733 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.

15 KiB could be saved by minifying JavaScript.

8 KiB could be saved by minifying CSS.

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

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

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

Your largest element takes 22.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Webinar - Giovedì 22 ottobre 2026 Ore 14:30 L’AI per ridise…”.

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

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

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

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

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

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.

Your homepage downloads 6.8 MB in 159 requests on a phone: scripts 3.6 MB (45), images 2.0 MB (30) and other files 364 KiB (40). Under 2 MB keeps phones on slow connections fast.

11 images (1.1 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.

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

11 images are downloaded at several times the size a phone draws them, for example soluzioni_sap_hp.jpg at 952 px wide, shown at 317 px. Resized copies would save about 2 KiB.

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

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

5 links inside paragraphs rely on colour alone to stand out.

3 frames have no title, so screen-reader users cannot tell what they contain.

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

Document should not have more than one banner landmark: 1 element on the page fails 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 viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Your title is 69 characters, so Google will cut it off around 60: “Software e Soluzioni ICT, Consulenza, Tecnologie e Servizi | Interlem”.

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

The homepage links to 74 pages on interlem.it and 6 external pages.

There is no https://www.interlem.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.

https://www.interlem.it/soluzioni/soluzioni-per-la-pianificazione and https://www.interlem.it/servizi took over 3 s to send their HTML from our server.

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

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

1 image is served at too low a resolution for sharp phone screens.

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

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.

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

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.

Opening the homepage sets 3 cookies, 1 of them by other companies (measured from a US location before any click).

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.

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