plantswagshop.com website review

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

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

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

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

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

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

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

About 609 KiB of JavaScript is downloaded but never used on this page.

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

Klaviyo costs a phone 309 ms of main-thread work and 351 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.

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

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

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

31 KiB could be saved by minifying JavaScript.

About 22 KiB of CSS is downloaded but never applied on this page.

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 20.3 s. Good is under 3.8 s.

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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.7 MB in 401 requests on a phone: scripts 1.7 MB (256), images 1.1 MB (33) and fonts 337 KiB (7). Under 2 MB keeps phones on slow connections fast.

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

By the Sustainable Web Design model, a visit to your homepage emits about 1.04 g of CO₂e: 125.4 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.

Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

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

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

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

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

Your <h1> is empty.

The homepage links to 169 pages on plantswagshop.com and 13 external pages.

https://www.plantswagshop.com/collections/perfect-plant-gifts 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.plantswagshop.com/collections/perfect-plant-gifts all use the title “The Plant Swag Shop delivers houseplants to your door!”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.plantswagshop.com/collections/pre-potted and https://www.plantswagshop.com/collections/perfect-plant-gifts took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Invalid left-hand side in assignment”.

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

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 1,792 words of visible text.

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