Skip to content
Audit Complete

Results for https://www.wwf.org.uk

Visit site
GB · GBP (£) · Estimated Applicable regulations: UK GDPR · PECR · Equality Act 2010 Dev cost: £75/hr How jurisdiction is detected
Brazil Brazil · Sao Paulo Completed: Apr 14, 2026 12:19 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C78

Site Health

Score: 78 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

Reasonable footprint with room for optimization.

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

Drupal sites average 75
At average
Better than 76% of Drupal sites See full Drupal benchmark →
AOS sites average 75
At average
Better than 85% of AOS sites See full AOS benchmark →

Top Priorities (5)

1

1 link(s) with no accessible text

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

Accessibility › Link & Button Quality
2

2 control(s) without accessible label

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

Accessibility › Form Accessibility
3

67 third-party resources (67% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory
4

Cross-Origin-Embedder-Policy header is missing

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

Security › Security Headers
5

Cross-Origin-Opener-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

Quick Wins

2

High impact, low effort — start here.

Strategic

3

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.wwf.org.uk)](https://beavercheck.com/results/79e835de-2a84-4e38-a751-559414d75197)
<a href="https://beavercheck.com/results/79e835de-2a84-4e38-a751-559414d75197"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.wwf.org.uk" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.wwf.org.uk

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 15.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 audience reach.

2 accessibility issues exclude users who rely on assistive technology.
Your LCP is 15.4s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.
2 security gaps detected — browsers may warn visitors about your site.

Return on Investment

£450 investment → £0.42/month returns + GBP 18,050,000 risk avoided

Payback period: > 2 years First-year ROI: -99%

Investment

£450

6h · 5 findings

Monthly returns

£0.42 /mo

~£5.04 / year

  • Bandwidth savings £0.42

Regulatory risk avoided

GBP 18,050,000

if kept compliant

  • UK GDPR GBP 17,500,000
  • PECR GBP 500,000
  • Equality Act 2010 GBP 50,000

£75 — 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

£450

6.0 developer hours at £75/hr

Based on United Kingdom rates (£75/hr)

Quick wins
£75 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
£ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

£1,504,167 / month at risk

~£18,050,005 / year if left unfixed

Compliance Risk

£18,050,000

UK GDPRPECREquality Act 2010
  • No privacy policy link detected
    UK GDPR: GBP 10,000 – GBP 17,500,000
  • Trackers detected but no cookie policy found
    UK GDPR: GBP 10,000 – GBP 17,500,000
  • Trackers detected but no cookie policy found
    PECR: GBP 1,000 – GBP 500,000

+6 more

Bandwidth Waste

£0.42 /mo

6665.3 MB/mo × 0.063 GBP/GB

  • Optimize transfer: save ~667 KB per page load
    Saves £0.42/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

Unique monthly visitors from your analytics

Purchases, signups, or key actions

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

Global Performance 6/6 locations
BR Sao Paulo
Full audit
350ms
DNS 20ms · TLS 109ms
US Santa Clara
18ms
DNS 9ms · TLS 4ms
ES Madrid
98ms
DNS 28ms · TLS 24ms
NL Amsterdam
36ms
DNS 9ms · TLS 11ms
UN New York
259ms
DNS 236ms · TLS 9ms
SG Singapore
703ms
DNS 6ms · TLS 3ms
CDN: Sucuri (HIT) · Avg TTFB: 244ms · Cache: max-age=31536000

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

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

40
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
92
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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.

6.14 s

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

15.43 s

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

728 ms

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

0.011

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

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

15.49 s

Detailed Report

Audit breakdown by category with detailed findings.

40

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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:0.507 source:map[column:197 line:984 type:source-location url:https://www.googletagmanager.com/gtm.js?id=GTM-MBP22M urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:83.623 source:map[type:text value:[unattributed]]] map[reflowTime:0.507 source:map[column:55 line:981 type:source-location url:https://www.googletagmanager.com/gtm.js?id=GTM-MBP22M urlProvider:network]]]

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.

URLResource SizeEst Savings
Pangaia div.grid > div#product-1 > a.media-block__inner > img.media-block__image
/sites/default/files/styles/landscape_m/public/2026-02/IM...156.3 KiB129.3 KiB
Feel good forest trail div#feel-good-forest-trail > div.media-block__wrapper > a > img.media-block__image
/sites/default/files/styles/links_block_call_to_action/pu...78.6 KiB62.0 KiB
Emperor penguin (Aptenodytes forsteri)  adult and chicks walking, Antarctica. div.grid > div.split-hero-content > picture.banner--image > img
/sites/default/files/styles/ar_16x9_1024px/public/2025-11...37.8 KiB31.6 KiB
Gifts for her div.grid > div#product-2 > a.media-block__inner > img.media-block__image
/sites/default/files/styles/landscape_m/public/2026-02/Ti...58.0 KiB31.0 KiB
Best sellers div.grid > div#product-3 > a.media-block__inner > img.media-block__image
/sites/default/files/styles/landscape_m/public/2026-02/Or...55.4 KiB28.5 KiB
How you're helping div#how-youre-helping > div.media-block__wrapper > a > img.media-block__image
/sites/default/files/styles/links_block_call_to_action_me...22.5 KiB6.5 KiB
WWF logo main#about-wwf > div.grid > div.paragraph > img
/sites/default/files/styles/square_200x200/public/2025-03...6.6 KiB5.6 KiB

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:346.7060001220703 label:Time to first byte subpart:timeToFirstByte] map[duration:93.14799987792969 label:Resource load delay subpart:resourceLoadDelay] map[duration:649.678 label:Resource load duration subpart:resourceLoadDuration] map[duration:1430.108 label:Element render delay subpart:elementRenderDelay]]
lhId: page-2-IMG
nodeLabel: Emperor penguin (Aptenodytes forsteri)  adult and chicks walking, Antarctica.
path: 4,HTML,2,BODY,2,DIV,1,MAIN,0,DIV,1,DIV,0,ARTICLE,0,DIV,0,SECTION,0,DIV,1,DIV,0,PICTURE,0,IMG
selector: div.grid > div.split-hero-content > picture.banner--image > img
snippet: <img loading="eager" srcset="/sites/default/files/styles/ar_16x9_640px/public/2025-11/_WW1446916%20%281…" sizes="(min-width:1500px) 940px, (min-width:1024px) 63vw, 100vw" width="640" height="360" src="https://www.wwf.org.uk/sites/default/files/styles/ar_16x9_1024px/public/20…" alt="Emperor penguin (Aptenodytes forsteri) &nbsp;adult and chicks walking, Antarcti…">

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-2-IMG
nodeLabel: Emperor penguin (Aptenodytes forsteri)  adult and chicks walking, Antarctica.
path: 4,HTML,2,BODY,2,DIV,1,MAIN,0,DIV,1,DIV,0,ARTICLE,0,DIV,0,SECTION,0,DIV,1,DIV,0,PICTURE,0,IMG
selector: div.grid > div.split-hero-content > picture.banner--image > img
snippet: <img loading="eager" srcset="/sites/default/files/styles/ar_16x9_640px/public/2025-11/_WW1446916%20%281…" sizes="(min-width:1500px) 940px, (min-width:1024px) 63vw, 100vw" width="640" height="360" src="https://www.wwf.org.uk/sites/default/files/styles/ar_16x9_1024px/public/20…" alt="Emperor penguin (Aptenodytes forsteri) &nbsp;adult and chicks walking, Antarcti…">

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

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

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

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.

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

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation1.4 s
Other827 ms
Style & Layout612 ms
Script Parsing & Compilation262 ms
Parse HTML & CSS147 ms
Rendering72 ms
Garbage Collection39 ms

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
WWF Panda Logo div.header_main > div.content > a.logo_panda_planet > img.panda_logo
www.wwf.org.uk/sites/default/files/wwf-logo.svg
WWF Panda Logo div.footer_bottom_bar > div.content > div.copyright > img.logo
www.wwf.org.uk/themes/custom/wwf/img/wwf-logo.svg
Registered with Fundraising Regulator div.social > div.footer_bottom_bar > div.content > img.fundraising_icon
www.wwf.org.uk/themes/custom/wwf/img/FR_Fundraising-Badge_Primary_Black.svg

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

