Skip to content
Audit Complete

Results for https://rotary.org

Visit site
Netherlands Netherlands · Amsterdam Completed: Apr 22, 2026 22:48 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)
C75

Site Health

Score: 75 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

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.

Strong compliance posture across regulations.

Good content signals with minor gaps.

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

Drupal · 362 peers
You 75
·
Avg 73
At average
0 50 100
Better than 62% of Drupal sites See full Drupal benchmark →
Apple · 1227 peers
You 75
·
Avg 72
At average
0 50 100
Better than 70% of Apple sites See full Apple benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

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

Security › Security Headers
2

HSTS header is missing

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

Security › Security Headers
3

No Content-Security-Policy header found

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

Security › Content Security Policy
4

5 image(s) missing alt attribute

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

Accessibility › Alt Text Quality
5

81 third-party resources (100% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

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%2Frotary.org)](https://beavercheck.com/results/69220367-8d6b-4e86-9a91-b48e16cb46c4)
<a href="https://beavercheck.com/results/69220367-8d6b-4e86-9a91-b48e16cb46c4"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Frotary.org" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Frotary.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 15.9s 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 15.9s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.

Conversion Barriers

2 critical 4 warning

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

Speed (2)

Page takes 15.9s to load

+12% bounce

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

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

Page feels frozen for 1.1s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

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

Content (2)

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, …)

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

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

Return on Investment

€425 investment → €0.48/month returns + EUR 20,500,000 risk avoided

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

Investment

€425

5h · 5 findings

Monthly returns

€0.48 /mo

~€5.73 / year

  • Bandwidth savings €0.48

Regulatory risk avoided

EUR 20,500,000

if kept compliant

  • GDPR EUR 20,000,000
  • EAA EUR 500,000

€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
/hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

€1,708,334 / month at risk

~€20,500,006 / year if left unfixed

Compliance Risk

€20,500,000

GDPREAA
  • 3 advertising/retargeting trackers detected
    GDPR: EUR 10,000 – EUR 20,000,000
  • Heading level skipped: H2 → H5 (missing H3)
    EAA: EUR 1,000 – EUR 500,000
  • Heading level skipped: H2 → H4 (missing H3)
    EAA: EUR 1,000 – EUR 500,000

+4 more

Bandwidth Waste

€0.48 /mo

6443.8 MB/mo × 0.074 EUR/GB

  • Optimize transfer: save ~644 KB per page load
    Saves €0.48/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 4 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...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

33
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
88
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
83
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.

7.50 s

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

15.87 s

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

1.13 s

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

0.087

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

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

16.11 s

Detailed Report

Audit breakdown by category with detailed findings.

