Spain · Madrid Completed: Apr 16, 2026 17:40 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 83 / 100
Based on 8 categories, 0 sections
Fast site — your users get a smooth experience.
Good foundation, but a few gaps could be exploited.
Several issues make your site difficult for assistive technology users.
Well-optimized for search — your content is discoverable.
Solid infrastructure — fast server responses across the board.
Strong compliance posture across regulations.
Missing metadata means poor previews on social media and search.
Lean and efficient — low environmental impact per visit.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
1 button(s) with no accessible text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
No <main> landmark found
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
No H1 heading found
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
Cross-Origin-Embedder-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/f3c15e5e-afb4-4948-9dc6-f3ebd504a71b)<a href="https://beavercheck.com/results/f3c15e5e-afb4-4948-9dc6-f3ebd504a71b"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fjquery.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fjquery.comThis badge auto-updates with your latest scan result.
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.
5 barrier(s) likely increasing bounce by ~10%.
No HSTS header
+1% bounceReturning visitors are briefly exposed to downgrade attacks on first request
Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
No Open Graph tags
+2% bounceLinks shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop
Fix: Add og:title, og:description, og:image, og:url to the page head
No structured data
+2% bounceNo rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices
Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
No skip-to-content link
+1% bounceKeyboard and screen-reader users must tab through the entire header on every page
Fix: 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.
$550 investment → $0.04/month returns + USD 157,500 risk avoided
$550
6h · 5 findings
$0.04 /mo
~$0.53 / year
USD 157,500
if kept compliant
$100 — 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.
5.5 developer hours at $100/hr
Based on United States rates ($100/hr)
Start here for the best return on investment
$13,125 / month at risk
~$157,501 / year if left unfixed
$157,500
+2 more
$0.04 /mo
551.6 MB/mo × 0.080 USD/GB
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.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 4 critical issues to capture this value
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
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
1.71 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.72 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.001
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
1.71 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.72 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| code.jquery.com/jquery-4.0.0.min.js | 27.2 KiB | 900 ms |
| jquery.com/wp-content/themes/jquery/js/main.js?v=10baaffd | 1.6 KiB | |
| jquery.com/wp-content/themes/jquery.com/style.css?v=8acf125c | 1.3 KiB | |
| jquery.com/wp-content/themes/jquery/css/base.css?v=4a1b65ae | 13.3 KiB | 333 ms |
| /wp-content/themes/jquery/lib/typesense-minibar/typesense... | 4.2 KiB |
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
jQuery in Action by Bear Bibeault, Yehuda Katz, and Aurelio De Rosa ul.books > li > a > img | jquery.com/wp-content/themes/jquery/content/books/jquery-in-action.jpg | 24.3 KiB | 22.6 KiB |
div#banner-secondary > div.features-box > div.feature-box > div.feature-box-image div#banner-secondary > div.features-box > div.feature-box > div.feature-box-image | jquery.com/wp-content/themes/jquery.com/i/feature-sprites.png | 18.3 KiB | 11.3 KiB |
Learning jQuery 4th Edition by Karl Swedberg and Jonathan Chaffer ul.books > li > a > img | jquery.com/wp-content/themes/jquery/content/books/learning-jquery-4th-ed.jpg | 6.8 KiB | 5.2 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| jquery.com/wp-content/themes/jquery/css/base.css?v=4a1b65ae | 13.3 KiB | 4.2 KiB |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
nav#main > typesense-minibar > form.searchform > button.visuallyhidden nav#main > typesense-minibar > form.searchform > button.visuallyhidden |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
herodevs.com body.jquery > div#banner > a |
Navigation div#container > nav#main > div.menu-top-container > button#menu-trigger |
v4.0.0 a.button > span.download-button-content > span.download-message > span.download-version |
"button.continue" div.container > div.line > code > span.hljs-string |
"Next Step..." div.container > div.line > code > span.hljs-string |
"#banner-message" div.container > div.line > code > span.hljs-string |
"#button-container button" div.container > div.line > code > span.hljs-string |
"click" div.container > div.line > code > span.hljs-string |
url div.container > div.line > code > span.hljs-attr |
"/api/getWeather" div.container > div.line > code > span.hljs-string |
data div.container > div.line > code > span.hljs-attr |
zipcode div.container > div.line > code > span.hljs-attr |
97201 div.container > div.line > code > span.hljs-number |
success div.container > div.line > code > span.hljs-attr |
"#weather-temp" div.container > div.line > code > span.hljs-string |
"<strong>" div.container > div.line > code > span.hljs-string |
"</strong> degrees" div.container > div.line > code > span.hljs-string |
These are opportunities to improve the legibility of your content.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Discover Support Options div#banner-secondary > div.download > div.download-options > a |
View Source on GitHub → div#banner-secondary > div.download > div.download-options > a |
How jQuery Works → div#banner-secondary > div.download > div.download-options > a |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html.js html.js |
These items highlight common accessibility best practices.
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Performance issues directly impact user engagement and conversion rates.
| URL | Aspect Ratio (Displayed) | Aspect Ratio (Actual) | |
|---|---|---|---|
jQuery Succinctly by Cody Lindley ul.books > li > a > img | jquery.com/wp-content/themes/jquery/content/books/jquery-succinctly.jpg | 90 x 112 (0.80) | 124 x 166 (0.75) |
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
jquery.com/ line 347, col 0 | Applying inline speculation rules violates the following Content Security Policy directive 'script-src 'self' 'nonce-db04281fedbe392c' code.jquery.com'. Either the 'unsafe-inline' keyword, a hash ('sha256-hZhXKqL3V9mpohqAHCc0GmfFPvqrhP8tP/zBKtvjXmg='), or a nonce ('nonce-...') is required to enable inline execution. The action has been blocked. |
jquery.com/ line 26, col 0 | Applying inline style violates the following Content Security Policy directive 'style-src 'self' 'nonce-db04281fedbe392c' code.jquery.com'. Either the 'unsafe-inline' keyword, a hash ('sha256-UIcrKzPURWyA4TnwsGBP76F3UAtE9ZnoB43rgcG+OVw='), or a nonce ('nonce-...') is required to enable inline execution. The action has been blocked. |
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Performance issues directly impact user engagement and conversion rates.
| Issue type |
|---|
| Content security policy |
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Performance issues directly impact user engagement and conversion rates.
| Link destination | Link Text |
|---|---|
| /2021/10/07/jquery-maintainers-update-and-transition-jque... | Learn more |
| /2021/10/jquery-maintainers-continue-modernization-initia... | Learn more |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
493 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
495 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.015
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
493 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.
495 ms
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| jquery.com/wp-content/themes/jquery/css/base.css?v=4a1b65ae | 13.3 KiB | 53 ms |
| jquery.com/wp-content/themes/jquery/js/main.js?v=10baaffd | 1.6 KiB | |
| jquery.com/wp-content/themes/jquery.com/style.css?v=8acf125c | 1.3 KiB | |
| /wp-content/themes/jquery/lib/typesense-minibar/typesense... | 4.2 KiB | |
| code.jquery.com/jquery-4.0.0.min.js | 27.2 KiB | 240 ms |
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
jQuery in Action by Bear Bibeault, Yehuda Katz, and Aurelio De Rosa ul.books > li > a > img | jquery.com/wp-content/themes/jquery/content/books/jquery-in-action.jpg | 24.3 KiB | 22.6 KiB |
div#banner-secondary > div.features-box > div.feature-box > div.feature-box-image div#banner-secondary > div.features-box > div.feature-box > div.feature-box-image | jquery.com/wp-content/themes/jquery.com/i/feature-sprites.png | 18.3 KiB | 11.3 KiB |
Learning jQuery 4th Edition by Karl Swedberg and Jonathan Chaffer ul.books > li > a > img | jquery.com/wp-content/themes/jquery/content/books/learning-jquery-4th-ed.jpg | 6.8 KiB | 5.2 KiB |
jQuery nav > div.constrain > ul.projects > li.project | jquery.com/wp-content/themes/jquery/images/jq-nav-icons.png | 7.8 KiB | 5.0 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| jquery.com/wp-content/themes/jquery/css/base.css?v=4a1b65ae | 13.3 KiB | 4.2 KiB |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Download
API Documentation
Blog
Plugins
Browser Support
Version Support div#container > nav#main > div.menu-top-container > ul#menu-top |
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
nav#main > typesense-minibar > form.searchform > button.visuallyhidden nav#main > typesense-minibar > form.searchform > button.visuallyhidden |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
herodevs.com body.jquery > div#banner > a |
v4.0.0 a.button > span.download-button-content > span.download-message > span.download-version |
"button.continue" div.container > div.line > code > span.hljs-string |
"Next Step..." div.container > div.line > code > span.hljs-string |
"#banner-message" div.container > div.line > code > span.hljs-string |
"#button-container button" div.container > div.line > code > span.hljs-string |
"click" div.container > div.line > code > span.hljs-string |
url div.container > div.line > code > span.hljs-attr |
"/api/getWeather" div.container > div.line > code > span.hljs-string |
data div.container > div.line > code > span.hljs-attr |
zipcode div.container > div.line > code > span.hljs-attr |
97201 div.container > div.line > code > span.hljs-number |
success div.container > div.line > code > span.hljs-attr |
"#weather-temp" div.container > div.line > code > span.hljs-string |
"<strong>" div.container > div.line > code > span.hljs-string |
"</strong> degrees" div.container > div.line > code > span.hljs-string |
These are opportunities to improve the legibility of your content.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Download nav#main > div.menu-top-container > ul#menu-top > li.menu-item |
API Documentation nav#main > div.menu-top-container > ul#menu-top > li.menu-item |
Blog nav#main > div.menu-top-container > ul#menu-top > li.menu-item |
Plugins nav#main > div.menu-top-container > ul#menu-top > li.menu-item |
Browser Support nav#main > div.menu-top-container > ul#menu-top > li.menu-item |
Version Support nav#main > div.menu-top-container > ul#menu-top > li.menu-item |
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Discover Support Options div#banner-secondary > div.download > div.download-options > a |
View Source on GitHub → div#banner-secondary > div.download > div.download-options > a |
How jQuery Works → div#banner-secondary > div.download > div.download-options > a |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html.js html.js |
These items highlight common accessibility best practices.
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Performance issues directly impact user engagement and conversion rates.
| URL | Aspect Ratio (Displayed) | Aspect Ratio (Actual) | |
|---|---|---|---|
jQuery Succinctly by Cody Lindley ul.books > li > a > img | jquery.com/wp-content/themes/jquery/content/books/jquery-succinctly.jpg | 90 x 112 (0.80) | 124 x 166 (0.75) |
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
jquery.com/ line 347, col 0 | Applying inline speculation rules violates the following Content Security Policy directive 'script-src 'self' 'nonce-db04281fedbe392c' code.jquery.com'. Either the 'unsafe-inline' keyword, a hash ('sha256-hZhXKqL3V9mpohqAHCc0GmfFPvqrhP8tP/zBKtvjXmg='), or a nonce ('nonce-...') is required to enable inline execution. The action has been blocked. |
jquery.com/ line 26, col 0 | Applying inline style violates the following Content Security Policy directive 'style-src 'self' 'nonce-db04281fedbe392c' code.jquery.com'. Either the 'unsafe-inline' keyword, a hash ('sha256-UIcrKzPURWyA4TnwsGBP76F3UAtE9ZnoB43rgcG+OVw='), or a nonce ('nonce-...') is required to enable inline execution. The action has been blocked. |
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Performance issues directly impact user engagement and conversion rates.
| Issue type |
|---|
| Content security policy |
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Performance issues directly impact user engagement and conversion rates.
| Link destination | Link Text |
|---|---|
| /2021/10/07/jquery-maintainers-update-and-transition-jque... | Learn more |
| /2021/10/jquery-maintainers-continue-modernization-initia... | Learn more |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback