rossmetals.com website review

About 414 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.

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

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

31 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

8 third-party services load with your homepage (Shopify, Yotpo and Clarity and others), adding 1.7 MB and 715 ms of main-thread time.

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

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

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

Yotpo costs a phone 178 ms of main-thread work and 383 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.

6 KiB could be saved by minifying CSS.

16 KiB could be saved by minifying JavaScript.

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

Polyfills for old browsers add 8 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.

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 30.3 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 16.1 s (Speed Index). Good is under 3.4 s.

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

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

Real visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.

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

The first text or image appears after 2.2 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 108 ms to 111 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 10.4 MB in 435 requests on a phone: images 7.7 MB (107), scripts 1.4 MB (171) and other files 869 KiB (100). Under 2 MB keeps phones on slow connections fast.

5 images further down the page (549 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example 2024-05-31-11-53-12-_B_R4_S5_068e757b-8b0b-4520-873d-3f450a8 at 800 px wide, shown at 114 px. Resized copies would save about 72 KiB.

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

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

Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 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.

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

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

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

Your title is 84 characters, so Google will cut it off around 60: “The Premier Wholesale Fine Jewelry Manufacturer-Gold, Platinum, Silver | Ross Metals”.

6 links have no real href, so search engines can't follow them.

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

The homepage links to 480 pages on rossmetals.com and 3 external pages.

https://rossmetals.com/blogs/notes and https://rossmetals.com/pages/theme-features-and-styles declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

/, https://rossmetals.com/blogs/notes and https://rossmetals.com/pages/theme-features-and-styles all use the title “The Premier Wholesale Fine Jewelry Manufacturer-Gold, Platinum, Silve…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://rossmetals.com/blogs/notes, https://rossmetals.com/pages/theme-features-and-styles and https://rossmetals.com/apps/iwish use the same meta description. A description written for each page earns more clicks.

https://rossmetals.com/blogs/notes and https://rossmetals.com/pages/theme-features-and-styles have no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=97103496&Ver=2&mid=7ebdebf9-6e36-4c41-882d-bddebdf8a4dd&bo=1&sid=bf890100d9a311f198d0159ae75f6761&vid=bf891320d9a311f19689b5ba827a7bcc&vids=1&msclkid=N&pi=918639831&lg.

53 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

1 image is served at too low a resolution for sharp phone screens.

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.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

The homepage carries about 716 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Microsoft Ads and Microsoft Clarity (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 25 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.