spccstore.com website review

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

8 third-party services load with your homepage (Google Tag Manager, Shopify and TikTok and others), adding 1.2 MB and 1.2 s of main-thread time.

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

Google Tag Manager costs a phone 705 ms of main-thread work and 504 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.

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

About 416 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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

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

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

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.

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

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

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

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

Real visitors wait 477 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

For real visitors the layout shifts by 0.13 (75th percentile). Good is under 0.1.

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

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

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

The layout shifts by 0.172 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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.4 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 12.4 MB in 290 requests on a phone: media 8.9 MB (1), scripts 1.2 MB (87) and images 1.0 MB (37). Under 2 MB keeps phones on slow connections fast.

cart-featured-img.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example Untitled_design_15_1200x.jpg at 1,200 px wide, shown at 177 px. Resized copies would save about 83 KiB.

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

15 elements hidden from screen readers can still receive keyboard focus.

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 4 elements on the page fail 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.

Your title is 79 characters, so Google will cut it off around 60: “S.P.C.C | Men's Streetwear, Jeans, Sneakers & Clothing – S.P.C.C Official Store”.

Your <h1> is empty.

The homepage links to 237 pages on spccstore.com and 15 external pages.

https://www.spccstore.com/policies/shipping-policy, https://www.spccstore.com/pages/first-time-buyer and https://www.spccstore.com/pages/uniforms have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.spccstore.com/collections/bottoms, https://www.spccstore.com/collections/bottoms/jeans, https://www.spccstore.com/collections/bottoms/pants, https://www.spccstore.com/collections/bottoms/shorts and https://www.spccstore.com/collections/bottoms/track-pants use the same meta description. A description written for each page earns more clicks.

https://www.spccstore.com/collections/all, https://www.spccstore.com/pages/first-time-buyer, https://www.spccstore.com/collections/vault-sale, https://www.spccstore.com/collections/new-in, https://www.spccstore.com/pages/uniforms and https://www.spccstore.com/collections/bottoms and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 87 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=17425466&tm=gtm002&Ver=2&mid=a8eff82a-12d8-4507-a3f7-5d1b4a476db4&bo=1&sid=51c0b310d81711f19078c134e0b2c5ab&vid=51c0c520d81711f1b62f8f8e21e8cea2&vids=1&msclkid=N&pi=91.

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

6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.spccstore.com/cdn/shop/t/656/assets/component-price.css?v=436655' because its …”.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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