Website review, no card needed

garofalogioielli.it logo

garofalogioielli.it website review

Visit site (opens in a new tab)Reviewed 11 November 202643 issues · 87 checks

This review found 43 issues worth fixing on garofalogioielli.it, 18 of them high impact, across 87 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
5.8 s1.5 sAug 8Nov 74.8 s
Show as table
DateReal-visitor load time (LCP)
Aug 8, 20262.0 s
Aug 22, 20262.2 s
Oct 3, 20262.4 s
Oct 17, 20265.3 s
Oct 24, 20264.9 s
Oct 31, 20264.8 s
Nov 7, 20264.8 s
Real-visitor tap response (INP)75th percentile, phones
206 ms99 msAug 8Nov 7194 ms
Show as table
DateReal-visitor tap response (INP)
Aug 8, 2026131 ms
Aug 22, 2026111 ms
Oct 24, 2026178 ms
Oct 31, 2026187 ms
Nov 7, 2026194 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of garofalogioielli.it (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. garofalogioielli.it at 0.4 s0.4 s
  2. garofalogioielli.it at 0.9 s0.9 s
  3. garofalogioielli.it at 1.3 s1.3 s
  4. garofalogioielli.it at 1.7 s1.7 s
  5. garofalogioielli.it at 2.1 s2.1 s
  6. garofalogioielli.it at 2.6 s2.6 s
  7. garofalogioielli.it at 3.0 s3.0 s
  8. garofalogioielli.it at 3.4 s3.4 s

Speed

6 to fix64
  • Render-blocking requests

    1.4 s

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

  • Mobile performance score: 64

    64/100

    Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.

  • Main-thread work: 3.5 s

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

  • 4 long tasks on the main thread

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

  • Reduce unused JavaScript

    285 KiB

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

  • 2,739 HTML elements

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Shopify, Klarna and Amazon Web Services and others), adding 577 KiB and 168 ms of main-thread time.

  • Improve image delivery

    47 KiB

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

  • Use efficient cache lifetimes

    38 KiB

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

  • Reduce unused CSS

    15 KiB

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

  • Duplicated JavaScript

    11 KiB

    11 KiB JavaScript is shipped twice across bundles.

  • Chained critical requests

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

  • Forced reflow

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

1 checks passed
  • Server response: 38 ms

    38 ms

    Your server sent the HTML in 38 ms, well inside Google's 600 ms guideline.

Core Web Vitals

12 to fix33
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user LCP: 8.3 s

    8.3 s

    Real visitors wait 8.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 3.4 s

    3.4 s

    Real visitors see the first content after 3.4 s (75th percentile). Good is under 1.8 s.

  • Largest Contentful Paint: 39.2 s

    39.2 s

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

  • Time to Interactive: 42.7 s

    42.7 s

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

  • Speed Index: 10.5 s

    10.5 s

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

  • Real-user INP: 270 ms

    270 ms

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

  • Tap response (INP) got 57% slower for real visitors

    +57%

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

  • Largest content (LCP) got 127% slower for real visitors

    +127%

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

  • Real-user TTFB: 1.7 s

    1.7 s

    Real visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.

  • 38 images without width and height

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

  • First Contentful Paint: 2.0 s

    2.0 s

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

3 checks passed
  • Real-user CLS: 0.02

    0.02

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

  • Cumulative Layout Shift: 0.018

    0.018

    The layout barely moves while loading (CLS 0.018, good is under 0.1).

  • Total Blocking Time: 4 ms

    4 ms

    Scripts block the page for only 4 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix47
  • Page weight: 11.7 MB in 238 requests

    11.7 MB

    Your homepage downloads 11.7 MB in 238 requests on a phone: images 10.0 MB (42), other files 788 KiB (103) and scripts 715 KiB (53). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

    2 images weigh 9.5 MB together. On a phone connection a single image that size takes seconds.

  • An image on the first screen is lazy-loaded

    mobile_870_x_638_px_1.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 3.3 g of CO₂ per visit

    3.32 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

11 to fixGoogle 8486
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • ARIA attributes must conform to valid values (1 element)

    ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • 13 text elements with low contrast

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

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • ARIA toggle fields must have an accessible name (1 element)

    ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • All page content should be contained by landmarks (23 elements)

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

  • 8 form fields without a label

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

  • ARIA role should be appropriate for the element (1 element)

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

  • Elements marked as presentational should be consistently ignored (1 element)

    Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 72 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 10 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9280
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (17 characters)

    Your title is only 17 characters: “Garofalo Gioielli”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 163 internal links, 8 external

    The homepage links to 163 pages on garofalogioielli.it and 8 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Garofalo Gioielli”.

  • Canonical URL set

    The canonical URL is https://garofalogioielli.it/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://garofalogioielli.it/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,308 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://garofalogioielli.it/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 7 pages without a meta description

    https://garofalogioielli.it/collections/all, https://garofalogioielli.it/collections/accessori, https://garofalogioielli.it/collections/anelli, https://garofalogioielli.it/collections/bracciali, https://garofalogioielli.it/collections/collane and https://garofalogioielli.it/collections/orecchini and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages without an H1

    https://garofalogioielli.it/collections/all, https://garofalogioielli.it/collections/accessori, https://garofalogioielli.it/collections/gioielli-1, https://garofalogioielli.it/collections/anelli, https://garofalogioielli.it/collections/bracciali and https://garofalogioielli.it/collections/collane and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://garofalogioielli.it/collections/accessori and https://garofalogioielli.it/collections/gioielli-1 took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 6 broken images

    6 images failed to load on a phone, for example https://garofalogioielli.it/cdn/shop/files/home.png?v=3362.

  • 26 small tap targets

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

  • 2 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • No analytics detected

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

  • A 11-field form

    Your longest form asks for 11 fields (0 required). Every extra field lowers completion.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 395 words of copy

    The homepage carries about 395 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop”.

  • 1 call to action

    The homepage has 1 call to action, for example “Shop”.

  • Social proof on the page

    Social proof on the homepage: 26 testimonial or review blocks and 30 customer or partner logos.

  • Direct contact links

    Visitors can reach you directly: 0 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Meta Pixel (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.

  • 10 cookies set on arrival

    10

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

  • No consent tool detected

    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.

  • 16 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at garofalogioielli.it, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

King Product Options · Dondy Whatsapp Chat Widget · Ecomsend Restock · amazonaws.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
Tailwind CSS
E-commerce
Shopify
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on garofalogioielli.it, including 18 speed issues, 3 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25