Website review, no card needed

smartpots.com logo

smartpots.com website review

Visit site (opens in a new tab)Reviewed 10 November 202631 issues · 76 checks

This review found 31 issues worth fixing on smartpots.com, 10 of them high impact, across 76 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
6.5 s1.4 sMay 23Nov 73.6 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.0 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.1 s
Jun 20, 20264.7 s
Jun 27, 20265.2 s
Jul 4, 20265.3 s
Jul 11, 20265.5 s
Jul 18, 20265.4 s
Jul 25, 20265.4 s
Aug 1, 20265.4 s
Aug 8, 20265.5 s
Aug 15, 20265.8 s
Aug 22, 20265.8 s
Aug 29, 20265.9 s
Sep 5, 20265.8 s
Sep 12, 20265.4 s
Sep 19, 20265.3 s
Sep 26, 20264.6 s
Oct 3, 20264.1 s
Oct 10, 20263.8 s
Oct 17, 20263.6 s
Oct 24, 20263.6 s
Oct 31, 20263.6 s
Nov 7, 20263.6 s
Real-visitor tap response (INP)75th percentile, phones
726 ms42 msMay 23Nov 7597 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026121 ms
May 30, 2026129 ms
Jun 6, 2026137 ms
Jun 13, 2026146 ms
Jun 20, 2026348 ms
Jun 27, 2026405 ms
Jul 4, 2026439 ms
Jul 11, 2026462 ms
Jul 18, 2026483 ms
Jul 25, 2026522 ms
Aug 1, 2026542 ms
Aug 8, 2026570 ms
Aug 15, 2026601 ms
Aug 22, 2026612 ms
Aug 29, 2026630 ms
Sep 5, 2026645 ms
Sep 12, 2026647 ms
Sep 19, 2026645 ms
Sep 26, 2026610 ms
Oct 3, 2026556 ms
Oct 10, 2026528 ms
Oct 17, 2026520 ms
Oct 24, 2026523 ms
Oct 31, 2026572 ms
Nov 7, 2026597 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

Full-page screenshot of smartpots.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. smartpots.com at 1.0 s1.0 s
  2. smartpots.com at 2.0 s2.0 s
  3. smartpots.com at 3.0 s3.0 s
  4. smartpots.com at 4.0 s4.0 s
  5. smartpots.com at 5.0 s5.0 s
  6. smartpots.com at 6.0 s6.0 s
  7. smartpots.com at 7.0 s7.0 s
  8. smartpots.com at 8.0 s8.0 s

Speed

6 to fix73
  • Render-blocking requests

    1.1 s

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

  • Main-thread work: 4.5 s

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

  • Improve image delivery

    150 ms · 1.2 MB

    13 images could be 1.2 MB 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.

  • Mobile performance score: 73

    73/100

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Shopify, Google Tag Manager and Klaviyo and others), adding 961 KiB and 575 ms of main-thread time.

  • Shopify adds 254 ms

    254 ms

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

  • 7 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 48 KiB

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

  • Reduce unused JavaScript

    184 KiB

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

  • Minify JavaScript

    39 KiB

    39 KiB could be saved by minifying JavaScript.

  • Use efficient cache lifetimes

    21 KiB

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

  • Legacy JavaScript

    19 KiB

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

  • 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: 18 ms

    18 ms

    Your server sent the HTML in 18 ms, well inside Google's 600 ms guideline.

Core Web Vitals

10 to fix33
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user INP: 631 ms

    631 ms

    Real visitors wait 631 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 3.1 s

    3.1 s

    Real visitors see the first content after 3.1 s (75th percentile). Good is under 1.8 s.

  • Time to Interactive: 9.4 s

    9.4 s

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

  • Largest Contentful Paint: 4.2 s

    4.2 s

    Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “100-gallon Natural Smart Pot”.

  • Real-user LCP: 3.8 s

    3.8 s

    Real visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Tap response (INP) got 368% slower for real visitors

    +368%

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

  • Largest content (LCP) got 79% slower for real visitors

    +79%

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

  • Real-user TTFB: 1.4 s

    1.4 s

    Real visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 479 ms

    479 ms

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

4 checks passed
  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Speed Index: 3.3 s

    3.3 s

    Visually, the page fills in at 3.3 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

1 to fix85
  • Page weight: 3.8 MB in 335 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 335 requests on a phone: images 1.5 MB (18), scripts 970 KiB (139) and other files 964 KiB (160). Under 2 MB keeps phones on slow connections fast.

  • About 1.1 g of CO₂ per visit

    1.09 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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

3 to fixGoogle 9296
  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (15 elements)

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

  • 2 links without text

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

1 checks passed
  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 3 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9281
  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “Smart Pots — USA-Made Fabric Grow Bags & Raised Beds | BPA & Lead Free”.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “BLACKFRIDAY”). One clear main headline is easier for people and search engines.

  • Meta description is long (181 characters)

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 102 internal links, 7 external

    The homepage links to 102 pages on smartpots.com and 7 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://smartpots.com/.

  • Structured data in place

    Structured data found: OnlineStore, 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://smartpots.com/sitemap.xml.

AI search readiness

100
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, logo, description and contact details; url and sameAs (social profiles) would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,162 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://smartpots.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix68
  • 1 page without a title

    https://smartpots.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://smartpots.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 13 pages without a meta description

    https://smartpots.com/collections/shop-all-smart-pots, https://smartpots.com/pages/why-smart-pot, https://smartpots.com/customer_authentication/redirect, https://smartpots.com/pages/store-locator, https://smartpots.com/pages/resources-tips and https://smartpots.com/pages/how-it-works and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://smartpots.com/collections/shop-all-smart-pots, https://smartpots.com/customer_authentication/redirect, https://smartpots.com/pages/store-locator, https://smartpots.com/pages/resources-tips, https://smartpots.com/pages/faq and https://smartpots.com/pages/contact and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://smartpots.com/products/smart-pot-fabric-planter 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.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

    33 of 36 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 729 words of copy

    The homepage carries about 729 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 50% off large pots →”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Shop Online”, “Contact us” and “Shop the sale →”.

  • 14 short forms

    14 short forms (2 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 1 email link.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 14 cookies set on arrival

    14

    Opening the homepage sets 14 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.

  • 22 other companies contacted

    Loading the homepage contacts 22 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 smartpots.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 5 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Ex Show Variants · Inbox · Klaviyo Email Marketing Sms · Judge Me Reviews · Variants As Separate Products

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

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Google Analytics
Hosting
Shopify

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on smartpots.com, including 16 speed issues, 4 SEO issues 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25