vondiamonds.com website review

Signyfyd costs a phone 1.1 s of main-thread work and 281 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, 4.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

8 third-party services load with your homepage (Signyfyd, Google Tag Manager and Hotjar and others), adding 2.6 MB and 2.7 s of main-thread time.

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

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

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

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

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

Hotjar costs a phone 369 ms of main-thread work and 261 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.

Shopify costs a phone 293 ms of main-thread work and 893 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,037 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

Optanon costs a phone 85 ms of main-thread work and 542 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.

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

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

28 KiB could be saved by minifying CSS.

28 KiB could be saved by minifying JavaScript.

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.

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

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

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

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

Your homepage downloads 6.5 MB in 551 requests on a phone: scripts 2.6 MB (197), images 2.3 MB (113) and other files 1.1 MB (212). Under 2 MB keeps phones on slow connections fast.

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

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (6 elements).

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 212 pages on vondiamonds.com and 7 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

robots.txt blocks GPTBot and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://vondiamonds.com/pages/track-your-order has no meta description, so Google writes the search snippet from whatever text it finds.

https://vondiamonds.com/pages/contact and https://vondiamonds.com/pages/faq have no <h1> headline, so visitors and search engines get no clear main topic.

https://vondiamonds.com/collections/side-stone-engagement-rings took over 3 s to send its HTML from our server.

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

51 of 105 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.

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

The homepage carries about 438 words of visible text.

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

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

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