Spain · Madrid Completed: Apr 16, 2026 17:02 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 80 / 100
Based on 8 categories, 0 sections
Decent speed, but optimizing further could improve engagement.
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.
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.
'unsafe-inline' found in script source
Security gaps expose your site and users to attacks, eroding trust.
1 control(s) without accessible label
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
25 image-only link(s) without alt text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
Soft 404: server returns HTTP 200 for non-existent pages
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/614842b4-56a8-43aa-8e6f-b696b1154c5e)<a href="https://beavercheck.com/results/614842b4-56a8-43aa-8e6f-b696b1154c5e"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fsentry.io" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fsentry.ioThis 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.
3 barrier(s) likely increasing bounce by ~7%.
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
1 form field(s) without a label
+2% 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
1 broken link(s) on the page
+2% bounceClicks land on 404s — trust drops and the session often ends
Fix: Fix or remove the broken destinations surfaced on the Content tab
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
$550 investment → $0.44/month returns + USD 157,500 risk avoided
$550
6h · 5 findings
$0.44 /mo
~$5.23 / 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,505 / year if left unfixed
$157,500
+3 more
$0.44 /mo
5444.0 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.
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.
3.33 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
0 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.
5.67 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.
0 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.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
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.
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 | |
|---|---|---|---|
Sentry issue detail page for a fatal read ETIMEDOUT error on a GET /api/project… div.accordion-wrapper > div.tab-item > div.tab-mobile-img-wrapper > img.shrink-0 | sentry.io/_vercel/image?url=_astro%2Ftabs-b-1.CxQnCdrJ.webp&w=640&q=100 | 49.4 KiB | 45.9 KiB |
Sentry Session Replay showing a user session on empower-plant.com with clicks, … div.accordion-wrapper > div.tab-item > div.tab-mobile-img-wrapper > img.shrink-0 | sentry.io/_vercel/image?url=_astro%2Ftabs-a-1.3EhRDHX9.webp&w=640&q=100 | 46.8 KiB | 43.5 KiB |
Left Installation Instructions Image Mobile section.relative > div.container > div.getting-started-container > img.md:hidden | sentry.io/_astro/getting-started-img-left.CRIbD4_5.webp | 36.7 KiB | 27.9 KiB |
Illustration of a terminal-style window showing the command npm install @sentry… div.flex > div.bg-gradient-to-r > div.rounded-[0.6625rem] > img.w-full | sentry.io/_vercel/image?url=_astro%2Finstall-1-line.CStr0HQx.webp&w=828&q=100 | 26.8 KiB | 21.9 KiB |
Right Installation Instructions Image div.container > div.getting-started-container > div.flex > img.relative | sentry.io/_astro/getting-started-img-right.uCQ8m_KR.webp | 27.4 KiB | 20.3 KiB |
div.container > div.animated-logo-grid-wrapper > div.ufo-container > img.ufo div.container > div.animated-logo-grid-wrapper > div.ufo-container > img.ufo | sentry.io/_astro/ufo-abduction-image.CCCweOzA.webp | 11.6 KiB | 10.8 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 |
|---|---|
| sentry.io/_astro/_slug_.utFj-uUR.css | 25.2 KiB |
| sentry.io/_astro/_slug_.BMaqGsss.css | 1.4 KiB |
| sentry.io/_astro/_slug_.C88tuRea.css | 4.4 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Performance issues directly impact user engagement and conversion rates.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
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 CSS files can reduce network payload sizes. Learn how to minify CSS.
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.
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Performance issues directly impact user engagement and conversion rates.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks
Performance issues directly impact user engagement and conversion rates.
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Performance issues directly impact user engagement and conversion rates.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| sentry.io/_astro/Welcome.astro_astro_type_script_index_0_lang.CxHIClDC.js | 6.1 s | 2.8 s | 0.5 ms |
| Unattributable | 956 ms | 395 ms | 0.0 ms |
| sentry.io/welcome/ | 450 ms | 134 ms | 18 ms |
| plausible.io/js/script.tagged-events.js | 360 ms | 24 ms | 0.6 ms |
| sentry.io/_astro/link-decorator.BP7leAsv.js | 100 ms | 2.3 ms | 0.2 ms |
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Other | 3.9 s |
| Script Evaluation | 3.4 s |
| Style & Layout | 515 ms |
| Rendering | 143 ms |
| Parse HTML & CSS | 75 ms |
| Garbage Collection | 53 ms |
| Script Parsing & Compilation | 21 ms |
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 | |
|---|---|
div.container > div.animated-logo-grid-wrapper > div.ufo-container > img.ufo div.container > div.animated-logo-grid-wrapper > div.ufo-container > img.ufo | sentry.io/_astro/ufo-abduction-image.CCCweOzA.webp |
Left Installation Instructions Image Mobile section.relative > div.container > div.getting-started-container > img.md:hidden | sentry.io/_astro/getting-started-img-left.CRIbD4_5.webp |
Right Installation Instructions Image div.container > div.getting-started-container > div.flex > img.relative | sentry.io/_astro/getting-started-img-right.uCQ8m_KR.webp |
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 an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
body.transition-colors > main#main-content > div.toggle-container body.transition-colors > main#main-content > div.toggle-container |
Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Automatically root-cause any issue
Catch critical issues before you merge and … div.feature-carousel-wrapper > div.carousel-gradient-container > div#feature-carousel-ojaxx97oi > div.carousel-item |
Break production less
Predict and prevent the errors that matter most before t… div.feature-carousel-wrapper > div.carousel-gradient-container > div#feature-carousel-ojaxx97oi > div.carousel-item |
Stay in the flow
From GitHub, Slack, Jira, and Linear to coding agents with Se… div.feature-carousel-wrapper > div.carousel-gradient-container > div#feature-carousel-ojaxx97oi > div.carousel-item |
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.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Next.js
Angular
Android
iOS
Flutter
React Native
.NET MAUI
Python
Node.js
React… div.getting-started-container > div.flex > div.select-wrapper > select#installation-dropdown-23 |
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.
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) | |
|---|---|---|---|
Left Installation Instructions Image div.container > div.getting-started-container > div.flex > img.hidden | sentry.io/_astro/getting-started-img-left.CRIbD4_5.webp | 248 x 410 (0.60) | 466 x 410 (1.14) |
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.
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.
787 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
1.35 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
14 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.03 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.39 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.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
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.
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 | |
|---|---|---|---|
GitHub code review by the Seer highlighting a potential bug: inconsistent error… div.flex-grid-cell > div.justify-items-center > div.relative > img.tab-img-2 | sentry.io/_vercel/image?url=_astro%2Ftabs-b-3.DBuDJxCL.webp&w=640&q=100 | 64.7 KiB | 48.7 KiB |
Sentry trace waterfall view for an HTTP POST to /api/v1/buy-plants, showing AI-… div.flex-grid-cell > div.justify-items-center > div.relative > img.tab-img-1 | sentry.io/_vercel/image?url=_astro%2Ftabs-a-2.BeO7Y7Ee.webp&w=640&q=100 | 60.4 KiB | 45.4 KiB |
Sentry issue detail page for a fatal read ETIMEDOUT error on a GET /api/project… div.flex-grid-cell > div.justify-items-center > div.relative > img.tab-img-0 | sentry.io/_vercel/image?url=_astro%2Ftabs-b-1.CxQnCdrJ.webp&w=640&q=100 | 49.4 KiB | 37.1 KiB |
Sentry Session Replay showing a user session on empower-plant.com with clicks, … div.flex-grid-cell > div.justify-items-center > div.relative > img.tab-img-0 | sentry.io/_vercel/image?url=_astro%2Ftabs-a-1.3EhRDHX9.webp&w=640&q=100 | 46.8 KiB | 35.2 KiB |
Code diff view showing new configurations added to prevent database timeout err… div.flex-grid-cell > div.justify-items-center > div.relative > img.tab-img-1 | sentry.io/_vercel/image?url=_astro%2Ftabs-b-2.Bc7JV4Tp.webp&w=640&q=100 | 42.7 KiB | 32.1 KiB |
Sentry issue view showing an unhandled exception in src/main.py at line 279: “E… div.flex-grid-cell > div.justify-items-center > div.relative > img.tab-img-2 | sentry.io/_vercel/image?url=_astro%2Ftabs-a-3.BH8DXd6a.webp&w=640&q=100 | 40.2 KiB | 30.2 KiB |
Illustration of a terminal-style window showing the command npm install @sentry… div.flex > div.bg-gradient-to-r > div.rounded-[0.6625rem] > img.w-full | sentry.io/_vercel/image?url=_astro%2Finstall-1-line.CStr0HQx.webp&w=828&q=100 | 26.8 KiB | 15.7 KiB |
div.container > div.animated-logo-grid-wrapper > div.ufo-container > img.ufo div.container > div.animated-logo-grid-wrapper > div.ufo-container > img.ufo | sentry.io/_astro/ufo-abduction-image.CCCweOzA.webp | 11.6 KiB | 10.8 KiB |
Chat-style interface showing “Sentry agent connected” and a user named “codydea… div.flex > div.bg-gradient-to-r > div.rounded-[0.6625rem] > img.w-full | sentry.io/_vercel/image?url=_astro%2Fmcp-integration.BsYvoh98.webp&w=828&q=100 | 15.9 KiB | 9.3 KiB |
A section labeled “Root Cause” with code insight stating: “The code attempts to… div.flex > div.bg-gradient-to-r > div.rounded-[0.6625rem] > img.w-full | sentry.io/_vercel/image?url=_astro%2Fautomatic-rca.CGAenFBp.webp&w=828&q=100 | 15.4 KiB | 9.0 KiB |
Code snippet with a console warning message and a Sentry UI section showing a b… div.flex > div.bg-gradient-to-r > div.rounded-[0.6625rem] > img.w-full | sentry.io/_vercel/image?url=_astro%2Fai-code-review.zf1XFlmB.webp&w=828&q=100 | 12.3 KiB | 7.2 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 |
|---|---|
| sentry.io/_astro/_slug_.BMaqGsss.css | 1.4 KiB |
| sentry.io/_astro/_slug_.utFj-uUR.css | 25.2 KiB |
| sentry.io/_astro/_slug_.C88tuRea.css | 4.4 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| sentry.io/_astro/_slug_.utFj-uUR.css | 25.2 KiB | 19.5 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| sentry.io/_astro/index.BSQljMam.js | 47.9 KiB | 23.3 KiB |
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Other | 1.2 s |
| Script Evaluation | 760 ms |
| Style & Layout | 143 ms |
| Rendering | 50 ms |
| Parse HTML & CSS | 23 ms |
| Garbage Collection | 16 ms |
| Script Parsing & Compilation | 5.7 ms |
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 | |
|---|---|
div.container > div.animated-logo-grid-wrapper > div.ufo-container > img.ufo div.container > div.animated-logo-grid-wrapper > div.ufo-container > img.ufo | sentry.io/_astro/ufo-abduction-image.CCCweOzA.webp |
More information about the performance of your application. These numbers don't directly affect the Performance score.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| sentry.io/ | 346 ms |
| sentry.io/welcome/ | 0.0 ms |
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 an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
main#main-content > div.toggle-container > div.toggle-wrapper > div.toggle-track main#main-content > div.toggle-container > div.toggle-wrapper > div.toggle-track |
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.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Next.js
Angular
Android
iOS
Flutter
React Native
.NET MAUI
Python
Node.js
React… div.getting-started-container > div.flex > div.select-wrapper > select#installation-dropdown-23 |
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.
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) | |
|---|---|---|---|
Left Installation Instructions Image Mobile section.relative > div.container > div.getting-started-container > img.md:hidden | sentry.io/_astro/getting-started-img-left.CRIbD4_5.webp | 248 x 410 (0.60) | 466 x 410 (1.14) |
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.
Send Feedback