starpilpro.com website review

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

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

8 third-party services load with your homepage (Clarity, Hubspot and Shopify and others), adding 10.1 MB and 534 ms of main-thread time.

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

Shopify costs a phone 37 ms of main-thread work and 9.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.

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

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

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

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

Hubspot costs a phone 171 ms of main-thread work and 334 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,508 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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

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

Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Get 15% Off Today!”.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 12.2 MB in 303 requests on a phone: media 9.1 MB (4), other files 1.1 MB (212) and scripts 1.1 MB (52). Under 2 MB keeps phones on slow connections fast.

pro_logo.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).

5 images are downloaded at several times the size a phone draws them, for example April_May_June_July_Banners_15_1200x800.png at 1,200 px wide, shown at 351 px. Resized copies would save about 68 KiB.

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

23 elements hidden from screen readers can still receive keyboard focus.

10 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: 3 elements on the page fail this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

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

There are 2 <h1> headlines (“THE STANDARD FOR PROFESSIONAL WAXING SUPPLIES” and “Kits for every service”). One clear main headline is easier for people and search engines.

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.

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

The homepage links to 138 pages on starpilpro.com and 18 external pages.

https://starpilpro.com/collections/professional-hard-wax and https://starpilpro.com/collections/30lb-bulk-hard-wax all use the title “Professional Hard Wax – Starpil Pro”. Search engines can't tell which page to show for a search, so each competes with the others.

https://starpilpro.com/collections/starpil-university-free-education, https://starpilpro.com/collections/waxing-by-speciality, https://starpilpro.com/pages/complete-facial-waxing-kit, https://starpilpro.com/pages/luxury-waxing-products, https://starpilpro.com/pages/professional-waxing-products-for-new-estheticians and https://starpilpro.com/pages/copy-of-professional-facial-waxing-products-for-estheticians have no meta description, so Google writes the search snippet from whatever text it finds.

https://starpilpro.com/collections/professional-hard-wax and https://starpilpro.com/collections/30lb-bulk-hard-wax 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://starpilpro.com/collections/30lb-bulk-hard-wax, whose canonical is https://starpilpro.com/collections/professional-hard-wax. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://starpilpro.com/pages/complete-facial-waxing-kit, https://starpilpro.com/pages/luxury-waxing-products, https://starpilpro.com/pages/professional-waxing-products-for-new-estheticians and https://starpilpro.com/pages/copy-of-professional-facial-waxing-products-for-estheticians have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

The homepage carries about 388 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, HubSpot and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

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

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