Skip to content
https://tobaccoseedshop.com Export & share
Scanned
2026-07-20 17:41 UTC
Worker
🇧🇷 Sao Paulo
Duration
1.2m
Vs prev

Global Performance

6/6 locations

High global latency — average 637ms across 6 locations, fastest from Amsterdam (385ms), slowest from Sao Paulo (935ms). No CDN detected. Cache-Control header is missing. 3 locations above the 500ms target.

Brazil - Sao Paulo
Full audit
935ms
DNS 131ms · TLS 211ms
Netherlands - Amsterdam
385ms
DNS 19ms · TLS 22ms
Spain - Madrid
391ms
DNS 108ms · TLS 40ms
United Stated - New York
476ms
DNS 43ms · TLS 90ms
Singapore - Singapore
834ms
DNS 148ms · TLS 170ms
United States - Santa Clara
804ms
DNS 206ms · TLS 143ms
CDN: No CDN · Avg TTFB: 637ms · Cache: No cache headers

Audit overview

Compliance needs attention; the rest of the categories are in good shape.

Fix Priority Matrix

5 findings

Quick Wins

4

High impact, low effort — start here.

Strategic

1

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Screenshots

DESKTOP + MOBILE
Desktop
Desktop screenshot
Mobile
Mobile screenshot

Top Priorities (5)

Sorted by impact
Critical: 1

HSTS header is missing

Without HSTS, a network attacker can downgrade the very first connection to HTTP and steal the user's session.

Security › Security Headers
Warning: 2

Cookie 'shop_currency' is missing the HttpOnly flag

Without HttpOnly, JavaScript can read the cookie — an XSS bug becomes a session-stealing attack.

Security › Cookie Security
Warning: 3

Cookie 'shop_currency_geo' is missing the HttpOnly flag

Without HttpOnly, JavaScript can read the cookie — an XSS bug becomes a session-stealing attack.

Security › Cookie Security
Warning: 4

Cookie 'shop_currency_manual' is missing the HttpOnly flag

Without HttpOnly, JavaScript can read the cookie — an XSS bug becomes a session-stealing attack.

Security › Cookie Security
Warning: 5

Cross-Origin-Embedder-Policy header is missing

COEP enforces that all embedded resources opt-in to cross-origin embedding — required for cross-origin isolation features.

Security › Security Headers
What fixing these means. Your site is in great shape. The remaining improvements are refinements rather than critical fixes. Addressing the critical issues below would have the most immediate impact on your user trust.
5 security gaps detected — browsers may warn visitors about your site.

Business case

What fixing the audit's findings is worth -- and what ignoring them keeps costing.

Return on investment

£150 investment → £999/month returns + GBP 18,050,000 risk avoided

Investment
£150
2.0 h · 5 findings
Monthly returns
£999
£11,990/yr
Payback
0.2 mo
+7894% Y1
Regulatory risk avoided GBP 18,050,000
Or — fix only the top 3 findings
£560.1 mo payback · +21216% Y1
Optimistic scenario assuming the top 3 capture most of the upside. Real-world recovery typically falls between this projection and the full-fix ROI above.
£75 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Conversion barriers

4 barrier(s) likely increasing bounce by ~10%.

Barriers
4
4 warn
Bounce delta
+10pp
added vs baseline
Score
88
A
Speed
0
Trust
2
Usability
0
Content
0
Nav
2
  • No HSTS header
    Returning visitors are briefly exposed to downgrade attacks on first request
    → Set Strict-Transport-Security: max-age=31536000; includeSubDomains
  • No Content-Security-Policy header
    Higher XSS blast radius — one compromised script can exfiltrate the checkout form
    → Ship a reporting-only CSP first, then enforce once violations are clean
  • No skip-to-content link
    Keyboard and screen-reader users must tab through the entire header on every page
    → Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
  • 2 broken link(s) on the page
    Clicks land on 404s — trust drops and the session often ends
    → Fix or remove the broken destinations surfaced on the Content tab

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Remediation cost

£150 2.0 developer hours at £75/hr
Quick wins
£75 4 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Team composition

Multiplier applied to dev hours to reflect QA, design, and PM overhead. Use Dev only for solo work; Full team for projects with formal review processes.

£ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

Warning:Cost of inaction

£999 / month at risk ~£11,990 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

£18,050,000

UK GDPRPECREquality Act 2010
  • 3 non-essential cookie(s) set without consent banner
    UK GDPR: GBP 10,000 – GBP 17,500,000
  • 3 non-essential cookie(s) set without consent banner
    PECR: GBP 1,000 – GBP 500,000
  • Privacy Policy not detected
    UK GDPR: GBP 10,000 – GBP 17,500,000

Bounce-Rate Cost

£999 /mo

+9.5pp bounce · ~952 lost visitors/mo

