Website review, no card needed
furybags.it website review
Visit site (opens in a new tab)Reviewed 6 November 202628 issues · 77 checks
This review found 28 issues worth fixing on furybags.it, 11 of them high impact, across 77 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
79C- #55,889 of 125,402 reviewed websitesbeats 50%
- #36,596 of 70,179 online storesbeats 42%
- #35,042 of 63,759 Shopify storesbeats 39%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 194 ms |
| May 23, 2026 | 195 ms |
| May 30, 2026 | 203 ms |
| Jun 6, 2026 | 213 ms |
| Jun 13, 2026 | 219 ms |
| Jun 20, 2026 | 221 ms |
| Jun 27, 2026 | 221 ms |
| Jul 4, 2026 | 227 ms |
| Jul 11, 2026 | 232 ms |
| Jul 18, 2026 | 229 ms |
| Jul 25, 2026 | 230 ms |
| Aug 1, 2026 | 230 ms |
| Aug 8, 2026 | 232 ms |
| Aug 15, 2026 | 238 ms |
| Aug 22, 2026 | 237 ms |
| Aug 29, 2026 | 233 ms |
| Sep 5, 2026 | 227 ms |
| Sep 12, 2026 | 221 ms |
| Sep 19, 2026 | 219 ms |
| Sep 26, 2026 | 212 ms |
| Oct 3, 2026 | 210 ms |
| Oct 10, 2026 | 206 ms |
| Oct 17, 2026 | 205 ms |
| Oct 24, 2026 | 208 ms |
| Oct 31, 2026 | 209 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
How it loaded on a phone
0.8 s
1.7 s
2.5 s
3.3 s
4.2 s
5.0 s
5.8 s
6.7 s
Speed
Reduce unused JavaScript
1.2 s · 416 KiBAbout 416 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Main-thread work: 5.9 s
A phone's processor spends 5.9 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
750 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Improve image delivery
450 ms · 271 KiB12 images could be 271 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, vitals.app and omnisnippet1.com and others), adding 2.1 MB and 480 ms of main-thread time.
Shopify adds 163 ms
163 msShopify costs a phone 163 ms of main-thread work and 845 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.
1,601 HTML elements
The page has 1,601 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
tidio.co adds 75 ms
75 mstidio.co costs a phone 75 ms of main-thread work and 515 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.
Use efficient cache lifetimes
129 KiB11 files are served with short cache lifetimes, so returning visitors download them again (129 KiB).
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 80 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
32 KiBAbout 32 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 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.
1 checks passed
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 13.4 s
13.4 sYour largest element takes 13.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 13.6 s
13.6 sThe page becomes fully interactive after 13.6 s. Good is under 3.8 s.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Speed Index: 4.5 s
4.5 sVisually, the page fills in at 4.5 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 194 ms to 209 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Real-user INP: 175 ms
175 msReal visitors wait 175 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 583 ms
583 msReal visitors wait 583 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 54 ms
54 msScripts block the page for only 54 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 5.0 MB in 563 requests
5.0 MBYour homepage downloads 5.0 MB in 563 requests on a phone: scripts 1.6 MB (192), other files 1.6 MB (282) and images 1.3 MB (43). Under 2 MB keeps phones on slow connections fast.
2 images below the first screen load straight away
2 images further down the page (53 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.42 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.42 g of CO₂e: 170.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 are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
21 text elements with low contrast
21 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “Borse, zaini e portafogli in vera pelle | Made in Italy | Fury Bags”.
Meta description is long (163 characters)
Your meta description is 163 characters; Google truncates after about 160, so the end of your pitch is cut.
95 internal links, 7 external
The homepage links to 95 pages on furybags.it and 7 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Fury”.
Canonical URL set
The canonical URL is https://www.furybags.it/.
Structured data in place
Structured data found: BreadcrumbList, Organization and WebSite.
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://www.furybags.it/sitemap.xml.
AI search readiness
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.
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 (764 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.furybags.it/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://www.furybags.it/blogs/racconti-fury has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.furybags.it/collections/catalogo has 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 39 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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
38 of 45 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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.
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.
About 644 words of copy
The homepage carries about 644 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact us”.
3 short forms
3 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
4 trackers load before any consent
4Before 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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
20 cookies set on arrival
20Opening the homepage sets 20 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.
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.
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 furybags.it, 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 16 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Consentmo Gdpr · Smart Seo · Easy Tag Gtm Data Layer · Ck Whatsapp · Simprosys Google Shopping Feed · Releasit Cod Fee · Vitals · Gdpr Backpack · Omnisend · Countdown Timer · Whatsapp Abandoned Cart · Stape Remix · Checkout Rules · tidio.co · amazonaws.com · carthike.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
- Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on furybags.it, including 14 speed issues, 2 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.