Layout shift culprits
Document request latency
Optimize DOM size
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 2,170 KiB
Avoid long main-thread tasks 13 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 110 ms
Server Backend Latencies 440 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 120 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
User Timing marks and measures
Avoid non-composited animations
92

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.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section#podcast > div.article_wrapper > div#embed-omny__199441 > iframe section#podcast > div.article_wrapper > div#embed-omny__199441 > iframe

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
PAGINATION div.kitchen_sink > div.resource_pagination > nav.pager > h4#pagination-heading
JOIN THE RACE TO SAVE OUR WORLD div.footer_full_row > nav.footer_nav > div.newsletter > h5

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 Current page Page 2 Page 3 Page 4 … Next page Last page Last div.kitchen_sink > div.resource_pagination > nav.pager > ul.js-pager__items

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
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
`[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
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 have a discernible name
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.
`[lang]` attributes have a valid value
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
`<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
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
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.
96

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
TypeError: Cannot read properties of null (reading 'classList') at https://www.wwf.org.uk/themes/custom/wwf/js/build/hotjar_polyfil.js?v=10.6.5:1:94 at NodeList.forEach (<anonymous>) at https://www.wwf.org.uk/themes/custom/wwf/js/build/hotjar_polyfil.js?v=10.6.5:1:53
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 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 DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
92

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.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
header.site_header > div.header_top_bar > div.content > a.search header.site_header > div.header_top_bar > div.content > a.search
nav#block-fundraisingheader > div.menu_fundraising_items > div.menu_fundraising_1 > a.icon-search--wrap

