thinkproducts.com website review

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

35 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.2 s.

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

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

8 third-party services load with your homepage (Google Tag Manager, FontAwesome CDN and Optanon and others), adding 1.7 MB and 959 ms of main-thread time.

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

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

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

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

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

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

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.

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 first text or image appears after 7.7 s on a phone. Good is under 1.8 s.

Your largest element takes 23.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “meet your high protein match!”.

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

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

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

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

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

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

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

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

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

Your homepage downloads 4.2 MB in 361 requests on a phone: scripts 2.0 MB (132), other files 1.1 MB (128) and images 459 KiB (41). Under 2 MB keeps phones on slow connections fast.

Atkins_HP_Mobile.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 (35 KiB) is 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.

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

1 image has no alt text, which hurts accessibility and image search.

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

Document should not have more than one banner landmark: 1 element on the page fails 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.

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

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Your title is 85 characters, so Google will cut it off around 60: “think!® Official Site & Online Store | Protein Bars & Healthy Snacks – Think Products”.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 106 pages on thinkproducts.com and 3 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://www.thinkproducts.com/pages/mobile-shop is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

https://www.thinkproducts.com/pages/think-promise and https://www.thinkproducts.com/pages/about-us all use the title “About Us – Think Products”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.thinkproducts.com/policies/shipping-policy, https://www.thinkproducts.com/collections/all-products, https://www.thinkproducts.com/pages/think-promise, https://www.thinkproducts.com/pages/all-blog-articles, https://www.thinkproducts.com/blogs/recipes and https://www.thinkproducts.com/pages/about-us and 1 other 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://www.thinkproducts.com/pages/think-promise, whose canonical is https://www.thinkproducts.com/pages/about-us. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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.

The homepage carries about 261 words of visible text.

Before a visitor clicks anything, the page loads FullStory, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 1 more (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 25 cookies (measured from a US location before any click).

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