Skip to content
Scanned
2026-04-21 21:28 UTC
Worker
🇪🇸 Madrid
Duration
1.1m
Vs prev

Audit overview

5 categories need attention: Security, and 4 others.

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

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

Content-Security-Policy header is missing

Without a CSP, a single XSS bug can exfiltrate everything your users type — including credentials.

Security › Security Headers
Critical: 2

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
Critical: 3

No Content-Security-Policy header found

Without a CSP, a single XSS bug can exfiltrate everything users type — credentials, payment data, session tokens.

Security › Content Security Policy
Critical: 4

No <main> landmark found

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Accessibility › Landmark Structure
Critical: 5

No favicon or icon links detected

Without a favicon, your tab shows a blank icon and bookmarks look unbranded — amateur signal in every browser surface.

Accessibility › Favicon & Branding
What fixing these means. Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.
3 security gaps detected — browsers may warn visitors about your site.
2 accessibility issues exclude users who rely on assistive technology.

Business case

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

Return on investment

CAD 657 investment → CAD 16,570/month returns + CAD 350,000 risk avoided

Investment
CAD 657
6.9 h · 5 findings
Monthly returns
CAD 16,570
CAD 198,842/yr
Payback
0.0 mo
+30161% Y1
Regulatory risk avoided CAD 350,000
Or — fix only the top 3 findings
CAD 5940.0 mo payback · +33389% 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.
CAD 87 — 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

9 barrier(s) likely increasing bounce by ~38%.

Barriers
9
3 crit 6 warn
Bounce delta
+38pp
added vs baseline
Score
52
D
Speed
2
Trust
2
Usability
1
Content
3
Nav
1
  • Page takes 7.7s to load
    Users abandon at ~3s — you're 5.2s over the 2.5s threshold
    → Optimize render-blocking resources, preload the hero image, and compress images
  • Page feels frozen for 1.6s
    Clicks on the primary CTA are ignored while JavaScript runs
    → Break up long tasks; defer non-critical JavaScript to post-hydration
  • No viewport meta tag
    Mobile browsers render at desktop width and shrink — text unreadable, tap targets miniature
    → Add <meta name="viewport" content="width=device-width, initial-scale=1">
  • 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

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

Remediation cost

CA$657 6.9 developer hours at CA$95/hr
Quick wins
CA$87 3 fixes in ~55 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.

CA$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

Warning:Cost of inaction

CAD 10,548 / month at risk ~CAD 126,581 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

CAD 350,000

ACAPIPEDA
  • No privacy policy link detected
    PIPEDA: CAD 1,000 – CAD 100,000
  • Trackers detected but no cookie policy found
    PIPEDA: CAD 1,000 – CAD 100,000
  • Trackers detected but no privacy policy found
    PIPEDA: CAD 1,000 – CAD 100,000

Bounce-Rate Cost

CAD 10,548 /mo

+37.7pp bounce · ~3,767 lost visitors/mo

CPC: CAD 2.80

Bandwidth Waste

CAD 0.76 /mo

7067.8 MB/mo × 0.108 CAD/GB

  • Optimize transfer: save ~707 KB per page load
    Saves CAD 0.76/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 5 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

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

6.19 s

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

7.68 s

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

1.59 s

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

0.026

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

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

22.05 s

Desktop

83
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.
92
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.41 s

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

1.74 s

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

79 ms

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

0.002

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

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

4.51 s

Categories

8
Avg score 70.1

How you compare

Where this site stands against peers running the same stack.

Facebook · 1424 peers
You 70
·
Avg 73
At average
0 50 100
Compliance P2Accessibility P7Content P7SEO P27Infrastructure P66Sustainability P37Performance P57Security P57

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

Better than 14% of Facebook sites See full Facebook benchmark →
Google Search Console · 3894 peers
You 70
·
Avg 73
At average
0 50 100
Compliance P4Accessibility P9Content P10SEO P24Sustainability P29Infrastructure P62Security P56Performance P46

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

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

Technology stack

Facebook

4 technologies detected 1 stack layers Standard

Stack Architecture

Framework
Facebook Google Search Console Microsoft Microsoft 365

All Detected Technologies (4)

Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: facebook-domain-verification=xvikrfa0dip6aib1q6wf0jaunrzdmt
Categories Analytics Detected by BeaverCheck · Medium Evidence TXT record: google-site-verification=duCnDq0p1NMt0NuNuUVsogkw2u2y7fK2fsMi97f9cCU
Categories Analytics Detected by BeaverCheck · Low Evidence TXT record: MS=ms96016385
Categories Email Detected by BeaverCheck Evidence MX record: discovermagazine-com.mail.protection.outlook.com

Observations (1)

No build tool detected

A framework (Facebook) 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.

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%2Fdiscovermagazine.com)](https://beavercheck.com/sites/discovermagazine.com)
<a href="https://beavercheck.com/sites/discovermagazine.com"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fdiscovermagazine.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fdiscovermagazine.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 · 7h total → projected C (79)

Sprint 1: Quick Wins

+5

Highest ROI — low effort, high impact

3 findings 1h → C (75)
  • · No <main> landmark found
  • · HSTS header is missing
  • · No favicon or icon links detected

Sprint 2: Core Fixes

+4

Medium effort, high structural impact

2 findings 6h → C (79)
  • · Content-Security-Policy header is missing
  • · No Content-Security-Policy header found

Send Feedback