Website review, no card needed

gianfrancoferre.com logo

gianfrancoferre.com website review

Visit site (opens in a new tab)Reviewed 23 October 202640 issues · 77 checks

This review found 40 issues worth fixing on gianfrancoferre.com, 12 of them high impact, across 77 checks. The most urgent: page weight: 37.4 MB in 70 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
2.6 s2.0 sMay 2Oct 172.4 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.3 s
May 9, 20262.2 s
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20262.0 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.0 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.2 s
Aug 29, 20262.2 s
Sep 5, 20262.3 s
Sep 12, 20262.4 s
Sep 19, 20262.5 s
Sep 26, 20262.5 s
Oct 3, 20262.5 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
198 ms129 msMay 2Oct 17183 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026153 ms
May 9, 2026144 ms
May 16, 2026144 ms
May 23, 2026144 ms
May 30, 2026146 ms
Jun 6, 2026145 ms
Jun 13, 2026141 ms
Jun 20, 2026138 ms
Jun 27, 2026138 ms
Jul 4, 2026137 ms
Jul 11, 2026137 ms
Jul 18, 2026138 ms
Jul 25, 2026137 ms
Aug 1, 2026140 ms
Aug 8, 2026138 ms
Aug 15, 2026138 ms
Aug 22, 2026146 ms
Aug 29, 2026149 ms
Sep 5, 2026161 ms
Sep 12, 2026172 ms
Sep 19, 2026179 ms
Sep 26, 2026185 ms
Oct 3, 2026190 ms
Oct 10, 2026187 ms
Oct 17, 2026183 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 gianfrancoferre.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix46
  • Improve image delivery

    1.0 s · 551 KiB

    7 images could be 551 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.0 s faster on a phone.

  • Mobile performance score: 46

    46/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Shopify and Facebook and others), adding 2.8 MB and 956 ms of main-thread time.

  • Reduce unused JavaScript

    450 ms · 527 KiB

    About 527 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Shopify adds 293 ms

    293 ms

    Shopify costs a phone 293 ms of main-thread work and 1.9 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.

  • Google Tag Manager adds 322 ms

    322 ms

    Google Tag Manager costs a phone 322 ms of main-thread work and 498 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.

  • Render-blocking requests

    300 ms

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

  • Main-thread work: 2.5 s

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

  • 16 long tasks on the main thread

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

  • Use efficient cache lifetimes

    202 KiB

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

  • Legacy JavaScript

    30 KiB

    Polyfills for old browsers add 30 KiB JavaScript that modern phones do not need.

  • Reduce unused CSS

    12 KiB

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

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

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

10 to fix100
  • 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.

  • Largest Contentful Paint: 73.4 s

    73.4 s

    Your largest element takes 73.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Dear clients, please note that delivery timelines may be te…”.

  • Time to Interactive: 73.6 s

    73.6 s

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

  • Speed Index: 9.6 s

    9.6 s

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

  • First Contentful Paint: 3.6 s

    3.6 s

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

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

    +25%

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

  • Real-user FCP: 1.9 s

    1.9 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • Total Blocking Time: 507 ms

    507 ms

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

  • 1 image without width and height

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

  • 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 2.3 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

4 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 184 ms

    184 ms

    Real visitors wait 184 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.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix53
  • Page weight: 37.4 MB in 70 requests

    37.4 MB

    Your homepage downloads 37.4 MB in 70 requests on a phone: media 34.5 MB (5), images 1.5 MB (17) and scripts 1.3 MB (28). Under 2 MB keeps phones on slow connections fast.

  • 4 images below the first screen load straight away

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

  • 6 images far larger than shown

    469 KiB

    6 images are downloaded at several times the size a phone draws them, for example 680_FR_8005_Closeup.png at 1,376 px wide, shown at 374 px. Resized copies would save about 469 KiB.

  • About 10.6 g of CO₂ per visit

    10.60 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

6 to fix83
  • 13 images without alt text

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

  • 2 buttons without a name

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

  • 1 form field without a label

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Positive tabindex

    1 element has a tabindex above 0, which scrambles the keyboard order.

  • 1 tap target too small

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

SEO

3 to fixGoogle 10083
  • No H1 headline

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

  • Canonical points to another host

    Your canonical URL points to hydrogen.shop, not gianfrancoferre.com, so Google may credit that host instead.

  • No social preview image

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

  • 29 internal links, 7 external

    The homepage links to 29 pages on gianfrancoferre.com and 7 external pages.

5 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “Shop Gianfranco Ferré’s finest pieces with contemporary and signature designs for an unparalleled ensemble. Browse our …”.

  • Title: 35 characters

    Your title is a healthy 35 characters: “Gianfranco Ferré | Gianfranco Ferré”.

  • Structured data in place

    Structured data found: Thing.

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

AI search readiness

1 to fix83
  • 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.

  • No llms.txt

    There is no https://gianfrancoferre.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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

Other pages

3 to fix86
  • 15 pages share 2 titles

    /, https://gianfrancoferre.com/ferre, https://gianfrancoferre.com/gf, https://gianfrancoferre.com/gf-ferre, https://gianfrancoferre.com/about and https://gianfrancoferre.com/contact and 2 others all use the title “Gianfranco Ferré | Gianfranco Ferré”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages share a meta description

    https://gianfrancoferre.com/ferre, https://gianfrancoferre.com/gf, https://gianfrancoferre.com/gf-ferre, https://gianfrancoferre.com/about, https://gianfrancoferre.com/wishlist and https://gianfrancoferre.com/collections/women and 9 others use the same meta description. A description written for each page earns more clicks.

  • 4 pages without an H1

    https://gianfrancoferre.com/ferre, https://gianfrancoferre.com/gf, https://gianfrancoferre.com/gf-ferre and https://gianfrancoferre.com/about have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://gianfrancoferre.com/ferre, https://gianfrancoferre.com/gf, https://gianfrancoferre.com/gf-ferre and https://gianfrancoferre.com/wishlist have 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 22 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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 9287
  • 3 small tap targets

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

  • 3 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • No direct contact details

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

  • Only about 85 words

    The homepage has only about 85 words of visible text; thin pages give Google and first-time buyers little to go on.

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “WOMEN SHOP FOR HER” and “MEN SHOP FOR HIM”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact Us” and “Download our App”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, Microsoft Clarity and TikTok Pixel.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 11 cookies set on arrival

    11

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

  • 17 other companies contacted

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

Upkeep, stack and company

Stack

Framework
Remix
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on gianfrancoferre.com, including 18 speed issues, 3 SEO issues and 3 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