jeandousset.com website review

2 images could be 802 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.9 s faster on a phone.

About 988 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

Signyfyd costs a phone 1.9 s of main-thread work and 493 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (Signyfyd, hsappstatic.net and Bugsnag and others), adding 2.0 MB and 3.4 s of main-thread time.

42 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).

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

hsappstatic.net costs a phone 486 ms of main-thread work and 715 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.

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

About 124 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 77 KiB JavaScript that modern phones do not need.

15 KiB JavaScript is shipped twice across bundles.

12 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 12.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

Real visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

Your homepage downloads 19.8 MB in 366 requests on a phone: media 14.0 MB (2), scripts 3.0 MB (138) and images 1.1 MB (35). Under 2 MB keeps phones on slow connections fast.

HP_Store_locator.jpg weighs 824 KiB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example HP_Store_locator.jpg at 4,096 px wide, shown at 390 px. Resized copies would save about 757 KiB.

2 images further down the page (884 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 5.61 g of CO₂e: 673.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Interactive controls must not be nested: 7 elements on the page fail this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

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

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

The homepage links to 57 pages on jeandousset.com and 8 external pages.

Your homepage links to https://www.jeandousset.com/collections/lab-grown-diamond-engagement-rings and https://www.jeandousset.com/collections/lab-diamond-eternity-bands, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.jeandousset.com/pages/faq-engagement has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.jeandousset.com/pages/store-locations, https://www.jeandousset.com/pages/contact, https://www.jeandousset.com/pages/our-story, https://www.jeandousset.com/pages/craftsmanship, https://www.jeandousset.com/blogs/news and https://www.jeandousset.com/pages/faq-engagement have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.jeandousset.com/collections/lab-grown-diamond-jewelry took over 3 s to send its HTML from our server.

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

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

1 third-party cookie is 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_FAILED”.

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

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.

Social proof on the homepage: 5 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 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 30 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 50 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.