Website review, no card needed
hbada.eu website review
Visit site (opens in a new tab)Reviewed 20 November 202640 issues · 90 checks
This review found 40 issues worth fixing on hbada.eu, 16 of them high impact, across 90 checks. The most urgent: avoid multiple page redirects. 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
84B- #22,080 of 123,862 reviewed websitesbeats 77%
- #14,229 of 69,698 online storesbeats 74%
- #13,801 of 63,406 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| 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.8 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.7 s |
| Nov 7, 2026 | 1.6 s |
| Nov 14, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 171 ms |
| Jun 6, 2026 | 175 ms |
| Jun 13, 2026 | 185 ms |
| Jun 20, 2026 | 186 ms |
| Jun 27, 2026 | 185 ms |
| Jul 4, 2026 | 186 ms |
| Jul 11, 2026 | 181 ms |
| Jul 18, 2026 | 178 ms |
| Jul 25, 2026 | 171 ms |
| Aug 1, 2026 | 168 ms |
| Aug 8, 2026 | 167 ms |
| Aug 15, 2026 | 167 ms |
| Aug 22, 2026 | 170 ms |
| Aug 29, 2026 | 176 ms |
| Sep 5, 2026 | 184 ms |
| Sep 12, 2026 | 194 ms |
| Sep 19, 2026 | 204 ms |
| Sep 26, 2026 | 212 ms |
| Oct 3, 2026 | 212 ms |
| Oct 10, 2026 | 212 ms |
| Oct 17, 2026 | 213 ms |
| Oct 24, 2026 | 220 ms |
| Oct 31, 2026 | 229 ms |
| Nov 7, 2026 | 236 ms |
| Nov 14, 2026 | 241 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
Speed
Avoid multiple page redirects
13.8 sThe page goes through 2 redirects before it starts loading, costing about 13.8 s. Link and advertise the final URL directly.
Reduce unused JavaScript
5.1 s · 931 KiBAbout 931 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.1 s faster on a phone.
Use efficient cache lifetimes
1.1 s · 169 KiB19 files are served with short cache lifetimes, so returning visitors download them again (169 KiB).
Main-thread work: 12.0 s
A phone's processor spends 12.0 s on main-thread work while loading, 6.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 1.1 s
1.1 sShopify costs a phone 1.1 s of main-thread work and 817 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 42
42/100Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,031 HTML elements
The page has 3,031 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, hbada.com and Clarity and others), adding 7.3 MB and 3.0 s of main-thread time.
hbada.com adds 617 ms
617 mshbada.com costs a phone 617 ms of main-thread work and 5.3 MB 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.
Clarity adds 406 ms
406 msClarity costs a phone 406 ms of main-thread work and 53 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 370 ms
370 msGoogle Tag Manager costs a phone 370 ms of main-thread work and 196 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
300 ms · 46 KiBAbout 46 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.
Render-blocking requests
300 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Klaviyo adds 178 ms
178 msKlaviyo costs a phone 178 ms of main-thread work and 366 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.
Improve image delivery
200 ms · 162 KiB8 images could be 162 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 212 ms. During a long task the page ignores taps.
Document request latency
100 msThe HTML itself could arrive about 100 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Legacy JavaScript
44 KiBPolyfills for old browsers add 44 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: 13 ms
13 msYour server sent the HTML in 13 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 26.1 s
26.1 sYour largest element takes 26.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 27.4 s
27.4 sThe page becomes fully interactive after 27.4 s. Good is under 3.8 s.
Speed Index: 13.5 s
13.5 sVisually, the page fills in at 13.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.7 s
5.7 sThe first text or image appears after 5.7 s on a phone. Good is under 1.8 s.
Tap response (INP) got 38% slower for real visitors
+38%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 171 ms to 241 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 541 ms
541 msScripts block taps and scrolling for 541 ms in total while the page loads. Good is under 200 ms.
8 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: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 146 ms
146 msReal visitors wait 146 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: 754 ms
754 msReal visitors wait 754 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-11-14, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 9.2 MB in 517 requests
9.2 MBYour homepage downloads 9.2 MB in 517 requests on a phone: scripts 3.3 MB (245), media 2.7 MB (1) and images 1.5 MB (58). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
180 KiB1 image is downloaded at several times the size a phone draws it, for example 2132321_97d0cb09-bfdf-41ba-8bd8-2dd442c87b53.png at 1,280 px wide, shown at 74 px. Resized copies would save about 180 KiB.
About 2.6 g of CO₂ per visit
2.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.61 g of CO₂e: 313.4 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 button without a name
1 button has no accessible name, so screen readers announce just “button”.
15 text elements with low contrast
15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
13 tap targets too small
13 tap targets are too small or too close together to hit reliably with a finger.
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 10 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
28 links with vague text
28 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Meta description is long (178 characters)
Your meta description is 178 characters; Google truncates after about 160, so the end of your pitch is cut.
161 internal links, 15 external
The homepage links to 161 pages on hbada.eu and 15 external pages.
7 checks passed
One H1 headline
Your main headline reads: “HBADA Official Europe: Next-Gen AI Smart & Bio-Synchronized Ergonomic Chairs”.
Title: 63 characters
Your title is a healthy 63 characters: “HBADA Official | AI-Powered & Bio-Synchronized Ergonomic Chairs”.
Canonical URL set
The canonical URL is https://www.hbada.eu/.
Structured data in place
Structured data found: 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.hbada.eu/sitemap.xml.
AI search readiness
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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (2,539 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.hbada.eu/llms.txt (31 KiB, 89 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://www.hbada.eu/products/hbada-x7-smart-ergonomic-chair and https://www.hbada.eu/products/hbada-x7-air-smart-ergonomic-office-chair all use the title “Hbada X7 Smart Ergonomic Massage Office Chair, Lumbar Back Support”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.hbada.eu/pages/find-your-chair-guide has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.hbada.eu/products/hbada-x7-smart-ergonomic-chair and https://www.hbada.eu/products/hbada-x7-air-smart-ergonomic-office-chair use the same meta description. A description written for each page earns more clicks.
5 pages without an H1
https://www.hbada.eu/pages/black-friday, https://www.hbada.eu/collections/all-products, https://www.hbada.eu/collections/e3-series, https://www.hbada.eu/products/hbada-x7-prestige-smart-ergonomic-chair and https://www.hbada.eu/products/hbada-x7-air-smart-ergonomic-office-chair 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 51 found) and read each the way a search engine does.
4 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.
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
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
45 of 49 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
About 1,200 words of copy
The homepage carries about 1,200 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 Now”.
59 calls to action
The homepage has 59 calls to action, for example “Learn More”, “Buy Now” and “Bulk Order”.
9 short forms
9 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 3 customer or partner logos and 9 trust badges.
Analytics in place
Analytics detected: Google Analytics and 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
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and LinkedIn Insight and 3 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
28 cookies set on arrival
28Opening the homepage sets 28 cookies, 2 of them by other companies (measured from a US location before any click).
49 other companies contacted
Loading the homepage contacts 49 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 hbada.eu, 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
Convbox Analytics · T Lab Ai Translate · Geolocation Flow · Zigpoll Customer Surveys · Hulk Form Builder · Microsoft Clarity · Klaviyo Email Marketing Sms · Judge Me Reviews · Xapps Geo · Referralcandy · Pushowl · Vanchat · Restockrocket · Free Gift · amazonaws.com · oceanpayment.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
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google 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 40 issues on hbada.eu, including 20 speed issues and 2 SEO issues. 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.