gardeningexpress.co.uk

Readiness by lane

Green: gardeningexpress.co.uk. Thin bar: E-Commerce & Marketplaces peer median.

Priority fixes for gardeningexpress.co.uk

Ordered by impact and by how common each practice is among peers.

1. Priority 1 · Enable

   Meta description written

   Observed: The homepage had no meta description.

   Why it matters: Search engines often use it for the snippet under your link, so a clear description can improve click-through.

   What to do: Write a short, specific description of the page for people, not a list of keywords.

   95% of E-Commerce & Marketplaces peers do this. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

   Guide: Meta Titles and Descriptions That Match Search Intent

2. Priority 2 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for gardeningexpress.co.uk was p=none, which asks receivers to take no action on failing mail.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   39% of E-Commerce & Marketplaces peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 3 external scripts without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   44% of E-Commerce & Marketplaces peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

4. Priority 4 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   48% of E-Commerce & Marketplaces peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

What gardeningexpress.co.uk already does well

Practices fewer than half of E-Commerce & Marketplaces peers use.

• HSTS kept for at least a yearHSTS with a 365-day max-age.32% of peers
• Reachable over IPv6IPv6 address published.40% of peers
• Modern image formats in useWebP or AVIF images detected.47% of peers

What we saw

Homepage checked

https://www.gardeningexpress.co.uk/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Google Trust Services, 90-day validity, expiring 2026-12-24

CDN or edge

Cloudflare

Platform or framework

Magento / Adobe Commerce

DNS operators

Cloudflare

HSTS

max-age 365 days

DMARC policy

p=none

Homepage HTML

977 KB, br

Images on homepage

81 (webp 79, jpg 40, png 19, svg 6, gif 3)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other E-Commerce & Marketplaces sites

• flip.kz72
• foxtale.in72
• francfranc.com72
• glassesdirect.co.uk72
• gooutdoors.co.uk72

E-Commerce & Marketplaces readiness benchmark