sockstack.com website review

Not measured in this review.

• Fails Core Web Vitals for real visitors

  Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

• Real-user INP: 250 ms

  250 ms

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

• Tap response (INP) got 33% slower for real visitors

  +33%

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

• Largest content (LCP) held steady for real visitors

  0%

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

• Page weight: 4.9 MB

  4.9 MB

  Your homepage downloads 4.9 MB on a phone, 1.2 MB of it images (25%). Under 2 MB keeps phones on slow connections fast.

• An image on the first screen is lazy-loaded

  Sock_Stack_Banner_Thermal_Wool_Socks.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).

  Elements (1)

• 4 images in older formats

  4 images (389 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.

  Elements (4)

• About 1.4 g of CO₂ per visit

  1.39 g

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

• Certain ARIA roles must contain particular children (1 element)

  Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  Elements (1)

• 68 text elements with low contrast

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

  Elements (3)

• Scrollable region must have keyboard access (1 element)

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

  Elements (1)

• 1 tap target too small

  1 tap target is too small or too close together to hit reliably with a finger.

  Elements (1)

• All page content should be contained by landmarks (6 elements)

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

  Elements (3)

• Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

  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.

  Elements (1)

• 4 form fields without a label

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

  View source

• 1 link without text

  1 visible link has no text or label, so screen readers cannot say where it goes.

• 2 H1 headlines

  There are 2 <h1> headlines (“Sock Stack” and “Stock Up.”). One clear main headline is easier for people and search engines.

  View source

• Meta description is long (227 characters)

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

  View source

• Open Graph partly set

  Open Graph is missing og:description, so shared links fall back to guesses.

  View source

• 320 internal links, 14 external

  The homepage links to 320 pages on sockstack.com and 14 external pages.

• 1 page without a title

  https://www.sockstack.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  Elements (1)

• 1 linked page hidden from search

  https://www.sockstack.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  Elements (1)

• 1 page without a meta description

  https://www.sockstack.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (1)

• 15 pages without an H1

  https://www.sockstack.com/customer_authentication/redirect, https://www.sockstack.com/collections/new-arrivals, https://www.sockstack.com/collections/best-sellers, https://www.sockstack.com/collections/men, https://www.sockstack.com/collections/mens-socks and https://www.sockstack.com/collections/mens-underwear and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

• 8 pages with very little text

  https://www.sockstack.com/collections/new-arrivals, https://www.sockstack.com/collections/best-sellers, https://www.sockstack.com/collections/men, https://www.sockstack.com/collections/mens-socks, https://www.sockstack.com/collections/mens-underwear and https://www.sockstack.com/collections/women and 2 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

• 15 internal pages checked

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

• 1 broken image

  1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=136029046&tm=gtm002&Ver=2&mid=e6516b79-8ff8-443b-92c5-36b4f1e53dd7&bo=1&sid=2fd69c20def911f1b4727b6caa686a87&vid=2fd6c850def911f185856744cb6c0c25&vids=1&msclkid=N&gtm_.

• 64 small tap targets

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

• 4 JavaScript errors while loading

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

• Local business without LocalBusiness data

  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.

  View source

• No phone number on the homepage

  A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

• Thin social proof

  Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

• No direct contact details

  No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

• No opening hours

  The homepage shows no opening hours. If customers visit or call, show when.

• No map or directions link

  There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

• No risk reducer

  No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

• About 3,049 words of copy

  The homepage carries about 3,049 words of visible text.

• 10 trackers load before any consent

  10

  Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 5 mores (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

• 44 cookies set on arrival

  44

  Opening the homepage sets 44 cookies, 4 of them by other companies (measured from a US location before any click).

• 45 other companies contacted

  Loading the homepage contacts 45 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.