thinksun.com website review

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

Signyfyd costs a phone 1.1 s of main-thread work and 265 KiB of downloads while your page loads. That alone is enough to make taps feel slow. 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 10.5 s on main-thread work while loading, 4.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

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

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

8 third-party services load with your homepage (Signyfyd, Google Tag Manager and tracead.com and others), adding 2.5 MB and 2.5 s of main-thread time.

About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

Google Tag Manager costs a phone 298 ms of main-thread work and 553 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 260 ms of main-thread work and 556 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.

tracead.com costs a phone 289 ms of main-thread work and 87 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.

zotabox.com costs a phone 199 ms of main-thread work and 549 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.

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

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

24 KiB could be saved by minifying JavaScript.

1 image could be 17 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

6 KiB could be saved by minifying CSS.

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.

Your largest element takes 10.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Banner Image”.

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

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

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

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

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

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

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

Your homepage downloads 5.4 MB in 424 requests on a phone: scripts 3.4 MB (170), other files 975 KiB (170) and images 491 KiB (55). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

Elements with visible text labels do not have matching accessible names. (10 elements).

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 8 characters: “thinksun”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 188 pages on thinksun.com and 10 external pages.

There is no https://thinksun.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://thinksun.com/collections/dermatologist-recommended-think-sun-care and https://thinksun.com/collections/shop-all-think-sun-care all use the title “thinksun- Trusted For Little Ones and Beyond”. Search engines can't tell which page to show for a search, so each competes with the others.

https://thinksun.com/collections/daily-sunscreen has no meta description, so Google writes the search snippet from whatever text it finds.

https://thinksun.com/collections/dermatologist-recommended-think-sun-care and https://thinksun.com/collections/shop-all-think-sun-care use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://thinksun.com/collections/dermatologist-recommended-think-sun-care, whose canonical is https://thinksun.com/collections/shop-all-think-sun-care. 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 78 found) and read each the way a search engine does.

2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=56347214&Ver=2&mid=962c6dd7-3e8c-4ba3-97d5-e49cb77c792f&bo=1&sid=274aee90dba211f18c0de9ba9855dbdc&vid=274b00e0dba211f197c7d3911415bbf4&vids=1&msclkid=N&pi=918639831&lg.

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

6 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://free.freeipapi.com/api/json/' from origin 'https://thinksun.com' has been blocked by CORS p…”.

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

The page uses urgency cues (a countdown or limited-time wording).

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