C — https://samaritans.org | BeaverCheck Audit

Site Health

Score: 77 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Mostly accessible, but some users still face barriers.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

Lean and efficient — low environmental impact per visit.

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.

How the composite score is calculated

How you compare

Wagtail · 27 peers

You 77

Avg 76

At average

0 50 100

Better than 40% of Wagtail sites See full Wagtail benchmark →

Awesomplete · 9 peers

You 77

Avg 73

At average

0 50 100

Better than 66% of Awesomplete sites See full Awesomplete benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy

1 control(s) without accessible label

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Form Accessibility

40 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory

Cross-Origin-Embedder-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fsamaritans.org)](https://beavercheck.com/results/212922e3-fedd-4709-b407-1afca6fb866a)

HTML

<a href="https://beavercheck.com/results/212922e3-fedd-4709-b407-1afca6fb866a"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fsamaritans.org" alt="BeaverCheck Score"></a>

Image URL

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

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 9.4s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.

1 accessibility issue excludes users who rely on assistive technology.

Your LCP is 9.4s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

Could reach Estimate based on resolving critical issues

Conversion Barriers

1 critical 5 warning

6 barrier(s) likely increasing bounce by ~24%.

Speed (2)

Page takes 9.4s to load

+12% bounce

Users abandon at ~3s — you're 6.9s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

High main-thread blocking time

+2% bounce

Page is non-interactive for 394ms after first paint

Fix: Defer third-party scripts and split large bundles

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (1)

1 form field(s) without a label

+2% bounce

Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes

Fix: Associate every input with a visible <label for="…">; add autocomplete attributes

Content (1)

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

€425 investment → €4,751/month returns + EUR 120,500,000 risk avoided

Payback period: < 1 month First-year ROI: +13314%

Investment

€425

5h · 5 findings

Monthly returns

€4,751 /mo

~€57,008 / year

Conversions recovered €4,750
Bandwidth savings €0.40

Regulatory risk avoided

EUR 120,500,000

if kept compliant

ePrivacy Directive EUR 100,000,000
GDPR EUR 20,000,000
EAA EUR 500,000

Payback period

0 12mo 24mo

€128 — 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.

Full methodology & sources

Estimated Remediation Cost

€425

5.0 developer hours at €85/hr

Based on European Union rates (€85/hr)

Quick wins

€128 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

€ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€10,041,667 / month at risk

~€120,500,005 / year if left unfixed

Compliance Risk

€120,500,000

ePrivacy DirectiveGDPREAA

No privacy policy link detected
GDPR: EUR 10,000 – EUR 20,000,000
Trackers detected but no cookie policy found
GDPR: EUR 5,000 – EUR 10,000,000
Trackers detected but no cookie policy found
GDPR: EUR 10,000 – EUR 20,000,000

+4 more

Bandwidth Waste

€0.40 /mo

5385.4 MB/mo × 0.074 EUR/GB

Optimize transfer: save ~539 KB per page load
Saves €0.40/mo

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.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Monthly visitors

Unique monthly visitors from your analytics

Conversion rate (%)

Purchases, signups, or key actions

Avg. order value

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue

Current bounce (est.)

After fixes (est.)

Estimated bounce reduction

Fix 3 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

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.

3.09 s

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

9.43 s

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

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

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

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

Why this matters

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

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
/images/grace-anne-story-small-talk-save.2e16d0ba.fill-13...	1800.0 s	227.5 KiB
media.samaritans.org/images/9960_AR.width-1300.jpg	1800.0 s	223.8 KiB
media.samaritans.org/images/Office_420_AR.width-1300.jpg	1800.0 s	114.3 KiB
media.samaritans.org/images/1_UibKksY.2e16d0ba.fill-1100x600.jpg	1800.0 s	67.7 KiB
cdn-apac.onetrust.com/scripttemplates/202401.2.0/otBannerSdk.js	86400.0 s	104.5 KiB
script.platform.veracitytrustnetwork.com/4.13.0/index.js	0.0 ms	41.1 KiB
/images/Heldiney-homepage.2e16d0ba.fill-768x500.jpegquali...	1800.0 s	20.3 KiB
cdn-apac.onetrust.com/logos/static/ot_company_logo.png	86400.0 s	19.2 KiB
cdn-apac.onetrust.com/scripttemplates/otSDKStub.js	86400.0 s	9.1 KiB
script.platform.veracitytrustnetwork.com/loader/index.js	0.0 ms	1.2 KiB
cdn-apac.onetrust.com/logos/static/powered_by_logo.svg	86400.0 s	2.6 KiB

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

Why this matters

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
Grace-Anne Small Talk Saves Lives `div.block-story_highlight > div.simple-media-with-quote > div.simple-media-with-quote__media-wrapper > img`	/images/grace-anne-story-small-talk-save.2e16d0ba.fill-13...	227.0 KiB	170.1 KiB
div.wrapper > section.horizontal-card > div.horizontal-card__inner > div.horizontal-card__image `div.wrapper > section.horizontal-card > div.horizontal-card__inner > div.horizontal-card__image`	media.samaritans.org/images/9960_AR.width-1300.jpg	223.3 KiB	47.5 KiB
1 - Nick - Feb appeal 26 - not cropped `div.wrapper > div.homepage-donate-slider__wrapper > div.homepage-donate-slider__inner > img.homepage-donate-slider__image`	media.samaritans.org/images/1_UibKksY.2e16d0ba.fill-1100x600.jpg	67.3 KiB	47.4 KiB
Heldiney-homepage `main.wrapper > div#homepage > div.donate-landing-hero__image--mobile > img`	/images/Heldiney-homepage.2e16d0ba.fill-768x500.jpegquali...	20.0 KiB	4.0 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-3-IMG

nodeLabel: Heldiney-homepage

path: 1,HTML,1,BODY,5,MAIN,0,DIV,1,DIV,0,IMG

selector: main.wrapper > div#homepage > div.donate-landing-hero__image--mobile > img

snippet: <img src="https://media.samaritans.org/images/Heldiney-homepage.2e16d0ba.fill-768x50…" alt="Heldiney-homepage">

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
cdn-apac.onetrust.com/scripttemplates/otSDKStub.js	9.1 KiB	812 ms
www.samaritans.org/static/css/website.d310d4eaaac5.css	69.0 KiB	1.1 s

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 801 ms

URL	Time Spent
samaritans.org/	801 ms
www.samaritans.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 450 ms 79.8 KiB

URL	Transfer Size	Est Savings
www.samaritans.org/static/css/website.d310d4eaaac5.css	68.5 KiB	63.4 KiB
#onetrust-banner-sdk{-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%} …	19.3 KiB	16.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.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

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

Estimated savings: 1.1 s 289.9 KiB

URL	Transfer Size	Est Savings
www.samaritans.org/static/js/website.051629d080b6.js	241.9 KiB	89.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-PCSWFRF	172.8 KiB	80.1 KiB
www.googletagmanager.com/gtag/js?id=G-YPYKJ55JNV&cx=c&gtm=4e64k1h1	157.0 KiB	65.4 KiB
cdn-apac.onetrust.com/scripttemplates/202401.2.0/otBannerSdk.js	104.3 KiB	54.6 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL
Heldiney-homepage `main.wrapper > div#homepage > div.donate-landing-hero__image--mobile > img`	/images/Heldiney-homepage.2e16d0ba.fill-768x500.jpegquali...

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,753 KiB

●User Timing marks and measures 7 user timings

●JavaScript execution time 1.2 s

●Minimizes main-thread work 1.9 s

●Avoid long main-thread tasks 9 long tasks found

●Page didn't prevent back/forward cache restoration

●Network Requests

●Network Round Trip Times 40 ms

●Server Backend Latencies 60 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

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

○INP breakdown

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

Contrast

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go `div.nation-selector__form > a.button > div.button__inner > span.nation-selector__button-text--mobile`
More about volunteering `div.horizontal-card__container > a.horizontal-card__link > span > span.horizontal-card__link-text`
view other ways to get in touch `div.call-to-action > div.call-to-action__inner > a.button > div.button__inner`

These are opportunities to improve the legibility of your content.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
United Kingdom England Scotland Ireland Northern Ireland Wales `div.nation-selector__form > div.filters > div.filters__filter-wrapper > select.filters__select`

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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Donate today Make today the day you make a gift to Samaritans. Your donation w… `section.section > div.wrapper > div.grid > a.card-new`
Talk to someone Suicidal thoughts can be complex, frightening and confusing. I… `section.section > div.wrapper > div.grid > a.card-new`
What we do We make sure there’s always someone to listen if you’re in crisis o… `section.section > div.wrapper > div.grid > a.card-new`
How the 10 Year Health Plan could support suicide prevention 13th April 2026 `div.wrapper > section.section > div.grid > a.card-new`
Suicide Prevention Consortium: what we learned and what’s next 2nd April 2026 `div.wrapper > section.section > div.grid > a.card-new`
Megan Boxall runs 200 marathons in 200 days for Samaritans 30th March 2026 `div.wrapper > section.section > div.grid > a.card-new`
Suicide facts and figures We're the only organisation collating suicide data f… `div.grid > div.grid__double-width > div.grid > a.card-new`
Samaritans' Media Guidelines Samaritans' Media Guidelines help journalists rep… `div.grid > div.grid__double-width > div.grid > a.card-new`
The internet and suicide The role online content can play in suicide risk and … `div.grid > div.grid__double-width > div.grid > a.card-new`
Our policy and research Our research and policy work drives change that helps … `div.grid > div.grid__double-width > div.grid > a.card-new`
Newsletter Stay on top of our latest news and updates `div.footer__inner > div.footer__nav-container > section.grid > a.footer-cta`

○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

●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

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

●Form elements have associated labels

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

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

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

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

○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

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

○`<object>` elements have alternate text

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

○`[lang]` attributes have a valid value

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

General

Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
www.samaritans.org/static/js/website.051629d080b6.js

●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

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

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

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
www.samaritans.org/privacy-statement/	More information

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

●Document has a meta description

●Page has successful HTTP status code

●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

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.

886 ms

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

2.15 s

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

45 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

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

1.21 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more ▾

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Request	Cache TTL	Transfer Size
/images/grace-anne-story-small-talk-save.2e16d0ba.fill-13...	1800.0 s	227.5 KiB
media.samaritans.org/images/9960_AR.width-1300.jpg	1800.0 s	223.8 KiB
media.samaritans.org/images/Office_420_AR.width-1300.jpg	1800.0 s	114.2 KiB
/images/Heldiney-homepage.2e16d0ba.fill-1900x1250.jpegqua...	1800.0 s	93.8 KiB
media.samaritans.org/images/1_UibKksY.2e16d0ba.fill-1100x600.jpg	1800.0 s	67.7 KiB
cdn-apac.onetrust.com/scripttemplates/202401.2.0/otBannerSdk.js	86400.0 s	104.5 KiB
script.platform.veracitytrustnetwork.com/4.13.0/index.js	0.0 ms	41.1 KiB
/images/Heldiney-homepage.2e16d0ba.fill-768x500.jpegquali...	1800.0 s	20.4 KiB
cdn-apac.onetrust.com/logos/static/ot_company_logo.png	86400.0 s	19.1 KiB
cdn-apac.onetrust.com/scripttemplates/otSDKStub.js	86400.0 s	9.1 KiB
script.platform.veracitytrustnetwork.com/loader/index.js	0.0 ms	1.2 KiB
cdn-apac.onetrust.com/logos/static/powered_by_logo.svg	86400.0 s	2.7 KiB

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

Why this matters

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

	URL	Resource Size	Est Savings
Grace-Anne Small Talk Saves Lives `div.block-story_highlight > div.simple-media-with-quote > div.simple-media-with-quote__media-wrapper > img`	/images/grace-anne-story-small-talk-save.2e16d0ba.fill-13...	227.0 KiB	167.4 KiB
1 - Nick - Feb appeal 26 - not cropped `div.wrapper > div.homepage-donate-slider__wrapper > div.homepage-donate-slider__inner > img.homepage-donate-slider__image`	media.samaritans.org/images/1_UibKksY.2e16d0ba.fill-1100x600.jpg	67.3 KiB	50.3 KiB
div.wrapper > section.horizontal-card > div.horizontal-card__inner > div.horizontal-card__image `div.wrapper > section.horizontal-card > div.horizontal-card__inner > div.horizontal-card__image`	media.samaritans.org/images/9960_AR.width-1300.jpg	223.3 KiB	47.5 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-3-DIV

nodeLabel: body.template-home-page > main.wrapper > div#homepage > div.donate-landing-hero__image--desktop

path: 1,HTML,1,BODY,5,MAIN,0,DIV,0,DIV

selector: body.template-home-page > main.wrapper > div#homepage > div.donate-landing-hero__image--desktop

snippet: <div class="donate-landing-hero__image--desktop" style="background-image: url("https://media.samaritans.org/images/Heldiney-homepag…");">

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
cdn-apac.onetrust.com/scripttemplates/otSDKStub.js	9.1 KiB	262 ms
www.samaritans.org/static/css/website.d310d4eaaac5.css	68.7 KiB	160 ms

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 180 ms 76.6 KiB

URL	Transfer Size	Est Savings
www.samaritans.org/static/css/website.d310d4eaaac5.css	68.5 KiB	60.1 KiB
#onetrust-banner-sdk{-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%} …	19.3 KiB	16.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.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more ▾

Source: Google web.dev / Lighthouse

Estimated savings: 310 ms 289.3 KiB

URL	Transfer Size	Est Savings
www.samaritans.org/static/js/website.051629d080b6.js	241.9 KiB	89.8 KiB
www.googletagmanager.com/gtm.js?id=GTM-PCSWFRF	172.4 KiB	79.8 KiB
www.googletagmanager.com/gtag/js?id=G-YPYKJ55JNV&cx=c&gtm=4e64m0h2	156.4 KiB	65.1 KiB
cdn-apac.onetrust.com/scripttemplates/202401.2.0/otBannerSdk.js	104.3 KiB	54.6 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 249 ms

URL	Time Spent
samaritans.org/	249 ms
www.samaritans.org/	0.0 ms

●Time to Interactive 2.2 s

●Max Potential First Input Delay 100 ms

●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,847 KiB

●User Timing marks and measures 7 user timings

●JavaScript execution time 0.3 s

●Minimizes main-thread work 0.6 s

●Avoid long main-thread tasks 1 long task 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 120 ms

○INP breakdown

○Avoid non-composited animations

○Avoid large layout shifts

Accessibility

Contrast

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Continue `div.nation-selector__form > a.button > div.button__inner > span.nation-selector__button-text--desktop`
view other ways to get in touch `div.call-to-action > div.call-to-action__inner > a.button > div.button__inner`

These are opportunities to improve the legibility of your content.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
United Kingdom England Scotland Ireland Northern Ireland Wales `div.nation-selector__form > div.filters > div.filters__filter-wrapper > select.filters__select`

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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Donate today Make today the day you make a gift to Samaritans. Your donation w… `section.section > div.wrapper > div.grid > a.card-new`
Talk to someone Suicidal thoughts can be complex, frightening and confusing. I… `section.section > div.wrapper > div.grid > a.card-new`
What we do We make sure there’s always someone to listen if you’re in crisis o… `section.section > div.wrapper > div.grid > a.card-new`
How the 10 Year Health Plan could support suicide prevention 13th April 2026 `div.wrapper > section.section > div.grid > a.card-new`
Suicide Prevention Consortium: what we learned and what’s next 2nd April 2026 `div.wrapper > section.section > div.grid > a.card-new`
Megan Boxall runs 200 marathons in 200 days for Samaritans 30th March 2026 `div.wrapper > section.section > div.grid > a.card-new`
Suicide facts and figures We're the only organisation collating suicide data f… `div.grid > div.grid__double-width > div.grid > a.card-new`
Samaritans' Media Guidelines Samaritans' Media Guidelines help journalists rep… `div.grid > div.grid__double-width > div.grid > a.card-new`
The internet and suicide The role online content can play in suicide risk and … `div.grid > div.grid__double-width > div.grid > a.card-new`
Our policy and research Our research and policy work drives change that helps … `div.grid > div.grid__double-width > div.grid > a.card-new`
Newsletter Stay on top of our latest news and updates `div.footer__inner > div.footer__nav-container > section.grid > a.footer-cta`

○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

●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

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

●Form elements have associated labels

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

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

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

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

○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

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

○`<object>` elements have alternate text

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

○`[lang]` attributes have a valid value

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

General

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
www.samaritans.org/static/js/website.051629d080b6.js

●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

●Mitigate DOM-based XSS with Trusted Types

●Detected JavaScript libraries

○Redirects HTTP traffic to HTTPS

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

SEO

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destination	Link Text
www.samaritans.org/privacy-statement/	More information

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

●Document has a meta description

●Page has successful HTTP status code

●Links are crawlable

●robots.txt is valid

●Image elements have `[alt]` attributes

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Results for https://samaritans.org

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Speed (2)

Trust (2)

Usability (1)

Content (1)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Payback period

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Names and labels

Best Practices

General

SEO

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Contrast

Names and labels

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts