daisous.com website review

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

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

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

Shopify costs a phone 126 ms of main-thread work and 578 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.

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

8 third-party services load with your homepage (Shopify, Google Tag Manager and accessibly.app and others), adding 915 KiB and 268 ms of main-thread time.

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

5 files block the first paint until they finish downloading. Deferring or inlining them could save about 100 ms.

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

About 21 KiB of CSS is downloaded but never applied on this page.

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.

2 KiB JavaScript is shipped twice across bundles.

Your largest element takes 6.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “a cartoon elephant holding a bag and a bag”.

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

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

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

The first text or image appears after 2.1 s on a phone. Good is under 1.8 s.

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

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

Your homepage downloads 19.5 MB in 332 requests on a phone: media 16.2 MB (2), other files 1.1 MB (198) and scripts 1,008 KiB (69). Under 2 MB keeps phones on slow connections fast.

EC_bulk_mobile_banner_EN.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).

1 image further down the page (29 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

Your <h1> is empty.

The homepage links to 36 pages on daisous.com and 28 external pages.

/customer_authentication/redirect has no <title>, so Google invents the link text in results.

/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/blogs/daiso-updates, /pages/daizo, /customer_authentication/redirect, /pages/ec-bulk, /a/store-locator/list and /pages/subscribe have no meta description, so Google writes the search snippet from whatever text it finds.

/pages/about-us, /customer_authentication/redirect, /pages/ec-bulk and /pages/subscribe have no <h1> headline, so visitors and search engines get no clear main topic.

/a/store-locator/list and /pages/subscribe have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

1 image failed to load on a phone, for example https://daisous.com/.

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

1 link to other sites is dead, for example https://www.threeppy.jp/ (503).

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

1 link go through two or more redirects, for example https://daisous.com/customer_authentication/redirect?locale=en&region_country=US.

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.

daisous.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

daisous.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

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 338 words of visible text.

DMARC is set to p=none, so mail pretending to be daisous.com is still delivered. Add a report address, check the reports, then move to quarantine.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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 Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

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

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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