Website review, no card needed
sbaragliastore.com website review
Visit site (opens in a new tab)Reviewed 7 November 202646 issues · 89 checks
This review found 46 issues worth fixing on sbaragliastore.com, 17 of them high impact, across 89 checks. The most urgent: improve image delivery. 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
71C- #100,091 of 124,235 reviewed websitesbeats 17%
- #61,175 of 69,818 online storesbeats 10%
- #56,762 of 63,496 Shopify storesbeats 9%
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 | 1.9 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 130 ms |
| May 23, 2026 | 133 ms |
| May 30, 2026 | 136 ms |
| Jun 6, 2026 | 139 ms |
| Jun 13, 2026 | 139 ms |
| Jun 20, 2026 | 138 ms |
| Jun 27, 2026 | 136 ms |
| Jul 4, 2026 | 129 ms |
| Jul 11, 2026 | 135 ms |
| Jul 18, 2026 | 135 ms |
| Jul 25, 2026 | 135 ms |
| Aug 1, 2026 | 140 ms |
| Aug 8, 2026 | 135 ms |
| Aug 15, 2026 | 133 ms |
| Aug 22, 2026 | 138 ms |
| Aug 29, 2026 | 135 ms |
| Sep 5, 2026 | 140 ms |
| Sep 12, 2026 | 144 ms |
| Sep 19, 2026 | 145 ms |
| Sep 26, 2026 | 155 ms |
| Oct 3, 2026 | 148 ms |
| Oct 10, 2026 | 148 ms |
| Oct 17, 2026 | 147 ms |
| Oct 24, 2026 | 135 ms |
| Oct 31, 2026 | 146 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.4 s
0.9 s
1.3 s
1.8 s
2.2 s
2.7 s
3.1 s
3.6 s
Speed
Improve image delivery
1.7 s · 333 KiB1 image could be 333 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.7 s faster on a phone.
Render-blocking requests
1.1 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 45
45/100Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,351 HTML elements
The page has 3,351 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
580 ms · 504 KiBAbout 504 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 580 ms faster on a phone.
Reduce unused CSS
580 ms · 138 KiBAbout 138 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 580 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Shopify and iubenda and others), adding 1.1 MB and 573 ms of main-thread time.
Main-thread work: 3.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 201 ms
201 msShopify costs a phone 201 ms of main-thread work and 598 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.
Google Tag Manager adds 214 ms
214 msGoogle Tag Manager costs a phone 214 ms of main-thread work and 309 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 180 ms. During a long task the page ignores taps.
Minify CSS
130 ms · 15 KiB15 KiB could be saved by minifying CSS.
Use efficient cache lifetimes
76 KiB14 files are served with short cache lifetimes, so returning visitors download them again (76 KiB).
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: 6 ms
6 msYour server sent the HTML in 6 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: 7.7 s
7.7 sYour largest element takes 7.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Sbaragliastore.com”.
Time to Interactive: 16.5 s
16.5 sThe page becomes fully interactive after 16.5 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.4
0.4The layout shifts by 0.4 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user CLS: 0.16
0.16For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.
Speed Index: 5.3 s
5.3 sVisually, the page fills in at 5.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 324 ms
324 msScripts block taps and scrolling for 324 ms in total while the page loads. Good is under 200 ms.
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
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 130 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 191 ms
191 msReal visitors wait 191 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 725 ms
725 msReal visitors wait 725 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.
Images and page weight
Page weight: 3.2 MB in 243 requests
3.2 MBYour homepage downloads 3.2 MB in 243 requests on a phone: scripts 1.3 MB (59), other files 856 KiB (137) and images 496 KiB (13). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
283 KiB1 image is downloaded at several times the size a phone draws it, for example image_15.png at 2,457 px wide, shown at 390 px. Resized copies would save about 283 KiB.
About 0.9 g of CO₂ per visit
0.91 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.91 g of CO₂e: 109.1 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
Unlabelled dropdowns
1 dropdown has no label.
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.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA input fields do not have accessible names
ARIA input fields do not have accessible names (1 element).
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 9 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (91 characters)
Your title is 91 characters, so Google will cut it off around 60: “Sbaraglia Store | Vendita online Abbigliamento Scarpe e Accessori Moda – Sbaragliastore.c…”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
15 links crawlers can't follow
15 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
92 internal links, 9 external
The homepage links to 92 pages on sbaragliastore.com and 9 external pages.
6 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “Su Sbaraglia potrai trovare abbigliamento uomo donna, vendita online scarpe uomo donna e accessori moda delle migliori …”.
One H1 headline
Your main headline reads: “Sbaraglia Store”.
Canonical URL set
The canonical URL is https://www.sbaragliastore.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://www.sbaragliastore.com/sitemap.xml.
AI search readiness
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 (440 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.sbaragliastore.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://www.sbaragliastore.com/collections/vendors, which answers with an error. Visitors hit a dead end and search engines drop it.
1 page without a title
https://www.sbaragliastore.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.sbaragliastore.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://www.sbaragliastore.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.sbaragliastore.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.sbaragliastore.com/customer_authentication/redirect took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 48 found) and read each the way a search engine does.
1 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Best practices
12 small tap targets
12 of 45 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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.”).
Requests the notification permission on page load
Requests the notification permission on page load.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 366 words of copy
The homepage carries about 366 words of visible text.
2 checks passed
4 short forms
4 short forms (5 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and TikTok 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.
12 cookies set on arrival
12Opening the homepage sets 12 cookies (measured from a US location before any click).
24 other companies contacted
Loading the homepage contacts 24 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 sbaragliastore.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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Event Promotion Bar · Pushowl · Sidekick · Ecomsend · trustpilot.com · hextom.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
- The footer still says © 2011.
Stack
- Framework
- jQuery
- 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 46 issues on sbaragliastore.com, including 18 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.