Website review, no card needed

biaggi.com logo

biaggi.com website review

Visit site (opens in a new tab)Reviewed 7 November 202636 issues · 84 checks

This review found 36 issues worth fixing on biaggi.com, 8 of them high impact, across 84 checks. The most urgent: page weight: 15.0 MB in 367 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.7 s2.2 sMay 16Oct 312.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.6 s
May 23, 20262.5 s
May 30, 20262.4 s
Jun 6, 20262.4 s
Jun 13, 20262.4 s
Jun 20, 20262.4 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20262.4 s
Jul 25, 20262.4 s
Aug 1, 20262.5 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.4 s
Aug 29, 20262.4 s
Sep 5, 20262.4 s
Sep 12, 20262.4 s
Sep 19, 20262.4 s
Sep 26, 20262.4 s
Oct 3, 20262.4 s
Oct 10, 20262.3 s
Oct 17, 20262.3 s
Oct 24, 20262.3 s
Oct 31, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
164 ms114 msMay 16Oct 31137 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026120 ms
May 23, 2026123 ms
May 30, 2026131 ms
Jun 6, 2026138 ms
Jun 13, 2026138 ms
Jun 20, 2026138 ms
Jun 27, 2026141 ms
Jul 4, 2026138 ms
Jul 11, 2026142 ms
Jul 18, 2026138 ms
Jul 25, 2026137 ms
Aug 1, 2026137 ms
Aug 8, 2026136 ms
Aug 15, 2026141 ms
Aug 22, 2026146 ms
Aug 29, 2026150 ms
Sep 5, 2026158 ms
Sep 12, 2026156 ms
Sep 19, 2026154 ms
Sep 26, 2026154 ms
Oct 3, 2026154 ms
Oct 10, 2026151 ms
Oct 17, 2026150 ms
Oct 24, 2026139 ms
Oct 31, 2026137 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 biaggi.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. biaggi.com at 0.7 s0.7 s
  2. biaggi.com at 1.3 s1.3 s
  3. biaggi.com at 2.0 s2.0 s
  4. biaggi.com at 2.7 s2.7 s
  5. biaggi.com at 3.4 s3.4 s
  6. biaggi.com at 4.0 s4.0 s
  7. biaggi.com at 4.7 s4.7 s
  8. biaggi.com at 5.4 s5.4 s

Speed

12 to fix56
  • Main-thread work: 7.2 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, rebuyengine.com and Shopify and others), adding 1.9 MB and 1.2 s of main-thread time.

  • Mobile performance score: 56

    56/100

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

  • Reduce unused JavaScript

    150 ms · 745 KiB

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

  • Improve image delivery

    350 ms · 517 KiB

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

  • Render-blocking requests

    800 ms

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

  • Use efficient cache lifetimes

    774 KiB

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

  • 14 long tasks on the main thread

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

  • Klaviyo adds 262 ms

    262 ms

    Klaviyo costs a phone 262 ms of main-thread work and 502 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.

  • 2,951 HTML elements

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

  • rebuyengine.com adds 198 ms

    198 ms

    rebuyengine.com costs a phone 198 ms of main-thread work and 331 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.

  • Attentive adds 148 ms

    148 ms

    Attentive costs a phone 148 ms of main-thread work and 525 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 · 81 KiB

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

  • Legacy JavaScript

    56 KiB

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

  • Font display

    50 ms

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

  • Minify JavaScript

    10 KiB

    10 KiB could be saved by minifying JavaScript.

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

  • Duplicated JavaScript

    4 KiB

    4 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 14 ms

    14 ms

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

Core Web Vitals

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

  • Time to Interactive: 24.2 s

    24.2 s

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

  • Largest Contentful Paint: 7.2 s

    7.2 s

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

  • Speed Index: 10.3 s

    10.3 s

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

  • Real-user LCP: 2.9 s

    2.9 s

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

  • Total Blocking Time: 399 ms

    399 ms

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

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

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

    +14%

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

