Website review, no card needed

fabbriboutiques.com logo

fabbriboutiques.com website review

Visit site (opens in a new tab)Reviewed 25 October 202632 issues · 85 checks

This review found 32 issues worth fixing on fabbriboutiques.com, 13 of them high impact, across 85 checks. The most urgent: use efficient cache lifetimes. 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
1.4 s1.1 sMay 2Oct 171.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.2 s
May 9, 20261.2 s
May 16, 20261.2 s
May 23, 20261.2 s
May 30, 20261.1 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.4 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.2 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
205 ms121 msMay 2Oct 17164 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026135 ms
May 9, 2026135 ms
May 16, 2026134 ms
May 23, 2026133 ms
May 30, 2026131 ms
Jun 6, 2026134 ms
Jun 13, 2026134 ms
Jun 20, 2026138 ms
Jun 27, 2026141 ms
Jul 4, 2026142 ms
Jul 11, 2026144 ms
Jul 18, 2026146 ms
Jul 25, 2026153 ms
Aug 1, 2026161 ms
Aug 8, 2026171 ms
Aug 15, 2026180 ms
Aug 22, 2026187 ms
Aug 29, 2026194 ms
Sep 5, 2026195 ms
Sep 12, 2026194 ms
Sep 19, 2026190 ms
Sep 26, 2026182 ms
Oct 3, 2026174 ms
Oct 10, 2026164 ms
Oct 17, 2026164 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 fabbriboutiques.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. fabbriboutiques.com at 0.4 s0.4 s
  2. fabbriboutiques.com at 0.8 s0.8 s
  3. fabbriboutiques.com at 1.1 s1.1 s
  4. fabbriboutiques.com at 1.5 s1.5 s
  5. fabbriboutiques.com at 1.9 s1.9 s
  6. fabbriboutiques.com at 2.3 s2.3 s
  7. fabbriboutiques.com at 2.6 s2.6 s
  8. fabbriboutiques.com at 3.0 s3.0 s

Speed

8 to fix57
  • Use efficient cache lifetimes

    1.6 s · 192 KiB

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

  • Reduce unused JavaScript

    1.2 s · 237 KiB

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

  • Improve image delivery

    450 ms · 1.0 MB

    19 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

  • Mobile performance score: 57

    57/100

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

  • Render-blocking requests

    500 ms

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

  • Reduce unused CSS

    300 ms · 25 KiB

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

  • 2,800 HTML elements

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

  • gameball.co adds 71 ms

    71 ms

    gameball.co costs a phone 71 ms of main-thread work and 313 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 third-party services on the page

    8 third-party services load with your homepage (gameball.co, Google Tag Manager and Klaviyo and others), adding 698 KiB and 219 ms of main-thread time.

  • 2 long tasks on the main thread

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

  • Legacy JavaScript

    100 ms · 25 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 82 but mobile only 57. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 719 ms of it running JavaScript. That is comfortably low.

  • Server response: 36 ms

    36 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 21.8 s

    21.8 s

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

  • Time to Interactive: 22.6 s

    22.6 s

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

  • Speed Index: 10.2 s

    10.2 s

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

  • First Contentful Paint: 4.8 s

    4.8 s

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

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

    +21%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

8 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.4 s

    1.4 s

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

  • Real-user INP: 186 ms

    186 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 577 ms

    577 ms

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 57 ms

    57 ms

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

Images and page weight

3 to fix43
  • Page weight: 5.7 MB in 270 requests

    5.7 MB

    Your homepage downloads 5.7 MB in 270 requests on a phone: images 3.8 MB (86), other files 934 KiB (105) and scripts 773 KiB (66). Under 2 MB keeps phones on slow connections fast.

  • 6 images far larger than shown

    563 KiB

    6 images are downloaded at several times the size a phone draws them, for example b0c597e05d5e051192f94190f05a2598.webp at 700 px wide, shown at 76 px. Resized copies would save about 563 KiB.

  • 7 images below the first screen load straight away

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

  • 3 images in older formats

    3 images (398 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.

  • About 1.6 g of CO₂ per visit

    1.62 g

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

Accessibility

8 to fixGoogle 8690
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Hidden but focusable

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

  • 11 tap targets too small

    11 tap targets are too small or too close together to hit reliably with a finger.

  • 2 text elements with low contrast

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

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

    All page content should be contained by landmarks: 2 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)

    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.

  • 2 form fields without a label

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

  • ARIA role should be appropriate for the element (6 elements)

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

  • Elements with visible text labels do not have matching accessible names.

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

2 checks passed
  • Every image has alt text

    All 85 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

2 to fixGoogle 10089
  • Title is long (69 characters)

    Your title is 69 characters, so Google will cut it off around 60: “Boutique Online Capi Firmati, Abbigliamento Online - Fabbri Boutiques”.

  • No structured data

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

  • No X (Twitter) card tag

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

  • 319 internal links, 3 external

    The homepage links to 319 pages on fabbriboutiques.com and 3 external pages.

6 checks passed
  • Meta description: 98 characters

    Your meta description is 98 characters: “Negozio online di abbigliamento firmato uomo donna, accessori, borse e scarpe dei migliori brands.”.

  • One H1 headline

    Your main headline reads: “Fabbri Boutiques”.

  • Canonical URL set

    The canonical URL is https://fabbriboutiques.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://fabbriboutiques.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

3 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.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

1 to fix95
  • 1 page without a meta description

    https://fabbriboutiques.com/pages/brands-donna has no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

6 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.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9678
  • 3 broken images

    3 images failed to load on a phone, for example https://fabbriboutiques.com/.

  • 58 small tap targets

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

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • Thin social proof

    Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 886 words of copy

    The homepage carries about 886 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “VAI ALLO SHOP”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “VAI ALLO SHOP”.

  • 6 short forms

    6 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo 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.

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 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.

  • 23 other companies contacted

    Loading the homepage contacts 23 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 fabbriboutiques.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

E-commerce
Shopify
Analytics
Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on fabbriboutiques.com, including 13 speed issues, 2 SEO issues and 1 conversion gap. 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