Skip to content
https://evilempire.com Export & share
Scanned
2026-07-29 18:42 UTC
Worker
🇪🇸 Madrid
Duration
33.00s
Vs prev

Global Performance

6/6 locations

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

Spain - Madrid
Full audit
123ms
DNS 49ms · TLS 35ms
Netherlands - Amsterdam
96ms
DNS 25ms · TLS 32ms
United Stated - New York
381ms
DNS 87ms · TLS 91ms
United States - Santa Clara
517ms
DNS 56ms · TLS 171ms
Singapore - Singapore
741ms
DNS 161ms · TLS 277ms
Brazil - Sao Paulo
993ms
DNS 307ms · TLS 278ms
CDN: No CDN · Avg TTFB: 475ms · 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

45 link(s) with no accessible text

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Accessibility › Link & Button Quality
Critical: 2

No H1 heading found

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Accessibility › Heading Hierarchy
Warning: 3

1 software version(s) disclosed in HTML: Hugo 0.155.3

Each disclosed version enables direct CVE lookup -- attacker reads the version, searches the CVE database, targets the site with a tested exploit.

Security › HTML Version Disclosure
Warning: 4

46 link(s) open in a new tab without rel=noopener

target="_blank" without rel="noopener" lets the destination tab navigate the original via window.opener -- a reverse-tabnabbing phishing primitive.

Security › Cross-Origin Tab Safety
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 performs reasonably well, but a few targeted fixes could meaningfully improve results. Addressing the critical issues below would have the most immediate impact on your audience reach.
2 accessibility issues exclude users who rely on assistive technology.
3 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

€173 investment → €1,289/month returns + EUR 120,500,000 risk avoided

Investment
€173
2.2 h · 5 findings
Monthly returns
€1.289
€15.471/yr
Payback
0.1 mo
+8826% Y1
Regulatory risk avoided EUR 120.500.000
Or — fix only the top 3 findings
€730.1 mo payback · +20997% 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.
€93 — 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

7 barrier(s) likely increasing bounce by ~21%.

Barriers
7
7 warn
Bounce delta
+21pp
added vs baseline
Score
79
B
Speed
1
Trust
1
Usability
1
Content
2
Nav
2
  • Page loads in 2.7s
    Every additional 100ms above 2.5s costs conversions — you're 233ms over
    → Target <2.5s LCP: defer non-critical scripts and optimize the hero image
  • 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
  • Layout shifts during page load
    Content movement causes mis-clicks on CTAs and form fields
    → Add width/height to images; reserve space for late-loading embeds
  • No structured data
    No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices
    → Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
  • Thin content
    Under 300 words — visitors bounce looking for substance, search engines rank competitors first
    → Add a substantive FAQ, product detail, or case-study section

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

Remediation cost

€173 2.2 developer hours at €80/hr
Quick wins
€93 4 fixes in ~70 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

€930 / month at risk ~€11.165 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

€120.500.000

ePrivacy DirectiveRGPDEAA
  • No privacy policy link detected
    RGPD: EUR 10.000 – EUR 20.000.000
  • Trackers detected but no cookie policy found
    RGPD: EUR 5.000 – EUR 10.000.000
  • Trackers detected but no cookie policy found
    RGPD: EUR 10.000 – EUR 20.000.000

Bounce-Rate Cost

€930 /mo

+20.7pp bounce · ~2,067 lost visitors/mo

CPC: EUR 0.45

Bandwidth Waste

€0,36 /mo

4801.1 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~480 KB per page load
    Saves €0,36/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 2 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

88
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
85
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.23 s

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

2.73 s

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

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

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

2.73 s

Desktop

97
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
85
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.

367 ms

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

1.15 s

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

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

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

1.15 s

Categories

8
Avg score 80.8

How you compare

Where this site stands against peers running the same stack.

Font Awesome · 612 peers
You 82
·
Avg 74
+8 above average
0 50 100
Compliance P2SEO P5Performance P94Security P91Accessibility P91Sustainability P74Content P61Infrastructure P46

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

Better than 92% of Font Awesome sites See full Font Awesome benchmark →
HSTS · 2691 peers
You 82
·
Avg 75
+7 above average
0 50 100
Compliance P3Performance P86Accessibility P86Security P82SEO P21Sustainability P66Infrastructure P38Content P56

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

Better than 86% of HSTS sites See full HSTS benchmark →

Technology stack

Font Awesome, with Nginx CDN

8 technologies detected 3 stack layers 2 with CPE identifier Complex

Stack Architecture

Analytics
Matomo Analytics
Framework
Font Awesome HSTS Hugo 0.155.3Microsoft Microsoft 365 Open Graph
CDN
Nginx

All Detected Technologies (8)

Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.

Categories Web servers, Reverse proxies Website https://nginx.org/en Detected by BeaverCheck Evidence Server header: nginx
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

Font Awesome is a font and icon toolkit based on CSS and Less.

Categories Font scripts Website https://fontawesome.com/ Detected by BeaverCheck

HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.

Categories Security Website https://www.rfc-editor.org/rfc/rfc6797#section-6.1 Detected by BeaverCheck

Hugo is an open-source static site generator written in Go.

Categories Static site generator Website https://gohugo.io Detected by BeaverCheck
Categories Analytics Detected by BeaverCheck · Low Evidence TXT record: MS=ms86956150
Categories Email Detected by BeaverCheck Evidence MX record: evilempire-com.mail.protection.outlook.com

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

Matomo Analytics is a free and open-source web analytics application, that runs on a PHP/MySQL web-server.

Categories Analytics Website https://matomo.org Detected by BeaverCheck
This technology has a CPE identifier — check for known vulnerabilities Search NVD →

Observations (2)

No build tool detected

A framework (Font Awesome) 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%2Fevilempire.com)](https://beavercheck.com/sites/evilempire.com)
<a href="https://beavercheck.com/sites/evilempire.com"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fevilempire.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fevilempire.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 B (88)

Sprint 1: Quick Wins

+5

Highest ROI — low effort, high impact

4 findings 1h → B (87)
  • · No H1 heading found
  • · 45 link(s) with no accessible text
  • · 1 software version(s) disclosed in HTML: Hugo 0.155.3
  • · 46 link(s) open in a new tab without rel=noopener

Sprint 2: Core Fixes

+1

Medium effort, high structural impact

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

Send Feedback