C — https://www.signal.org | BeaverCheck Audit

Site Health

Score: 79 / 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

1 image-in-link without alt text

Accessibility › Alt Text Quality

1 link(s) with no accessible text

Accessibility › Link & Button Quality

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.signal.org)](https://beavercheck.com/results/581f0ea3-9250-9138-403d-8001e0a76201)

HTML

<a href="https://beavercheck.com/results/581f0ea3-9250-9138-403d-8001e0a76201"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.signal.org" alt="BeaverCheck Score"></a>

Image URL

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

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

100

Best Practices

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.

2.83 s

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

7.61 s

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

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

2.83 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.87 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.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Request	Cache TTL	Transfer Size
signal.org/assets/images/features/signal-iphone.png	14400.0 s	207.3 KiB
signal.org/assets/fonts/inter/Inter-ExtraBold.woff2	14400.0 s	105.6 KiB
signal.org/assets/fonts/inter/Inter-SemiBold.woff2	14400.0 s	105.3 KiB
signal.org/assets/images/features/Calls.png	14400.0 s	105.1 KiB
signal.org/assets/fonts/inter/Inter-Regular.woff2	14400.0 s	98.4 KiB
signal.org/assets/javascripts/vendor/lottie-player-2.0.3.min.js	14400.0 s	94.9 KiB
signal.org/assets/stylesheets/vendor/bulma-1.0.4.min.css	14400.0 s	63.1 KiB
signal.org/assets/images/features/signal-pixel.png	14400.0 s	49.4 KiB
signal.org/assets/images/features/Media.png	14400.0 s	34.0 KiB
signal.org/assets/javascripts/vendor/jquery-3.7.1.min.js	14400.0 s	30.2 KiB
signal.org/assets/images/features/Groups.png	14400.0 s	19.6 KiB
signal.org/assets/images/features/Nonprofit503.png	14400.0 s	19.3 KiB
signal.org/assets/images/features/Stickers.png	14400.0 s	16.7 KiB
signal.org/assets/images/features/No-Ads.png	14400.0 s	9.7 KiB
signal.org/assets/images/header/logo.png	14400.0 s	4.6 KiB
signal.org/assets/stylesheets/ultramarine.css	14400.0 s	4.0 KiB
signal.org/assets/images/icons/external-link-alt.svg	14400.0 s	1.0 KiB
signal.org/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js	172800.0 s	835 B

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.container > div.columns > div.column > img.screenshot1 `div.container > div.columns > div.column > img.screenshot1`	signal.org/assets/images/features/signal-iphone.png	206.7 KiB	158.0 KiB
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`	signal.org/assets/images/features/Calls.png	104.5 KiB	65.4 KiB
div.container > div.columns > div.column > img.screenshot2 `div.container > div.columns > div.column > img.screenshot2`	signal.org/assets/images/features/signal-pixel.png	48.8 KiB	29.1 KiB
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`	signal.org/assets/images/features/Media.png	33.5 KiB	18.8 KiB
div.container > div.columns > div.column > img `div.container > div.columns > div.column > img`	signal.org/assets/images/features/Nonprofit503.png	18.8 KiB	15.4 KiB
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`	signal.org/assets/images/features/Groups.png	19.1 KiB	10.7 KiB
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`	signal.org/assets/images/features/Stickers.png	16.1 KiB	9.1 KiB
div.container > div.columns > div.column > img `div.container > div.columns > div.column > img`	signal.org/assets/images/features/No-Ads.png	9.2 KiB	7.5 KiB

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

lhId: page-2-IMG

nodeLabel: div.container > div.columns > div.column > img.screenshot2

path: 1,HTML,1,BODY,1,SECTION,0,DIV,0,DIV,0,DIV,1,DIV,1,IMG

selector: div.container > div.columns > div.column > img.screenshot2

snippet: <img class="screenshot2" src="/assets/images/features/signal-pixel.png">

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

value: no origins were preconnected

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
signal.org/assets/stylesheets/vendor/bulma-1.0.4.min.css	63.1 KiB	788 ms
signal.org/assets/stylesheets/ultramarine.css	4.0 KiB	488 ms

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

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: 781 ms

URL	Time Spent
www.signal.org/	781 ms
signal.org/	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: 150 ms 45.1 KiB

URL	Transfer Size	Est Savings
signal.org/assets/stylesheets/vendor/bulma-1.0.4.min.css	62.6 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: 320 ms 75.5 KiB

URL	Transfer Size	Est Savings
signal.org/assets/javascripts/vendor/lottie-player-2.0.3.min.js	94.4 KiB	54.0 KiB
signal.org/assets/javascripts/vendor/jquery-3.7.1.min.js	29.6 KiB	21.6 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

	URL
div.container > div.columns > div.column > img `div.container > div.columns > div.column > img`	signal.org/assets/images/features/No-Ads.png
div.container > div.columns > div.column > img `div.container > div.columns > div.column > img`	signal.org/assets/images/features/Nonprofit503.png
div.container > div.columns > div.column > img.screenshot1 `div.container > div.columns > div.column > img.screenshot1`	signal.org/assets/images/features/signal-iphone.png
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`	signal.org/assets/images/features/Stickers.png
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`	signal.org/assets/images/features/Media.png
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`	signal.org/assets/images/features/Calls.png
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`	signal.org/assets/images/features/Groups.png
div.container > div.navbar-brand > a > img.signal-logo `div.container > div.navbar-brand > a > img.signal-logo`	signal.org/assets/images/header/logo.png

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

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

●JavaScript execution time 0.9 s

●Minimizes main-thread work 2.0 s

●Avoid long main-thread tasks 5 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 30 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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Failing Elements
New Zealand! `div#animation > svg > g > g`
*Ep!z4GoqI `div#animation > svg > g > g`
Whoa where are you!? `div#animation > svg > g > g`
3TF{*2Rhh2!dO:pR^ `div#animation > svg > g > g`
7a#v9^ht035v:q* `div#animation > svg > g > g`
Hey check this out! `div#animation > svg > g > g`

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.

Names and labels

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.

Failing Elements
div.container > div.navbar-brand > a > img.signal-logo `div.container > div.navbar-brand > a > img.signal-logo`
div.container > div.columns > div.column > img.screenshot1 `div.container > div.columns > div.column > img.screenshot1`
div.container > div.columns > div.column > img.screenshot2 `div.container > div.columns > div.column > img.screenshot2`
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`
div.container > div.columns > div.column > img `div.container > div.columns > div.column > img`
div.container > div.columns > div.column > img `div.container > div.columns > div.column > img`

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Failing Elements
nav.navbar > div.container > div.navbar-brand > a `nav.navbar > div.container > div.navbar-brand > a`

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.

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
Donate `div.column > ul > li > a`
Careers `div.column > ul > li > a`
Mac `div.column > ul > li > a`
Linux `div.column > ul > li > a`
Bluesky `div.column > ul > li > a`
GitHub `div.column > ul > li > a`
Instagram `div.column > ul > li > a`
Mastodon `div.column > ul > li > a`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Failing Elements
html `html`

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

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

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

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

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

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

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

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

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○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

○Buttons have an accessible name

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

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

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

○Identical links have the same purpose.

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

100

Best Practices

●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

●Displays images with correct aspect ratio

●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

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

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.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

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.

Failing Elements
div.container > div.navbar-brand > a > img.signal-logo `div.container > div.navbar-brand > a > img.signal-logo`
div.container > div.columns > div.column > img.screenshot1 `div.container > div.columns > div.column > img.screenshot1`
div.container > div.columns > div.column > img.screenshot2 `div.container > div.columns > div.column > img.screenshot2`
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`
div.container > div.columns > div.column > img `div.container > div.columns > div.column > img`
div.container > div.columns > div.column > img `div.container > div.columns > div.column > img`

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Document has a valid `hreflang`

○robots.txt is valid

○Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

100

Best Practices

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.

732 ms

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

1.46 s

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

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

732 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.51 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.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Request	Cache TTL	Transfer Size
signal.org/assets/images/features/signal-iphone.png	14400.0 s	207.3 KiB
signal.org/assets/fonts/inter/Inter-ExtraBold.woff2	14400.0 s	105.6 KiB
signal.org/assets/fonts/inter/Inter-SemiBold.woff2	14400.0 s	105.3 KiB
signal.org/assets/images/features/Calls.png	14400.0 s	105.1 KiB
signal.org/assets/fonts/inter/Inter-Regular.woff2	14400.0 s	98.4 KiB
signal.org/assets/javascripts/vendor/lottie-player-2.0.3.min.js	14400.0 s	94.9 KiB
signal.org/assets/stylesheets/vendor/bulma-1.0.4.min.css	14400.0 s	63.1 KiB
signal.org/assets/images/features/signal-pixel.png	14400.0 s	49.4 KiB
signal.org/assets/images/features/Media.png	14400.0 s	34.0 KiB
signal.org/assets/javascripts/vendor/jquery-3.7.1.min.js	14400.0 s	30.2 KiB
signal.org/assets/images/features/Groups.png	14400.0 s	19.6 KiB
signal.org/assets/images/features/Nonprofit503.png	14400.0 s	19.3 KiB
signal.org/assets/images/features/Stickers.png	14400.0 s	16.7 KiB
signal.org/assets/images/features/No-Ads.png	14400.0 s	9.7 KiB
signal.org/assets/images/header/logo.png	14400.0 s	4.6 KiB
signal.org/assets/stylesheets/ultramarine.css	14400.0 s	4.0 KiB
signal.org/assets/images/icons/solid_globe.svg	14400.0 s	1.1 KiB
signal.org/cdn-cgi/scripts/5c5dd728/cloudflare-static/email-decode.min.js	172800.0 s	835 B

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.container > div.columns > div.column > img.screenshot1 `div.container > div.columns > div.column > img.screenshot1`	signal.org/assets/images/features/signal-iphone.png	206.7 KiB	172.4 KiB
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`	signal.org/assets/images/features/Calls.png	104.5 KiB	82.2 KiB
div.container > div.columns > div.column > img.screenshot2 `div.container > div.columns > div.column > img.screenshot2`	signal.org/assets/images/features/signal-pixel.png	48.8 KiB	36.6 KiB
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`	signal.org/assets/images/features/Media.png	33.5 KiB	25.1 KiB
div.container > div.columns > div.column > img `div.container > div.columns > div.column > img`	signal.org/assets/images/features/Nonprofit503.png	18.8 KiB	15.0 KiB
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`	signal.org/assets/images/features/Groups.png	19.1 KiB	14.3 KiB
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`	signal.org/assets/images/features/Stickers.png	16.1 KiB	12.1 KiB
div.container > div.columns > div.column > img `div.container > div.columns > div.column > img`	signal.org/assets/images/features/No-Ads.png	9.2 KiB	7.3 KiB

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

lhId: page-0-IMG

nodeLabel: div.container > div.columns > div.column > img.screenshot1

path: 1,HTML,1,BODY,1,SECTION,0,DIV,0,DIV,0,DIV,1,DIV,0,IMG

selector: div.container > div.columns > div.column > img.screenshot1

snippet: <img class="screenshot1" src="/assets/images/features/signal-iphone.png">

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

value: no origins were preconnected

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
signal.org/assets/stylesheets/vendor/bulma-1.0.4.min.css	63.1 KiB	185 ms
signal.org/assets/stylesheets/ultramarine.css	4.0 KiB	145 ms

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

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: 40 ms 44.9 KiB

URL	Transfer Size	Est Savings
signal.org/assets/stylesheets/vendor/bulma-1.0.4.min.css	62.6 KiB	44.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: 90 ms 76.0 KiB

URL	Transfer Size	Est Savings
signal.org/assets/javascripts/vendor/lottie-player-2.0.3.min.js	94.4 KiB	54.0 KiB
signal.org/assets/javascripts/vendor/jquery-3.7.1.min.js	29.6 KiB	22.1 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

	URL
div.container > div.columns > div.column > img `div.container > div.columns > div.column > img`	signal.org/assets/images/features/No-Ads.png
div.container > div.columns > div.column > img `div.container > div.columns > div.column > img`	signal.org/assets/images/features/Nonprofit503.png
div.container > div.columns > div.column > img.screenshot1 `div.container > div.columns > div.column > img.screenshot1`	signal.org/assets/images/features/signal-iphone.png
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`	signal.org/assets/images/features/Stickers.png
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`	signal.org/assets/images/features/Media.png
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`	signal.org/assets/images/features/Calls.png
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`	signal.org/assets/images/features/Groups.png
div.container > div.navbar-brand > a > img.signal-logo `div.container > div.navbar-brand > a > img.signal-logo`	signal.org/assets/images/header/logo.png

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: 230 ms

URL	Time Spent
www.signal.org/	230 ms
signal.org/	0.0 ms

●Time to Interactive 1.5 s

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●LCP breakdown

●Modern HTTP

●Optimize viewport for mobile

●Max Potential First Input Delay 60 ms

●Minify CSS

●Minify JavaScript

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

●JavaScript execution time 0.2 s

●Minimizes main-thread work 0.5 s

●Avoid long main-thread tasks 1 long task found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 20 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

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Failing Elements
New Zealand! `div#animation > svg > g > g`
*Ep!z4GoqI `div#animation > svg > g > g`
Whoa where are you!? `div#animation > svg > g > g`
3TF{*2Rhh2!dO:pR^ `div#animation > svg > g > g`
7a#v9^ht035v:q* `div#animation > svg > g > g`
Hey check this out! `div#animation > svg > g > g`

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.

Names and labels

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.

Failing Elements
div.container > div.navbar-brand > a > img.signal-logo `div.container > div.navbar-brand > a > img.signal-logo`
div.container > div.columns > div.column > img.screenshot1 `div.container > div.columns > div.column > img.screenshot1`
div.container > div.columns > div.column > img.screenshot2 `div.container > div.columns > div.column > img.screenshot2`
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`
div.container > div.columns > div.column > img `div.container > div.columns > div.column > img`
div.container > div.columns > div.column > img `div.container > div.columns > div.column > img`

Failing Elements
nav.navbar > div.container > div.navbar-brand > a `nav.navbar > div.container > div.navbar-brand > a`

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.

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
Donate `div.column > ul > li > a`
Careers `div.column > ul > li > a`
Mac `div.column > ul > li > a`
Linux `div.column > ul > li > a`
Bluesky `div.column > ul > li > a`
GitHub `div.column > ul > li > a`
Instagram `div.column > ul > li > a`
Mastodon `div.column > ul > li > a`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Failing Elements
html `html`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Failing Elements
English `div.container > div#signalNavbar > div.navbar-end > a#language-selector`

○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

●`[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

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

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

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

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

○`[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

○Buttons have an accessible name

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

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

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

○Identical links have the same purpose.

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

100

Best Practices

●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

●Displays images with correct aspect ratio

●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

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

SEO

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

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.

Failing Elements
div.container > div.navbar-brand > a > img.signal-logo `div.container > div.navbar-brand > a > img.signal-logo`
div.container > div.columns > div.column > img.screenshot1 `div.container > div.columns > div.column > img.screenshot1`
div.container > div.columns > div.column > img.screenshot2 `div.container > div.columns > div.column > img.screenshot2`
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`
div.columns > div.column > div.box > img `div.columns > div.column > div.box > img`
div.container > div.columns > div.column > img `div.container > div.columns > div.column > img`
div.container > div.columns > div.column > img `div.container > div.columns > div.column > img`

Format your HTML in a way that enables crawlers to better understand your app’s content.

○Structured data is valid

●Page isn’t blocked from indexing

●Document has a `<title>` element

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●Document has a valid `hreflang`

○robots.txt is valid

○Document has a valid `rel=canonical`

Browse & Analyze

Learn

Results for https://www.signal.org

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Names and labels

Best practices

Best Practices

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Names and labels

Best practices

Best Practices

SEO

Content Best Practices

Keyboard Shortcuts