B — https://www.proton.me | BeaverCheck Audit

Site Health

Score: 81 / 100

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

Content-Security-Policy header is missing

Security › Security Headers

HSTS header is missing

Security › Security Headers

No Content-Security-Policy header found

Security › Content Security Policy

3 image-only link(s) without alt text

Accessibility › Link & Button Quality

125 HTTP requests — consider bundling or reducing

Performance › Page Weight Budget

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.proton.me)](https://beavercheck.com/results/c93958bd-662a-e5c3-0ed1-61de9baf67e9)

HTML

<a href="https://beavercheck.com/results/c93958bd-662a-e5c3-0ed1-61de9baf67e9"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.proton.me" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fwww.proton.me

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

100

SEO

Core Web Vitals

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.08 s

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

7.64 s

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

192 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.64 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.

7.80 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

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.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:33.871 source:map[type:text value:[unattributed]]]]

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-0-IMG

nodeLabel: div.flex > div.w-full > picture.contents > img.w-full

path: 1,HTML,1,BODY,7,MAIN,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,PICTURE,1,IMG

selector: div.flex > div.w-full > picture.contents > img.w-full

snippet: <img src="https://pmecdn.protonweb.com/image-transformation/?s=s&image=proton_apps_l…" width="420" height="285" loading="lazy" decoding="async" alt="" class="w-full dtc-object-contain md:dtc-object-contain dtc-object-center md:dtc-o…">

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.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

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.

URL	Transfer Size	Duration
proton.me/_astro/_form_.DQ5Uv3cP.css	48.9 KiB	300 ms

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

	URL	Resource Size	Est Savings
div.flex > div#slider-item-4a2ylhqh-0 > div.absolute > img.h-full `div.flex > div#slider-item-4a2ylhqh-0 > div.absolute > img.h-full`	/image-transformation/?s=s&image=card_proton_mail_ui_aed2...	52.9 KiB	14.0 KiB
div.@container/aside > div.flex > div > img.shrink-0 `div.@container/aside > div.flex > div > img.shrink-0`	/image-transformation/?s=c&image=image%2Fupload%2Fv175804...	9.2 KiB	4.9 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 838 ms

URL	Time Spent
www.proton.me/	838 ms
proton.me/	0.0 ms

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.

TTI

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.

Diagnostics

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.

Estimated savings: 180 ms 45.1 KiB

URL	Transfer Size	Est Savings
proton.me/_astro/_form_.DQ5Uv3cP.css	47.0 KiB	45.1 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.

Estimated savings: 180 ms 23.2 KiB

URL	Transfer Size	Est Savings
proton.me/_astro/DropdownButton.DR7HMx3f.js	37.1 KiB	23.2 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

Category	Time Spent
Other	1.0 s
Script Evaluation	929 ms
Parse HTML & CSS	452 ms
Style & Layout	194 ms
Rendering	113 ms
Script Parsing & Compilation	37 ms

More information about the performance of your application. These numbers don't directly affect the Performance score.

●Use efficient cache lifetimes

●Layout shift culprits

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,021 KiB

●JavaScript execution time 1.0 s

●Avoid long main-thread tasks 8 long tasks found

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 70 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 40 ms

○INP breakdown

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

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.

Best practices

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.

Failing Elements
Privacy Policy `div.space-y-6 > ul.text-xs > li.sm:mr-2 > a.text-body`
Terms & conditions `div.space-y-6 > ul.text-xs > li.sm:mr-2 > a.text-body`
Transparency report `div.space-y-6 > ul.text-xs > li.sm:mr-2 > a.text-body`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
span.flex > span.h-9 > div.inline-flex > img.inline-flex `span.flex > span.h-9 > div.inline-flex > img.inline-flex`	/image-transformation/?s=c&image=image%2Fupload%2Fv174196...	36 x 36 (1.00)	24 x 15 (1.60)

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

100

SEO

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.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

100

SEO

Core Web Vitals

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.

840 ms

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

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

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

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

1.90 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

lhId: page-0-IMG

nodeLabel: div.flex > div.w-full > picture.contents > img.w-full

path: 1,HTML,1,BODY,7,MAIN,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,PICTURE,1,IMG

selector: div.flex > div.w-full > picture.contents > img.w-full

