Website review, no card needed

plantsarepurple.com logo

plantsarepurple.com website review

Visit site (opens in a new tab)Reviewed 21 November 202636 issues · 79 checks

This review found 36 issues worth fixing on plantsarepurple.com, 10 of them high impact, across 79 checks. The most urgent: reduce unused JavaScript. 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
5.1 s3.9 sMay 30Nov 144.2 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20264.6 s
Jun 6, 20264.5 s
Jun 13, 20264.6 s
Jun 20, 20264.4 s
Jul 25, 20264.3 s
Aug 1, 20264.3 s
Aug 8, 20264.2 s
Aug 15, 20264.9 s
Aug 22, 20264.4 s
Oct 17, 20264.0 s
Oct 24, 20264.1 s
Oct 31, 20264.5 s
Nov 7, 20264.5 s
Nov 14, 20264.2 s
Real-visitor tap response (INP)75th percentile, phones
297 ms227 msMay 30Oct 31287 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026246 ms
Jun 13, 2026264 ms
Jun 20, 2026235 ms
Jul 25, 2026274 ms
Aug 1, 2026277 ms
Aug 8, 2026281 ms
Aug 15, 2026289 ms
Oct 24, 2026270 ms
Oct 31, 2026287 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 plantsarepurple.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. plantsarepurple.com at 1.0 s1.0 s
  2. plantsarepurple.com at 2.1 s2.1 s
  3. plantsarepurple.com at 3.1 s3.1 s
  4. plantsarepurple.com at 4.1 s4.1 s
  5. plantsarepurple.com at 5.2 s5.2 s
  6. plantsarepurple.com at 6.2 s6.2 s
  7. plantsarepurple.com at 7.2 s7.2 s
  8. plantsarepurple.com at 8.3 s8.3 s

Speed

9 to fix51
  • Reduce unused JavaScript

    1.0 s · 339 KiB

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

  • Main-thread work: 10.1 s

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

  • Mobile performance score: 51

    51/100

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

  • 8 third-party services on the page

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

  • Improve image delivery

    300 ms · 313 KiB

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

  • Shopify adds 366 ms

    366 ms

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

  • Reduce unused CSS

    370 ms · 39 KiB

    About 39 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 370 ms faster on a phone.

  • 2,962 HTML elements

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

  • Klaviyo adds 170 ms

    170 ms

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

  • 12 long tasks on the main thread

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Legacy JavaScript

    25 KiB

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

  • Use efficient cache lifetimes

    14 KiB

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

  • Minify JavaScript

    12 KiB

    12 KiB could be saved by minifying JavaScript.

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

    21 ms

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

Core Web Vitals

6 to fix54
  • Largest Contentful Paint: 12.9 s

    12.9 s

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

  • Time to Interactive: 14.2 s

    14.2 s

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

  • Speed Index: 9.4 s

    9.4 s

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • Total Blocking Time: 448 ms

    448 ms

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

  • 7 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +9%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

  • Not enough real-visitor data yet

    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.

1 checks passed
  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix75
  • Page weight: 3.8 MB in 319 requests

    3.8 MB

    Your homepage downloads 3.8 MB in 319 requests on a phone: other files 1.2 MB (172), scripts 1.1 MB (90) and images 1.1 MB (42). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    33 KiB

    1 image is downloaded at several times the size a phone draws it, for example PAP_MegaMenu_Skin_aba2974d-9f0d-45bd-843f-70dac698ecfe.jpg at 700 px wide, shown at 163 px. Resized copies would save about 33 KiB.

  • 2 images in older formats

    2 images (134 KiB) are 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.1 g of CO₂ per visit

    1.08 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

9 to fixGoogle 7888
  • Form elements must have labels (8 elements)

    Form elements must have labels: 8 elements on the page fail this check, rated critical by axe-core.

  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • Hidden but focusable

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

  • 2 text elements with low contrast

    2 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 (5 elements)

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 32 links without text

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

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 47 automated accessibility rules passed

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

SEO

2 to fixGoogle 8595
  • No social preview image

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 192 internal links, 37 external

    The homepage links to 192 pages on plantsarepurple.com and 37 external pages.

7 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “We help you to care for your skin effectively with pure and uncomplicated natural cosmetic products at fair prices, and…”.

  • One H1 headline

    Your main headline reads: “plantsarepurple.com”.

  • Title: 44 characters

    Your title is a healthy 44 characters: “Plants are Purple - Simply natural skin care”.

  • Canonical URL set

    The canonical URL is https://plantsarepurple.com/en-us.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization and WebSite.

  • 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://plantsarepurple.com/sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (2 of 6 facts)

    Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 15 pages without a meta description

    https://plantsarepurple.com/en-us/collections/acne-prone-skin, https://plantsarepurple.com/en-us/collections/pro-aging, https://plantsarepurple.com/en-us/collections/dry-skin, https://plantsarepurple.com/en-us/collections/sensitive-skin, https://plantsarepurple.com/en-us/collections/cleaning-toner and https://plantsarepurple.com/en-us/collections/eyes-eyelashes and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://plantsarepurple.com/en-us/collections/acne-prone-skin, https://plantsarepurple.com/en-us/collections/pro-aging, https://plantsarepurple.com/en-us/collections/dry-skin, https://plantsarepurple.com/en-us/collections/sensitive-skin, https://plantsarepurple.com/en-us/collections/cleaning-toner and https://plantsarepurple.com/en-us/collections/eyes-eyelashes and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

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

  • 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 to fixGoogle 9687
  • 36 small tap targets

    36 of 72 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 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

2 to fix79
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

  • About 627 words of copy

    The homepage carries about 627 words of visible text.

5 checks passed
  • 9 calls to action

    The homepage has 9 calls to action, for example “Shop all ›”, “Shop our Sets” and “Shop all”.

  • 27 short forms

    27 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 28 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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.

  • 16 cookies set on arrival

    16

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

  • 30 other companies contacted

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

Apps your storefront loads

Consentmo Gdpr · Klaviyo Email Marketing Sms · Judge Me Reviews · Sami B2b Lock · Ta Banner Pop Up · Gdpr Backpack · Upez · Wholesale Lock Hide Price

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 Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on plantsarepurple.com, including 15 speed issues, 2 SEO issues and 2 conversion gaps. 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