CPC: GBP 1.05

Bandwidth Waste

£0.05 /mo

780.3 MB/mo × 0.063 GBP/GB

  • Optimize transfer: save ~78 KB per page load
    Saves £0.05/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 1 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Lighthouse

Mobile

99
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
100
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.40 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.61 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

2 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

2.18 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

1.61 s

Desktop

99
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
96
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

734 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

769 ms

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

994 ms

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

771 ms

Categories

8
Avg score 87.2

How you compare

Where this site stands against peers running the same stack.

Cart Functionality · 576 peers
You 88
·
Avg 73
+15 above average
0 50 100
Performance P99Security P99Sustainability P98Accessibility P97Compliance P4SEO P89Content P73Infrastructure P59

Top 10% of Cart Functionality sites score 86+ on Compliance; you're at 64 — closing this gap is the highest-leverage improvement.

Better than 99% of Cart Functionality sites See full Cart Functionality benchmark →
Google Search Console · 3916 peers
You 88
·
Avg 73
+15 above average
0 50 100
Performance P98Compliance P3Security P97Accessibility P97Sustainability P93SEO P89Content P75Infrastructure P54

Top 10% of Google Search Console sites score 85+ on Compliance; you're at 64 — closing this gap is the highest-leverage improvement.

Better than 98% of Google Search Console sites See full Google Search Console benchmark →

Technology stack

Google Search Console, on LiteSpeed/PHP

8 technologies detected 5 stack layers 3 with CPE identifier Complex

Stack Architecture

Analytics
Hostinger
Ecommerce
Cart Functionality
Framework
Google Search Console HTTP/3 Open Graph Priority Hints
Runtime
PHP 8.3.30
Server
LiteSpeed

All Detected Technologies (8)

LiteSpeed is a high-scalability web server.

Categories Web servers Website https://litespeedtech.com Detected by BeaverCheck Evidence Server header: LiteSpeed
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

PHP is a general-purpose scripting language used for web development.

Categories Programming languages Website https://php.net Detected by BeaverCheck Evidence x-powered-by: PHP/8.3.30
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

Websites that have a shopping cart or checkout page, either using a known ecommerce platform or a custom solution.

Categories Ecommerce Website https://www.wappalyzer.com/technologies/ecommerce/cart-functionality Detected by BeaverCheck
Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: google-site-verification=bdDNvyZ9GoFHfRmYnB2-O3k3CM-qQw14arsBDQM7fuI

HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.

Categories Miscellaneous Website https://httpwg.org/ Detected by BeaverCheck

Open Graph is a protocol that is used to integrate any web page into the social graph.

Categories Miscellaneous Website https://ogp.me Detected by BeaverCheck

Priority Hints exposes a mechanism for developers to signal a relative priority for browsers to consider when fetching resources.

Categories Performance Website https://wicg.github.io/priority-hints/ Detected by BeaverCheck

Hostinger is an employee-owned Web hosting provider and internet domain registrar.

Categories Hosting Website https://www.hostinger.com Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

Observations (3)

Runtime exposed via X-Powered-By header

The X-Powered-By header reveals 'PHP 8.3.30'. Remove this header in production to reduce information leakage.

→ Security

No build tool detected

A framework (Google Search Console) was detected but no bundler was identified. The build tool may not be detectable from output patterns, or the site may use the framework's built-in bundler.

Complex technology stack detected

8 technologies identified. A complex stack increases maintenance burden and attack surface. Consider whether all components are actively needed.

Show your score

Drop this badge on your README, marketing site, or status page. It auto-updates every time the audit re-runs and links back to this report.

BeaverCheck badge

This badge auto-updates with your latest scan result.

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Ftobaccoseedshop.com)](https://beavercheck.com/sites/tobaccoseedshop.com)
<a href="https://beavercheck.com/sites/tobaccoseedshop.com"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ftobaccoseedshop.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Ftobaccoseedshop.com

Export & share

Download the audit, share with your team, or grab a fix plan ready to copy into your tracker.

Share

Copies markdown to clipboard

Export
Download Markdown Report Download JSON

Fix Plan

Three-week roadmap to ship the audit's findings, with one-click copy targets for your tracker.

Three-week fix plan

2 sprints · 2h total → projected A (91)

Sprint 1: Quick Wins

+3

Highest ROI — low effort, high impact

4 findings 1h → A (91)
  • · HSTS header is missing
  • · Cookie 'shop_currency' is missing the HttpOnly flag
  • · Cookie 'shop_currency_geo' is missing the HttpOnly flag
  • · Cookie 'shop_currency_manual' is missing the HttpOnly flag

Sprint 2: Core Fixes

Medium effort, high structural impact

1 findings 1h → A (91)
  • · Cross-Origin-Embedder-Policy header is missing

Send Feedback