epijewelry.com website review

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

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

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

8 third-party services load with your homepage (Shopify, gotolstoy.com and Google CDN and others), adding 2.1 MB and 938 ms of main-thread time.

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

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

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

Shopify costs a phone 420 ms of main-thread work and 1.1 MB 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.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 300 ms).

Google CDN costs a phone 117 ms of main-thread work and 299 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.

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

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

About 22 KiB of CSS is downloaded but never applied on this page.

14 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.

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

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

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

The layout shifts by 0.194 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Your homepage downloads 15.1 MB in 959 requests on a phone: images 10.4 MB (667), fonts 1.8 MB (25) and scripts 1.4 MB (105). Under 2 MB keeps phones on slow connections fast.

epi-jewelry-christmas-sale-m.jpg weighs 548 KiB. On a phone connection a single image that size takes seconds.

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

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

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

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

Alternative text of images should not be repeated as text: 10 elements on the page fail this check, rated minor by axe-core.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 68 characters, so Google will cut it off around 60: “Affordable luxury Lab Grown Diamond & Moissanite rings | EPI Jewelry”.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 343 pages on epijewelry.com and 10 external pages.

Your homepage links to https://epijewelry.com/pages/fall-jewelry-sale, which answers with an error. Visitors hit a dead end and search engines drop it.

https://epijewelry.com/pages/black-friday-sale, https://epijewelry.com/collections/best-sellers, https://epijewelry.com/collections/new-arrivals, https://epijewelry.com/collections/moi-et-toi-engagement-rings, https://epijewelry.com/collections/stacking-rings and https://epijewelry.com/collections/the-bezel-edit and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://epijewelry.com/pages/black-friday-sale, https://epijewelry.com/collections/best-sellers, https://epijewelry.com/collections/new-arrivals, https://epijewelry.com/collections/valentines-day-special and https://epijewelry.com/collections/20-off-sale took over 3 s to send their HTML from our server.

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

Social proof on the homepage: 108 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

The homepage carries about 1,323 words of visible text.

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