sweetplaid.shop website review

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

8 third-party services load with your homepage (sweetplaid.com, Google Tag Manager and TikTok and others), adding 1.1 MB and 1.4 s of main-thread time.

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

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

sweetplaid.com costs a phone 641 ms of main-thread work and 484 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.

3 images could be 65 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.

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

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

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

About 22 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 29 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 CSS.

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

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

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

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

The layout shifts by 0.13 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

7 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 3.2 MB in 219 requests on a phone: scripts 1.5 MB (68), other files 894 KiB (111) and images 694 KiB (23). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (27 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

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

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

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

Your title is 76 characters, so Google will cut it off around 60: “SweetPlaid Official | N ° 1 Giant Ultra Comfortable Sweaters – SweetPlaid US”.

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

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

Your <h1> is empty.

The homepage links to 54 pages on sweetplaid.shop and 4 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.sweetplaid.shop/discount/HOODIE20 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.sweetplaid.shop/discount/HOODIE20 all use the title “SweetPlaid Official | N ° 1 Giant Ultra Comfortable Sweaters – SweetP…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.sweetplaid.shop/collections/frontpage, https://www.sweetplaid.shop/collections/all-kids-sweetplaids, https://www.sweetplaid.shop/collections/all-xxl-sweetplaids and https://www.sweetplaid.shop/collections/the-classics have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.sweetplaid.shop/products/sweetplaid%E2%84%A2-pick-your-design, https://www.sweetplaid.shop/collections/the-classics/products/sweetplaid-red and https://www.sweetplaid.shop/collections/the-classics/products/sweetplaid-grey use the same meta description. A description written for each page earns more clicks.

https://www.sweetplaid.shop/collections/frontpage, https://www.sweetplaid.shop/collections/all-kids-sweetplaids, https://www.sweetplaid.shop/collections/all-xxl-sweetplaids and https://www.sweetplaid.shop/collections/the-classics have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.sweetplaid.shop/collections has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

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

1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=136018914&Ver=2&mid=7aa88180-671a-45a4-8d55-00e2c2d2b4cc&bo=3&sid=825d2050dae911f1b61d7b3f56e03101&vid=82647da0dae911f1a9c665988ddc22a2&vids=0&msclkid=N&pi=918639831&l.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

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

Chrome logged issues while loading the page (“Cookie”).

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

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