siistore.com website review

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

Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

8 third-party services load with your homepage (Hotjar, Google Tag Manager and Facebook and others), adding 1.0 MB and 1.7 s of main-thread time.

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

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

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

Hotjar costs a phone 543 ms of main-thread work and 65 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.

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

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

Facebook costs a phone 305 ms of main-thread work and 228 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,501 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

About 45 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).

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

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 8.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SUBLIMATION”.

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

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

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

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

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

Your homepage downloads 2.8 MB in 228 requests on a phone: scripts 1.2 MB (79), other files 762 KiB (112) and images 501 KiB (20). Under 2 MB keeps phones on slow connections fast.

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

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Alternative text of images should not be repeated as text: 11 elements on the page fail this check, rated minor by axe-core.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 74 characters, so Google will cut it off around 60: “Wholesale Embroidery Supplies | Embroidery Parts | Accessories — Sii Store”.

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

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

4 links have no real href, so search engines can't follow them.

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

The homepage links to 322 pages on siistore.com and 22 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://stitchitintl.com/collections/machines, https://stitchitintl.com/collections/accessories, https://stitchitintl.com/collections/embroidery-supplies, https://stitchitintl.com/collections/heat-transfer, https://stitchitintl.com/collections/black-friday-deals and https://stitchitintl.com/collections/multi-needle-embroidery-machines and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://stitchitintl.com/pages/financing, https://stitchitintl.com/pages/swf-single-head-machines and https://stitchitintl.com/pages/swf-multi-head-embroidery-machines use the same meta description. A description written for each page earns more clicks.

https://stitchitintl.com/pages/swf-single-head-machines and https://stitchitintl.com/pages/swf-multi-head-embroidery-machines have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

Social proof on the homepage: 44 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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