plantsbasically.com website review

Not measured in this review.

• Page weight: 4.1 MB

  4.1 MB

  Your homepage downloads 4.1 MB on a phone, 432 KiB of it images (10%). Under 2 MB keeps phones on slow connections fast.

• About 1.2 g of CO₂ per visit

  1.18 g

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

• ARIA attributes must conform to valid values (1 element)

  ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  Elements (1)

• 5 text elements with low contrast

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

  Elements (3)

• Hidden but focusable

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

  Elements (3)

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

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

  Elements (2)

• 4 links without text

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

• 2 form fields without a label

  2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  View source

• Headings skip levels

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

  View sourceElements (1)

• No structured data

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

• 2 H1 headlines

  There are 2 <h1> headlines (“PLANTSBASICALLY” and “A DAILY SYSTEM FOR JOINT & SPINE HEALTH.”). One clear main headline is easier for people and search engines.

  View source

• 66 internal links, 47 external

  The homepage links to 66 pages on plantsbasically.com and 47 external pages.

• No Organization structured data

  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.

• 6 pages without a meta description

  /pages/black-friday-2026-early-access, /pages/shop, /products/ultimate-joint-system-welcome-kit, /products/joint-relief-system-welcome-kit, /products/deluxe-joint-system-welcome-kit and /pages/reviews have no meta description, so Google writes the search snippet from whatever text it finds.

  Elements (6)

• 2 pages without an H1

  /pages/shop and /pages/faq 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 29 found) and read each the way a search engine does.

• 6 small tap targets

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

• 1 JavaScript error while loading

  1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

• 1 broken link to your own pages

  1 link from your homepage to your own site is broken, for example https://www.plantsbasically.com/collections/juicy-joint (404).

• Short HSTS lifetime

  HSTS is set, but max-age is 91 days; one year is the recommended minimum.

• 2 links through redirect chains

  2 links go through two or more redirects, for example https://instagram.com/plantsbasically.

• No Referrer-Policy

  No Referrer-Policy header, so full URLs can leak to the sites you link to.

• No Permissions-Policy

  No Permissions-Policy header to switch off camera, microphone and location for embedded content.

• Deprecated X-XSS-Protection

  X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

• No security.txt

  There is no /.well-known/security.txt telling researchers how to report a security problem to you.

• DNSSEC is off

  plantsbasically.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

• About 2,398 words of copy

  The homepage carries about 2,398 words of visible text.

• No DKIM key on the usual selectors

  We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

• Email authentication score: 85/100

  Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

• 9 trackers load before any consent

  9

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

• 24 cookies set on arrival

  24

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

• 48 other companies contacted

  Loading the homepage contacts 48 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.