skinesa.com website review

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

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

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

About 228 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.

8 third-party services load with your homepage (heatmap.com, Klaviyo and Google CDN and others), adding 1.1 MB and 814 ms of main-thread time.

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

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

22 KiB could be saved by minifying CSS.

Shopify costs a phone 162 ms of main-thread work and 621 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 184 ms of main-thread work and 322 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 1,638 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

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 16.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Skin probiotic supplement package with daily capsules”.

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

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

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

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

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

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

Your homepage downloads 4.8 MB in 447 requests on a phone: images 1.9 MB (86), other files 1.4 MB (253) and scripts 958 KiB (88). Under 2 MB keeps phones on slow connections fast.

30 images (4.0 MB) are 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.

25 images further down the page (2.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

4 images are downloaded at several times the size a phone draws them, for example 1_2.webp at 1,440 px wide, shown at 250 px. Resized copies would save about 261 KiB.

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://www.skinesa.com/search?q={search_term_string}")”.

The homepage links to 44 pages on skinesa.com and 4 external pages.

https://www.skinesa.com/products/skinesa-skin-probiotic and https://www.skinesa.com/products/skinesa-kids-skin-probiotic all use the title “Skinesa® | Best Probiotic Supplements for Skin Health | Probiotic Pil…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.skinesa.com/pages/bulk-buying-options, https://www.skinesa.com/pages/bulk-buying-options-kids, https://www.skinesa.com/pages/faq, https://www.skinesa.com/blogs/bite-sized-science, https://www.skinesa.com/policies/terms-of-service and https://www.skinesa.com/policies/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.skinesa.com/products/skinesa-skin-probiotic and https://www.skinesa.com/products/skinesa-kids-skin-probiotic use the same meta description. A description written for each page earns more clicks.

https://www.skinesa.com/pages/reviews and https://www.skinesa.com/pages/faq have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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