silvers-na.com website review

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

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

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

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

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

8 third-party services load with your homepage (Judge.me, Affirm and Key CDN and others), adding 703 KiB and 482 ms of main-thread time.

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.

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

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

4 KiB could be saved by minifying CSS.

3 KiB JavaScript is shipped twice across bundles.

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

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

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

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

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

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

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

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

Your title is 87 characters, so Google will cut it off around 60: “Silver's North America | Performance Suspensions, Coilover Kits – Silvers North America”.

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

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

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

Your <h1> is empty.

The homepage links to 152 pages on silvers-na.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://silvers-na.com/pages/neomax-coilovers and https://silvers-na.com/collections/neomax-coilovers all use the title “Neomax Coilovers – Silvers North America”. Search engines can't tell which page to show for a search, so each competes with the others.

https://silvers-na.com/pages/about, https://silvers-na.com/policies/shipping-policy, https://silvers-na.com/pages/neomax-coilovers, https://silvers-na.com/pages/neomax-2-way-coilovers, https://silvers-na.com/collections/wheels and https://silvers-na.com/pages/swift-springs and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://silvers-na.com/pages/about, https://silvers-na.com/pages/neomax-coilovers and https://silvers-na.com/pages/neomax-2-way-coilovers have no <h1> headline, so visitors and search engines get no clear main topic.

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

3 images failed to load on a phone, for example https://silvers-na.com/.

3 errors were 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.

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 1,751 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 15 cookies, 1 of them by other companies (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 31 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.