saint.cc website review

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

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

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

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

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

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

8 third-party services load with your homepage (Shopify, Google CDN and Klaviyo and others), adding 1.7 MB and 546 ms of main-thread time.

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

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

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

Klaviyo costs a phone 141 ms of main-thread work and 313 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.

Google CDN costs a phone 141 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.

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

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

11 KiB could be saved by minifying JavaScript.

10 KiB JavaScript is shipped twice across bundles.

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 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Video Cover”.

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

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

Real visitors wait 2.8 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' tap response (inp) went from 106 ms to 136 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

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

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

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

Your homepage downloads 77.0 MB in 513 requests on a phone: media 69.4 MB (13), images 4.0 MB (78) and scripts 1.5 MB (118). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example 200811-moto-lp-technology-desktop-s9_16160599-7d28-4e5c-a923 at 480 px wide, shown at 36 px. Resized copies would save about 54 KiB.

7 images (363 KiB) are 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.

3 images further down the page (105 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 21.83 g of CO₂e: 2619.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

All page content should be contained by landmarks: 13 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: 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.

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

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

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

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

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: “SA1NT - CE-Rated Unbreakable Motorcycle Jeans & Toughest Riding Gear – SA1NT MOTO AU”.

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

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

The homepage links to 410 pages on saint.cc and 16 external pages.

https://www.saint.cc/products/sa1nt-moto-boots-2 declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://www.saint.cc/products/sa1nt-moto-boots-2 all use the title “SA1NT - CE-Rated Unbreakable Motorcycle Jeans & Toughest Riding Gear …”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.saint.cc/pages/bundles and https://www.saint.cc/products/sa1nt-moto-boots-2 use the same meta description. A description written for each page earns more clicks.

https://www.saint.cc/collections/all-outlet-items, https://www.saint.cc/collections/all-engineered-denim, https://www.saint.cc/collections/new-in-mens, https://www.saint.cc/collections/mens-coretec, https://www.saint.cc/collections/motowear-mens and https://www.saint.cc/collections/mens-best-sellers and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.saint.cc/collections/mens-jeans-all, https://www.saint.cc/collections/mens-jacket-all, https://www.saint.cc/collections/gloves, https://www.saint.cc/products/sa1nt-moto-boots-2, https://www.saint.cc/collections/mens-compression-base-layers and https://www.saint.cc/collections/mens-hoodie-sweatshirts and 1 other took over 3 s to send their HTML from our server.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Chrome logged issues while loading the page (“Cookie”).

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.

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

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 5,164 words of visible text.

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