sssoffroad.com website review

About 906 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.1 s faster on a phone.

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

8 third-party services load with your homepage (zbcdn.net, zotabox.com and reamaze.com and others), adding 1.6 MB and 887 ms of main-thread time.

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

zbcdn.net costs a phone 232 ms of main-thread work and 377 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.

zotabox.com costs a phone 205 ms of main-thread work and 559 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.

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

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

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

1 image could be 59 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

Polyfills for old browsers add 33 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

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

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

28 KiB JavaScript is shipped twice across bundles.

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

4 KiB could be saved by minifying CSS.

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

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

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

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

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

Scripts block taps and scrolling for 282 ms in total while the page loads. Good is under 200 ms.

Your homepage downloads 17.5 MB in 164 requests on a phone: media 14.8 MB (3), scripts 1.6 MB (60) and other files 646 KiB (79). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

There are 2 <h1> headlines (“SSS Off-Road” and “Premium UHMW Skid Plates & Underbody Protection f…”). One clear main headline is easier for people and search engines.

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

Structured data found (BreadcrumbList, Organization and WebSite) but with 1 problem, for example “ld+json block 3 is not valid JSON (Unexpected token ',', ..." ,, "... is not va)”.

The homepage links to 148 pages on sssoffroad.com and 1 external page.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://sssoffroad.com/collections/can-am-maverick, https://sssoffroad.com/collections/can-am-maverick-max, https://sssoffroad.com/collections/can-am-maverick-r, https://sssoffroad.com/collections/can-am-maverick-r-max, https://sssoffroad.com/collections/can-am-maverick-trail and https://sssoffroad.com/collections/can-am-maverick-trail-max have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

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

The homepage carries about 779 words of visible text.

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