Website review, no card needed

qb24.com logo

qb24.com website review

Visit site (opens in a new tab)Reviewed 16 November 202633 issues · 86 checks

This review found 33 issues worth fixing on qb24.com, 9 of them high impact, across 86 checks. The most urgent: page weight: 38.3 MB in 241 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.2 s737 msMay 30Nov 142.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.1 s
Jun 6, 20261.0 s
Jun 13, 2026962 ms
Jun 20, 2026962 ms
Jun 27, 2026936 ms
Jul 4, 2026918 ms
Jul 11, 2026977 ms
Jul 18, 2026910 ms
Jul 25, 2026911 ms
Aug 1, 2026963 ms
Aug 8, 2026943 ms
Aug 15, 2026997 ms
Aug 22, 20261.1 s
Aug 29, 20261.2 s
Sep 5, 20261.4 s
Sep 19, 20261.2 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.5 s
Oct 31, 20261.8 s
Nov 7, 20262.0 s
Nov 14, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
136 ms81 msMay 30Nov 14130 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202688 ms
Jun 6, 202687 ms
Jun 13, 202690 ms
Jun 20, 202689 ms
Jun 27, 202693 ms
Jul 4, 202694 ms
Jul 25, 202687 ms
Aug 1, 202695 ms
Aug 8, 202695 ms
Aug 29, 2026118 ms
Oct 10, 202689 ms
Oct 17, 202688 ms
Nov 14, 2026130 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 qb24.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. qb24.com at 0.4 s0.4 s
  2. qb24.com at 0.8 s0.8 s
  3. qb24.com at 1.1 s1.1 s
  4. qb24.com at 1.5 s1.5 s
  5. qb24.com at 1.9 s1.9 s
  6. qb24.com at 2.3 s2.3 s
  7. qb24.com at 2.6 s2.6 s
  8. qb24.com at 3.0 s3.0 s

Speed

6 to fix81
  • Render-blocking requests

    1.2 s

    7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.

  • Mobile performance score: 81

    81/100

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

  • Improve image delivery

    450 ms · 343 KiB

    8 images could be 343 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.

  • Use efficient cache lifetimes

    500 ms · 57 KiB

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

  • 1,589 HTML elements

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

  • JSDelivr CDN adds 59 ms

    59 ms

    JSDelivr CDN costs a phone 59 ms of main-thread work and 341 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.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Cookiebot, JSDelivr CDN and Shopify and others), adding 727 KiB and 312 ms of main-thread time.

  • Reduce unused JavaScript

    150 ms · 136 KiB

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

  • Reduce unused CSS

    150 ms · 40 KiB

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

  • 4 long tasks on the main thread

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

  • Duplicated JavaScript

    42 KiB

    42 KiB JavaScript is shipped twice across bundles.

  • Minify JavaScript

    37 KiB

    37 KiB could be saved by minifying JavaScript.

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

2 checks passed
  • Main-thread work: 1.9 s

    A phone's processor spends 1.9 s on main-thread work while loading, 664 ms of it running JavaScript. That is comfortably low.

  • Server response: 9 ms

    9 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 5.0 s

    5.0 s

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

  • Time to Interactive: 9.1 s

    9.1 s

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

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

    +25%

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

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

    +90%

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

  • 3 images without width and height

    3 images have no width and height attributes, so the layout jumps as each one loads.

10 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 2.1 s

    2.1 s

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

  • Real-user INP: 130 ms

    130 ms

    Real visitors wait 130 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.4 s

    1.4 s

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

  • Real-user TTFB: 542 ms

    542 ms

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

  • Speed Index: 3.0 s

    3.0 s

    Visually, the page fills in at 3.0 s (Speed Index), inside the 3.4 s “good” threshold.

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

  • Total Blocking Time: 81 ms

    81 ms

    Scripts block the page for only 81 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0.033

    0.033

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

Images and page weight

2 to fix64
  • Page weight: 38.3 MB in 241 requests

    38.3 MB

    Your homepage downloads 38.3 MB in 241 requests on a phone: media 36.0 MB (2), scripts 846 KiB (154) and images 622 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Banner-M.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).

  • About 10.8 g of CO₂ per visit

    10.85 g

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

8 to fixGoogle 7390
  • 4 buttons without a name

    4 buttons have no accessible name, so screen readers announce just “button”.

  • 8 images without alt text

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

  • All page content should be contained by landmarks (10 elements)

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 14 links without text

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

  • 8 form fields without a label

    8 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 4 tap targets too small

    4 tap targets are too small or too close together to hit reliably with a finger.

  • Headings skip levels

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

1 checks passed
  • 43 automated accessibility rules passed

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

SEO

3 to fixGoogle 9279
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (4 characters)

    Your title is only 4 characters: “QB24”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("Liquid error (snippets/schema line 16): invalid url inp…”.

  • 98 internal links, 15 external

    The homepage links to 98 pages on qb24.com and 15 external pages.

5 checks passed
  • Meta description: 133 characters

    Your meta description is 133 characters: “Su QB24.com, realizziamo il miglior abbigliamento uomo: giacche, jeans, t-shirt e abiti per uno stile raffinato, modern…”.

  • Canonical URL set

    The canonical URL is https://qb24.com/it-it.

  • 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://qb24.com/sitemap.xml.

AI search readiness

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

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (668 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 3 pages without an H1

    https://qb24.com/it-it/pages/iscrizione-newsletter-qb24, https://qb24.com/it-it/collections/giacche-uomo and https://qb24.com/it-it/collections/maglieria-e-cardigan-uomo 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 31 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

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

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 3 pages that loaded have a meta description.

  • 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 3 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9291
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://qb24.com/cdn/shop/t/44/assets/base.css?v=18928' because its MIME type ('text/html'…”.

  • 3 distorted images

    3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

    28 of 30 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix50
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 4 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 313 words of copy

    The homepage carries about 313 words of visible text.

2 checks passed
  • 6 short forms

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

  • Analytics in place

    Analytics detected: Microsoft Clarity.

Privacy and tracking

  • 6 cookies set on arrival

    6

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

  • 5 other companies contacted

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

2 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 qb24.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 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Oxi Social Login Wishlist · Microsoft Clarity · Restockrocket

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

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on qb24.com, including 11 speed issues, 3 SEO issues and 6 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