basksuncare.com website review

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

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

Your mobile performance score is 44. 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, Klaviyo and rebuyengine.com and others), adding 53.8 MB and 2.3 s of main-thread time.

Shopify costs a phone 228 ms of main-thread work and 51.5 MB 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 936 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

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

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

rebuyengine.com costs a phone 347 ms of main-thread work and 733 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 351 ms of main-thread work and 507 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.

gotolstoy.com costs a phone 291 ms of main-thread work and 160 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.

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

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

Polyfills for old browsers add 67 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).

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.

2 KiB could be saved by minifying JavaScript.

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 page becomes fully interactive after 28.0 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 “baskbalmtexture.png”.

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

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

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

Real visitors wait 983 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

Your homepage downloads 55.7 MB in 395 requests on a phone: media 50.7 MB (13), scripts 2.6 MB (131) and images 1.0 MB (88). Under 2 MB keeps phones on slow connections fast.

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

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

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

5 images have no alt text, which hurts accessibility and image search.

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

Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one main 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.

Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.

Headings skip levels (h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.

Your title is 66 characters, so Google will cut it off around 60: “Bask Sunscreen - The World's Best Feeling Sunscreen – Bask Suncare”.

There are 3 <h1> headlines (“<img src="//basksuncare.com/cdn/shop/files/Collab…”, “THE WORLD'S BEST FEELING SUNSCREEN” and “”). One clear main headline is easier for people and search engines.

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

The homepage links to 89 pages on basksuncare.com and 8 external pages.

https://basksuncare.com/pages/subscribe, https://basksuncare.com/a/loop_subscriptions/bundle/6707be1d4b584111b4d3f0e5d94000d1, https://basksuncare.com/pages/store-locator and https://basksuncare.com/collections/mineral-sunscreen use the same meta description. A description written for each page earns more clicks.

https://basksuncare.com/pages/subscribe, https://basksuncare.com/a/loop_subscriptions/bundle/6707be1d4b584111b4d3f0e5d94000d1, https://basksuncare.com/pages/store-locator, https://basksuncare.com/pages/our-mission, https://basksuncare.com/pages/faq and https://basksuncare.com/products/bask-balm-spf30-lip-balm-and-lip-gloss-with-sunscreen and 3 others took over 3 s to send their HTML from our server.

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

2 images failed to load on a phone, for example https://d.adroll.com/uev/DLINZQAV65HKFGR6GMR7RE/3XVDBKISZNB23CT5AGAVQ5/?af0=0fe6f973&adroll_fpc=120268512e3a7bf4bb7834cfbb27be4a-1794346160980&pv=28446422737.01571&arrfrr=https%3A%2F%2Fbasksuncare.com.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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 1,221 words of visible text.

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