Website review, no card needed
hellochair.nl website review
Visit site (opens in a new tab)Reviewed 9 November 202627 issues · 81 checks
This review found 27 issues worth fixing on hellochair.nl, 8 of them high impact, across 81 checks. The most urgent: render-blocking requests. 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
88B- #5,301 of 109,987 reviewed websitesbeats 93%
- #2,935 of 62,419 online storesbeats 93%
- #2,848 of 56,942 Shopify storesbeats 92%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.4 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.4 s |
| Nov 7, 2026 | 1.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 154 ms |
| May 30, 2026 | 153 ms |
| Jun 6, 2026 | 154 ms |
| Jun 13, 2026 | 157 ms |
| Jun 20, 2026 | 161 ms |
| Jun 27, 2026 | 160 ms |
| Jul 4, 2026 | 162 ms |
| Jul 11, 2026 | 162 ms |
| Jul 18, 2026 | 166 ms |
| Jul 25, 2026 | 169 ms |
| Aug 1, 2026 | 171 ms |
| Aug 8, 2026 | 169 ms |
| Aug 15, 2026 | 164 ms |
| Aug 22, 2026 | 163 ms |
| Aug 29, 2026 | 160 ms |
| Sep 5, 2026 | 160 ms |
| Sep 12, 2026 | 160 ms |
| Sep 19, 2026 | 160 ms |
| Sep 26, 2026 | 158 ms |
| Oct 3, 2026 | 159 ms |
| Oct 10, 2026 | 161 ms |
| Oct 17, 2026 | 155 ms |
| Oct 24, 2026 | 154 ms |
| Oct 31, 2026 | 147 ms |
| Nov 7, 2026 | 143 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
Render-blocking requests
1.3 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
4,171 HTML elements
The page has 4,171 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
600 ms · 604 KiBAbout 604 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Mobile performance score: 73
73/100Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
300 ms · 592 KiB17 images could be 592 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Use efficient cache lifetimes
400 ms · 446 KiB14 files are served with short cache lifetimes, so returning visitors download them again (446 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Cookiebot, Shopify and Google Tag Manager and others), adding 1.4 MB and 683 ms of main-thread time.
Main-thread work: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 987 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Cookiebot adds 254 ms
254 msCookiebot costs a phone 254 ms of main-thread work and 162 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.
Shopify adds 141 ms
141 msShopify costs a phone 141 ms of main-thread work and 475 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.
tweakwisenavigator.net adds 70 ms
70 mstweakwisenavigator.net costs a phone 70 ms of main-thread work and 327 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 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 86 ms. During a long task the page ignores taps.
Reduce unused CSS
25 KiBAbout 25 KiB of CSS is downloaded but never applied on this page.
Duplicated JavaScript
8 KiB8 KiB JavaScript is shipped twice across bundles.
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: 43 ms
43 msYour server sent the HTML in 43 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 text “We gebruiken cookies om content en advertenties te personal…”.
Time to Interactive: 10.9 s
10.9 sThe page becomes fully interactive after 10.9 s. Good is under 3.8 s.
Speed Index: 3.9 s
3.9 sVisually, the page fills in at 3.9 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 154 ms to 143 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
9 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.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 129 ms
129 msReal visitors wait 129 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.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 305 ms
305 msReal visitors wait 305 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 122 ms
122 msScripts block the page for only 122 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 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).
Images and page weight
Page weight: 3.6 MB in 277 requests
3.6 MBYour homepage downloads 3.6 MB in 277 requests on a phone: scripts 1.5 MB (76), images 1,013 KiB (33) and other files 858 KiB (125). Under 2 MB keeps phones on slow connections fast.
About 1.0 g of CO₂ per visit
1.01 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.01 g of CO₂e: 121.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 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.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
50 text elements with low contrast
50 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
54 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
One H1 headline
Your <h1> is empty.
497 internal links, 6 external
The homepage links to 497 pages on hellochair.nl and 6 external pages.
7 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Mooie momenten beleef je met HelloChair. Shop jouw stoelen, tafels en barkrukken online of in de winkels in Breda, Buss…”.
Title: 39 characters
Your title is a healthy 39 characters: “HelloChair - Grootste collectie stoelen”.
Canonical URL set
The canonical URL is https://hellochair.nl/.
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://hellochair.nl/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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,348 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://hellochair.nl/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://hellochair.nl/products/3d-configurator-chairs is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages without a meta description
https://hellochair.nl/products/3d-configurator-chairs and https://hellochair.nl/collections/hellochair have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages slow to respond
https://hellochair.nl/collections/gestoffeerde-stoelen, https://hellochair.nl/collections/armstoelen, https://hellochair.nl/collections/tuinstoelen, https://hellochair.nl/collections/barkrukken, https://hellochair.nl/collections/eetkamerbanken and https://hellochair.nl/collections/bureaustoelen took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 192 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.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
12 small tap targets
12 of 48 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 711 words of copy
The homepage carries about 711 words of visible text.
4 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact” and “Shop nu”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 4 phone links and 0 email links.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Tag Manager and Klaviyo (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.
8 cookies set on arrival
8Opening the homepage sets 8 cookies (measured from a US location before any click).
9 other companies contacted
Loading the homepage contacts 9 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 hellochair.nl, 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 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Ta Labels Badges · Judge Me Reviews · Hulk Form Builder · Free Gift · trustpilot.com · nfcube.com · tidio.co · conversionbear.com · cloudfront.net
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
- 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 27 issues on hellochair.nl, including 14 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.