Website review, no card needed

suitnegozi.com logo

suitnegozi.com website review

Visit site (opens in a new tab)Reviewed 5 November 202634 issues · 79 checks

This review found 34 issues worth fixing on suitnegozi.com, 10 of them high impact, across 79 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
3.1 s1.8 sMay 16Oct 312.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.3 s
May 23, 20262.2 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.0 s
Jun 20, 20261.9 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.2 s
Jul 18, 20262.3 s
Jul 25, 20262.4 s
Aug 1, 20262.5 s
Aug 8, 20262.6 s
Aug 15, 20262.6 s
Aug 22, 20262.8 s
Aug 29, 20262.9 s
Sep 5, 20262.9 s
Sep 12, 20263.0 s
Sep 19, 20262.8 s
Sep 26, 20262.8 s
Oct 3, 20262.5 s
Oct 17, 20262.6 s
Oct 24, 20262.5 s
Oct 31, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
171 ms95 msMay 16Oct 31119 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026120 ms
May 23, 2026112 ms
May 30, 2026111 ms
Jun 6, 2026111 ms
Jun 13, 2026106 ms
Jun 20, 2026104 ms
Jun 27, 2026106 ms
Jul 4, 2026112 ms
Jul 11, 2026126 ms
Jul 18, 2026131 ms
Jul 25, 2026130 ms
Aug 1, 2026131 ms
Aug 8, 2026142 ms
Aug 15, 2026136 ms
Aug 22, 2026149 ms
Aug 29, 2026161 ms
Sep 5, 2026157 ms
Sep 12, 2026162 ms
Sep 19, 2026159 ms
Sep 26, 2026136 ms
Oct 3, 2026115 ms
Oct 17, 2026112 ms
Oct 24, 2026110 ms
Oct 31, 2026119 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 suitnegozi.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. suitnegozi.com at 1.0 s1.0 s
  2. suitnegozi.com at 2.1 s2.1 s
  3. suitnegozi.com at 3.1 s3.1 s
  4. suitnegozi.com at 4.1 s4.1 s
  5. suitnegozi.com at 5.1 s5.1 s
  6. suitnegozi.com at 6.2 s6.2 s
  7. suitnegozi.com at 7.2 s7.2 s
  8. suitnegozi.com at 8.2 s8.2 s

Speed

9 to fix65
  • Reduce unused JavaScript

    2.0 s · 369 KiB

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

  • Main-thread work: 6.7 s

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

  • 3,469 HTML elements

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

  • Improve image delivery

    900 ms · 174 KiB

    6 images could be 174 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.

  • Mobile performance score: 65

    65/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, iubenda and Cloudflare CDN and others), adding 1.2 MB and 877 ms of main-thread time.

  • Use efficient cache lifetimes

    750 ms · 180 KiB

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

  • Render-blocking requests

    700 ms

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

  • Shopify adds 610 ms

    610 ms

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

  • Reduce unused CSS

    150 ms · 39 KiB

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

  • 12 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    24 KiB

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

  • 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

    4 KiB

    4 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 11 ms

    11 ms

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

Core Web Vitals

8 to fix67
  • 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: 10.7 s

    10.7 s

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

  • Time to Interactive: 10.9 s

    10.9 s

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

  • Real-user LCP: 3.3 s

    3.3 s

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • Speed Index: 5.7 s

    5.7 s

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

  • Total Blocking Time: 266 ms

    266 ms

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

  • Tap response (INP) held steady for real visitors

    -1%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 120 ms to 119 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-31, 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 INP: 147 ms

    147 ms

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix60
  • Page weight: 14.1 MB in 300 requests

    14.1 MB

    Your homepage downloads 14.1 MB in 300 requests on a phone: media 11.1 MB (1), scripts 1.2 MB (135) and other files 792 KiB (125). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    65 KiB

    2 images are downloaded at several times the size a phone draws them, for example 099-loewe-a510plsx203918.jpg at 900 px wide, shown at 189 px. Resized copies would save about 65 KiB.

  • About 4.0 g of CO₂ per visit

    4.00 g

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

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

5 to fixGoogle 8993
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 tap target too small

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

  • 2 images without alt text

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

  • 17 links without text

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

  • Alternative text of images should not be repeated as text (3 elements)

    Alternative text of images should not be repeated as text: 3 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. (2 elements).

1 checks passed
  • 52 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: 52 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9296
  • Structured data has 1 problem

    Structured data found (BreadcrumbList, Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://suitnegozi.com)”.

  • 338 internal links, 6 external

    The homepage links to 338 pages on suitnegozi.com and 6 external pages.

7 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Discover the elegance and quality of luxury fashion on Suit Stores. Exclusive collections for those who love to stand o…”.

  • One H1 headline

    Your main headline reads: “Suit Negozi”.

  • Title: 56 characters

    Your title is a healthy 56 characters: “Suit Boutique Online | The best of Luxury Fashion online”.

  • Canonical URL set

    The canonical URL is https://row.suitnegozi.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://row.suitnegozi.com/sitemap.xml.

AI search readiness

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

    Your Organization JSON-LD is missing logo, 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.

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

  • llms.txt published

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

Other pages

2 to fix90
  • 14 pages without a meta description

    https://row.suitnegozi.com/collections/fw26-woman, https://row.suitnegozi.com/collections/fw26-woman-clothing, https://row.suitnegozi.com/collections/fw26-woman-shoes, https://row.suitnegozi.com/collections/fw26-woman-bag, https://row.suitnegozi.com/collections/fw26-woman-accessories and https://row.suitnegozi.com/collections/fw26-man and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://row.suitnegozi.com/collections/fw26-woman, https://row.suitnegozi.com/collections/fw26-woman-clothing, https://row.suitnegozi.com/collections/fw26-woman-shoes, https://row.suitnegozi.com/collections/fw26-woman-bag, https://row.suitnegozi.com/collections/fw26-woman-accessories and https://row.suitnegozi.com/collections/fw26-man and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 143 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 9 small tap targets

    9 of 22 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 “Access to XMLHttpRequest at 'https://assets.smartwishlist.webmarked.net/static/v7/css/smartwishlist.min.css?20260510' f…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix71
  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • 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 231 words

    The homepage has only about 231 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
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn more and customize”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Sign Up” and “Contact”.

  • 8 short forms

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

Privacy and tracking

  • 4 trackers load before any consent

    4

    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.

  • 19 cookies set on arrival

    19

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

  • 30 other companies contacted

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

1 checks passed
  • Consent tool: iubenda

    A consent management tool (iubenda) 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 suitnegozi.com, 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 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Scalapay On Site Messaging · Smart Wishlist · Scalapay Widget Installer Prod · Booking · Back In Stock

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

  • The footer still says © 2019.

Stack

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 34 issues on suitnegozi.com, including 17 speed issues, 1 SEO issue 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