rockher.com website review

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

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

7 third-party services load with your homepage (Klaviyo, Shopify and run.app and others), adding 2.9 MB and 128 ms of main-thread time.

Shopify costs a phone 16 ms of main-thread work and 2.6 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.

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

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

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

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

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

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

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.

5 KiB could be saved by minifying JavaScript.

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 9.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A couple at sunset; she wears her engagement ring”.

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 118 ms to 128 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.3 MB in 195 requests on a phone: media 2.2 MB (5), other files 784 KiB (101) and scripts 544 KiB (64). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example P561_1400x.jpg at 1,312 px wide, shown at 350 px. Resized copies would save about 49 KiB.

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

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

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

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

The homepage links to 402 pages on rockher.com and 12 external pages.

There is no https://www.rockher.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://www.rockher.com/apps/diamondsearch is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

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

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

The homepage shows no opening hours. If customers visit or call, show when.

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

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