Mobile 375 × 812

Desktop 1440 × 900

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.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
1 link(s) with no accessible text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
2 control(s) without accessible label
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
67 third-party resources (67% of weight)
Performance issues directly impact user engagement and conversion rates.
Cross-Origin-Embedder-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
Cross-Origin-Opener-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/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.ukThis badge auto-updates with your latest scan result.
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.
£450 investment → £0.42/month returns + GBP 18,050,000 risk avoided
£450
6h · 5 findings
£0.42 /mo
~£5.04 / year
GBP 18,050,000
if kept compliant
£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.
6.0 developer hours at £75/hr
Based on United Kingdom rates (£75/hr)
Start here for the best return on investment
£1,504,167 / month at risk
~£18,050,005 / year if left unfixed
£18,050,000
+6 more
£0.42 /mo
6665.3 MB/mo × 0.063 GBP/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 2 critical issues to capture this value
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
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
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
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| cdn-ukwest.onetrust.com/scripttemplates/202404.1.0/otBannerSdk.js | 86400.0 s | 108.8 KiB |
| player.vimeo.com/api/player.js | 1800.0 s | 9.0 KiB |
| try.abtasty.com/f994040e22ec159cbb7f07c33f704fc0.js | 30.0 s | 3.6 KiB |
| cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js | 86400.0 s | 7.6 KiB |
| cdn-ukwest.onetrust.com/logos/static/ot_company_logo.png | 86400.0 s | 4.1 KiB |
| cdn-ukwest.onetrust.com/logos/static/powered_by_logo.svg | 86400.0 s | 2.1 KiB |
| cdn-ukwest.onetrust.com/logos/static/ot_close.svg | 86400.0 s | 621 B |
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
Performance issues directly impact user engagement and conversion rates.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
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 KiB | 129.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 KiB | 62.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 KiB | 31.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 KiB | 31.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 KiB | 28.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 KiB | 6.5 KiB |
WWF logo main#about-wwf > div.grid > div.paragraph > img | /sites/default/files/styles/square_200x200/public/2025-03... | 6.6 KiB | 5.6 KiB |
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Performance issues directly impact user engagement and conversion rates.
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Performance issues directly impact user engagement and conversion rates.
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /sites/default/files/css/css_nTpT-tfhW5OLN8igY9IoqJbj9LTT... | 34.2 KiB | 31.3 KiB |
| #onetrust-banner-sdk{-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%} … | 21.1 KiB | 18.2 KiB |
| cdnjs.cloudflare.com/ajax/libs/font-awesome/6.7.2/css/all.min.css | 17.8 KiB | 17.5 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.googletagmanager.com/gtm.js?id=GTM-MBP22M | 192.5 KiB | 75.3 KiB |
| cdn-ukwest.onetrust.com/scripttemplates/202404.1.0/otBannerSdk.js | 108.6 KiB | 57.5 KiB |
| /sites/default/files/js/js_MO8NeVflXPapiwcOgOwSh8acD9s7Cl... | 81.3 KiB | 52.6 KiB |
| try.abtasty.com/f994040e22ec159cbb7f07c33f704fc0/main.baef0936fa8495327986.js | 54.6 KiB | 28.9 KiB |
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Performance issues directly impact user engagement and conversion rates.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| www.wwf.org.uk/ | 860 ms | 9.2 ms | 0.6 ms |
| Unattributable | 716 ms | 181 ms | 0.0 ms |
| www.googletagmanager.com/gtm.js?id=GTM-MBP22M | 683 ms | 547 ms | 98 ms |
| try.abtasty.com/f994040e22ec159cbb7f07c33f704fc0/main.baef0936fa8495327986.js | 359 ms | 252 ms | 29 ms |
| cdn-ukwest.onetrust.com/scripttemplates/202404.1.0/otBannerSdk.js | 355 ms | 199 ms | 66 ms |
| /sites/default/files/js/js_MO8NeVflXPapiwcOgOwSh8acD9s7Cl... | 195 ms | 139 ms | 35 ms |
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 1.4 s |
| Other | 827 ms |
| Style & Layout | 612 ms |
| Script Parsing & Compilation | 262 ms |
| Parse HTML & CSS | 147 ms |
| Rendering | 72 ms |
| Garbage Collection | 39 ms |
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
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.
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.
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
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.
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.
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.
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
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.
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
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 |
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.
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
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.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
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
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.
Performance issues directly impact user engagement and conversion rates.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| cdn-ukwest.onetrust.com/scripttemplates/202404.1.0/otBannerSdk.js | 86400.0 s | 108.8 KiB |
| player.vimeo.com/api/player.js | 1800.0 s | 9.0 KiB |
| try.abtasty.com/f994040e22ec159cbb7f07c33f704fc0.js | 30.0 s | 3.6 KiB |
| cdn-ukwest.onetrust.com/scripttemplates/otSDKStub.js | 86400.0 s | 7.6 KiB |
| cdn-ukwest.onetrust.com/logos/static/ot_company_logo.png | 86400.0 s | 4.1 KiB |
| cdn-ukwest.onetrust.com/logos/static/powered_by_logo.svg | 86400.0 s | 2.1 KiB |
| cdn-ukwest.onetrust.com/logos/static/ot_close.svg | 86400.0 s | 612 B |
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
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 KiB | 112.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 KiB | 48.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 KiB | 16.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 KiB | 14.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 KiB | 12.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 KiB | 5.9 KiB |
WWF logo main#about-wwf > div.grid > div.paragraph > img | /sites/default/files/styles/thumbnail/public/2025-03/old_... | 6.6 KiB | 5.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.
Performance issues directly impact user engagement and conversion rates.
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Performance issues directly impact user engagement and conversion rates.
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /sites/default/files/css/css_nTpT-tfhW5OLN8igY9IoqJbj9LTT... | 34.2 KiB | 30.7 KiB |
| #onetrust-banner-sdk{-ms-text-size-adjust:100%;-webkit-text-size-adjust:100%} … | 21.1 KiB | 18.1 KiB |
| cdnjs.cloudflare.com/ajax/libs/font-awesome/6.7.2/css/all.min.css | 17.8 KiB | 17.5 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| www.googletagmanager.com/gtm.js?id=GTM-MBP22M | 192.5 KiB | 75.3 KiB |
| cdn-ukwest.onetrust.com/scripttemplates/202404.1.0/otBannerSdk.js | 108.6 KiB | 57.5 KiB |
| /sites/default/files/js/js_MO8NeVflXPapiwcOgOwSh8acD9s7Cl... | 81.3 KiB | 52.6 KiB |
| try.abtasty.com/f994040e22ec159cbb7f07c33f704fc0/main.baef0936fa8495327986.js | 54.7 KiB | 28.9 KiB |
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
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.
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.
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
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.
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.
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.
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
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.
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.
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.
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
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
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 |
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.
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
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.
Send Feedback