starface.world website review

11 images could be 2.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Your mobile performance score is 66 (desktop: 63). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, Accessibe Accessibility Overlay and rechargecdn.com and others), adding 1.5 MB and 727 ms of main-thread time.

21 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.

Google Tag Manager costs a phone 482 ms of main-thread work and 674 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 497 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

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

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

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.

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

Your largest element takes 6.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Open Starface blue compact showing Hydro-Star® + Salicylic …”.

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

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

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

2 images weigh 7.4 MB together. On a phone connection a single image that size takes seconds.

Your homepage downloads 5.8 MB in 254 requests on a phone: images 3.1 MB (22), scripts 1.3 MB (60) and other files 1.0 MB (135). Under 2 MB keeps phones on slow connections fast.

3 images (7.6 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.

2 images are downloaded at several times the size a phone draws them, for example starface-star-wash-salicylic-acid-cleanser-star-strips-skinc at 1,080 px wide, shown at 70 px. Resized copies would save about 101 KiB.

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

All page content should be contained by landmarks: 2 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: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Headings should not be empty: 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.

Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected non-whitespace character after JSON at position 4)”.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

Your <h1> is empty.

The homepage links to 74 pages on starface.world and 8 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://starface.world/pages/where-to-shop has no meta description, so Google writes the search snippet from whatever text it finds.

https://starface.world/collections/all and https://starface.world/collections/best-sellers use the same meta description. A description written for each page earns more clicks.

https://starface.world/pages/star-corner has no <h1> headline, so visitors and search engines get no clear main topic.

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

1 image failed to load on a phone, for example https://starface.world/Liquid%20error%20(sections/free-product-modal%20line%2030):%20invalid%20url%20input.

5 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'toLocaleString')”.

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

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