helloboku.com website review

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

Your mobile performance score is 46. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 8.4 s on main-thread work while loading, 4.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Google Tag Manager, Klaviyo and OptiMonk and others), adding 1.4 MB and 1.8 s of main-thread time.

About 868 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

Google Tag Manager costs a phone 799 ms of main-thread work and 421 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.

4 images could be 115 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

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

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

Klaviyo costs a phone 237 ms of main-thread work and 360 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.

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

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

Polyfills for old browsers add 70 KiB JavaScript that modern phones do not need.

17 KiB JavaScript is shipped twice across bundles.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

5 KiB could be saved by minifying JavaScript.

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

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

Scripts block taps and scrolling for 1.3 s in total while the page loads. Good is under 200 ms.

Visually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.

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

Your homepage downloads 4.5 MB in 397 requests on a phone: scripts 2.3 MB (135), other files 1.0 MB (184) and images 1.0 MB (59). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 1.28 g of CO₂e: 153.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

17 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Some list items are not inside a list.

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

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

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

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

ARIA role should be appropriate for the element: 6 elements on the page fail this check, rated minor by axe-core.

There are 2 <h1> headlines (“Le WC japonais par BOKU” and “L’art du soin par l’eau”). One clear main headline is easier for people and search engines.

Your meta description is 277 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 184 pages on helloboku.com and 7 external pages.

/collections/accessoires-nav and /collections/packs-economiques are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/collections/packs-economiques and /collections/packs-economiques-1 all use the title “Packs économiques – BOKU”. Search engines can't tell which page to show for a search, so each competes with the others.

/collections/accessoires-nav, /collections/pieces-detaches, /collections/packs-economiques, /pages/installation-compatibilite, /collections/packs-economiques-1 and /pages/univers-salle-de-bain have no meta description, so Google writes the search snippet from whatever text it finds.

/collections/accessoires-nav, /collections/pieces-detaches, /collections/packs-economiques, /pages/installation-compatibilite and /collections/univers-wc have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 36 found) and read each the way a search engine does.

8 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_EMPTY_RESPONSE”.

Chrome logged issues while loading the page (“Cookie”).

HSTS is set, but max-age is 91 days; one year is the recommended minimum.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 767 words of visible text.

DMARC is set to p=none, so mail pretending to be helloboku.com is still delivered. Reports are on, so moving to quarantine is the next step.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Criteo, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 3 mores (measured from a US location before any click). A consent tool (Didomi) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 24 cookies, 2 of them by other companies (measured from a US location before any click).

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