Skip to content
Audit Complete

Results for https://epi.org

Visit site
Singapore Singapore · Singapore Completed: Apr 22, 2026 21:03 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)
C71

Site Health

Score: 71 / 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.

Solid SEO basics — a few optimizations could boost rankings.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

Reasonable footprint with room for optimization.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

WordPress · 625 peers
You 71
·
Avg 74
At average
0 50 100
Better than 11% of WordPress sites See full WordPress benchmark →
Google Search Console · 3223 peers
You 71
·
Avg 73
At average
0 50 100
Better than 22% of Google Search Console sites See full Google Search Console 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

Page weighs 8.4 MB (4.4 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
5

No <main> landmark found

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

Accessibility › Landmark Structure
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%2Fepi.org)](https://beavercheck.com/results/2bc62efb-cebf-4748-b3d7-b43b4f107625)
<a href="https://beavercheck.com/results/2bc62efb-cebf-4748-b3d7-b43b4f107625"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fepi.org" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fepi.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 27.8s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. 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.

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

Conversion Barriers

2 critical 7 warning

9 barrier(s) likely increasing bounce by ~32%.

Speed (2)

Page takes 27.8s to load

+12% bounce

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

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

Page feels frozen for 1.5s

+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

Usability (1)

Layout shifts during page load

+3% bounce

Content movement causes mis-clicks on CTAs and form fields

Fix: Add width/height to images; reserve space for late-loading embeds

Content (3)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

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

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Navigation (1)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

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

Return on Investment

$500 investment → $1.11/month returns + USD 157,500 risk avoided

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

Investment

$500

5h · 5 findings

Monthly returns

$1.11 /mo

~$13 / year

  • Bandwidth savings $1.11

Regulatory risk avoided

USD 157,500

if kept compliant

  • ADA Title III USD 150,000
  • CCPA/CPRA USD 7,500

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

Full methodology & sources

Estimated Remediation Cost

$500

5.0 developer hours at $100/hr

Based on United States rates ($100/hr)

Quick wins
$150 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

$13,126 / month at risk

~$157,513 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA
  • No privacy policy link detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no cookie policy found
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no privacy policy found
    CCPA/CPRA: USD 2,500 – USD 7,500

+4 more

Bandwidth Waste

$1.11 /mo

13839.4 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~1.4 MB per page load
    Saves $1.11/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 5 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.

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

9.71 s

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

27.79 s

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

1.48 s

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

0.242

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

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

27.98 s

Detailed Report

Audit breakdown by category with detailed findings.

18

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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.002133] map[node:map[boundingRect:map[bottom:1309 height:33 left:20 right:392 top:1276 width:372] lhId:page-10-DIV nodeLabel:April 15, 2026 By Ismael Cid-Martinez, Nina Mast, Margaret Poydock, and Valerie… path:6,HTML,2,BODY,3,DIV,1,DIV,0,DIV,2,DIV,1,UL,0,LI,1,DIV selector:div#main-left > ul.loop-list > li#post-319535 > div.loop-meta snippet:<div class="loop-meta"> type:node] score:0.002133 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:5660 height:296 left:37 right:333 top:5364 width:296] lhId:page-0-IMG nodeLabel:div#epi-widget-text-19 > div.epi-widget-body > a > img path:6,HTML,2,BODY,3,DIV,1,DIV,2,DIV,6,DIV,0,DIV,0,A,0,IMG selector:div#epi-widget-text-19 > div.epi-widget-body > a > img snippet:<img src="https://files.epi.org/uploads/Data-Lib-Award-Winning.png"> type:node]]] type:subitems]]]
headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.242078] map[node:map[boundingRect:map[bottom:1999 height:923 left:0 right:412 top:1077 width:412] lhId:page-11-DIV nodeLabel:Latest Research Misclassifying workers as independent contractors is costly for… path:6,HTML,2,BODY,3,DIV,1,DIV,0,DIV,2,DIV selector:div#wrap > div#main > div#content > div#main-left snippet:<div id="main-left"> type:node] score:0.242078]]

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.

URLEst Savings
/wp-content/themes/epi/dist/fonts/font-awesome/fonts/font...115 ms
/af/d7a560/00000000000000003b9acae1/27/l?primer=7cdcb44be...95 ms
use.typekit.com/af/3a798d/00000000000000000000ec0a/27/l?subset_id=2&fvd=i7&v=390 ms
/af/5bf3eb/00000000000000003b9b0944/27/l?primer=7cdcb44be...85 ms
/af/5b14cd/00000000000000003b9b0945/27/l?primer=7cdcb44be...85 ms
/af/bb2e37/00000000000000003b9b094b/27/l?primer=7cdcb44be...80 ms
/af/976aa6/00000000000000003b9b0943/27/l?primer=7cdcb44be...75 ms
/af/ba66d8/00000000000000003b9b093a/27/l?primer=7cdcb44be...70 ms
/af/3ad9c9/00000000000000003b9b094a/27/l?primer=7cdcb44be...70 ms
/af/1f55cd/00000000000000003b9b0932/27/l?primer=7cdcb44be...65 ms
use.typekit.com/af/f8c331/0000000000000000000100fe/27/l?subset_id=2&fvd=n3&v=360 ms
use.typekit.com/af/810490/000000000000000000010141/27/l?subset_id=2&fvd=i3&v=360 ms
use.typekit.com/af/1b8c3f/000000000000000000011aff/27/l?subset_id=2&fvd=n7&v=360 ms
use.typekit.com/af/1ec8cf/000000000000000000017099/27/l?subset_id=2&fvd=i3&v=355 ms
use.typekit.com/af/f0a7c7/00000000000000000000e807/27/l?subset_id=2&fvd=n9&v=355 ms
/af/1f7f57/00000000000000003b9b093b/27/l?primer=7cdcb44be...50 ms
/af/56978c/00000000000000003b9b0935/27/l?primer=7cdcb44be...45 ms
use.typekit.com/af/55aa58/00000000000000000000e802/27/l?subset_id=2&fvd=i3&v=345 ms
use.typekit.com/af/dc6ba3/00000000000000000000e806/27/l?subset_id=2&fvd=i7&v=345 ms
/af/fce0a9/00000000000000003b9acae2/27/l?primer=7cdcb44be...40 ms
use.typekit.com/af/f6d549/00000000000000000000e7fe/27/l?subset_id=2&fvd=n3&v=340 ms
use.typekit.com/af/c2dac6/00000000000000000000e805/27/l?subset_id=2&fvd=n7&v=340 ms
use.typekit.com/af/fb6723/0000000000000000000170b4/27/l?subset_id=2&fvd=i7&v=335 ms
/af/ae1174/00000000000000003b9acadd/27/l?primer=7cdcb44be...35 ms
/af/a20313/00000000000000003b9acade/27/l?primer=7cdcb44be...35 ms
use.typekit.com/af/8cf19a/00000000000000000001709a/27/l?subset_id=2&fvd=n4&v=330 ms
use.typekit.com/af/c1298f/0000000000000000000170ae/27/l?subset_id=2&fvd=n4&v=325 ms
use.typekit.com/af/a51230/0000000000000000000170b0/27/l?subset_id=2&fvd=i4&v=325 ms
use.typekit.com/af/04a489/00000000000000000001709f/27/l?subset_id=2&fvd=i7&v=325 ms
use.typekit.com/af/bce065/00000000000000000001709b/27/l?subset_id=2&fvd=i4&v=325 ms
use.typekit.com/af/341571/000000000000000000017098/27/l?subset_id=2&fvd=n3&v=325 ms
use.typekit.com/af/69b489/0000000000000000000170b3/27/l?subset_id=2&fvd=n7&v=320 ms
/af/773235/00000000000000003b9b0934/27/l?primer=7cdcb44be...15 ms
use.typekit.com/af/9a5180/00000000000000000001709e/27/l?subset_id=2&fvd=n7&v=315 ms

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:98.437 source:map[type:text value:[unattributed]]]]

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#epi-widget-text-19 > div.epi-widget-body > a > img div#epi-widget-text-19 > div.epi-widget-body > a > img
files.epi.org/uploads/Data-Lib-Award-Winning.png322.9 KiB284.4 KiB
'NO TAX ON TIPS' div#custom_html-7 > div.textwidget > div.faq-buttons > a#notaxtips
files.epi.org/uploads/no-tax-on-tips-button-e1770902303121.png116.2 KiB82.2 KiB
'NO TAX ON OVERTIME' div#custom_html-7 > div.textwidget > div.faq-buttons > a#notaxot
files.epi.org/uploads/notaxonot.png178.8 KiB55.8 KiB
div.narrow > p > a > img div.narrow > p > a > img
files.epi.org/uploads/Four-Star-Rating-Badge-Full-Color-1.webp33.1 KiB33.0 KiB
div.rsSlide > div.rsContent > a > img.rsImg div.rsSlide > div.rsContent > a > img.rsImg
files.epi.org/uploads/shutterstock_2145740941-768x553.jpg80.7 KiB31.0 KiB
div.rsSlide > div.rsContent > a > img.rsImg div.rsSlide > div.rsContent > a > img.rsImg
files.epi.org/uploads/chandler-denise-Lgaw-BnaAAI-unsplash-768x512.jpg60.6 KiB17.1 KiB
div.narrow > p > a > img div.narrow > p > a > img
files.epi.org/uploads/candid-seal-gold-2025.png12.7 KiB12.5 KiB
TARIFFS div#custom_html-7 > div.textwidget > div.faq-buttons > a#tariffs
files.epi.org/uploads/tariffs-faq_red.png17.1 KiB7.4 KiB
SOCIAL SECURITY div#custom_html-7 > div.textwidget > div.faq-buttons > a#social-security
files.epi.org/uploads/social-security-faq_red.png15.0 KiB5.2 KiB
div.rsSlide > div.rsContent > a > img.rsImg div.rsSlide > div.rsContent > a > img.rsImg
files.epi.org/uploads/U.S.-born-unemployment-is-higher-under-Trump.png37.7 KiB4.9 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:392.868 label:Time to first byte subpart:timeToFirstByte] map[duration:24.466 label:Resource load delay subpart:resourceLoadDelay] map[duration:1082.095 label:Resource load duration subpart:resourceLoadDuration] map[duration:2643.582 label:Element render delay subpart:elementRenderDelay]]
lhId: page-5-IMG
nodeLabel: div.rsSlide > div.rsContent > a > img.rsImg
path: 6,HTML,2,BODY,3,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,A,0,IMG
selector: div.rsSlide > div.rsContent > a > img.rsImg
snippet: <img width="600" height="400" src="https://files.epi.org/uploads/chandler-denise-Lgaw-BnaAAI-unsplash-768x512…" class="rsImg rsMainSlideImage" alt="" decoding="async" fetchpriority="high" srcset="https://files.epi.org/uploads/chandler-denise-Lgaw-BnaAAI-unsplash-950x633…" sizes="(max-width: 600px) 100vw, 600px" style="width: 372px; height: 248px; margin-left: 0px; margin-top: -43px;">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer SizeDuration
/wp-content/themes/epi/dist/css/epi-main.css?ver=04bf9473...704.9 KiB6.7 s
use.typekit.com/gfy6bkz.js7.0 KiB153 ms
use.typekit.com/uhs7xha.js7.2 KiB306 ms
use.typekit.com/mez6pee.js6.9 KiB306 ms
www.googleadservices.com/pagead/conversion_async.js22.8 KiB2.2 s
www.epi.org/wp-includes/js/jquery/jquery.min.js?ver=3.7.130.2 KiB1.5 s
www.epi.org/wp-includes/js/dist/vendor/lodash.min.js?ver=4.17.2124.8 KiB1.4 s
www.epi.org/wp-includes/css/dashicons.min.css?ver=176401263235.0 KiB1.8 s
/wp-content/mu-plugins/epi-charts/js/requirejs/vendor/req...20.8 KiB1.1 s
/wp-content/mu-plugins/epi-charts/js/requirejs/epi_main.j...483 B191 ms
/wp-content/mu-plugins/epi-charts/js/requirejs/requirejs-...333 B191 ms
/wp-content/mu-plugins/epi-charts/js/epi/epi.utility.js?v...3.1 KiB342 ms
/wp-content/mu-plugins/epi-charts/js/epi/epi.namespace.js...509 B191 ms
www.epi.org/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.15.0 KiB342 ms
/wp-content/themes/epi/dist/css/font-ss-standard.css?ver=...2.4 KiB191 ms
www.epi.org/wp-content/plugins/add-to-any/addtoany.min.css?ver=1.16800 B191 ms
www.epi.org/wp-content/plugins/wp-pagenavi/pagenavi-css.css?ver=2.70506 B191 ms
/wp-content/mu-plugins/epi-automated-screenshots/dist/css...1.7 KiB191 ms
/wp-content/mu-plugins/epi-modals/dist/css/epi-modals.min...1.1 KiB191 ms
/wp-content/mu-plugins/epi-data-library/dist/css/epi-data...1.9 KiB493 ms
/wp-content/mu-plugins/epi-issue-tags/dist/css/epi-issue-...1.5 KiB191 ms
/wp-content/themes/epi/dist/css/front-page-slider.css?ver...11.2 KiB945 ms
/wp-content/mu-plugins/epi-manage-content/dist/css/epi-ma...1.4 KiB493 ms
/wp-content/mu-plugins/epi-charts/dist/css/epi-charts--ma...14.3 KiB1.1 s
/wp-content/mu-plugins/epi-shortcodes/dist/css/epi-shortc...13.1 KiB1.1 s
/wp-content/mu-plugins/epi-charts/dist/css/epi-charts.min...19.3 KiB1.1 s

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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.7 s
URLTime Spent
epi.org/1.1 s
www.epi.org/630 ms
www.epi.org/0.0 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

ElementLayout shift score
Latest Research Misclassifying workers as independent contractors is costly for… div#wrap > div#main > div#content > div#main-left
0.242
April 15, 2026 By Ismael Cid-Martinez, Nina Mast, Margaret Poydock, and Valerie… div#main-left > ul.loop-list > li#post-319535 > div.loop-meta
0.002

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.

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

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

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation3.1 s
Other1.4 s
Style & Layout805 ms
Script Parsing & Compilation585 ms
Parse HTML & CSS202 ms
Rendering138 ms
Garbage Collection76 ms

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 2.8 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
div.narrow > p > a > img div.narrow > p > a > img
files.epi.org/uploads/Four-Star-Rating-Badge-Full-Color-1.webp
div#epi-widget-text-19 > div.epi-widget-body > a > img div#epi-widget-text-19 > div.epi-widget-body > a > img
files.epi.org/uploads/Data-Lib-Award-Winning.png
div.narrow > p > a > img div.narrow > p > a > img
files.epi.org/uploads/candid-seal-gold-2025.png

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

Optimize DOM size
LCP request discovery
Modern HTTP
Optimize viewport for mobile
User Timing marks and measures 11 user timings
Avoid long main-thread tasks 20 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 240 ms
Server Backend Latencies 350 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 20 ms
INP breakdown
Avoid non-composited animations
82

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
College athletes div.rsNav > div.rsThumbsContainer > div.rsNavItem > span.rsTmb
RELATED div#slider-content > div.slider-content-container > div.slider-content-right > h3
OVERTIME PAY div#custom_html-8 > div.textwidget > div.state-solutions > a#ot
CHILD LABOR div#custom_html-8 > div.textwidget > div.state-solutions > a#child-labor
Accessible, up-to-date data on the living standards of workers in the United St… footer#epi-footer > div.width-wrap > div.wide > p
The state and local network of organizations improving workers' lives through r… footer#epi-footer > div.width-wrap > div.wide > p
Exploring how race, ethnicity, and class intersect to affect economic outcomes … footer#epi-footer > div.width-wrap > div.wide > p
Why give to EPI | Donate EIN 52-1368964 footer#epi-footer > div.width-wrap > div.narrow > p
Why give to EPI div.width-wrap > div.narrow > p > a
Donate div.width-wrap > div.narrow > p > a
Newsroom footer#epi-footer > div.width-wrap > div.narrow > a
Contact us footer#epi-footer > div.width-wrap > div.narrow > a
The Economic Policy Institute staff is unionized with the Nonprofit Professiona… footer#epi-footer > div.width-wrap > div.narrow > p.small
Nonprofit Professional Employees Union. div.width-wrap > div.narrow > p.small > a

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Visit data.epi.org div#sidebar > div#epi-widget-text-19 > div.epi-widget-body > a
epi@epi.org div.width-wrap > div.wide > p > a
Privacy Policy div.width-wrap > div.wide > p.small > 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
RELATED div#slider-content > div.slider-content-container > div.slider-content-right > h3
Projects footer#epi-footer > div.width-wrap > div.wide > h5

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
div#epi-widget-text-19 > div.epi-widget-body > a > img div#epi-widget-text-19 > div.epi-widget-body > a > img

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header#epi-masthead > div.width-wrap > h1 > a.mobile header#epi-masthead > div.width-wrap > h1 > a.mobile
header#epi-masthead > div.width-wrap > h1 > a header#epi-masthead > div.width-wrap > h1 > a
div.rsContainer > div.rsSlide > div.rsContent > a div.rsContainer > div.rsSlide > div.rsContent > a
div.rsContainer > div.rsSlide > div.rsContent > a div.rsContainer > div.rsSlide > div.rsContent > a
div.rsContainer > div.rsSlide > div.rsContent > a div.rsContainer > div.rsSlide > div.rsContent > a
div.rsContainer > div.rsSlide > div.rsContent > a div.rsContainer > div.rsSlide > div.rsContent > a
div#sidebar > div#epi-widget-text-19 > div.epi-widget-body > a div#sidebar > div#epi-widget-text-19 > div.epi-widget-body > a
div.width-wrap > div.narrow > p.small > a.npeu-logo div.width-wrap > div.narrow > p.small > a.npeu-logo

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>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Input buttons have discernible text.
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
`[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
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Touch targets have sufficient size and spacing.
Document has a main landmark.
Deprecated ARIA roles were not used
ARIA IDs are unique
No form fields have multiple labels
All heading elements contain content.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
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
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
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
Buttons have an accessible name
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
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
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
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
62

Best Practices

Trust and Safety

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URLRequest Resolution
www.epi.org/Allowed

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
SharedStorage
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
77

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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
div#epi-widget-text-19 > div.epi-widget-body > a > img div#epi-widget-text-19 > div.epi-widget-body > a > img

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

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

2.37 s

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

6.30 s

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

14 ms

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

0.076

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

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

6.33 s

Detailed Report

Audit breakdown by category with detailed findings.

59

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.

URLEst Savings
/af/3ad9c9/00000000000000003b9b094a/27/l?primer=7cdcb44be...140 ms
/af/5b14cd/00000000000000003b9b0945/27/l?primer=7cdcb44be...135 ms
/af/976aa6/00000000000000003b9b0943/27/l?primer=7cdcb44be...125 ms
/af/5bf3eb/00000000000000003b9b0944/27/l?primer=7cdcb44be...125 ms
/af/bb2e37/00000000000000003b9b094b/27/l?primer=7cdcb44be...115 ms
/af/ba66d8/00000000000000003b9b093a/27/l?primer=7cdcb44be...110 ms
use.typekit.com/af/1ec8cf/000000000000000000017099/27/l?subset_id=2&fvd=i3&v=3105 ms
use.typekit.com/af/3a798d/00000000000000000000ec0a/27/l?subset_id=2&fvd=i7&v=3105 ms
/af/fce0a9/00000000000000003b9acae2/27/l?primer=7cdcb44be...100 ms
use.typekit.com/af/1b8c3f/000000000000000000011aff/27/l?subset_id=2&fvd=n7&v=3100 ms
/wp-content/themes/epi/dist/fonts/font-awesome/fonts/font...95 ms
/af/d7a560/00000000000000003b9acae1/27/l?primer=7cdcb44be...95 ms
/af/ae1174/00000000000000003b9acadd/27/l?primer=7cdcb44be...90 ms
use.typekit.com/af/810490/000000000000000000010141/27/l?subset_id=2&fvd=i3&v=385 ms
use.typekit.com/af/f8c331/0000000000000000000100fe/27/l?subset_id=2&fvd=n3&v=380 ms
use.typekit.com/af/f0a7c7/00000000000000000000e807/27/l?subset_id=2&fvd=n9&v=375 ms
use.typekit.com/af/f6d549/00000000000000000000e7fe/27/l?subset_id=2&fvd=n3&v=370 ms
use.typekit.com/af/dc6ba3/00000000000000000000e806/27/l?subset_id=2&fvd=i7&v=370 ms
use.typekit.com/af/c2dac6/00000000000000000000e805/27/l?subset_id=2&fvd=n7&v=360 ms
use.typekit.com/af/55aa58/00000000000000000000e802/27/l?subset_id=2&fvd=i3&v=355 ms
/af/a20313/00000000000000003b9acade/27/l?primer=7cdcb44be...50 ms
/af/56978c/00000000000000003b9b0935/27/l?primer=7cdcb44be...45 ms
use.typekit.com/af/8cf19a/00000000000000000001709a/27/l?subset_id=2&fvd=n4&v=345 ms
/af/773235/00000000000000003b9b0934/27/l?primer=7cdcb44be...40 ms
use.typekit.com/af/04a489/00000000000000000001709f/27/l?subset_id=2&fvd=i7&v=335 ms
use.typekit.com/af/bce065/00000000000000000001709b/27/l?subset_id=2&fvd=i4&v=335 ms
use.typekit.com/af/341571/000000000000000000017098/27/l?subset_id=2&fvd=n3&v=335 ms
/af/1f55cd/00000000000000003b9b0932/27/l?primer=7cdcb44be...30 ms
use.typekit.com/af/c1298f/0000000000000000000170ae/27/l?subset_id=2&fvd=n4&v=330 ms
use.typekit.com/af/a51230/0000000000000000000170b0/27/l?subset_id=2&fvd=i4&v=330 ms
use.typekit.com/af/fb6723/0000000000000000000170b4/27/l?subset_id=2&fvd=i7&v=330 ms
use.typekit.com/af/69b489/0000000000000000000170b3/27/l?subset_id=2&fvd=n7&v=325 ms
/af/1f7f57/00000000000000003b9b093b/27/l?primer=7cdcb44be...20 ms
use.typekit.com/af/9a5180/00000000000000000001709e/27/l?subset_id=2&fvd=n7&v=315 ms

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:95.79 source:map[type:text value:[unattributed]]] map[reflowTime:1.483 source:map[column:10449 line:7 type:source-location url:https://platform.twitter.com/widgets.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#epi-widget-text-19 > div.epi-widget-body > a > img div#epi-widget-text-19 > div.epi-widget-body > a > img
files.epi.org/uploads/Data-Lib-Award-Winning.png322.9 KiB314.3 KiB
'NO TAX ON TIPS' div#custom_html-7 > div.textwidget > div.faq-buttons > a#notaxtips
files.epi.org/uploads/no-tax-on-tips-button-e1770902303121.png116.2 KiB82.2 KiB
'NO TAX ON OVERTIME' div#custom_html-7 > div.textwidget > div.faq-buttons > a#notaxot
files.epi.org/uploads/notaxonot.png178.8 KiB55.8 KiB
div.narrow > p > a > img div.narrow > p > a > img
files.epi.org/uploads/Four-Star-Rating-Badge-Full-Color-1.webp33.1 KiB33.1 KiB
div.rsSlide > div.rsContent > a > img.rsImg div.rsSlide > div.rsContent > a > img.rsImg
files.epi.org/uploads/shutterstock_2145740941-650x468.jpg63.3 KiB13.8 KiB
div.narrow > p > a > img div.narrow > p > a > img
files.epi.org/uploads/candid-seal-gold-2025.png12.7 KiB12.6 KiB
TARIFFS div#custom_html-7 > div.textwidget > div.faq-buttons > a#tariffs
files.epi.org/uploads/tariffs-faq_red.png17.1 KiB7.4 KiB
SOCIAL SECURITY div#custom_html-7 > div.textwidget > div.faq-buttons > a#social-security
files.epi.org/uploads/social-security-faq_red.png15.0 KiB5.2 KiB
div.rsSlide > div.rsContent > a > img.rsImg div.rsSlide > div.rsContent > a > img.rsImg
files.epi.org/uploads/U.S.-born-unemployment-is-higher-under-Trump.png37.7 KiB4.9 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:412.16 label:Time to first byte subpart:timeToFirstByte] map[duration:20.81 label:Resource load delay subpart:resourceLoadDelay] map[duration:123.036 label:Resource load duration subpart:resourceLoadDuration] map[duration:2866.386 label:Element render delay subpart:elementRenderDelay]]
lhId: page-9-IMG
nodeLabel: div.rsSlide > div.rsContent > a > img.rsImg
path: 6,HTML,2,BODY,3,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,A,0,IMG
selector: div.rsSlide > div.rsContent > a > img.rsImg
snippet: <img width="600" height="400" src="https://files.epi.org/uploads/chandler-denise-Lgaw-BnaAAI-unsplash-650x433…" class="rsImg rsMainSlideImage" alt="" decoding="async" fetchpriority="high" srcset="https://files.epi.org/uploads/chandler-denise-Lgaw-BnaAAI-unsplash-950x633…" sizes="(max-width: 600px) 100vw, 600px" style="width: 607px; height: 405px; margin-left: 0px; margin-top: -47px;">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer SizeDuration
/wp-content/themes/epi/dist/css/epi-main.css?ver=04bf9473...705.0 KiB1.2 s
use.typekit.com/gfy6bkz.js7.0 KiB
use.typekit.com/mez6pee.js6.9 KiB
use.typekit.com/uhs7xha.js7.2 KiB125 ms
www.epi.org/wp-includes/js/jquery/jquery.min.js?ver=3.7.130.2 KiB244 ms
www.epi.org/wp-includes/js/dist/vendor/lodash.min.js?ver=4.17.2124.8 KiB203 ms
/wp-content/mu-plugins/epi-charts/js/requirejs/vendor/req...20.8 KiB203 ms
www.googleadservices.com/pagead/conversion_async.js22.8 KiB369 ms
www.epi.org/wp-includes/css/dashicons.min.css?ver=176401263235.0 KiB284 ms
/wp-content/mu-plugins/epi-charts/js/requirejs/epi_main.j...483 B81 ms
/wp-content/mu-plugins/epi-charts/js/requirejs/requirejs-...333 B81 ms
/wp-content/mu-plugins/epi-charts/js/epi/epi.utility.js?v...3.1 KiB81 ms
/wp-content/mu-plugins/epi-charts/js/epi/epi.namespace.js...509 B81 ms
www.epi.org/wp-includes/js/jquery/jquery-migrate.min.js?ver=3.4.15.0 KiB81 ms
www.epi.org/wp-content/plugins/add-to-any/addtoany.min.css?ver=1.16800 B81 ms
www.epi.org/wp-content/plugins/wp-pagenavi/pagenavi-css.css?ver=2.70506 B81 ms
/wp-content/themes/epi/dist/css/font-ss-standard.css?ver=...2.4 KiB81 ms
/wp-content/mu-plugins/epi-automated-screenshots/dist/css...1.7 KiB81 ms
/wp-content/mu-plugins/epi-modals/dist/css/epi-modals.min...1.1 KiB81 ms
/wp-content/mu-plugins/epi-issue-tags/dist/css/epi-issue-...1.5 KiB81 ms
/wp-content/mu-plugins/epi-data-library/dist/css/epi-data...1.9 KiB162 ms
/wp-content/themes/epi/dist/css/front-page-slider.css?ver...11.2 KiB203 ms
/wp-content/mu-plugins/epi-manage-content/dist/css/epi-ma...1.4 KiB162 ms
/wp-content/mu-plugins/epi-charts/dist/css/epi-charts--ma...14.3 KiB244 ms
/wp-content/mu-plugins/epi-shortcodes/dist/css/epi-shortc...13.1 KiB244 ms
/wp-content/mu-plugins/epi-charts/dist/css/epi-charts.min...19.3 KiB203 ms

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: 771 ms
URLTime Spent
epi.org/581 ms
www.epi.org/190 ms
www.epi.org/0.0 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

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.

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

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

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 2.8 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
div.narrow > p > a > img div.narrow > p > a > img
files.epi.org/uploads/Four-Star-Rating-Badge-Full-Color-1.webp
div#epi-widget-text-19 > div.epi-widget-body > a > img div#epi-widget-text-19 > div.epi-widget-body > a > img
files.epi.org/uploads/Data-Lib-Award-Winning.png
div.narrow > p > a > img div.narrow > p > a > img
files.epi.org/uploads/candid-seal-gold-2025.png

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

Layout shift culprits
Optimize DOM size
LCP request discovery
Modern HTTP
Optimize viewport for mobile
Max Potential First Input Delay 60 ms
User Timing marks and measures 13 user timings
JavaScript execution time 0.5 s
Minimizes main-thread work 1.6 s
Avoid long main-thread tasks 2 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 230 ms
Server Backend Latencies 350 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 30 ms
Avoid large layout shifts 3 layout shifts found
INP breakdown
Avoid non-composited animations
82

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
College athletes div.rsNav > div.rsThumbsContainer > div.rsNavItem > span.rsTmb
Unemployment div.rsNav > div.rsThumbsContainer > div.rsNavItem > span.rsTmb
Taxes div.rsNav > div.rsThumbsContainer > div.rsNavItem > span.rsTmb
RELATED div#slider-content > div.slider-content-container > div.slider-content-right > h3
OVERTIME PAY div#custom_html-8 > div.textwidget > div.state-solutions > a#ot
CHILD LABOR div#custom_html-8 > div.textwidget > div.state-solutions > a#child-labor
Accessible, up-to-date data on the living standards of workers in the United St… footer#epi-footer > div.width-wrap > div.wide > p
The state and local network of organizations improving workers' lives through r… footer#epi-footer > div.width-wrap > div.wide > p
Exploring how race, ethnicity, and class intersect to affect economic outcomes … footer#epi-footer > div.width-wrap > div.wide > p

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Visit data.epi.org div#sidebar > div#epi-widget-text-19 > div.epi-widget-body > a
epi@epi.org div.width-wrap > div.wide > p > a
Privacy Policy div.width-wrap > div.wide > p.small > 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
RELATED div#slider-content > div.slider-content-container > div.slider-content-right > h3
Projects footer#epi-footer > div.width-wrap > div.wide > h5

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
div#epi-widget-text-19 > div.epi-widget-body > a > img div#epi-widget-text-19 > div.epi-widget-body > a > img

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header#epi-masthead > div.width-wrap > h1 > a header#epi-masthead > div.width-wrap > h1 > a
div.rsContainer > div.rsSlide > div.rsContent > a div.rsContainer > div.rsSlide > div.rsContent > a
div.rsContainer > div.rsSlide > div.rsContent > a div.rsContainer > div.rsSlide > div.rsContent > a
div.rsContainer > div.rsSlide > div.rsContent > a div.rsContainer > div.rsSlide > div.rsContent > a
div.rsContainer > div.rsSlide > div.rsContent > a div.rsContainer > div.rsSlide > div.rsContent > a
div#sidebar > div#epi-widget-text-19 > div.epi-widget-body > a div#sidebar > div#epi-widget-text-19 > div.epi-widget-body > a
div.width-wrap > div.narrow > p.small > a.npeu-logo div.width-wrap > div.narrow > p.small > a.npeu-logo

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>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Input buttons have discernible text.
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
`[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
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Touch targets have sufficient size and spacing.
Document has a main landmark.
Deprecated ARIA roles were not used
ARIA IDs are unique
All heading elements contain content.
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
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
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
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
Buttons have an accessible name
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
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
Image elements do not have `[alt]` attributes that are redundant text.
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.
58

Best Practices

Trust and Safety

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URLRequest Resolution
www.epi.org/Allowed

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
div.rsSlide > div.rsContent > a > img.rsImg div.rsSlide > div.rsContent > a > img.rsImg
files.epi.org/uploads/U.S.-born-unemployment-is-higher-under-Trump.png607 x 312 (1.95)630 x 320 (1.97)

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
SharedStorage
StorageType.persistent is deprecated. Please use standardized navigator.storage instead.
Fledge
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
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
77

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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
div#epi-widget-text-19 > div.epi-widget-body > a > img div#epi-widget-text-19 > div.epi-widget-body > a > img

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 are crawlable
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback