stickiiclub.com website review

10 images could be 3.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 15.4 s faster on a phone.

About 541 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.

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

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

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

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

8 third-party services load with your homepage (Shopify, rechargecdn.com and octaneai.com and others), adding 1.0 MB and 608 ms of main-thread time.

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

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

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

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

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

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

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

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

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

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

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

Your homepage downloads 6.5 MB in 203 requests on a phone: images 4.3 MB (16), scripts 1,019 KiB (77) and other files 812 KiB (91). Under 2 MB keeps phones on slow connections fast.

3 images weigh 2.2 MB together. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example new_website_packs_sample__1_d37660be-5ed4-499e-88c3-1865690b at 1,801 px wide, shown at 170 px. Resized copies would save about 2.0 MB.

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

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

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

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is 68 characters, so Google will cut it off around 60: “STICKII Club | $12 Monthly Sticker Subscription that fits your style”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 7 characters: “STICKII”. 70 to 160 characters is enough to sell the click.

There are 4 <h1> headlines (“”, “” and “A Tiny Bit Obsessed”). One clear main headline is easier for people and search engines.

The homepage links to 83 pages on stickiiclub.com and 3 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://www.stickiiclub.com/products/stickii-sheets-organizer-spooky-season-collection declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.

/ and https://www.stickiiclub.com/products/stickii-sheets-organizer-spooky-season-collection all use the title “STICKII Club | $12 Monthly Sticker Subscription that fits your style”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.stickiiclub.com/collections/all-products, https://www.stickiiclub.com/collections/limited-editions, https://www.stickiiclub.com/collections/stamps, https://www.stickiiclub.com/collections/greeting-cards, https://www.stickiiclub.com/collections/stationery-set and https://www.stickiiclub.com/products/stickii-sheets-organizer-spooky-season-collection use the same meta description. A description written for each page earns more clicks.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“CSS appearance value `slider-vertical` is not standardized and will be removed.”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

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