Website review, no card needed

gianvitorossi.com logo

gianvitorossi.com website review

Visit site (opens in a new tab)Reviewed 26 October 202633 issues · 82 checks

This review found 33 issues worth fixing on gianvitorossi.com, 13 of them high impact, across 82 checks. The most urgent: reduce unused JavaScript. 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.8 s2.3 sMay 9Oct 242.6 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.4 s
May 16, 20262.3 s
May 23, 20262.4 s
May 30, 20262.4 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20262.5 s
Jul 25, 20262.5 s
Aug 1, 20262.5 s
Aug 8, 20262.6 s
Aug 15, 20262.6 s
Aug 22, 20262.6 s
Aug 29, 20262.7 s
Sep 5, 20262.7 s
Sep 12, 20262.8 s
Sep 19, 20262.8 s
Sep 26, 20262.7 s
Oct 3, 20262.7 s
Oct 10, 20262.7 s
Oct 17, 20262.6 s
Oct 24, 20262.6 s
Real-visitor tap response (INP)75th percentile, phones
147 ms128 msMay 9Oct 24138 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026130 ms
May 16, 2026135 ms
May 23, 2026136 ms
May 30, 2026136 ms
Jun 6, 2026138 ms
Jun 13, 2026137 ms
Jun 20, 2026137 ms
Jun 27, 2026138 ms
Jul 4, 2026142 ms
Jul 11, 2026145 ms
Jul 18, 2026145 ms
Jul 25, 2026142 ms
Aug 1, 2026133 ms
Aug 8, 2026130 ms
Aug 15, 2026131 ms
Aug 22, 2026132 ms
Aug 29, 2026137 ms
Sep 5, 2026137 ms
Sep 12, 2026139 ms
Sep 19, 2026142 ms
Sep 26, 2026142 ms
Oct 3, 2026144 ms
Oct 10, 2026139 ms
Oct 17, 2026138 ms
Oct 24, 2026138 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 gianvitorossi.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gianvitorossi.com at 0.7 s0.7 s
  2. gianvitorossi.com at 1.5 s1.5 s
  3. gianvitorossi.com at 2.2 s2.2 s
  4. gianvitorossi.com at 2.9 s2.9 s
  5. gianvitorossi.com at 3.7 s3.7 s
  6. gianvitorossi.com at 4.4 s4.4 s
  7. gianvitorossi.com at 5.1 s5.1 s
  8. gianvitorossi.com at 5.9 s5.9 s

Speed

10 to fix40
  • Reduce unused JavaScript

    6.2 s · 1,023 KiB

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

  • Mobile performance score: 40

    40/100

    Your mobile performance score is 40 (desktop: 69). 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, Google CDN and Accessibe Accessibility Overlay and others), adding 2.5 MB and 1.4 s of main-thread time.

  • Use efficient cache lifetimes

    750 ms · 183 KiB

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

  • Google CDN adds 541 ms

    541 ms

    Google CDN costs a phone 541 ms of main-thread work and 1.1 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 573 ms

    573 ms

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

    450 ms

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

  • Improve image delivery

    300 ms · 44 KiB

    1 image could be 44 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

  • Main-thread work: 3.4 s

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

  • Optanon adds 97 ms

    97 ms

    Optanon costs a phone 97 ms of main-thread work and 298 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.

  • Legacy JavaScript

    150 ms · 28 KiB

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

  • 14 long tasks on the main thread

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

  • Reduce unused CSS

    30 ms · 35 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 69 but mobile only 40. 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.

1 checks passed
  • Server response: 17 ms

    17 ms

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

Core Web Vitals

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

  • First Contentful Paint: 8.6 s

    8.6 s

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

  • Largest Contentful Paint: 18.2 s

    18.2 s

    Your largest element takes 18.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This website uses third-party cookies, pixels, and similar …”.

  • Time to Interactive: 19.5 s

    19.5 s

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

  • Speed Index: 8.6 s

    8.6 s

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

  • Total Blocking Time: 659 ms

    659 ms

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

  • Real-user TTFB: 830 ms

    830 ms

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

  • Tap response (INP) held steady for real visitors

    +4%

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

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

    +10%

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

5 checks passed
  • Real-user LCP: 2.5 s

    2.5 s

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

  • Real-user INP: 113 ms

    113 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Cumulative Layout Shift: 0.049

    0.049

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

Images and page weight

1 to fix70
  • Page weight: 10.7 MB in 88 requests

    10.7 MB

    Your homepage downloads 10.7 MB in 88 requests on a phone: media 7.0 MB (2), scripts 2.2 MB (23) and images 783 KiB (26). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (22 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 3.0 g of CO₂ per visit

    3.02 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.02 g of CO₂e: 362.4 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

4 to fixGoogle 9194
  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • 6 buttons without a name

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

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 10 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

3 to fixGoogle 9291
  • No social preview image

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

  • No XML sitemap

    No XML sitemap at https://www.gianvitorossi.com/sitemap.xml, so Google discovers your pages only by following links.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 99 internal links, 7 external

    The homepage links to 99 pages on gianvitorossi.com and 7 external pages.

6 checks passed
  • Meta description: 94 characters

    Your meta description is 94 characters: “Visit the Gianvito Rossi Boutique and discover the Made in Italy Luxury Shoes and Accessories.”.

  • One H1 headline

    Your main headline reads: “Gianvito Rossi United States”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “Gianvito Rossi: Italian Luxury Shoes and Accessories”.

  • Canonical URL set

    The canonical URL is https://www.gianvitorossi.com/us_en.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://www.gianvitorossi.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.

2 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 (457 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 1 linked page hidden from search

    https://www.gianvitorossi.com/us_en/wishlist is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 6 pages share a meta description

    https://www.gianvitorossi.com/us_en/woman/new-arrivals, https://www.gianvitorossi.com/us_en/woman, https://www.gianvitorossi.com/us_en/woman/fashion-fw26, https://www.gianvitorossi.com/us_en/woman/collections, https://www.gianvitorossi.com/us_en/woman/collections/fashion-fw26 and https://www.gianvitorossi.com/us_en/woman/collections/bridal use the same meta description. A description written for each page earns more clicks.

  • 1 page slow to respond

    https://www.gianvitorossi.com/us_en/woman/collections took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

6 checks passed
  • Linked pages load

    10 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 10 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 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 ()”.

2 checks passed
  • Tap targets are thumb-sized

    14 of 14 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • No call to action on the first screen

    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 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 199 words

    The homepage has only about 199 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.

3 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Register”, “Sign in / Register” and “Track order”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 cookies, 3 of them by other companies (measured from a US location before any click).

  • 12 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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

Upkeep, stack and company

Stack

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 33 issues on gianvitorossi.com, including 17 speed issues, 3 SEO issues and 4 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