Website review, no card needed

ilbisonte.com logo

ilbisonte.com website review

Visit site (opens in a new tab)Reviewed 19 October 202632 issues · 80 checks

This review found 32 issues worth fixing on ilbisonte.com, 7 of them high impact, across 80 checks. The most urgent: fails Core Web Vitals for real visitors. 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
4.8 s1.6 sApr 25Oct 104.4 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.0 s
May 2, 20262.0 s
May 9, 20262.0 s
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20261.9 s
Jun 20, 20262.0 s
Jun 27, 20262.8 s
Jul 4, 20263.4 s
Jul 11, 20263.7 s
Jul 18, 20263.9 s
Jul 25, 20264.0 s
Aug 1, 20264.0 s
Aug 8, 20264.0 s
Aug 15, 20264.0 s
Aug 22, 20264.1 s
Aug 29, 20264.2 s
Sep 5, 20264.3 s
Sep 12, 20264.3 s
Sep 19, 20264.4 s
Sep 26, 20264.4 s
Oct 3, 20264.4 s
Oct 10, 20264.4 s
Real-visitor tap response (INP)75th percentile, phones
93 ms77 msApr 25Oct 1091 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 202681 ms
May 2, 202681 ms
May 9, 202680 ms
May 16, 202679 ms
May 23, 202679 ms
May 30, 202679 ms
Jun 6, 202679 ms
Jun 13, 202682 ms
Jun 20, 202679 ms
Jun 27, 202679 ms
Jul 4, 202680 ms
Jul 11, 202679 ms
Jul 18, 202680 ms
Jul 25, 202679 ms
Aug 1, 202679 ms
Aug 8, 202679 ms
Aug 15, 202680 ms
Aug 22, 202682 ms
Aug 29, 202684 ms
Sep 5, 202685 ms
Sep 12, 202683 ms
Sep 19, 202686 ms
Sep 26, 202688 ms
Oct 3, 202688 ms
Oct 10, 202691 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 ilbisonte.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ilbisonte.com at 0.8 s0.8 s
  2. ilbisonte.com at 1.6 s1.6 s
  3. ilbisonte.com at 2.5 s2.5 s
  4. ilbisonte.com at 3.3 s3.3 s
  5. ilbisonte.com at 4.1 s4.1 s
  6. ilbisonte.com at 4.9 s4.9 s
  7. ilbisonte.com at 5.7 s5.7 s
  8. ilbisonte.com at 6.5 s6.5 s

Speed

9 to fix59
  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Accessibe Accessibility Overlay and Shopify and others), adding 1.7 MB and 1.5 s of main-thread time.

  • Mobile performance score: 59

    59/100

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

  • Google Tag Manager adds 806 ms

    806 ms

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

    787 KiB

    About 787 KiB of JavaScript is downloaded but never used on this page.

  • Render-blocking requests

    700 ms

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

  • Main-thread work: 3.8 s

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

  • Reduce unused CSS

    300 ms · 33 KiB

    About 33 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,586 HTML elements

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

  • Shopify adds 183 ms

    183 ms

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

  • 12 long tasks on the main thread

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

  • Improve image delivery

    56 KiB

    3 images could be 56 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Use efficient cache lifetimes

    29 KiB

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

  • Minify JavaScript

    19 KiB

    19 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    11 KiB

    Polyfills for old browsers add 11 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 CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 16 ms

    16 ms

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

Core Web Vitals

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

  • Real-user LCP: 4.8 s

    4.8 s

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

  • Real-user FCP: 4.8 s

    4.8 s

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

  • Time to Interactive: 17.6 s

    17.6 s

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

  • Speed Index: 9.9 s

    9.9 s

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

  • Total Blocking Time: 828 ms

    828 ms

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

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

    +119%

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

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Largest Contentful Paint: 3.5 s

    3.5 s

    Your largest element takes 3.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (2.9 s).

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

    +10%

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

3 checks passed
  • Real-user INP: 78 ms

    78 ms

    Real visitors wait 78 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

2 to fix81
  • Page weight: 3.3 MB in 221 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 221 requests on a phone: scripts 1.8 MB (71), other files 733 KiB (96) and images 550 KiB (29). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    search-cover_500x.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image in older formats

    1 image (39 KiB) is 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 0.9 g of CO₂ per visit

    0.93 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

1 to fixGoogle 10099
  • All page content should be contained by landmarks (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • Headings skip levels

    Headings skip levels (h2 → h4, h4 → h6 and h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 82 images in the HTML carry an alt attribute.

  • 45 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: 45 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

2 to fixGoogle 10090
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Il Bisonte - High Quality Leather Bags and Accessories | Il Bisonte”.

  • No social preview image

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

  • 267 internal links, 49 external

    The homepage links to 267 pages on ilbisonte.com and 49 external pages.

6 checks passed
  • Meta description: 147 characters

    Your meta description is 147 characters: “Discover Il Bisonte's high-quality leather bags and accessories: personalize and complete your style with the wide rang…”.

  • One H1 headline

    Your main headline reads: “Fall Winter Collection”.

  • Canonical URL set

    The canonical URL is https://www.ilbisonte.com/en-usa.

  • Structured data in place

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

  • llms.txt published

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

Other pages

2 to fix70
  • 8 linked pages are broken

    Your homepage links to https://www.ilbisonte.com/en-usa/collections/new-arrivals, https://www.ilbisonte.com/en-usa/collections/bags-women, https://www.ilbisonte.com/en-usa/collections/crossbody-bags-women, https://www.ilbisonte.com/en-usa/collections/hobo, https://www.ilbisonte.com/en-usa/collections/tote-bags-women and https://www.ilbisonte.com/en-usa/collections/backpacks-women and 2 others, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 1 page without a meta description

    https://www.ilbisonte.com/en-usa/collections/fall-winter-collection has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages slow to respond

    https://www.ilbisonte.com/en-usa/pages/returns and https://www.ilbisonte.com/en-usa/collections/wallets-women took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

5 checks passed
  • 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 4 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7385
  • 11 small tap targets

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

  • 2 third-party cookies

    2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 422 ()”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • Thin social proof

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

  • A 12-field form

    Your longest form asks for 12 fields (2 required). Every extra field lowers completion.

  • About 489 words of copy

    The homepage carries about 489 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: “Search the shop”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Search the shop”, “Subscribe” and “REQUEST A RETURN”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • 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

  • 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 (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

  • 11 cookies set on arrival

    11

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

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

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 ilbisonte.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
jQuery
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 ilbisonte.com, including 19 speed issues, 2 SEO issues and 2 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