33

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.

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.

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.

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:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:23.176 source:map[column:7 line:7291 type:source-location url:https://www.rotary.org/sites/default/files/js/js_h8htwjSoeI8cOWsuImUVRqoCXJJgtd6WjIpBsHOWjl8.js urlProvider:network]] map[reflowTime:69.405 source:map[column:35 line:7279 type:source-location url:https://www.rotary.org/sites/default/files/js/js_h8htwjSoeI8cOWsuImUVRqoCXJJgtd6WjIpBsHOWjl8.js urlProvider:network]] map[reflowTime:85.97 source:map[column:40 line:7386 type:source-location url:https://www.rotary.org/sites/default/files/js/js_h8htwjSoeI8cOWsuImUVRqoCXJJgtd6WjIpBsHOWjl8.js urlProvider:network]] map[reflowTime:0.842 source:map[column:7 line:6828 type:source-location url:https://www.rotary.org/sites/default/files/js/js_h8htwjSoeI8cOWsuImUVRqoCXJJgtd6WjIpBsHOWjl8.js urlProvider:network]] map[reflowTime:1.004 source:map[column:32 line:6819 type:source-location url:https://www.rotary.org/sites/default/files/js/js_h8htwjSoeI8cOWsuImUVRqoCXJJgtd6WjIpBsHOWjl8.js urlProvider:network]] map[reflowTime:2.048 source:map[column:21 line:285 type:source-location url:https://www.rotary.org/sites/default/files/js/js_h8htwjSoeI8cOWsuImUVRqoCXJJgtd6WjIpBsHOWjl8.js urlProvider:network]] map[reflowTime:0.86 source:map[column:21 line:4551 type:source-location url:https://www.rotary.org/sites/default/files/js/js_h8htwjSoeI8cOWsuImUVRqoCXJJgtd6WjIpBsHOWjl8.js 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-SPAN
nodeLabel: main#main > div.hero-type > div.hero-type-image > span#hero_type_css_69e94cd6c2550
path: 1,HTML,1,BODY,1,DIV,5,MAIN,2,DIV,0,DIV,0,SPAN
selector: main#main > div.hero-type > div.hero-type-image > span#hero_type_css_69e94cd6c2550
snippet: <span id="hero_type_css_69e94cd6c2550" class="hero-type-background" style="height: 352px;">

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

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
ul.home-causes-list > li#cause--6 > a.causes-link > span.home-causes-image ul.home-causes-list > li#cause--6 > a.causes-link > span.home-causes-image
/sites/default/files/styles/w_700/public/home-areas-of-fo...103.0 KiB23.2 KiB
div.u-container > div.hero-mosaic > article.hero-mosaic-item > span#field-right-top-feature_css_69e94cd6d8157 div.u-container > div.hero-mosaic > article.hero-mosaic-item > span#field-right-top-feature_css_69e94cd6d8157
/sites/default/files/styles/w_1200/public/2026-04-POA-Mex...73.7 KiB17.9 KiB
$2.9 BILLION ul.carousel-list > li.carousel-item > div.carousel-item-inner > h3.carousel-item-heading
www.rotary.org/sites/all/themes/rotary_rotaryorg/images/geo-green.png11.7 KiB7.7 KiB
$273 MILLION ul.carousel-list > li.carousel-item > div.carousel-item-inner > h3.carousel-item-heading
www.rotary.org/sites/all/themes/rotary_rotaryorg/images/geo-red.png10.9 KiB7.0 KiB
1.2 MILLION ul.carousel-list > li.carousel-item > div.carousel-item-inner > h3.carousel-item-heading
www.rotary.org/sites/all/themes/rotary_rotaryorg/images/geo-blue.png10.5 KiB6.6 KiB
ul.home-causes-list > li#cause--3 > a.causes-link > span.home-causes-image ul.home-causes-list > li#cause--3 > a.causes-link > span.home-causes-image
/sites/default/files/styles/w_700/public/home-areas-of-fo...85.0 KiB5.2 KiB
No challenge is too big for us For more than a century, we’ve bridged cultures … main#main > div#node-12023 > div.content > div.layout-container
www.rotary.org/sites/all/themes/rotary_rotaryorg/images/geo-darkblue.png8.3 KiB4.4 KiB

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.6 s
URLTime Spent
rotary.org/786 ms
www.rotary.org/768 ms
www.rotary.org/en0.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

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 310 ms 55.5 KiB

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: 240 ms 34.9 KiB
URLTransfer SizeEst Savings
/sites/default/files/css/css_rY0PMHOi_NMXJe4rk5ZCRsPotilI...39.7 KiB34.9 KiB

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

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 Evaluation2.5 s
Other1.0 s
Style & Layout1.0 s
Script Parsing & Compilation438 ms
Parse HTML & CSS107 ms
Rendering92 ms
Garbage Collection23 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.

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

Layout shift culprits
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Avoids enormous network payloads Total size was 2,098 KiB
User Timing marks and measures 7 user timings
Avoid long main-thread tasks 19 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 20 ms
Server Backend Latencies 190 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 100 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
Avoid non-composited animations
88

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
This website uses cookies. By continuing you are agreeing to our privacy policy. body.html > div.header-message-wrapper > div#cookie-message > p
privacy policy div.header-message-wrapper > div#cookie-message > p > a
CLOSE body.html > div.header-message-wrapper > div#cookie-message > button#cookie_close
MAIN MENU div > header.site-header > div.site-header-container > button.site-nav-toggle-mobile
SEARCH header.site-header > div.site-header-container > form > button.site-nav-toggle-search
EXPLORE MORE NEWS AND FEATURES section.news-features > div.news-features-container > div.field-formation-wrapper > a.u-button
EXPLORE div.carousel-item-inner > div.carousel-item-text > p > a
EXPLORE div.carousel-item-inner > div.carousel-item-text > p > a
EXPLORE div.carousel-item-inner > div.carousel-item-text > p > a
Solving some of the world’s most complex and pressing problems takes real commi… div.callout-section-left-content > div.callout-section-left-content-holder > div.callout-section-description > p
GET INVOLVED div.callout-section-left-content > div.callout-section-left-content-holder > p.u-text-centered > a.u-button

These are opportunities to improve the legibility of your content.

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
div.hero-mosaic > article.hero-mosaic-item > a > h5.support-link div.hero-mosaic > article.hero-mosaic-item > a > h5.support-link
Read more div.hero-mosaic > article.hero-mosaic-item > a > h4.support-link
Read more div.hero-mosaic > article.hero-mosaic-item > a > h4.support-link
Read more div.hero-mosaic > article.hero-mosaic-item > a > h4.support-link

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
li.carousel-item > div.carousel-item-inner > div.carousel-item-image > img.lazyload li.carousel-item > div.carousel-item-inner > div.carousel-item-image > img.lazyload
li.carousel-item > div.carousel-item-inner > div.carousel-item-image > img.lazyload li.carousel-item > div.carousel-item-inner > div.carousel-item-image > img.lazyload
li.carousel-item > div.carousel-item-inner > div.carousel-item-image > img.lazyload li.carousel-item > div.carousel-item-inner > div.carousel-item-image > img.lazyload

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.

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>`
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
`[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 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.
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Document has a main landmark.
All heading elements contain content.
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
`[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
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[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>`.
Uses ARIA roles only on compatible elements
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.
77

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
AttributionReporting

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
www.rotary.org/en line 14, col 8753
TypeError: Cannot read properties of null (reading 'dataset') at HTMLDocument.<anonymous> (https://www.rotary.org/sites/default/files/js/js_Ao0IwcE1jaJDqa6c6HqiVMTK223Vbt61ttHfldU_Dcc.js:386:15) at o (https://www.rotary.org/sites/default/files/js/js_DXn09oioKYn0nboQmlGhl3Fg6EnZd3ZetSGATk9UMio.js:2:14734) at Object.fireWith (https://www.rotary.org/sites/default/files/js/js_DXn09oioKYn0nboQmlGhl3Fg6EnZd3ZetSGATk9UMio.js:2:15503) at e.ready (https://www.rotary.org/sites/default/files/js/js_DXn09oioKYn0nboQmlGhl3Fg6EnZd3ZetSGATk9UMio.js:2:9594) at HTMLDocument.B (https://www.rotary.org/sites/default/files/js/js_DXn09oioKYn0nboQmlGhl3Fg6EnZd3ZetSGATk9UMio.js:2:14291) at HTMLDocument.nrWrapper (https://www.rotary.org/en:15:8712)
Uses HTTPS
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
83

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
li.carousel-item > div.carousel-item-inner > div.carousel-item-image > img.lazyload li.carousel-item > div.carousel-item-inner > div.carousel-item-image > img.lazyload
li.carousel-item > div.carousel-item-inner > div.carousel-item-image > img.lazyload li.carousel-item > div.carousel-item-inner > div.carousel-item-image > img.lazyload
li.carousel-item > div.carousel-item-inner > div.carousel-item-image > img.lazyload li.carousel-item > div.carousel-item-inner > div.carousel-item-image > img.lazyload

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

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

82
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
88
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
83
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.

983 ms

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

2.01 s

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

149 ms

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

0.041

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

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

3.13 s

Detailed Report

Audit breakdown by category with detailed findings.

82

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.

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.

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.

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:31.956 source:map[column:27 line:4304 type:source-location url:https://www.rotary.org/sites/default/files/js/js_h8htwjSoeI8cOWsuImUVRqoCXJJgtd6WjIpBsHOWjl8.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:23.668 source:map[column:7 line:7291 type:source-location url:https://www.rotary.org/sites/default/files/js/js_h8htwjSoeI8cOWsuImUVRqoCXJJgtd6WjIpBsHOWjl8.js urlProvider:network]] map[reflowTime:59.688 source:map[column:35 line:7279 type:source-location url:https://www.rotary.org/sites/default/files/js/js_h8htwjSoeI8cOWsuImUVRqoCXJJgtd6WjIpBsHOWjl8.js urlProvider:network]] map[reflowTime:114.555 source:map[column:40 line:7386 type:source-location url:https://www.rotary.org/sites/default/files/js/js_h8htwjSoeI8cOWsuImUVRqoCXJJgtd6WjIpBsHOWjl8.js urlProvider:network]] map[reflowTime:0.868 source:map[column:7 line:6828 type:source-location url:https://www.rotary.org/sites/default/files/js/js_h8htwjSoeI8cOWsuImUVRqoCXJJgtd6WjIpBsHOWjl8.js urlProvider:network]] map[reflowTime:4.173 source:map[column:32 line:6819 type:source-location url:https://www.rotary.org/sites/default/files/js/js_h8htwjSoeI8cOWsuImUVRqoCXJJgtd6WjIpBsHOWjl8.js urlProvider:network]] map[reflowTime:3.003 source:map[column:21 line:285 type:source-location url:https://www.rotary.org/sites/default/files/js/js_h8htwjSoeI8cOWsuImUVRqoCXJJgtd6WjIpBsHOWjl8.js urlProvider:network]] map[reflowTime:39.814 source:map[column:21 line:4551 type:source-location url:https://www.rotary.org/sites/default/files/js/js_h8htwjSoeI8cOWsuImUVRqoCXJJgtd6WjIpBsHOWjl8.js urlProvider:network]] map[reflowTime:1.944 source:map[column:15 line:2094 type:source-location url:https://www.rotary.org/sites/default/files/js/js_h8htwjSoeI8cOWsuImUVRqoCXJJgtd6WjIpBsHOWjl8.js urlProvider:network]] map[reflowTime:13.99 source:map[column:19879 line:1 type:source-location url:https://www.rotary.org/sites/default/files/js/js_DXn09oioKYn0nboQmlGhl3Fg6EnZd3ZetSGATk9UMio.js urlProvider:network]] map[reflowTime:0.476 source:map[column:19976 line:1 type:source-location url:https://www.rotary.org/sites/default/files/js/js_DXn09oioKYn0nboQmlGhl3Fg6EnZd3ZetSGATk9UMio.js urlProvider:network]] map[reflowTime:0.155 source:map[column:20211 line:1 type:source-location url:https://www.rotary.org/sites/default/files/js/js_DXn09oioKYn0nboQmlGhl3Fg6EnZd3ZetSGATk9UMio.js urlProvider:network]] map[reflowTime:0.419 source:map[column:20432 line:1 type:source-location url:https://www.rotary.org/sites/default/files/js/js_DXn09oioKYn0nboQmlGhl3Fg6EnZd3ZetSGATk9UMio.js urlProvider:network]] map[reflowTime:0.387 source:map[column:20565 line:1 type:source-location url:https://www.rotary.org/sites/default/files/js/js_DXn09oioKYn0nboQmlGhl3Fg6EnZd3ZetSGATk9UMio.js urlProvider:network]] map[reflowTime:0.562 source:map[column:20706 line:1 type:source-location url:https://www.rotary.org/sites/default/files/js/js_DXn09oioKYn0nboQmlGhl3Fg6EnZd3ZetSGATk9UMio.js urlProvider:network]] map[reflowTime:0.273 source:map[column:20829 line:1 type:source-location url:https://www.rotary.org/sites/default/files/js/js_DXn09oioKYn0nboQmlGhl3Fg6EnZd3ZetSGATk9UMio.js urlProvider:network]] map[reflowTime:0.4 source:map[column:20989 line:1 type:source-location url:https://www.rotary.org/sites/default/files/js/js_DXn09oioKYn0nboQmlGhl3Fg6EnZd3ZetSGATk9UMio.js urlProvider:network]] map[reflowTime:0.168 source:map[column:21157 line:1 type:source-location url:https://www.rotary.org/sites/default/files/js/js_DXn09oioKYn0nboQmlGhl3Fg6EnZd3ZetSGATk9UMio.js urlProvider:network]] map[reflowTime:11.814 source:map[column:41 line:1051 type:source-location url:https://www.rotary.org/sites/default/files/js/js_DXn09oioKYn0nboQmlGhl3Fg6EnZd3ZetSGATk9UMio.js urlProvider:network]] map[reflowTime:12.347 source:map[type:text value:[unattributed]]] map[reflowTime:0.326 source:map[column:29203 line:3 type:source-location url:https://www.rotary.org/sites/default/files/js/js_DXn09oioKYn0nboQmlGhl3Fg6EnZd3ZetSGATk9UMio.js urlProvider:network]] map[reflowTime:0.532 source:map[column:53 line:5014 type:source-location url:https://www.rotary.org/sites/default/files/js/js_h8htwjSoeI8cOWsuImUVRqoCXJJgtd6WjIpBsHOWjl8.js 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
div.aof > div#cause--6 > a.causes-link > span.home-causes-image div.aof > div#cause--6 > a.causes-link > span.home-causes-image
/sites/default/files/styles/w_700/public/home-areas-of-fo...103.0 KiB23.2 KiB
div.u-container > div.hero-mosaic > article.hero-mosaic-item > span#field-right-top-feature_css_69e94cd6d8157 div.u-container > div.hero-mosaic > article.hero-mosaic-item > span#field-right-top-feature_css_69e94cd6d8157
/sites/default/files/styles/w_1200/public/2026-04-POA-Mex...73.7 KiB17.9 KiB
$2.9 BILLION ul.carousel-list > li.carousel-item > div.carousel-item-inner > h3.carousel-item-heading
www.rotary.org/sites/all/themes/rotary_rotaryorg/images/geo-green.png11.7 KiB7.7 KiB
$273 MILLION ul.carousel-list > li.carousel-item > div.carousel-item-inner > h3.carousel-item-heading
www.rotary.org/sites/all/themes/rotary_rotaryorg/images/geo-red.png10.9 KiB7.0 KiB
1.2 MILLION ul.carousel-list > li.carousel-item > div.carousel-item-inner > h3.carousel-item-heading
www.rotary.org/sites/all/themes/rotary_rotaryorg/images/geo-blue.png10.5 KiB6.6 KiB
li.carousel-item > div.carousel-item-inner > div.carousel-item-image > img.lazyautosizes li.carousel-item > div.carousel-item-inner > div.carousel-item-image > img.lazyautosizes
/sites/default/files/styles/w_350/public/home-carousel-po...25.5 KiB5.6 KiB
div.aof > div#cause--3 > a.causes-link > span.home-causes-image div.aof > div#cause--3 > a.causes-link > span.home-causes-image
/sites/default/files/styles/w_700/public/home-areas-of-fo...85.0 KiB5.2 KiB
No challenge is too big for us For more than a century, we’ve bridged cultures … main#main > div#node-12023 > div.content > div.layout-container
www.rotary.org/sites/all/themes/rotary_rotaryorg/images/geo-darkblue.png8.3 KiB4.4 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-8-SPAN
nodeLabel: main#main > div.hero-type > div.hero-type-image > span#hero_type_css_69e94cd6c2550
path: 1,HTML,1,BODY,1,DIV,5,MAIN,2,DIV,1,DIV,0,SPAN
selector: main#main > div.hero-type > div.hero-type-image > span#hero_type_css_69e94cd6c2550
snippet: <span id="hero_type_css_69e94cd6c2550" class="hero-type-background" style="height: 590.625px;">

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

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: 450 ms
URLTime Spent
rotary.org/239 ms
www.rotary.org/212 ms
www.rotary.org/en0.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

Diagnostics

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 40 ms 55.5 KiB

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: 40 ms 31.8 KiB
URLTransfer SizeEst Savings
/sites/default/files/css/css_rY0PMHOi_NMXJe4rk5ZCRsPotilI...39.7 KiB31.8 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

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 Evaluation818 ms
Other567 ms
Style & Layout434 ms
Script Parsing & Compilation121 ms
Rendering67 ms
Parse HTML & CSS29 ms
Garbage Collection20 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page was evicted from back/forward cache because an active network request involved a redirect.Not actionable

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.

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

Max Potential First Input Delay 120 ms
Layout shift culprits
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
User Timing marks and measures 9 user timings
JavaScript execution time 0.8 s
Avoid long main-thread tasks 10 long tasks found
Avoid non-composited animations 3 animated elements found
Network Requests
Network Round Trip Times 30 ms
Server Backend Latencies 190 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 0 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
88

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
This website uses cookies. By continuing you are agreeing to our privacy policy. body.html > div.header-message-wrapper > div#cookie-message > p
privacy policy div.header-message-wrapper > div#cookie-message > p > a
CLOSE body.html > div.header-message-wrapper > div#cookie-message > button#cookie_close
MY ROTARY div.site-nav-utility-container > ul.site-nav-utility-links > li > a
CLUB FINDER div.site-nav-utility-container > ul.site-nav-utility-links > li > a
SEARCH ul.site-nav-utility-links > li > form > button.site-nav-toggle-search-desktop
JOIN A CLUB div.site-nav-utility-container > ul.site-nav-utility-ctas > li > a.u-button
DONATE div.site-nav-utility-container > ul.site-nav-utility-ctas > li > a.u-button
EXPLORE MORE NEWS AND FEATURES section.news-features > div.news-features-container > div.field-formation-wrapper > a.u-button
EXPLORE div.carousel-item-inner > div.carousel-item-text > p > a

These are opportunities to improve the legibility of your content.

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
div.hero-mosaic > article.hero-mosaic-item > a > h5.support-link div.hero-mosaic > article.hero-mosaic-item > a > h5.support-link
Read more div.hero-mosaic > article.hero-mosaic-item > a > h4.support-link
Read more div.hero-mosaic > article.hero-mosaic-item > a > h4.support-link
Read more div.hero-mosaic > article.hero-mosaic-item > a > h4.support-link

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
li.carousel-item > div.carousel-item-inner > div.carousel-item-image > img.lazyautosizes li.carousel-item > div.carousel-item-inner > div.carousel-item-image > img.lazyautosizes

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.

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>`
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
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.
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Document has a main landmark.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
All heading elements contain content.
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Deprecated ARIA roles were not used
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
`[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
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
Tables have different content in the summary attribute and `<caption>`.
Uses ARIA roles only on compatible elements
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.
77

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
AttributionReporting

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
www.rotary.org/en line 14, col 8753
TypeError: Cannot read properties of null (reading 'dataset') at HTMLDocument.<anonymous> (https://www.rotary.org/sites/default/files/js/js_Ao0IwcE1jaJDqa6c6HqiVMTK223Vbt61ttHfldU_Dcc.js:386:15) at o (https://www.rotary.org/sites/default/files/js/js_DXn09oioKYn0nboQmlGhl3Fg6EnZd3ZetSGATk9UMio.js:2:14734) at Object.fireWith (https://www.rotary.org/sites/default/files/js/js_DXn09oioKYn0nboQmlGhl3Fg6EnZd3ZetSGATk9UMio.js:2:15503) at e.ready (https://www.rotary.org/sites/default/files/js/js_DXn09oioKYn0nboQmlGhl3Fg6EnZd3ZetSGATk9UMio.js:2:9594) at HTMLDocument.B (https://www.rotary.org/sites/default/files/js/js_DXn09oioKYn0nboQmlGhl3Fg6EnZd3ZetSGATk9UMio.js:2:14291) at HTMLDocument.nrWrapper (https://www.rotary.org/en:15:8712)
Uses HTTPS
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
83

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
li.carousel-item > div.carousel-item-inner > div.carousel-item-image > img.lazyautosizes li.carousel-item > div.carousel-item-inner > div.carousel-item-image > img.lazyautosizes

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

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback