thisworks.com website review

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

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

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

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

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

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

Google Tag Manager costs a phone 501 ms of main-thread work and 546 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 61 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

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

7 KiB could be saved by minifying JavaScript.

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

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

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

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

Your largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Video placeholder”.

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

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

Visually, the page fills in at 5.7 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 181 ms to 201 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 12.1 MB in 275 requests on a phone: media 8.3 MB (2), scripts 1.8 MB (100) and other files 858 KiB (129). Under 2 MB keeps phones on slow connections fast.

October_Banners-19.png 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 3.44 g of CO₂e: 413.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

There are 3 <h1> headlines (“the science​ of switching off​”, “free luxury candle with orders £55+*” and “naturally effective, rooted in science, proven to…”). One clear main headline is easier for people and search engines.

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

Structured data found (BreadcrumbList, Organization and WebSite) but with 3 problems, for example “Organization: logo is not an absolute URL ("//www.thisworks.com/cdn/shop/files/THISWORKS_FAVICON.pn…”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

The homepage links to 338 pages on thisworks.com and 7 external pages.

We fetched 15 pages linked from your homepage (of 146 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=19000484&tm=gtm002&Ver=2&mid=bcfdfc22-8718-4b24-a681-f5f16db7bb12&bo=1&sid=2b8abd30d89811f19e5e8bc9ec7124aa&vid=2b8acd40d89811f1acae756e8c9459f8&vids=1&msclkid=N&pi=91.

91 of 248 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 “Failed to load resource: net::ERR_FAILED”.

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

The homepage carries about 1,899 words of visible text.

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

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

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