Mobile 375 × 812

Desktop 1440 × 900

Score: 83 / 100
Based on 8 categories, 0 sections
Fast site — your users get a smooth experience.
Several missing protections leave your users and data exposed.
Mostly accessible, but some users still face barriers.
Well-optimized for search — your content is discoverable.
Solid infrastructure — fast server responses across the board.
Mostly compliant — a few items need attention.
Rich content metadata — your pages look great everywhere.
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.
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.
Cross-Origin-Embedder-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
Cross-Origin-Opener-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/e19940a8-b126-44b9-9ad2-f5842c6a38ea)<a href="https://beavercheck.com/results/e19940a8-b126-44b9-9ad2-f5842c6a38ea"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fsymfony.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fsymfony.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.
4 barrier(s) likely increasing bounce by ~13%.
Page loads in 2.8s
+5% bounceEvery additional 100ms above 2.5s costs conversions — you're 335ms over
Fix: Target <2.5s LCP: defer non-critical scripts and optimize the hero image
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
Content is hard to read
+2% bounceGraduate-level reading difficulty — limits the addressable audience for product or blog pages
Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60
13 link(s) with generic text ("click here", "read more")
+1% bounceScreen-reader users navigating by link list see no context — and search engines can't infer relevance
Fix: Rewrite with descriptive phrases that identify the destination
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
€298 investment → €516/month returns + EUR 120,500,000 risk avoided
€298
4h · 5 findings
€516 /mo
~€6,197 / year
EUR 120,500,000
if kept compliant
€170 — 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.
3.5 developer hours at €85/hr
Based on European Union rates (€85/hr)
Start here for the best return on investment
€10,041,667 / month at risk
~€120,500,001 / year if left unfixed
€120,500,000
+4 more
€0.05 /mo
707.0 MB/mo × 0.074 EUR/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 3 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.
2.64 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.84 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
76 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.
4.41 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.84 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.
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 |
|---|---|---|
| connect.symfony.com/css/sln.css | 1800.0 s | 5.0 KiB |
| /beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312... | 86400.0 s | 10.7 KiB |
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
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 |
|---|---|---|
| connect.symfony.com/css/sln.css | 5.0 KiB | 914 ms |
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 | |
|---|---|---|---|
div.ui-page-container > div.footer-bottom > div.symfony-20-highlight > img.me-2 div.ui-page-container > div.footer-bottom > div.symfony-20-highlight > img.me-2 | symfony.com/assets/icons/logos/sf-20years-wordmark-dark--dFsFxh.webp | 15.3 KiB | 14.8 KiB |
div.sln-bar-inner > div.sln-highlight > a.sln-visible-phone > img div.sln-bar-inner > div.sln-highlight > a.sln-visible-phone > img | /uploads/sln/1991a94e-4351-4af1-88ab-4f17f6d20f45/8697a26... | 12.1 KiB | 11.7 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Performance issues directly impact user engagement and conversion rates.
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| symfony.com/assets/@symfony/ux-live-component/live_controller-qMGNvHD.js | 19.2 KiB | 2.8 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.
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 |
|---|
SymfonyLive Berlin 2026 div.top-horizontal-highlights > div.ui-page-container > div.top-horizontal-highlight > a.top-horizontal-highlight-title |
main div.ap-player > pre.ap-terminal > span.ap-line > span.fg-3 |
production div.ap-player > pre.ap-terminal > span.ap-line > span.fg-3 |
Symfony is a powerful PHP framework that empowers developers to build scalable,… section.section-what > div.ui-page-container > div.ui-heading > p.ui-heading-subtitle |
Symfony packages are battle-tested and ready to solve all your needs article.content > section.section-metrics > div.ui-page-container > p.section-metrics-heading |
Everything you need to get up to speed quickly! section.section-start > div.ui-page-container > div.ui-heading > p.ui-heading-subtitle |
Predictable, secure, and built to last — Symfony meets the demands of all compa… div.d-xl-flex > div.col-xl-6 > div.ui-heading > p.ui-heading-subtitle |
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
All rights reserved div.ui-page-container > div.footer-bottom > p.mb-3 > a |
These are opportunities to improve the legibility of your content.
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 |
|---|
div.ui-page-container > div.footer-bottom > div.symfony-20-highlight > img.me-2 div.ui-page-container > div.footer-bottom > div.symfony-20-highlight > img.me-2 |
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.
Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Apr 23–24, 2026 SymfonyLive Berlin 2026 In English
Jun 4, 2026 SymfonyDay Montr… div.d-lg-flex > div.col-lg-12 > div.community-item > table |
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 |
|---|---|
| symfony.com/doc/current/page_creation.html | Learn more |
| symfony.com/doc/current/console.html | Learn more |
| symfony.com/packages | Learn more |
| ux.symfony.com/ | Learn more |
| symfony.com/doc/current/contributing/community/releases.html | Learn more |
| symfony.com/doc/current/contributing/code/security.html | Learn more |
| symfony.com/releases | Learn more |
| symfony.com/doc/current/contributing/code/license.html | Learn more |
| /services/version-upgrade?utm_source=symfony&utm_medium=h... | Learn more |
| symfony.com/cloud/ | Learn more |
| insight.symfony.com/ | Learn more |
| /services?utm_source=symfony&utm_medium=homepage_banner&u... | Learn more |
| certification.symfony.com/ | Read more |
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 |
|---|
div.ui-page-container > div.footer-bottom > div.symfony-20-highlight > img.me-2 div.ui-page-container > div.footer-bottom > div.symfony-20-highlight > img.me-2 |
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.
521 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
521 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.006
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
689 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.
521 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.
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 |
|---|---|---|
| connect.symfony.com/css/sln.css | 5.0 KiB | 252 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.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| connect.symfony.com/css/sln.css | 1800.0 s | 5.0 KiB |
| /beacon.min.js/v8c78df7c7c0f484497ecbca7046644da177152312... | 86400.0 s | 10.7 KiB |
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 | |
|---|---|---|---|
div.sln-bar-inner > div.sln-highlight > a.sln-visible-desktop > img div.sln-bar-inner > div.sln-highlight > a.sln-visible-desktop > img | /uploads/sln/9dcfe3b7-4ac7-4fd7-bdaa-d690f48b40da/48b7025... | 5.7 KiB | 5.6 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| symfony.com/assets/@symfony/ux-live-component/live_controller-qMGNvHD.js | 19.3 KiB | 2.8 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.
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 |
|---|
SymfonyDay Montreal 2026 div.top-horizontal-highlights > div.ui-page-container > div.top-horizontal-highlight > a.top-horizontal-highlight-title |
June 4, 2026 div.top-horizontal-highlights > div.ui-page-container > div.top-horizontal-highlight > div.top-horizontal-highlight-data |
+20 talks and workshops div.top-horizontal-highlights > div.ui-page-container > div.top-horizontal-highlight > div.top-horizontal-highlight-data |
Register now div.top-horizontal-highlights > div.ui-page-container > div.top-horizontal-highlight > div.top-horizontal-highlight-data |
main div.ap-player > pre.ap-terminal > span.ap-line > span.fg-3 |
production div.ap-player > pre.ap-terminal > span.ap-line > span.fg-3 |
Symfony is a powerful PHP framework that empowers developers to build scalable,… section.section-what > div.ui-page-container > div.ui-heading > p.ui-heading-subtitle |
Everything you need to get up to speed quickly! section.section-start > div.ui-page-container > div.ui-heading > p.ui-heading-subtitle |
Predictable, secure, and built to last — Symfony meets the demands of all compa… div.d-xl-flex > div.col-xl-6 > div.ui-heading > p.ui-heading-subtitle |
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
All rights reserved div.ui-page-container > div.footer-bottom > p.mb-3 > a |
These are opportunities to improve the legibility of your content.
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 |
|---|
div.ui-page-container > div.footer-bottom > div.symfony-20-highlight > img.me-2 div.ui-page-container > div.footer-bottom > div.symfony-20-highlight > img.me-2 |
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.
Screen readers have features to make navigating tables easier. Ensuring that `<td>` elements in a large table (3 or more cells in width and height) have an associated table header may improve the experience for screen reader users. Learn more about table headers.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Apr 23–24, 2026 SymfonyLive Berlin 2026 In English
Jun 4, 2026 SymfonyDay Montr… div.d-lg-flex > div.col-lg-12 > div.community-item > table |
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 |
|---|---|
| symfony.com/doc/current/page_creation.html | Learn more |
| symfony.com/doc/current/console.html | Learn more |
| symfony.com/packages | Learn more |
| ux.symfony.com/ | Learn more |
| symfony.com/doc/current/contributing/community/releases.html | Learn more |
| symfony.com/doc/current/contributing/code/security.html | Learn more |
| symfony.com/releases | Learn more |
| symfony.com/doc/current/contributing/code/license.html | Learn more |
| /services/version-upgrade?utm_source=symfony&utm_medium=h... | Learn more |
| symfony.com/cloud/ | Learn more |
| insight.symfony.com/ | Learn more |
| /services?utm_source=symfony&utm_medium=homepage_banner&u... | Learn more |
| certification.symfony.com/ | Read more |
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 |
|---|
div.ui-page-container > div.footer-bottom > div.symfony-20-highlight > img.me-2 div.ui-page-container > div.footer-bottom > div.symfony-20-highlight > img.me-2 |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback