Brazil · Sao Paulo Completed: Apr 22, 2026 20:37 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 76 / 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.
Good server performance with room for optimization.
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.
'unsafe-eval' found in script source
Security gaps expose your site and users to attacks, eroding trust.
'unsafe-inline' found in script source
Security gaps expose your site and users to attacks, eroding trust.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
1 button(s) with no accessible text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
1 control(s) without accessible label
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
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/fcfdf321-5d57-433c-b8f9-f50182bb7d9b)<a href="https://beavercheck.com/results/fcfdf321-5d57-433c-b8f9-f50182bb7d9b"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fsplcenter.org" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fsplcenter.orgThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.
8 barrier(s) likely increasing bounce by ~32%.
Page takes 13.1s to load
+12% bounceUsers abandon at ~3s — you're 10.6s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
Page feels frozen for 782ms
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
No HSTS header
+1% bounceReturning 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% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
Layout shifts during page load
+3% bounceContent movement causes mis-clicks on CTAs and form fields
Fix: Add width/height to images; reserve space for late-loading embeds
1 form field(s) without a label
+2% bounceScreen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes
Fix: Associate every input with a visible <label for="…">; add autocomplete attributes
Content is hard to read
+2% bounceGraduate-level reading difficulty — limits the addressable audience for product or blog pages
Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60
61 broken link(s) on the page
+5% bounceClicks land on 404s — trust drops and the session often ends
Fix: Fix or remove the broken destinations surfaced on the Content tab
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
$450 investment → $2,065/month returns + USD 157,500 risk avoided
$450
4h · 5 findings
$2,065 /mo
~$24,780 / year
USD 157,500
if kept compliant
$150 — 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.
4.5 developer hours at $100/hr
Based on United States rates ($100/hr)
Start here for the best return on investment
$13,126 / month at risk
~$157,507 / year if left unfixed
$157,500
+6 more
$0.57 /mo
7097.2 MB/mo × 0.080 USD/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 5 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.69 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
13.05 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
782 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.122
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
29.72 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.
18.73 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.
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.
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.
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.
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 | |
|---|---|---|---|
Cutout of Lady Justice. A statue of a woman holding scales. div.wp-block-group > div.wp-block-group > figure.wp-block-image > img.wp-post-40526 | /wp-content/uploads/2025/03/web-issues-eliminating-unjust... | 152.3 KiB | 89.1 KiB |
Empowering Voters in the South article.wp-block-post > figure.wp-block-post-featured-image > a > img.attachment-post-thumbnail | www.splcenter.org/wp-content/uploads/2024/05/web-souths-got-now-new-768x384.jpg | 79.5 KiB | 54.3 KiB |
VoteRiders assists voters in obtaining ID, allowing them to register and vote li.wp-block-post > figure.wp-block-post-featured-image > a > img.attachment-post-thumbnail | /wp-content/uploads/2026/04/web-vyv-grantee-hero-craig-wa... | 61.8 KiB | 19.2 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.
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 |
|---|---|---|
| /signals/config/2049310922212412?v=2.9.303&r=stable&domai... | 1200.0 s | 125.3 KiB |
| connect.facebook.net/en_US/fbevents.js | 1200.0 s | 96.6 KiB |
| cdn.attn.tv/tag/4-latest/unified-tag.js?v=4-latest_0948d5cc5c | 300.0 s | 49.8 KiB |
| js.adsrvr.org/up_loader.3.0.0.js | 0.0 ms | 12.3 KiB |
| extend.vimeocdn.com/ga/139967050.js | 86400.0 s | 5.8 KiB |
| cdn.attn.tv/splcenter/dtag.js | 120.0 s | 1.7 KiB |
| js.adsrvr.org/universal_pixel.js | 0.0 ms | 957 B |
| cdn.attn.tv/growth-tag-assets/client-configs/UgJ.js | 0.0 ms | 370 B |
| /tr/?id=2049310922212412&ev=PageView&dl=https%3A%2F%2Fwww... | 0.0 ms | 19 B |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| splcenter.org/ | 954 ms |
| www.splcenter.org/ | 790 ms |
| www.splcenter.org/ | 516 ms |
| www.splcenter.org/ | 490 ms |
| www.splcenter.org/ | 0.0 ms |
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| www.splcenter.org/ | 13.8 s |
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Performance issues directly impact user engagement and conversion rates.
| Element | Layout shift score |
|---|---|
A BEACON OF HOPE FOR 55 YEARS
The Southern Poverty Law Center stands as a be… main#wp--skip-link--target > div.entry-content > header.alignfull > div.alignfull | 0.118 |
Story
VoteRiders assists voters in obtaining ID, allowing them to register and… div.alignfull > div.media-hero__content-wrapper > section.wp-block-group > section.wp-block-group | 0.005 |
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 |
|---|---|---|
| /wp-content/plugins/gravityforms/assets/css/dist/gravity-... | 22.3 KiB | 18.3 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/gtag/js?id=G-KVHVNMW5TE&cx=c>m=4e64k0 | 176.0 KiB | 68.9 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-N35NCMF | 133.6 KiB | 61.7 KiB |
| /signals/config/2049310922212412?v=2.9.303&r=stable&domai... | 125.2 KiB | 35.4 KiB |
| connect.facebook.net/en_US/fbevents.js | 96.5 KiB | 33.8 KiB |
| cdn.attn.tv/tag/4-latest/unified-tag.js?v=4-latest_0948d5cc5c | 49.4 KiB | 30.3 KiB |
| www.splcenter.org/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 | 30.8 KiB | 20.4 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.splcenter.org/ | 1.9 s | 38 ms | 17 ms |
| Unattributable | 999 ms | 211 ms | 0.0 ms |
| www.googletagmanager.com/gtag/js?id=G-KVHVNMW5TE&cx=c>m=4e64k0 | 466 ms | 371 ms | 90 ms |
| /signals/config/2049310922212412?v=2.9.303&r=stable&domai... | 372 ms | 315 ms | 57 ms |
| www.googletagmanager.com/gtm.js?id=GTM-N35NCMF | 344 ms | 276 ms | 56 ms |
| /wp-includes/js/dist/script-modules/interactivity/index.m... | 266 ms | 49 ms | 0.4 ms |
| connect.facebook.net/en_US/fbevents.js | 166 ms | 119 ms | 45 ms |
| www.splcenter.org/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 | 146 ms | 78 ms | 11 ms |
| /wp-content/mu-plugins/splc-plugin/dist/blocks/alert-bar/... | 112 ms | 2.0 ms | 0.1 ms |
| cdn.attn.tv/tag/4-latest/unified-tag.js?v=4-latest_0948d5cc5c | 92 ms | 68 ms | 21 ms |
| /wp-content/mu-plugins/splc-plugin/dist/blocks/site-heade... | 64 ms | 14 ms | 0.1 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 |
|---|---|
| Style & Layout | 1.8 s |
| Script Evaluation | 1.8 s |
| Other | 1.1 s |
| Script Parsing & Compilation | 350 ms |
| Parse HTML & CSS | 181 ms |
| Rendering | 149 ms |
| Garbage Collection | 41 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 | |
|---|---|
SPLC Home div.wp-block-group > figure.wp-block-image > a > img | www.splcenter.org/wp-content/themes/splc-theme/patterns/images/svg/splc_logo.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.
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Open Menu div.wp-block-group > div.wp-block-group > div.wp-block-splc-navigation-flyout > button.wp-block-splc-navigation-flyout__trigger |
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Donate
Open submenu
Support Us
Member Center
Friends of the Center
Seen us on T… div.wp-block-group > div.wp-block-group > nav.wp-block-splc-navigation > ul.wp-block-splc-navigation__list |
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Donate li.is-style-button > div.splc-navigation-megamenu__item-wrap > a.wp-block-navigation-item > span.wp-block-navigation-item__label |
These are opportunities to improve the legibility of your content.
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 |
|---|
VoteRiders assists voters in obtaining ID, allowing them to register and vote div.wp-block-query > ul.columns-3 > li.wp-block-post > h3.wp-block-post-title |
These are opportunities to improve keyboard navigation in your application.
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.wp-block-group > div.wp-block-group > p.wp-block-paragraph > a#https://www.splcenter.org/beacon-hope-55-years/ div.wp-block-group > div.wp-block-group > p.wp-block-paragraph > a#https://www.splcenter.org/beacon-hope-55-years/ |
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.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Donate
Open submenu
Support Us
Member Center
Friends of the Center
Seen us on T… div.wp-block-group > nav.wp-block-splc-navigation > ul.wp-block-splc-navigation__list > li.is-style-button |
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Performance issues directly impact user engagement and conversion rates.
| Insecure URL | Request Resolution |
|---|---|
| www.splcenter.org/ | Allowed |
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| AttributionReporting | connect.facebook.net/en_US/fbevents.js line 279, col 769 |
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.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Performance issues directly impact user engagement and conversion rates.
| Link destination | Link Text |
|---|---|
| /presscenter/save-act-fails-millions-of-voters-retain-rig... | Learn More |
Format your HTML in a way that enables crawlers to better understand your app’s content.
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.21 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.09 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
92 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.034
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.21 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
3.01 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.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
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.
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 | |
|---|---|---|---|
Empowering Voters in the South article.wp-block-post > figure.wp-block-post-featured-image > a > img.attachment-post-thumbnail | www.splcenter.org/wp-content/uploads/2024/05/web-souths-got-now-new-1536x768.jpg | 260.9 KiB | 239.8 KiB |
Cutout of Lady Justice. A statue of a woman holding scales. div.wp-block-group > div.wp-block-group > figure.wp-block-image > img.wp-post-40526 | /wp-content/uploads/2025/03/web-issues-eliminating-unjust... | 152.3 KiB | 136.3 KiB |
div#racial-justicedrives-democracy > div.alignwide > div.geo-focus__image > img.attachment-full div#racial-justicedrives-democracy > div.alignwide > div.geo-focus__image > img.attachment-full | /wp-content/uploads/2025/02/web-outcry-rally-homepage-153... | 200.0 KiB | 56.3 KiB |
VoteRiders assists voters in obtaining ID, allowing them to register and vote li.wp-block-post > figure.wp-block-post-featured-image > a > img.attachment-post-thumbnail | /wp-content/uploads/2026/04/web-vyv-grantee-hero-craig-wa... | 61.8 KiB | 46.2 KiB |
Unwanted: A lawsuit and the resurgent hateful language of ‘conversion therapy’ li.wp-block-post > figure.wp-block-post-featured-image > a > img.attachment-post-thumbnail | /wp-content/uploads/2026/04/022626-web-hatewatch-unwanted... | 46.1 KiB | 30.5 KiB |
April 2026 Intelligence Project Dispatch: Trends and incidents of the hard right li.wp-block-post > figure.wp-block-post-featured-image > a > img.attachment-post-thumbnail | /wp-content/uploads/2026/04/040926-web-ip-monthly-memo-he... | 42.4 KiB | 26.9 KiB |
Hate Map article.wp-block-post > figure.wp-block-post-featured-image > a > img.attachment-post-thumbnail | www.splcenter.org/wp-content/uploads/2025/01/web-hate-map-model-768x480.jpg | 43.0 KiB | 26.0 KiB |
Illustration of Confederate battle flag infilled with scenes of protest and mon… div.entry-content > div#racial-justicedrives-democracy > figure.wp-block-media-text__media > img.wp-post-40526 | /wp-content/uploads/2021/08/web-whose-heritage-4thedition... | 53.7 KiB | 19.9 KiB |
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.
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 |
|---|---|---|
| /signals/config/2049310922212412?v=2.9.303&r=stable&domai... | 1200.0 s | 125.3 KiB |
| connect.facebook.net/en_US/fbevents.js | 1200.0 s | 96.6 KiB |
| cdn.attn.tv/tag/4-latest/unified-tag.js?v=4-latest_0948d5cc5c | 300.0 s | 49.8 KiB |
| js.adsrvr.org/up_loader.3.0.0.js | 0.0 ms | 12.3 KiB |
| extend.vimeocdn.com/ga/139967050.js | 86400.0 s | 5.8 KiB |
| cdn.attn.tv/splcenter/dtag.js | 120.0 s | 1.7 KiB |
| js.adsrvr.org/universal_pixel.js | 0.0 ms | 957 B |
| cdn.attn.tv/growth-tag-assets/client-configs/UgJ.js | 0.0 ms | 370 B |
| /tr/?id=2049310922212412&ev=PageView&dl=https%3A%2F%2Fwww... | 0.0 ms | 16 B |
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.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| splcenter.org/ | 404 ms |
| www.splcenter.org/ | 253 ms |
| www.splcenter.org/ | 0.0 ms |
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
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 |
|---|---|---|
| /wp-content/plugins/gravityforms/assets/css/dist/gravity-... | 22.3 KiB | 18.3 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/gtag/js?id=G-KVHVNMW5TE&cx=c>m=4e64k0 | 176.0 KiB | 69.0 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-N35NCMF | 133.6 KiB | 61.7 KiB |
| /signals/config/2049310922212412?v=2.9.303&r=stable&domai... | 125.2 KiB | 34.6 KiB |
| connect.facebook.net/en_US/fbevents.js | 96.5 KiB | 33.8 KiB |
| cdn.attn.tv/tag/4-latest/unified-tag.js?v=4-latest_0948d5cc5c | 49.4 KiB | 30.3 KiB |
| www.splcenter.org/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 | 30.8 KiB | 20.4 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
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 | |
|---|---|
SPLC Home div.wp-block-group > figure.wp-block-image > a > img | www.splcenter.org/wp-content/themes/splc-theme/patterns/images/svg/splc_logo.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.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Press Center
Donate
Open submenu
Support Us
Member Center
Friends of the Center… div.wp-block-group > div.wp-block-group > nav.wp-block-splc-navigation > ul.wp-block-splc-navigation__list |
Racial Justice Issues
Open submenu
Strengthening Democracy & Voting Rights
Dism… div.wp-block-group > div.wp-block-splc-navigation-portal > nav.wp-block-splc-navigation--main > ul.wp-block-splc-navigation__list |
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Open Menu div.wp-block-group > div.wp-block-group > div.wp-block-splc-navigation-flyout > button.wp-block-splc-navigation-flyout__trigger |
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Donate li.is-style-button > div.splc-navigation-megamenu__item-wrap > a.wp-block-navigation-item > span.wp-block-navigation-item__label |
These are opportunities to improve the legibility of your content.
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 |
|---|
VoteRiders assists voters in obtaining ID, allowing them to register and vote div.wp-block-query > ul.columns-3 > li.wp-block-post > h3.wp-block-post-title |
These are opportunities to improve keyboard navigation in your application.
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.wp-block-group > div.wp-block-group > p.wp-block-paragraph > a#https://www.splcenter.org/beacon-hope-55-years/ div.wp-block-group > div.wp-block-group > p.wp-block-paragraph > a#https://www.splcenter.org/beacon-hope-55-years/ |
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.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Press Center div.wp-block-group > nav.wp-block-splc-navigation > ul.wp-block-splc-navigation__list > li.wp-block-navigation-item |
Donate
Open submenu
Support Us
Member Center
Friends of the Center
Seen us on T… div.wp-block-group > nav.wp-block-splc-navigation > ul.wp-block-splc-navigation__list > li.is-style-button |
Racial Justice Issues
Open submenu
Strengthening Democracy & Voting Rights
Dism… div.wp-block-splc-navigation-portal > nav.wp-block-splc-navigation--main > ul.wp-block-splc-navigation__list > li.wp-block-splc-navigation-megamenu |
Find Resources
Open submenu
Elevating Hope
Hopewatch
Civil Rights Memorial Cent… div.wp-block-splc-navigation-portal > nav.wp-block-splc-navigation--main > ul.wp-block-splc-navigation__list > li.wp-block-splc-navigation-megamenu |
State Support
Open submenu
Alabama
Florida
Georgia
Louisiana
Mississippi div.wp-block-splc-navigation-portal > nav.wp-block-splc-navigation--main > ul.wp-block-splc-navigation__list > li.is-style-dropdown |
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 |
|---|
Open submenu ul.wp-block-splc-navigation__list > li.wp-block-splc-navigation-megamenu > div.splc-navigation-megamenu__item-wrap > button.wp-block-splc-navigation-megamenu__icon |
Open submenu ul.wp-block-splc-navigation__list > li.wp-block-splc-navigation-megamenu > div.splc-navigation-megamenu__item-wrap > button.wp-block-splc-navigation-megamenu__icon |
Open submenu ul.wp-block-splc-navigation__list > li.is-style-dropdown > div.splc-navigation-megamenu__item-wrap > button.wp-block-splc-navigation-megamenu__icon |
These items highlight common accessibility best practices.
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Performance issues directly impact user engagement and conversion rates.
| Insecure URL | Request Resolution |
|---|---|
| www.splcenter.org/ | Allowed |
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| AttributionReporting | connect.facebook.net/en_US/fbevents.js line 279, col 769 |
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.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Performance issues directly impact user engagement and conversion rates.
| Link destination | Link Text |
|---|---|
| /presscenter/save-act-fails-millions-of-voters-retain-rig... | Learn More |
Format your HTML in a way that enables crawlers to better understand your app’s content.
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.
Performance issues directly impact user engagement and conversion rates.
To appear in search results, crawlers need access to your app.
Send Feedback