wearethought.com website review

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

Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (bc-solutions.net, Shopify and Klaviyo and others), adding 2.0 MB and 1.9 s of main-thread time.

bc-solutions.net costs a phone 788 ms of main-thread work and 243 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.

15 images could be 255 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.

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

Shopify costs a phone 394 ms of main-thread work and 987 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 365 ms of main-thread work and 316 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.

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

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

Feefo.com costs a phone 105 ms of main-thread work and 339 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.

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

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

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

51 KiB could be saved by minifying CSS.

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

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.

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

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

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

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

8 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 119 ms to 133 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.1 MB in 296 requests on a phone: scripts 1.4 MB (113), images 1.2 MB (41) and other files 768 KiB (83). Under 2 MB keeps phones on slow connections fast.

b8780045-55fd-4363-a180-52533dc15fac.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).

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

2 buttons have no accessible name, so screen readers announce just “button”.

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

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

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

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

The homepage links to 123 pages on wearethought.com and 6 external pages.

Your Organization JSON-LD is missing logo, 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://thoughtsocks.com/collections/3-for-15, https://thoughtsocks.com/en-us/collections/striped-socks, https://thoughtsocks.com/en-us/collections/mens-trainer-socks, https://thoughtsocks.com/en-us/collections/mens-birthday-socks, https://thoughtsocks.com/en-us/collections/mens-celebration-socks and https://thoughtsocks.com/en-us/collections/mens-sports-socks and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://thoughtsocks.com/pages/delivery, whose canonical is https://thoughtsocks.com/en-us/pages/delivery. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://thoughtsocks.com/en-us/collections/sustainable-socks-mens and https://thoughtsocks.com/en-us/collections/mens-gift-boxes have no <h1> headline, so visitors and search engines get no clear main topic.

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

6 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'addEventListener')”.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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 299 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 20 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 33 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.