dayplus.co website review

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

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

8 third-party services load with your homepage (Klaviyo, Facebook and Yotpo and others), adding 1.3 MB and 863 ms of main-thread time.

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

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

About 476 KiB of JavaScript is downloaded but never used on this page.

Klaviyo costs a phone 228 ms of main-thread work and 512 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,766 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

1 image could be 23 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

18 KiB could be saved by minifying JavaScript.

6 KiB could be saved by minifying CSS.

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.

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

Your largest element takes 11.0 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 23.4 s. Good is under 3.8 s.

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

Real visitors wait 225 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

Your homepage downloads 5.2 MB in 300 requests on a phone: images 2.8 MB (86), scripts 1.4 MB (90) and other files 796 KiB (106). Under 2 MB keeps phones on slow connections fast.

23 images (2.1 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

5 images further down the page (252 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

All page content should be contained by landmarks: 6 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: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

4 links have no real href, so search engines can't follow them.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 284 pages on dayplus.co and 16 external pages.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /products/masque-biocellulose-glow, whose canonical is /fr-us/products/masque-biocellulose-glow. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

6 errors were logged to the browser console while the page loaded, for example “Error: <svg> attribute width: Expected length, "auto".”.

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://dayplus.co/customer_authentication/redirect?locale=fr&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.

dayplus.co 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.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

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 Hotjar and 4 mores (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 25 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 49 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.