6 checks passed
  • Real-user INP: 96 ms

    96 ms

    Real visitors wait 96 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.3 s

    1.3 s

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

  • Real-user TTFB: 436 ms

    436 ms

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

  • Largest content (LCP) got 13% faster for real visitors

    -13%

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

  • 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: 15.0 MB in 367 requests

    15.0 MB

    Your homepage downloads 15.0 MB in 367 requests on a phone: media 10.2 MB (2), scripts 1.9 MB (125) and images 1.5 MB (57). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    52 KiB

    1 image is downloaded at several times the size a phone draws it, for example c42b70fb4290e7206501487710475ac0.png at 389 px wide, shown at 52 px. Resized copies would save about 52 KiB.

  • About 4.2 g of CO₂ per visit

    4.24 g

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

1 to fixGoogle 8995
  • 3 text elements with low contrast

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

2 checks passed
  • Every image has alt text

    All 250 images in the HTML carry an alt attribute.

  • 17 automated accessibility rules passed

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

SEO

3 to fixGoogle 9290
  • 2 H1 headlines

    There are 2 <h1> headlines (“Introducing The Glide Collection!” and “Stock Up For Summer Travel!”). One clear main headline is easier for people and search engines.

  • No social preview image

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

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 128 internal links, 6 external

    The homepage links to 128 pages on biaggi.com and 6 external pages.

6 checks passed
  • Meta description: 150 characters

    Your meta description is 150 characters: “Biaggi will make Your Business Trips & Weekends Away A Whole Lot Easier. Shop Now! Travel in Style · As Seen on Shark T…”.

  • Title: 34 characters

    Your title is a healthy 34 characters: “Biaggi | Fits Right in Your Closet”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, 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://biaggi.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 (1,286 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

5 to fix76
  • 2 pages share a title

    https://biaggi.com/products/runway-hybrid-expandable-underseater and https://biaggi.com/collections/bestsellers/products/runway-hybrid-expandable-underseater all use the title “Runway Hybrid Expandable Underseater – Biaggi”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 11 pages without a meta description

    https://biaggi.com/collections/trolley-luggage-1, https://biaggi.com/collections/carry-on-luggage, https://biaggi.com/collections/totes-backpacks, https://biaggi.com/collections/zipsak-1, https://biaggi.com/collections/packing-cubes-and-organizers and https://biaggi.com/collections/all and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://biaggi.com/products/runway-hybrid-expandable-underseater and https://biaggi.com/collections/bestsellers/products/runway-hybrid-expandable-underseater use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://biaggi.com/collections/bestsellers/products/runway-hybrid-expandable-underseater, whose canonical is https://biaggi.com/products/runway-hybrid-expandable-underseater. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://biaggi.com/products/runway-hybrid-expandable-underseater and https://biaggi.com/collections/bestsellers/products/runway-hybrid-expandable-underseater have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://biaggi.com/products/runway-hybrid-expandable-underseater, https://biaggi.com/collections/bestsellers/products/runway-hybrid-expandable-underseater and https://biaggi.com/products/carry-cubes-backpack 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 46 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

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

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7776
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=343178436&tm=shpfy_ui&Ver=2&mid=51e6eb7f-ce4d-432a-a3fe-6eba422adbb1&bo=1&sid=6743bda0dacc11f18bd539207173937d&vid=6743fe80dacc11f1ad334fd9675b13d6&vids=1&msclkid=N&pi.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 5 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • About 513 words of copy

    The homepage carries about 513 words of visible text.

6 checks passed
  • Clear next step on the first screen

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

  • 16 calls to action

    The homepage has 16 calls to action, for example “Shop All”, “Shop Glide” and “Shop Now”.

  • 24 short forms

    24 short forms (1 field at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 60 testimonial or review blocks and 4 customer or partner logos.

  • Analytics in place

    Analytics detected: Microsoft Clarity.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 49 cookies set on arrival

    49

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

  • 59 other companies contacted

    Loading the homepage contacts 59 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 biaggi.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 18 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Attentive · Klaviyo Email Marketing Sms · Yotpo Product Reviews · Redo · C Edd Estimated Delivery Date · Geoip Country Redirect · Ground · Mntn · Triplewhale · Freegifts · cloudfront.net · gorgias.chat · getredo.com · rebuyengine.com · amazonaws.com · retention.com · attn.tv · 9gtb.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

E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

Company

Headquarters
New York

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on biaggi.com, including 19 speed issues, 3 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