Skip to content
https://he.wikipedia.org Export & share
Recent Trends
Performance stable →
56
TTFB stable →
112ms
FCP stable →
3.0s
LCP stable →
6.9s
Scanned
2026-05-09 09:36 UTC
Worker
🇪🇸 Madrid
Duration
53.00s
Vs prev

Global Performance

6/6 locations

Excellent global latency — average 59ms across 6 locations, fastest from Singapore (11ms), slowest from Sao Paulo (168ms). No CDN detected.

Spain - Madrid
Full audit
114ms
DNS 33ms · TLS 28ms
Netherlands - Amsterdam
11ms
DNS 5ms · TLS 5ms
Singapore - Singapore
11ms
DNS 5ms · TLS 4ms
Brazil - Sao Paulo
168ms
DNS 5ms · TLS 4ms
United States - Santa Clara
20ms
DNS 7ms · TLS 5ms
United Stated - New York
32ms
DNS 9ms · TLS 9ms
CDN: No CDN · Avg TTFB: 59ms · Cache: s-maxage=1200, must-revalidate, max-age=0

Audit overview

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

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

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

10 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: 4

45 image-only link(s) without alt text

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Accessibility › Link & Button Quality
Critical: 5

48 image-in-link without alt text

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Accessibility › Alt Text Quality
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 user trust.
2 security gaps detected — browsers may warn visitors about your site.
3 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

₪2,250 investment → ₪3,696/month returns + ILS 500,000 risk avoided

Investment
₪2,250
7.5 h · 5 findings
Monthly returns
₪3,696
₪44,351/yr
Payback
0.6 mo
+1871% Y1
Regulatory risk avoided ILS 500,000
Or — fix only the top 3 findings
₪1,9500.5 mo payback · +2174% 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.
₪450 — 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

5 barrier(s) likely increasing bounce by ~15%.

Barriers
5
1 crit 4 warn
Bounce delta
+15pp
added vs baseline
Score
78
B
Speed
0
Trust
1
Usability
1
Content
0
Nav
3
  • 35 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
  • 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
  • 10 link(s) with generic text ("click here", "read more")
    Screen-reader users navigating by link list see no context — and search engines can't infer relevance
    → Rewrite with descriptive phrases that identify the destination
  • 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

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

Remediation cost

₪2,250 7.5 developer hours at ₪300/hr
Quick wins
₪450 3 fixes in ~90 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

Cost of inaction

₪45,363 / month at risk ~₪544,351 / year if left unfixed
Default is 10,000. Use your own number for accurate $-figures.

Compliance Risk

ILS 500,000

Privacy Protection Law
  • 5 non-essential cookie(s) set without consent banner
    Privacy Protection Law: ILS 10,000 – ILS 500,000
  • 2 tracking cookie(s) set before consent interaction
    Privacy Protection Law: ILS 10,000 – ILS 500,000
  • Privacy Policy not detected
    Privacy Protection Law: ILS 10,000 – ILS 500,000

Bounce-Rate Cost

₪3,695 /mo

+15.3pp bounce · ~1,535 lost visitors/mo

CPC: ILS 2.41

Bandwidth Waste

₪1.00 /mo

3381.5 MB/mo × 0.296 ILS/GB

  • Optimize transfer: save ~338 KB per page load
    Saves ₪1.00/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

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

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

1.36 s

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

42 ms

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

0.187

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

1.82 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.44 s

Desktop

99
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
89
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
85
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.

325 ms

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

609 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.071

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

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

609 ms

Categories

8
Avg score 79.0

How you compare

Where this site stands against peers running the same stack.

HSTS · 2430 peers
You 80
·
Avg 75
At average
0 50 100
Compliance P1Accessibility P90Security P83Performance P82Sustainability P67SEO P35Content P36Infrastructure P52

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

Better than 85% of HSTS sites See full HSTS benchmark →
jQuery · 1825 peers
You 80
·
Avg 73
+7 above average
0 50 100
Compliance P1Accessibility P95Security P94Performance P90SEO P14Sustainability P74Content P30Infrastructure P60

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

Better than 94% of jQuery sites See full jQuery benchmark →

Technology stack

HSTS, on PHP

8 technologies detected 2 stack layers 4 with CPE identifier Complex

Stack Architecture

Framework
HSTS MediaWiki Open Graph RSS Redux jQuery 3.7.1 jQuery UI 1.9.2
Runtime
PHP

All Detected Technologies (8)

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

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

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

MediaWiki is a free and open-source wiki engine.

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

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

RSS is a family of web feed formats used to publish frequently updated works—such as blog entries, news headlines, audio, and video—in a standardized format.

Categories Miscellaneous Website https://www.rssboard.org/rss-specification Detected by BeaverCheck

Redux is a predictable state container for JavaScript applications.

Categories JavaScript frameworks Website https://redux.js.org Detected by BeaverCheck

jQuery is a JavaScript library which is a free, open-source software designed to simplify HTML DOM tree traversal and manipulation, as well as event handling, CSS animation, and Ajax.

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

jQuery UI is a collection of GUI widgets, animated visual effects, and themes implemented with jQuery, Cascading Style Sheets, and HTML.

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

Observations (2)

No build tool detected

A framework (HSTS) 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%2Fhe.wikipedia.org)](https://beavercheck.com/results/1cdc345a-62fa-42b6-8c2d-62db53882fc1)
<a href="https://beavercheck.com/results/1cdc345a-62fa-42b6-8c2d-62db53882fc1"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fhe.wikipedia.org" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fhe.wikipedia.org

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 · 8h total → projected B (89)

Sprint 1: Quick Wins

+4

Highest ROI — low effort, high impact

3 findings 2h → B (84)
  • · 10 link(s) with no accessible text
  • · 45 image-only link(s) without alt text
  • · 48 image-in-link without alt text

Sprint 2: Core Fixes

+5

Medium effort, high structural impact

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

Send Feedback