profumeriegriffe.com website review

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

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

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

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

8 third-party services load with your homepage (iubenda, Shopify and 506.io and others), adding 556 KiB and 252 ms of main-thread time.

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

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

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

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

Polyfills for old browsers add 21 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.

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

3 KiB could be saved by minifying JavaScript.

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 6.8 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 11.5 s. Good is under 3.8 s.

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

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

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

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

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

Your homepage downloads 3.1 MB in 339 requests on a phone: images 1.2 MB (102), scripts 789 KiB (90) and other files 777 KiB (98). Under 2 MB keeps phones on slow connections fast.

6 images (281 KiB) 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.

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

1 tap target is too small or too close together to hit reliably with a finger.

1 image has no alt text, which hurts accessibility and image search.

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

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.

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

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

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

Your title is 66 characters, so Google will cut it off around 60: “Profumerie GRIFFE | Profumi, MakeUp, Cosmetica – Profumerie Griffe”.

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

The homepage links to 816 pages on profumeriegriffe.com and 36 external pages.

https://profumeriegriffe.com/pages/programma-fedelta-griffe has no meta description, so Google writes the search snippet from whatever text it finds.

https://profumeriegriffe.com/pages/programma-fedelta-griffe, https://profumeriegriffe.com/products/gift-card, https://profumeriegriffe.com/pages/punti-vendita, https://profumeriegriffe.com/collections/promo, https://profumeriegriffe.com/collections/novita and https://profumeriegriffe.com/collections/the-ordinary 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 193 found) and read each the way a search engine does.

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

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 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 2,245 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta 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 11 cookies (measured from a US location before any click).

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