epson.it website review

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

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

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

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

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

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

8 third-party services load with your homepage (Google CDN, Adobe Tag Manager and Optanon and others), adding 1.6 MB and 1.2 s of main-thread time.

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

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

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

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

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

10 KiB could be saved by minifying JavaScript.

11 KiB JavaScript is shipped twice across bundles.

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.

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.

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

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

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

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

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

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

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

29 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-24, real Chrome visitors' tap response (inp) went from 149 ms to 164 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 11.8 MB in 135 requests on a phone: media 9.1 MB (9), scripts 1.6 MB (50) and other files 434 KiB (22). Under 2 MB keeps phones on slow connections fast.

1 image (74 KiB) is 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.

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

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

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

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

Some list items are not inside a list.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

2 images have no alt text, which hurts accessibility and image search.

ARIA role should be appropriate for the element: 14 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 14 elements on the page fail this check, rated minor by axe-core.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

Elements with visible text labels do not have matching accessible names. (1 element).

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 5 <h1> headlines (“Ancora pochi giorni: Offerte Halloween con sconti…”, “Grande schermo, grande divertimento” and “Risparmia 100 € sull’acquisto di uno dei videopro…”). One clear main headline is easier for people and search engines.

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

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 328 pages on epson.it and 42 external pages.

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.

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

/products/ink-and-paper/paper-and-media/c/paper has no <h1> headline, so visitors and search engines get no clear main topic.

/for-home, /printer-finder and /inkfinder took over 3 s to send their HTML from our server.

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

38 of 107 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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 3,129 words of visible text.

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

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