dayvia.com website review

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

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

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

ZenDesk costs a phone 231 ms of main-thread work and 402 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 third-party services load with your homepage (ZenDesk, Google Tag Manager and Shopify and others), adding 697 KiB and 427 ms of main-thread time.

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

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

3 images could be 48 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

slim_noire_recadree.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 (66 KiB) is 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.

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

3 elements hidden from screen readers can still receive keyboard focus.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

The homepage links to 49 pages on dayvia.com and 7 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://dayvia.com/products/lunettes-de-luminotherapie-sunactive-2 and https://dayvia.com/collections/nos-lampes-et-lunettes-de-luminotherapie/products/lunettes-de-luminotherapie-sunactive-2 all use the title “Lunettes de luminothérapie DAYVIA-SUNACTIV 2”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://dayvia.com/collections/all and https://dayvia.com/blogs/luminoblog have no meta description, so Google writes the search snippet from whatever text it finds.

https://dayvia.com/products/lunettes-de-luminotherapie-sunactive-2 and https://dayvia.com/collections/nos-lampes-et-lunettes-de-luminotherapie/products/lunettes-de-luminotherapie-sunactive-2 use the same meta description. A description written for each page earns more clicks.

Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://dayvia.com/collections/nos-lampes-et-lunettes-de-luminotherapie/products/lunettes-de-luminotherapie-sunactive-2, whose canonical is https://dayvia.com/products/lunettes-de-luminotherapie-sunactive-2. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://dayvia.com/collections/all has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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.

The homepage has only about 212 words of visible text; thin pages give Google and first-time buyers little to go on.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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