Website review, no card needed
houseplant.com website review
Visit site (opens in a new tab)Reviewed 5 November 202628 issues · 80 checks
This review found 28 issues worth fixing on houseplant.com, 9 of them high impact, across 80 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
84B- #21,711 of 121,172 reviewed websitesbeats 77%
- #14,075 of 68,578 online storesbeats 73%
- #13,657 of 62,496 Shopify storesbeats 72%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.0 s |
| Oct 10, 2026 | 978 ms |
| Oct 17, 2026 | 1.0 s |
| Oct 24, 2026 | 1.0 s |
| Oct 31, 2026 | 995 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 102 ms |
| May 23, 2026 | 104 ms |
| May 30, 2026 | 104 ms |
| Jun 6, 2026 | 105 ms |
| Jun 13, 2026 | 105 ms |
| Jun 20, 2026 | 104 ms |
| Jun 27, 2026 | 105 ms |
| Jul 4, 2026 | 104 ms |
| Jul 11, 2026 | 104 ms |
| Jul 18, 2026 | 104 ms |
| Jul 25, 2026 | 104 ms |
| Aug 1, 2026 | 104 ms |
| Aug 8, 2026 | 104 ms |
| Aug 15, 2026 | 103 ms |
| Aug 22, 2026 | 103 ms |
| Aug 29, 2026 | 104 ms |
| Sep 5, 2026 | 104 ms |
| Sep 12, 2026 | 110 ms |
| Sep 19, 2026 | 113 ms |
| Sep 26, 2026 | 116 ms |
| Oct 3, 2026 | 121 ms |
| Oct 10, 2026 | 129 ms |
| Oct 17, 2026 | 131 ms |
| Oct 24, 2026 | 136 ms |
| Oct 31, 2026 | 135 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.0 s
2.0 s
3.1 s
4.1 s
5.1 s
6.1 s
7.2 s
8.2 s
Speed
Reduce unused JavaScript
1.8 s · 991 KiBAbout 991 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Mobile performance score: 43
43/100Your mobile performance score is 43. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.2 s
A phone's processor spends 7.2 s on main-thread work while loading, 3.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, alia-prod.com and rebuyengine.com and others), adding 3.0 MB and 2.0 s of main-thread time.
Use efficient cache lifetimes
850 ms · 689 KiB32 files are served with short cache lifetimes, so returning visitors download them again (689 KiB).
Google Tag Manager adds 652 ms
652 msGoogle Tag Manager costs a phone 652 ms of main-thread work and 702 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.
alia-prod.com adds 489 ms
489 msalia-prod.com costs a phone 489 ms of main-thread work and 999 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.
Improve image delivery
200 ms · 315 KiB14 images could be 315 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Render-blocking requests
300 ms20 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
rebuyengine.com adds 182 ms
182 msrebuyengine.com costs a phone 182 ms of main-thread work and 333 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.
Shopify adds 164 ms
164 msShopify costs a phone 164 ms of main-thread work and 432 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.
1,694 HTML elements
The page has 1,694 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 212 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 59 KiBPolyfills for old browsers add 59 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused CSS
74 KiBAbout 74 KiB of CSS is downloaded but never applied on this page.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 15.6 s
15.6 sYour largest element takes 15.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 33.9 s
33.9 sThe page becomes fully interactive after 33.9 s. Good is under 3.8 s.
Speed Index: 11.4 s
11.4 sVisually, the page fills in at 11.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 854 ms
854 msScripts block taps and scrolling for 854 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 32% slower for real visitors
+32%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 102 ms to 135 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 150 ms
150 msReal visitors wait 150 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 433 ms
433 msReal visitors wait 433 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 29% faster for real visitors
-29%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.8 MB in 508 requests
5.8 MBYour homepage downloads 5.8 MB in 508 requests on a phone: scripts 2.7 MB (182), images 976 KiB (68) and other files 934 KiB (183). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (68 KiB) is 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.
About 1.6 g of CO₂ per visit
1.64 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.64 g of CO₂e: 196.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
12 links without text
12 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 42 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 0 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (173 characters)
Your meta description is 173 characters; Google truncates after about 160, so the end of your pitch is cut.
120 internal links, 3 external
The homepage links to 120 pages on houseplant.com and 3 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Ceramics, Home Goods & Accessories”.
Title: 61 characters
Your title is a healthy 61 characters: “Ceramics, Home Goods & Accessories | Houseplant by Seth Rogen”.
Canonical URL set
The canonical URL is https://www.houseplant.com/.
Structured data in place
Structured data found: Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.houseplant.com/sitemap.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (734 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.houseplant.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 47 found) and read each the way a search engine does.
7 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
2 broken images
2 images failed to load on a phone, for example https://jointcommerce-files.s3-us-west-2.amazonaws.com/static/dashboard/media/logos/jointcommerce_logo_short.png.
7 small tap targets
7 of 30 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 408 words of copy
The homepage carries about 408 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop All”.
8 calls to action
The homepage has 8 calls to action, for example “Shop”, “Shop All” and “Contact”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 16 testimonial or review blocks, 8 customer or partner logos and a star rating.
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel 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.
28 cookies set on arrival
28Opening the homepage sets 28 cookies (measured from a US location before any click).
No consent tool detected
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.
63 other companies contacted
Loading the homepage contacts 63 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at houseplant.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 16 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Consentmo Gdpr · Elevar Conversion Tracking · Instafeed · Okendo · Klaviyo Email Marketing Sms · Microsoft Clarity · Attentive · Triplewhale · Gdpr Backpack · Restockrocket · b-cdn.net · yotpo.com · cevoid.com · rebuyengine.com · nfcube.com · stamped.io
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Analytics
- Google Analytics | Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Chino Hills
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on houseplant.com, including 19 speed issues, 1 SEO issue and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.