snippet: <img src="https://pmecdn.protonweb.com/image-transformation/?s=s&image=better_intern…" width="420" height="285" loading="lazy" decoding="async" alt="" class="w-full dtc-object-contain md:dtc-object-contain dtc-object-center md:dtc-o…">

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.

title: Preconnected origins

description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.

title: Preconnect candidates

value: No additional origins are good candidates for preconnecting

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.

URL	Transfer Size	Duration
proton.me/_astro/_form_.DQ5Uv3cP.css	48.9 KiB	80 ms

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

	URL	Resource Size	Est Savings
div#slider-item-o4mgs0im-0 > div.flex > picture.contents > img.w-full `div#slider-item-o4mgs0im-0 > div.flex > picture.contents > img.w-full`	/image-transformation/?s=s&image=Pass_password_d14b4d77f2...	51.7 KiB	41.7 KiB
div.flex > div#slider-item-0stbzsgf-0 > div.flex > img.w-full `div.flex > div#slider-item-0stbzsgf-0 > div.flex > img.w-full`	/image-transformation/?s=s&image=slider_proton_meet_1_45a...	26.5 KiB	12.3 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Diagnostics

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.

Estimated savings: 70 ms 43.9 KiB

URL	Transfer Size	Est Savings
proton.me/_astro/_form_.DQ5Uv3cP.css	47.0 KiB	43.9 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.

Estimated savings: 70 ms 23.2 KiB

URL	Transfer Size	Est Savings
proton.me/_astro/DropdownButton.DR7HMx3f.js	37.1 KiB	23.2 KiB

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.

Estimated savings: 276 ms

URL	Time Spent
www.proton.me/	276 ms
proton.me/	0.0 ms

●Time to Interactive 1.9 s

●Use efficient cache lifetimes

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 40 ms

●Minify CSS

●Minify JavaScript

●Avoids enormous network payloads Total size was 1,180 KiB

●JavaScript execution time 0.2 s

●Minimizes main-thread work 0.7 s

●Image elements have explicit `width` and `height`

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 30 ms

●Server Backend Latencies 130 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 40 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○User Timing marks and measures

○Avoid long main-thread tasks

○Avoid non-composited animations

Accessibility

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Failing Elements
Slide 1 Slide 2 Slide 3 Slide 4 `div.flex > div.slider-controls > div.slider-control-container > ol.slider-pagination`

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Failing Elements
Slide 1 `div.slider-control-container > ol.slider-pagination > li.flex > button#slider-item-label-4a2ylhqh-0`
Slide 2 `div.slider-control-container > ol.slider-pagination > li.flex > button#slider-item-label-4a2ylhqh-1`
Slide 3 `div.slider-control-container > ol.slider-pagination > li.flex > button#slider-item-label-4a2ylhqh-2`
Slide 4 `div.slider-control-container > ol.slider-pagination > li.flex > button#slider-item-label-4a2ylhqh-3`

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements
New `ul.mt-4 > li.flex > span.*:-my-1 > div.inline-block`
New `ul.mt-4 > li.flex > span.*:-my-1 > div.inline-block`

These are opportunities to improve the legibility of your content.

Tables and lists

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.

Failing Elements
Slide 1 `div.slider-controls > div.slider-control-container > ol.slider-pagination > li.flex`
Slide 2 `div.slider-controls > div.slider-control-container > ol.slider-pagination > li.flex`
Slide 3 `div.slider-controls > div.slider-control-container > ol.slider-pagination > li.flex`
Slide 4 `div.slider-controls > div.slider-control-container > ol.slider-pagination > li.flex`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

	URL	Aspect Ratio (Displayed)	Aspect Ratio (Actual)
span.flex > span.h-9 > div.inline-flex > img.inline-flex `span.flex > span.h-9 > div.inline-flex > img.inline-flex`	/image-transformation/?s=c&image=image%2Fupload%2Fv174196...	36 x 36 (1.00)	24 x 15 (1.60)

●Uses HTTPS

●Avoids deprecated APIs

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

100

SEO

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Document has a meta description

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Browse & Analyze

Learn

Results for https://www.proton.me

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best practices

Best Practices

User Experience

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Contrast

Tables and lists

Best Practices

User Experience

SEO

Keyboard Shortcuts