To appear in search results, crawlers need access to your app.

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

86
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
89
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

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.

1.46 s

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

1.50 s

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

47 ms

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

0.073

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

2.06 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.86 s

Detailed Report

Audit breakdown by category with detailed findings.

86

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:28.077 source:map[column:152063 line:1 type:source-location url:https://try.abtasty.com/f994040e22ec159cbb7f07c33f704fc0/main.baef0936fa8495327986.js urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:90.193 source:map[type:text value:[unattributed]]] map[reflowTime:0.154 source:map[column:85575 line:2 type:source-location url:https://www.wwf.org.uk/sites/default/files/js/js_MO8NeVflXPapiwcOgOwSh8acD9s7ClYvmJ-JYBD4-cc.js?scope=footer&delta=0&language=en&theme=wwf&include=eJx1UdFuwyAM_CEWPslyiEPdAmaYJM3fz2Fap1Xai43vLPmOQ1XqwOVOoUvzd51ukqliJOiHQJAEFRvGhvXmZuqdGtCzitICKycb1ePWBXSbM_f_ViIVapj-oxOXh8KmBHjHpwsPWtjkQCOtUpR3U4NzIv8OwMJaE55uxc-VKS3-5zFhCNIWluJi4njrszw9F5P4Gs22HSb_DrgoEtN1Ifpo5X2ehsg_YHY706F-1G9-PCFs2iXDKi1jH15nWmH4dcex-qFVp9Hst-vZLi2DiklmTB_aT1uPA3pFMZnNgey8kPxGBDtnkosBFEtGxpVLJGQslmrz1tLZOegXtZfI1g urlProvider:network]] map[reflowTime:27.77 source:map[column:86232 line:0 type:source-location url:https://try.abtasty.com/f994040e22ec159cbb7f07c33f704fc0/main.baef0936fa8495327986.js urlProvider:network]] map[reflowTime:0.307 source:map[column:87529 line:0 type:source-location url:https://try.abtasty.com/f994040e22ec159cbb7f07c33f704fc0/main.baef0936fa8495327986.js urlProvider:network]] map[reflowTime:5.614 source:map[column:13668 line:1 type:source-location url:https://www.wwf.org.uk/sites/default/files/js/js_EgpACPuV00EXVaoIheeQwUlmeoMJCfcl0TKEfXSrOn4.js?scope=footer&delta=9&language=en&theme=wwf&include=eJx1UdFuwyAM_CEWPslyiEPdAmaYJM3fz2Fap1Xai43vLPmOQ1XqwOVOoUvzd51ukqliJOiHQJAEFRvGhvXmZuqdGtCzitICKycb1ePWBXSbM_f_ViIVapj-oxOXh8KmBHjHpwsPWtjkQCOtUpR3U4NzIv8OwMJaE55uxc-VKS3-5zFhCNIWluJi4njrszw9F5P4Gs22HSb_DrgoEtN1Ifpo5X2ehsg_YHY706F-1G9-PCFs2iXDKi1jH15nWmH4dcex-qFVp9Hst-vZLi2DiklmTB_aT1uPA3pFMZnNgey8kPxGBDtnkosBFEtGxpVLJGQslmrz1tLZOegXtZfI1g urlProvider:network]]]

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-0-IMG
nodeLabel: Emperor penguin (Aptenodytes forsteri)  adult and chicks walking, Antarctica.
path: 4,HTML,2,BODY,2,DIV,1,MAIN,0,DIV,1,DIV,0,ARTICLE,0,DIV,0,SECTION,0,DIV,1,DIV,0,PICTURE,0,IMG
selector: div.grid > div.split-hero-content > picture.banner--image > img
snippet: <img loading="eager" srcset="/sites/default/files/styles/ar_16x9_640px/public/2025-11/_WW1446916%20%281…" sizes="(min-width:1500px) 940px, (min-width:1024px) 63vw, 100vw" width="640" height="360" src="https://www.wwf.org.uk/sites/default/files/styles/ar_16x9_1024px/public/20…" alt="Emperor penguin (Aptenodytes forsteri) &nbsp;adult and chicks walking, Antarcti…">

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

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.

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.

URLResource SizeEst Savings
Pangaia div.grid > div#product-1 > a.media-block__inner > img.media-block__image
/sites/default/files/styles/landscape_m/public/2026-02/IM...156.3 KiB112.7 KiB
Feel good forest trail div#feel-good-forest-trail > div.media-block__wrapper > a > img.media-block__image
/sites/default/files/styles/links_block_call_to_action/pu...78.6 KiB48.4 KiB
Gifts for her div.grid > div#product-2 > a.media-block__inner > img.media-block__image
/sites/default/files/styles/landscape_m/public/2026-02/Ti...58.0 KiB16.9 KiB
Best sellers div.grid > div#product-3 > a.media-block__inner > img.media-block__image
/sites/default/files/styles/landscape_m/public/2026-02/Or...55.4 KiB14.4 KiB
Go Wild div.node__content > section#go-wild-banner > div.image > img
/sites/default/files/styles/ar_3x1_1024px/public/2025-07/...56.6 KiB12.9 KiB
How you're helping div#how-youre-helping > div.media-block__wrapper > a > img.media-block__image
/sites/default/files/styles/links_block_call_to_action_me...22.5 KiB5.9 KiB
WWF logo main#about-wwf > div.grid > div.paragraph > img
/sites/default/files/styles/thumbnail/public/2025-03/old_...6.6 KiB5.6 KiB

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

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

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.

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

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
WWF Panda Logo div.header_main > div.content > a.logo_panda_planet > img.panda_logo
www.wwf.org.uk/sites/default/files/wwf-logo.svg
WWF Panda Logo div.footer_bottom_bar > div.content > div.copyright > img.logo
www.wwf.org.uk/themes/custom/wwf/img/wwf-logo.svg
Registered with Fundraising Regulator div.social > div.footer_bottom_bar > div.content > img.fundraising_icon
www.wwf.org.uk/themes/custom/wwf/img/FR_Fundraising-Badge_Primary_Black.svg

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

Layout shift culprits
Document request latency
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 2,227 KiB
JavaScript execution time 0.5 s
Minimizes main-thread work 1.0 s
Avoid long main-thread tasks 2 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 110 ms
Server Backend Latencies 440 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 120 ms
Avoid large layout shifts 3 layout shifts found
INP breakdown
User Timing marks and measures
Avoid non-composited animations
89

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.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section#podcast > div.article_wrapper > div#embed-omny__199441 > iframe section#podcast > div.article_wrapper > div#embed-omny__199441 > iframe

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
PAGINATION div.kitchen_sink > div.resource_pagination > nav.pager > h4#pagination-heading
JOIN THE RACE TO SAVE OUR WORLD div.footer_full_row > nav.footer_nav > div.newsletter > h5

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 Current page Page 2 Page 3 Page 4 … Next page Last page Last div.kitchen_sink > div.resource_pagination > nav.pager > ul.js-pager__items

These are opportunities to improve the experience of reading tabular or list data using 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
follow us on Facebook div.social > div > div.social_icons > a.facebook

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
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
`[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
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 have a discernible name
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
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
`<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
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
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.
96

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
TypeError: Cannot read properties of null (reading 'classList') at https://www.wwf.org.uk/themes/custom/wwf/js/build/hotjar_polyfil.js?v=10.6.5:1:94 at NodeList.forEach (<anonymous>) at https://www.wwf.org.uk/themes/custom/wwf/js/build/hotjar_polyfil.js?v=10.6.5:1:53
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 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 DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
92

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.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
search … header.site_header > div.header_top_bar > div.content > a.search
nav#block-fundraisingheader > div.menu_fundraising_items > div.menu_fundraising_1 > a.icon-search--wrap nav#block-fundraisingheader > div.menu_fundraising_items > div.menu_fundraising_1 > a.icon-search--wrap

To appear in search results, crawlers need access to your app.

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
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback