gaffistore.com website review

43 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.4 s faster on a phone.

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

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

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

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

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

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

8 third-party services load with your homepage (iubenda, Shopify and omnisnippet1.com and others), adding 2.3 MB and 1.8 s of main-thread time.

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

iubenda costs a phone 885 ms of main-thread work and 129 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.

Shopify costs a phone 479 ms of main-thread work and 1.3 MB 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.

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

64 KiB could be saved by minifying JavaScript.

omnisnippet1.com costs a phone 302 ms of main-thread work and 119 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.

Soundest costs a phone 0 ms of main-thread work and 538 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.

8 KiB could be saved by minifying CSS.

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 34.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Noi e terze parti selezionate raccogliamo informazioni pers…”. Most of its time is element render delay (18.8 s).

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 140 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-11-07, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.5 MB in 294 requests on a phone: images 4.2 MB (72), scripts 1.3 MB (94) and other files 549 KiB (85). Under 2 MB keeps phones on slow connections fast.

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

11 elements hidden from screen readers can still receive keyboard focus.

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

ARIA commands must have an accessible name: 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.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

ARIA toggle fields do not have accessible names (2 elements).

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

Elements with visible text labels do not have matching accessible names. (26 elements).

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

Your title is 82 characters, so Google will cut it off around 60: “GAFFI 1966 | Clothing, Shoes and Accessories Store in Rome – Gaffi Store 1966 Roma”.

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

The homepage links to 242 pages on gaffistore.com and 0 external pages.

https://gaffistore.com/en/collections/nuova-collezione-ai26, https://gaffistore.com/en/collections/uomo, https://gaffistore.com/en/collections/abbigliamento-uomo, https://gaffistore.com/en/collections/maglie-felpe-uomo and https://gaffistore.com/en/collections/scarpe-uomo have no meta description, so Google writes the search snippet from whatever text it finds.

https://gaffistore.com/en/collections/scarpe-uomo has no <h1> headline, so visitors and search engines get no clear main topic.

https://gaffistore.com/en/collections/scarpe-uomo has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

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

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 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 1,214 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok Pixel (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 19 cookies, 1 of them by other companies (measured from a US location before any click).

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