Netherlands · Amsterdam Completed: Apr 22, 2026 22:44 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 76 / 100
Based on 8 categories, 0 sections
Fast site — your users get a smooth experience.
Several missing protections leave your users and data exposed.
Several issues make your site difficult for assistive technology users.
Well-optimized for search — your content is discoverable.
Good server performance with room for optimization.
Several regulatory requirements are not yet met.
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.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
1 image(s) missing alt attribute
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
2 control(s) without accessible label
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
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/d775b0e8-8c94-4a73-b273-0398dc19b4dd)<a href="https://beavercheck.com/results/d775b0e8-8c94-4a73-b273-0398dc19b4dd"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fllvm.org" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fllvm.orgThis badge auto-updates with your latest scan result.
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.
7 barrier(s) likely increasing bounce by ~29%.
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
2 form field(s) without a label
+4% bounceScreen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes
Fix: Associate every input with a visible <label for="…">; add autocomplete attributes
No viewport meta tag
+15% bounceMobile browsers render at desktop width and shrink — text unreadable, tap targets miniature
Fix: Add <meta name="viewport" content="width=device-width, initial-scale=1">
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.
$450 investment → $0.07/month returns + USD 157,500 risk avoided
$450
4h · 5 findings
$0.07 /mo
~$0.78 / year
USD 157,500
if kept compliant
$150 — 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.
4.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
+7 more
$0.07 /mo
812.5 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 5 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.
902 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
902 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.
1.61 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.
924 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.
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.
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.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| llvm.org/img/LLVMWyvernSmall.png | 0.0 ms | 255.2 KiB |
| llvm.org/llvm.css | 0.0 ms | 1.5 KiB |
| llvm.org/img/lines.gif | 0.0 ms | 336 B |
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 | |
|---|---|---|---|
body > div.www_title > img body > div.www_title > img | llvm.org/img/LLVMWyvernSmall.png | 254.9 KiB | 253.4 KiB |
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 |
|---|---|---|
| llvm.org/llvm.css | 1.5 KiB | 151 ms |
Tap interactions may be delayed by up to 300 ms if the viewport is not optimized for mobile.
Performance issues directly impact user engagement and conversion rates.
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
body > div.www_title > img body > div.www_title > img | llvm.org/img/LLVMWyvernSmall.png |
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.
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These are opportunities to improve the interpretation of your content by users in different locales.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
body > div.www_title > img body > div.www_title > img |
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.www_sidebar > form > div > input div.www_sidebar > form > div > input |
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.
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 |
|---|
Overview tr > td > div.www_sidebar > a |
Features tr > td > div.www_sidebar > a |
Documentation tr > td > div.www_sidebar > a |
Command Guide tr > td > div.www_sidebar > a |
FAQ tr > td > div.www_sidebar > a |
Publications tr > td > div.www_sidebar > a |
LLVM Projects tr > td > div.www_sidebar > a |
Open Projects tr > td > div.www_sidebar > a |
LLVM Users tr > td > div.www_sidebar > a |
Bug tracker tr > td > div.www_sidebar > a |
LLVM Logo tr > td > div.www_sidebar > a |
Blog tr > td > div.www_sidebar > a |
Meetings tr > td > div.www_sidebar > a |
LLVM Foundation tr > td > div.www_sidebar > a |
All Releases tr > td > div.www_sidebar > a |
APT Packages tr > td > div.www_sidebar > a |
RPM Snapshots tr > td > div.www_sidebar > a |
Pre-releases tr > td > div.www_sidebar > a |
div.www_sidebar > form > div > input div.www_sidebar > form > div > input |
div.www_sidebar > form > div > input div.www_sidebar > form > div > input |
doxygen tr > td > div.www_sidebar > a |
Sources (GitHub) tr > td > div.www_sidebar > a |
Code Review tr > td > div.www_sidebar > a |
Blog tr > td > div.www_sidebar > a |
Bug tracker tr > td > div.www_sidebar > a |
Buildbot tr > td > div.www_sidebar > a |
Green Dragon tr > td > div.www_sidebar > a |
LNT tr > td > div.www_sidebar > a |
Scan-build tr > td > div.www_sidebar > a |
llvm-cov tr > td > div.www_sidebar > a |
All Announcements td > div.www_sidebar > span > a |
October 27-29, 2025 div.www_text > ul > li > a |
June 10, 2025 div.www_text > ul > li > a |
April 14-16, 2025 div.www_text > ul > li > a |
October 22-24, 2024 div.www_text > ul > li > a |
April 10-11, 2024 div.www_text > ul > li > a |
October 9-11, 2023 div.www_text > ul > li > a |
May 10-11, 2023 div.www_text > ul > li > a |
November 8-9, 2022 div.www_text > ul > li > a |
May 10-11, 2022 div.www_text > ul > li > a |
November 16-19, 2021 div.www_text > ul > li > a |
October 6-8, 2020 div.www_text > ul > li > a |
October 22-23, 2019 div.www_text > ul > li > a |
April 8-9, 2019 div.www_text > ul > li > a |
October 17-18, 2018 div.www_text > ul > li > a |
April 16-17, 2018 div.www_text > ul > li > a |
October 18-19, 2017 div.www_text > ul > li > a |
March 27-28, 2017 div.www_text > ul > li > a |
November 3-4, 2016 div.www_text > ul > li > a |
March 17-18, 2016 div.www_text > ul > li > a |
October 29-30, 2015 div.www_text > ul > li > a |
April 13-14, 2015 div.www_text > ul > li > a |
October 28-29, 2014 div.www_text > ul > li > a |
April 7-8, 2014 div.www_text > ul > li > a |
Nov 6-7, 2013 div.www_text > ul > li > a |
April 29-30, 2013 div.www_text > ul > li > a |
November 7-8, 2012 div.www_text > ul > li > a |
April 12, 2012 div.www_text > ul > li > a |
November 18, 2011 div.www_text > ul > li > a |
September 2011 div.www_text > ul > li > a |
November 2010 div.www_text > ul > li > a |
October 2009 div.www_text > ul > li > a |
August 2008 div.www_text > ul > li > a |
May 2007 div.www_text > ul > li > 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 html |
These items highlight common accessibility best practices.
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.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Performance issues directly impact user engagement and conversion rates.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
body > div.www_title > img body > div.www_title > img |
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.
242 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
242 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.001
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
662 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.
242 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.
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.
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.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| llvm.org/img/LLVMWyvernSmall.png | 0.0 ms | 255.2 KiB |
| llvm.org/llvm.css | 0.0 ms | 1.5 KiB |
| llvm.org/img/lines.gif | 0.0 ms | 336 B |
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 | |
|---|---|---|---|
body > div.www_title > img body > div.www_title > img | llvm.org/img/LLVMWyvernSmall.png | 254.9 KiB | 254.4 KiB |
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 |
|---|---|
| llvm.org/llvm.css | 1.5 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
body > div.www_title > img body > div.www_title > img | llvm.org/img/LLVMWyvernSmall.png |
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.
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These are opportunities to improve the interpretation of your content by users in different locales.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
body > div.www_title > img body > div.www_title > img |
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.www_sidebar > form > div > input div.www_sidebar > form > div > input |
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.
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 |
|---|
Overview tr > td > div.www_sidebar > a |
Features tr > td > div.www_sidebar > a |
Documentation tr > td > div.www_sidebar > a |
Command Guide tr > td > div.www_sidebar > a |
FAQ tr > td > div.www_sidebar > a |
Publications tr > td > div.www_sidebar > a |
LLVM Projects tr > td > div.www_sidebar > a |
Open Projects tr > td > div.www_sidebar > a |
LLVM Users tr > td > div.www_sidebar > a |
Bug tracker tr > td > div.www_sidebar > a |
LLVM Logo tr > td > div.www_sidebar > a |
Blog tr > td > div.www_sidebar > a |
Meetings tr > td > div.www_sidebar > a |
LLVM Foundation tr > td > div.www_sidebar > a |
All Releases tr > td > div.www_sidebar > a |
APT Packages tr > td > div.www_sidebar > a |
RPM Snapshots tr > td > div.www_sidebar > a |
Pre-releases tr > td > div.www_sidebar > a |
div.www_sidebar > form > div > input div.www_sidebar > form > div > input |
div.www_sidebar > form > div > input div.www_sidebar > form > div > input |
doxygen tr > td > div.www_sidebar > a |
Sources (GitHub) tr > td > div.www_sidebar > a |
Code Review tr > td > div.www_sidebar > a |
Blog tr > td > div.www_sidebar > a |
Bug tracker tr > td > div.www_sidebar > a |
Buildbot tr > td > div.www_sidebar > a |
Green Dragon tr > td > div.www_sidebar > a |
LNT tr > td > div.www_sidebar > a |
Scan-build tr > td > div.www_sidebar > a |
llvm-cov tr > td > div.www_sidebar > a |
Compile-time tracker tr > td > div.www_sidebar > a |
All Announcements td > div.www_sidebar > span > a |
October 27-29, 2025 div.www_text > ul > li > a |
June 10, 2025 div.www_text > ul > li > a |
April 14-16, 2025 div.www_text > ul > li > a |
October 22-24, 2024 div.www_text > ul > li > a |
April 10-11, 2024 div.www_text > ul > li > a |
October 9-11, 2023 div.www_text > ul > li > a |
May 10-11, 2023 div.www_text > ul > li > a |
November 8-9, 2022 div.www_text > ul > li > a |
May 10-11, 2022 div.www_text > ul > li > a |
November 16-19, 2021 div.www_text > ul > li > a |
October 6-8, 2020 div.www_text > ul > li > a |
October 22-23, 2019 div.www_text > ul > li > a |
April 8-9, 2019 div.www_text > ul > li > a |
October 17-18, 2018 div.www_text > ul > li > a |
April 16-17, 2018 div.www_text > ul > li > a |
October 18-19, 2017 div.www_text > ul > li > a |
March 27-28, 2017 div.www_text > ul > li > a |
November 3-4, 2016 div.www_text > ul > li > a |
March 17-18, 2016 div.www_text > ul > li > a |
October 29-30, 2015 div.www_text > ul > li > a |
April 13-14, 2015 div.www_text > ul > li > a |
October 28-29, 2014 div.www_text > ul > li > a |
April 7-8, 2014 div.www_text > ul > li > a |
Nov 6-7, 2013 div.www_text > ul > li > a |
April 29-30, 2013 div.www_text > ul > li > a |
November 7-8, 2012 div.www_text > ul > li > a |
April 12, 2012 div.www_text > ul > li > a |
November 18, 2011 div.www_text > ul > li > a |
September 2011 div.www_text > ul > li > a |
November 2010 div.www_text > ul > li > a |
October 2009 div.www_text > ul > li > a |
August 2008 div.www_text > ul > li > a |
May 2007 div.www_text > ul > li > 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 html |
These items highlight common accessibility best practices.
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.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Performance issues directly impact user engagement and conversion rates.
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
body > div.www_title > img body > div.www_title > img |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback