originjewelry.com website review

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

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

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

4 third-party services load with your homepage (Google CDN, Shopify and Google Fonts and others), adding 160 KiB and 122 ms of main-thread time.

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

About 11 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 60 ms faster on a phone.

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

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.

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

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

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

The first text or image appears after 2.2 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.

Your homepage downloads 2.1 MB in 179 requests on a phone: images 1.0 MB (52), other files 748 KiB (87) and scripts 237 KiB (33). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (89 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 0.59 g of CO₂e: 70.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

8 images have no alt text, which hurts accessibility and image search.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

1 visible link has no text or label, so screen readers cannot say where it goes.

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

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

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

There are 3 <h1> headlines (“Left Engagement Rings Right”, “Left Wedding Bands Right” and “Custom Ring Designs”). One clear main headline is easier for people and search engines.

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

The homepage links to 57 pages on originjewelry.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://originjewelry.com/apps/origin-jewelry/women/rings/styles/019/ring_materials/14KW/color_arrangements/B/stone_quantities/HALFETERNITY/variants/2 has no <title>, so Google invents the link text in results.

https://originjewelry.com/collections/luxe-engagement-rings/products/14k-white-gold-round-diamond-engagement-ring-2 and https://originjewelry.com/collections/luxe-engagement-rings/products/14k-white-gold-round-diamond-engagement-ring-3 all use the title “14K White Gold Round Diamond Engagement Ring – Origin Jewelry”. Search engines can't tell which page to show for a search, so each competes with the others.

https://originjewelry.com/collections/luxe-engagement-rings and https://originjewelry.com/collections/luxe-wedding-bands have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 11 pages by a URL that isn't their canonical one, for example https://originjewelry.com/collections/luxe-engagement-rings/products/14k-white-gold-round-diamond-engagement-ring-2, whose canonical is https://originjewelry.com/products/14k-white-gold-round-diamond-engagement-ring-2. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://originjewelry.com/apps/origin-jewelry/women/rings/styles/019/ring_materials/14KW/color_arrangements/B/stone_quantities/HALFETERNITY/variants/2 has no <h1> headline, so visitors and search engines get no clear main topic.

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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