Skip to content
Audit Complete

Results for https://thetrevorproject.org

Visit site
Nonprofit / NGO · estimated Tracking: donations
Spain Spain · Madrid Completed: Apr 22, 2026 20:25 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)
C72

Site Health

Score: 72 / 100

Based on 8 categories, 0 sections

Room to improve — your 19.0s load time is above Google's 2.5s 'Good' threshold.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Good server performance with room for optimization.

Mostly compliant — a few items need attention.

Rich content metadata — your pages look great everywhere.

Heavier than average — reducing page weight saves energy and bandwidth.

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 · 542 peers
You 72
·
Avg 74
At average
0 50 100
Better than 18% of WordPress sites See full WordPress benchmark →
Apple · 1007 peers
You 72
·
Avg 72
At average
0 50 100
Better than 33% of Apple sites See full Apple benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

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

Security › Security Headers
2

HSTS header is missing

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

Security › Security Headers
3

No Content-Security-Policy header found

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

Security › Content Security Policy
4

Page weighs 18.0 MB (5.8 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
5

1 button(s) with no accessible text

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

Accessibility › Link & Button Quality
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%2Fthetrevorproject.org)](https://beavercheck.com/results/9527d2a0-be5a-4cf3-81c2-70e7772e49e9)
<a href="https://beavercheck.com/results/9527d2a0-be5a-4cf3-81c2-70e7772e49e9"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fthetrevorproject.org" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fthetrevorproject.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 19.0s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.
Your LCP is 19.0s — 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

3 critical 4 warning

7 barrier(s) likely increasing bounce by ~30%.

Speed (2)

Page takes 19.0s to load

+12% bounce

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

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

Page feels frozen for 2.2s

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

1 form field(s) without a label

+2% bounce

Screen 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 (1)

Content is hard to read

+2% bounce

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

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

Navigation (1)

17 broken link(s) on the page

+5% bounce

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

Return on Investment

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

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

Investment

$500

5h · 5 findings

Monthly returns

$1.46 /mo

~$18 / year

  • Bandwidth savings $1.46

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,518 / 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
  • 3 advertising/retargeting trackers detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no cookie policy found
    CCPA/CPRA: USD 2,500 – USD 7,500

+3 more

Bandwidth Waste

$1.46 /mo

18262.0 MB/mo × 0.080 USD/GB

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

27
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
96
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.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

7.01 s

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

19.05 s

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

2.19 s

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

0.041

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

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

34.25 s

Detailed Report

Audit breakdown by category with detailed findings.

27

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
/wp-content/themes/trevor/static/js/frontend.js?ver=1.0.0...1800.0 s606.6 KiB
/wp-content/uploads/2024/10/TTP_Individual_Julia1_Homepag...1800.0 s428.3 KiB
/wp-content/uploads/2024/10/TTP_Individual_Mel2_Homepage-...1800.0 s382.3 KiB
/wp-content/themes/trevor/static/css/frontend.css?ver=1.0...1800.0 s342.8 KiB
/wp-content/uploads/2024/10/TTP_Individual_Yev_Homepage-s...1800.0 s333.9 KiB
/wp-content/uploads/2024/10/TTP_Individual_Breanna_Homepa...1800.0 s306.9 KiB
/wp-content/uploads/2024/10/TTP_Individual_Ryan1_Homepage...1800.0 s295.8 KiB
/wp-content/uploads/2024/10/TTP_Individual_Alexis_Homepag...1800.0 s264.3 KiB
/wp-content/uploads/2024/06/TTP_BrandIllustrations_DayAnd...1800.0 s187.1 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
/wp-content/uploads/2021/08/AdobeStock_410814393-768x768....1800.0 s55.3 KiB
/script/75427f25d4841735a1427c2121894372.experiment.js?ve...60.0 s43.8 KiB
/signals/config/249611735914172?v=2.9.303&r=stable&domain...1200.0 s35.9 KiB
www.thetrevorproject.org/wp-includes/js/jquery/jquery.min.js?ver=3.7.11800.0 s29.8 KiB
www.redditstatic.com/ads/pixel.js60.0 s19.0 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
/wp-includes/css/dist/block-library/style.min.css?ver=6.5.61800.0 s14.8 KiB
/wp-content/uploads/2024/07/TTP_Icons_Indigo_Fundraising.svg1800.0 s13.6 KiB
/wp-content/uploads/2024/07/TTP_Icons_Indigo_Program-Advo...1800.0 s10.7 KiB
/wp-content/uploads/2024/07/TTP_Icons_Indigo_Work-at-Trev...1800.0 s8.6 KiB
/wp-content/uploads/2024/07/TTP_Icons_Indigo_Volunteer.svg1800.0 s7.7 KiB
static.hotjar.com/c/hotjar-1362548.js?sv=660.0 s6.3 KiB
/wp-content/themes/trevor/static/icon-font/trevor-ti_0aed...1800.0 s5.3 KiB
acdn.adnxs.com/dmp/up/pixie.js86402.0 s9.2 KiB
/wp-content/themes/trevor/static/js/site-banners.js?ver=1...1800.0 s3.0 KiB
/wp-content/plugins/trevor/static/js/runtime.js?ver=6.5.61800.0 s1.8 KiB
/wp-content/plugins/kadence-creative-kit/build/blocks/mar...1800.0 s1.3 KiB
/rp.gif?ts=1776889447125&id=t2_h5ketmce&event=PageVisit&m...0.0 ms666 B
/wp-content/plugins/trevor-chat-button/public/js/trevor-c...1800.0 s771 B
/wp-content/plugins/amplitude/scripts/amplitude-configure...1800.0 s629 B
rules.quantcount.com/rules-p-0pKCsepujNCRX.js3600.0 s643 B
/config/org/fbdea188-1841-4a11-842d-3aed7e8f1e65.js?v=3.5...0.0 ms480 B
/wp-content/plugins/trevor-chat-button/public/css/trevor-...1800.0 s328 B
www.gstatic.com/recaptcha/api2/logo_48.png604800.0 s2.3 KiB
/pixel/?ad_log=referer&action=lead&pixid=28155bd1-e089-4e...0.0 ms131 B
/tr/?id=249611735914172&ev=PageView&dl=https%3A%2F%2Fwww....0.0 ms19 B
/a?v=3&t=l&pid=1776098251&rv=64k1&tag_exp=0~115616986~115...0.0 ms11 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:31.683 source:map[column:73 line:62836 type:source-location url:https://www.thetrevorproject.org/wp-content/themes/trevor/static/js/frontend.js?ver=1.0.0-alpha urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:103.472 source:map[type:text value:[unattributed]]] map[reflowTime:14.641 source:map[column:84992 line:1 type:source-location url:https://www.thetrevorproject.org/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:3.21 source:map[column:19 line:56324 type:source-location url:https://www.thetrevorproject.org/wp-content/themes/trevor/static/js/frontend.js?ver=1.0.0-alpha urlProvider:network]] map[reflowTime:0.459 source:map[column:68 line:56685 type:source-location url:https://www.thetrevorproject.org/wp-content/themes/trevor/static/js/frontend.js?ver=1.0.0-alpha urlProvider:network]] map[reflowTime:2.682 source:map[column:27 line:61434 type:source-location url:https://www.thetrevorproject.org/wp-content/themes/trevor/static/js/frontend.js?ver=1.0.0-alpha urlProvider:network]] map[reflowTime:2.709 source:map[column:65 line:54992 type:source-location url:https://www.thetrevorproject.org/wp-content/themes/trevor/static/js/frontend.js?ver=1.0.0-alpha urlProvider:network]] map[reflowTime:0.369 source:map[column:35 line:56673 type:source-location url:https://www.thetrevorproject.org/wp-content/themes/trevor/static/js/frontend.js?ver=1.0.0-alpha urlProvider:network]] map[reflowTime:22.509 source:map[column:32 line:63096 type:source-location url:https://www.thetrevorproject.org/wp-content/themes/trevor/static/js/frontend.js?ver=1.0.0-alpha urlProvider:network]] map[reflowTime:3.06 source:map[column:49 line:58647 type:source-location url:https://www.thetrevorproject.org/wp-content/themes/trevor/static/js/frontend.js?ver=1.0.0-alpha urlProvider:network]] map[reflowTime:0.211 source:map[column:39 line:61439 type:source-location url:https://www.thetrevorproject.org/wp-content/themes/trevor/static/js/frontend.js?ver=1.0.0-alpha urlProvider:network]] map[reflowTime:0.453 source:map[column:33 line:27111 type:source-location url:https://www.thetrevorproject.org/wp-content/themes/trevor/static/js/frontend.js?ver=1.0.0-alpha urlProvider:network]] map[reflowTime:1.21 source:map[column:32 line:27158 type:source-location url:https://www.thetrevorproject.org/wp-content/themes/trevor/static/js/frontend.js?ver=1.0.0-alpha urlProvider:network]] map[reflowTime:0.244 source:map[column:26 line:27178 type:source-location url:https://www.thetrevorproject.org/wp-content/themes/trevor/static/js/frontend.js?ver=1.0.0-alpha 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
An LGBTQ+ young person in a striped sweater clutches a rainbow friendship brace… div.page-header-img-wrap > div.page-header-images > div.page-header-image > img.block
/wp-content/uploads/2024/10/TTP_Individual_Julia1_Homepag...427.6 KiB418.4 KiB
An LGBTQ+ young person smiles and looks up in front of foliage. div.page-header-img-wrap > div.page-header-images > div.page-header-image > img.block
/wp-content/uploads/2024/10/TTP_Individual_Mel2_Homepage-...381.9 KiB371.7 KiB
A Black LGBTQ+ young person with facial piercings smiles in front of foliage. div.page-header-img-wrap > div.page-header-images > div.page-header-image > img.block
/wp-content/uploads/2024/10/TTP_Individual_Yev_Homepage-s...333.3 KiB329.2 KiB
An LGBTQ+ young person leans against a window in a jean jacket. div.page-header-img-wrap > div.page-header-images > div.page-header-image > img.block
/wp-content/uploads/2024/10/TTP_Individual_Breanna_Homepa...306.6 KiB301.0 KiB
An LGBTQ+ young person lies forward on a couch. div.page-header-img-wrap > div.page-header-images > div.page-header-image > img.block
/wp-content/uploads/2024/10/TTP_Individual_Ryan1_Homepage...295.5 KiB289.6 KiB
An LGBTQ+ young person in a vivid pink blouse smiles in front of an orange tree. div.page-header-img-wrap > div.page-header-images > div.page-header-image > img.block
/wp-content/uploads/2024/10/TTP_Individual_Alexis_Homepag...263.9 KiB258.0 KiB
Smiling young person speaking on the phone to a happy Trevor counselor on a lap… div.overlapping-text-image-tiles > div.overlapping-text-image-tiles__container > div.overlapping-text-image-tiles__image > img.block
/wp-content/uploads/2024/06/TTP_BrandIllustrations_DayAnd...186.2 KiB174.7 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:2895.7359990234377 label:Time to first byte subpart:timeToFirstByte] map[duration:558.9850009765624 label:Element render delay subpart:elementRenderDelay]]
lhId: page-7-P
nodeLabel: And so do the people you care about. Here you can reach out to a counselor if y…
path: 1,HTML,1,BODY,12,MAIN,0,HEADER,0,DIV,0,DIV,0,DIV,0,DIV,1,P
selector: div.page-header > div.page-header-inner > div.page-header-content-wrap > p.page-header-desc
snippet: <p class="page-header-desc">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 2.7 s
URLTime Spent
www.thetrevorproject.org/2.8 s

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 750 ms 158.8 KiB
URLTransfer SizeEst Savings
/wp-content/themes/trevor/static/js/frontend.js?ver=1.0.0...606.4 KiB158.8 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.8 s 350.4 KiB

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

Why this matters

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

Learn more

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

Source: Google web.dev / Lighthouse

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTotal CPU TimeScript EvaluationScript Parse
www.thetrevorproject.org/2.0 s31 ms6.7 ms
/wp-content/themes/trevor/static/js/frontend.js?ver=1.0.0...1.1 s326 ms533 ms
Unattributable956 ms134 ms0.0 ms
www.gstatic.com/recaptcha/releases/gTpTIWhbKpxADzTzkcabhXN4/recaptcha__en.js796 ms659 ms86 ms
www.thetrevorproject.org/wp-includes/js/jquery/jquery.min.js?ver=3.7.1466 ms341 ms6.9 ms
www.googletagmanager.com/gtm.js?id=GTM-K652FKQ464 ms387 ms63 ms
www.googletagmanager.com/gtag/js?id=G-BD80V9CE2Q&cx=c&gtm=4e64k1h2458 ms332 ms40 ms
/wp-content/themes/trevor/static/css/frontend.css?ver=1.0...291 ms0.0 ms0.0 ms
analytics.tiktok.com/i18n/pixel/static/main.MWE0ZWQ3ZWQwOQ.js268 ms219 ms44 ms
www.googletagmanager.com/gtag/js?id=G-DZG3N29WTN&cx=c&gtm=4e64k1h2265 ms227 ms36 ms
www.googletagmanager.com/gtag/js?id=G-A2ABC2ABCD&cx=c&gtm=4e64k1h2245 ms210 ms32 ms
www.googletagmanager.com/gtag/js?id=AW-773281065&cx=c&gtm=4e64k1h2229 ms190 ms38 ms
www.googletagmanager.com/gtag/js?id=DC-13177022&cx=c&gtm=4e64k1h2218 ms187 ms31 ms
www.googletagmanager.com/gtag/destination?id=AW-923482947&cx=c&gtm=4e64k1h2197 ms162 ms35 ms
script.hotjar.com/modules.6a0f3932cb1341a35c18.js177 ms151 ms20 ms
connect.facebook.net/en_US/fbevents.js171 ms115 ms55 ms
sc-static.net/scevent.min.js141 ms129 ms5.3 ms
cdn.amplitude.com/libs/plugin-session-replay-browser-1.8.2-min.js.gz?ver=6.5.6132 ms104 ms25 ms
/signals/config/249611735914172?v=2.9.303&r=stable&domain...114 ms99 ms13 ms
/script/75427f25d4841735a1427c2121894372.experiment.js?ve...81 ms65 ms15 ms
www.google-analytics.com/analytics.js80 ms71 ms3.9 ms
secure.quantserve.com/quant.js78 ms72 ms5.3 ms
analytics.tiktok.com/i18n/pixel/static/identify_5cff1caf.js55 ms40 ms14 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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation4.5 s
Other2.1 s
Script Parsing & Compilation1.1 s
Style & Layout1.1 s
Parse HTML & CSS299 ms
Garbage Collection150 ms
Rendering56 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
Indigo line art illustration of a bill and 2 coins. div#swiper-wrapper-a9b6c7f10f4fbbc4d > div.org-mission__card > div.org-mission__image > img
/wp-content/uploads/2024/07/TTP_Icons_Indigo_Fundraising.svg
Indigo line art illustration of a megaphone. div#swiper-wrapper-a9b6c7f10f4fbbc4d > div.org-mission__card > div.org-mission__image > img
/wp-content/uploads/2024/07/TTP_Icons_Indigo_Program-Advo...
Indigo line art illustration of a hand holding a heart above it. div#swiper-wrapper-a9b6c7f10f4fbbc4d > div.org-mission__card > div.org-mission__image > img
/wp-content/uploads/2024/07/TTP_Icons_Indigo_Volunteer.svg
Indigo line art illustration of the Trevor star with a comet trail. div#swiper-wrapper-a9b6c7f10f4fbbc4d > div.org-mission__card > div.org-mission__image > img
/wp-content/uploads/2024/07/TTP_Icons_Indigo_Work-at-Trev...

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

Layout shift culprits
Optimize DOM size
Modern HTTP
Optimize viewport for mobile
Minify CSS
User Timing marks and measures 199 user timings
Avoid long main-thread tasks 20 long tasks found
Avoid non-composited animations 1 animated element found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 100 ms
Server Backend Latencies 180 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid large layout shifts 1 layout shift found
INP breakdown
LCP request discovery
96

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
And so do the people you care about. Here you can reach out to a counselor if y… div.page-header > div.page-header-inner > div.page-header-content-wrap > p.page-header-desc
day or night. div.messaging > div.messaging__container > p.messaging__title > tilt

These are opportunities to improve the legibility of your content.

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

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

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Mixed content
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
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
92

SEO

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

Content Best Practices

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.

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
Document has a meta description
Page has successful HTTP status code
Links are crawlable
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`
Image elements have `[alt]` attributes

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

62
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
96
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.
92
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.84 s

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

4.14 s

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

110 ms

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

0.022

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

4.14 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.21 s

Detailed Report

Audit breakdown by category with detailed findings.

62

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
/wp-content/themes/trevor/static/js/frontend.js?ver=1.0.0...1800.0 s606.5 KiB
/wp-content/uploads/2024/10/TTP_Individual_Julia1_Homepag...1800.0 s428.0 KiB
/wp-content/uploads/2024/10/TTP_Individual_Mel2_Homepage-...1800.0 s382.2 KiB
/wp-content/themes/trevor/static/css/frontend.css?ver=1.0...1800.0 s342.6 KiB
/wp-content/uploads/2024/10/TTP_Individual_Yev_Homepage-s...1800.0 s333.6 KiB
/wp-content/uploads/2024/10/TTP_Individual_Breanna_Homepa...1800.0 s306.9 KiB
/wp-content/uploads/2024/10/TTP_Individual_Ryan1_Homepage...1800.0 s295.8 KiB
/wp-content/uploads/2024/10/TTP_Individual_Alexis_Homepag...1800.0 s264.2 KiB
/wp-content/uploads/2024/06/TTP_BrandIllustrations_DayAnd...1800.0 s186.5 KiB
/wp-content/uploads/2021/08/AdobeStock_410814393-1440x144...1800.0 s124.9 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
/script/75427f25d4841735a1427c2121894372.experiment.js?ve...60.0 s43.8 KiB
/signals/config/249611735914172?v=2.9.303&r=stable&domain...1200.0 s35.9 KiB
www.thetrevorproject.org/wp-includes/js/jquery/jquery.min.js?ver=3.7.11800.0 s29.9 KiB
www.redditstatic.com/ads/pixel.js60.0 s19.0 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
/wp-includes/css/dist/block-library/style.min.css?ver=6.5.61800.0 s14.9 KiB
/wp-content/uploads/2024/07/TTP_Icons_Indigo_Fundraising.svg1800.0 s14.3 KiB
/wp-content/uploads/2024/07/TTP_Icons_Indigo_Program-Advo...1800.0 s10.7 KiB
/wp-content/uploads/2024/07/TTP_Icons_Indigo_Work-at-Trev...1800.0 s8.6 KiB
static.hotjar.com/c/hotjar-1362548.js?sv=660.0 s6.3 KiB
/wp-content/uploads/2024/07/TTP_Icons_Indigo_Volunteer.svg1800.0 s7.1 KiB
/wp-content/themes/trevor/static/icon-font/trevor-ti_0aed...1800.0 s5.3 KiB
acdn.adnxs.com/dmp/up/pixie.js86402.0 s9.2 KiB
/wp-content/themes/trevor/static/js/site-banners.js?ver=1...1800.0 s3.2 KiB
/wp-content/plugins/trevor/static/js/runtime.js?ver=6.5.61800.0 s1.9 KiB
/wp-content/plugins/kadence-creative-kit/build/blocks/mar...1800.0 s1.4 KiB
/rp.gif?ts=1776889471259&id=t2_h5ketmce&event=PageVisit&m...0.0 ms666 B
/wp-content/plugins/amplitude/scripts/amplitude-configure...1800.0 s771 B
rules.quantcount.com/rules-p-0pKCsepujNCRX.js3600.0 s643 B
/config/org/fbdea188-1841-4a11-842d-3aed7e8f1e65.js?v=3.5...0.0 ms480 B
/wp-content/plugins/trevor-chat-button/public/css/trevor-...1800.0 s457 B
www.gstatic.com/recaptcha/api2/logo_48.png604800.0 s2.3 KiB
/pixel/?ad_log=referer&action=lead&pixid=28155bd1-e089-4e...0.0 ms131 B
/tr/?id=249611735914172&ev=PageView&dl=https%3A%2F%2Fwww....0.0 ms19 B

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:1.291 source:map[column:37926 line:2 type:source-location url:https://www.thetrevorproject.org/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:96.543 source:map[type:text value:[unattributed]]] map[reflowTime:16.039 source:map[column:84992 line:1 type:source-location url:https://www.thetrevorproject.org/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.867 source:map[column:19 line:56324 type:source-location url:https://www.thetrevorproject.org/wp-content/themes/trevor/static/js/frontend.js?ver=1.0.0-alpha urlProvider:network]] map[reflowTime:0.416 source:map[column:68 line:56685 type:source-location url:https://www.thetrevorproject.org/wp-content/themes/trevor/static/js/frontend.js?ver=1.0.0-alpha urlProvider:network]] map[reflowTime:0.874 source:map[column:39 line:61439 type:source-location url:https://www.thetrevorproject.org/wp-content/themes/trevor/static/js/frontend.js?ver=1.0.0-alpha urlProvider:network]] map[reflowTime:0.49 source:map[column:65 line:54992 type:source-location url:https://www.thetrevorproject.org/wp-content/themes/trevor/static/js/frontend.js?ver=1.0.0-alpha urlProvider:network]] map[reflowTime:0.325 source:map[column:35 line:56673 type:source-location url:https://www.thetrevorproject.org/wp-content/themes/trevor/static/js/frontend.js?ver=1.0.0-alpha urlProvider:network]] map[reflowTime:0.649 source:map[column:33 line:27111 type:source-location url:https://www.thetrevorproject.org/wp-content/themes/trevor/static/js/frontend.js?ver=1.0.0-alpha urlProvider:network]] map[reflowTime:0.43 source:map[column:32 line:27158 type:source-location url:https://www.thetrevorproject.org/wp-content/themes/trevor/static/js/frontend.js?ver=1.0.0-alpha urlProvider:network]] map[reflowTime:0.212 source:map[column:26 line:27178 type:source-location url:https://www.thetrevorproject.org/wp-content/themes/trevor/static/js/frontend.js?ver=1.0.0-alpha urlProvider:network]] map[reflowTime:0.189 source:map[column:278 line:92 type:source-location url:https://www.google-analytics.com/analytics.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
An LGBTQ+ young person in a striped sweater clutches a rainbow friendship brace… div.page-header-img-wrap > div.page-header-images > div.page-header-image > img.block
/wp-content/uploads/2024/10/TTP_Individual_Julia1_Homepag...427.6 KiB419.5 KiB
An LGBTQ+ young person smiles and looks up in front of foliage. div.page-header-img-wrap > div.page-header-images > div.page-header-image > img.block
/wp-content/uploads/2024/10/TTP_Individual_Mel2_Homepage-...381.9 KiB374.4 KiB
A Black LGBTQ+ young person with facial piercings smiles in front of foliage. div.page-header-img-wrap > div.page-header-images > div.page-header-image > img.block
/wp-content/uploads/2024/10/TTP_Individual_Yev_Homepage-s...333.3 KiB328.3 KiB
An LGBTQ+ young person leans against a window in a jean jacket. div.page-header-img-wrap > div.page-header-images > div.page-header-image > img.block
/wp-content/uploads/2024/10/TTP_Individual_Breanna_Homepa...306.6 KiB299.1 KiB
An LGBTQ+ young person lies forward on a couch. div.page-header-img-wrap > div.page-header-images > div.page-header-image > img.block
/wp-content/uploads/2024/10/TTP_Individual_Ryan1_Homepage...295.5 KiB283.1 KiB
An LGBTQ+ young person in a vivid pink blouse smiles in front of an orange tree. div.page-header-img-wrap > div.page-header-images > div.page-header-image > img.block
/wp-content/uploads/2024/10/TTP_Individual_Alexis_Homepag...263.9 KiB254.8 KiB
Smiling young person speaking on the phone to a happy Trevor counselor on a lap… div.overlapping-text-image-tiles > div.overlapping-text-image-tiles__container > div.overlapping-text-image-tiles__image > img.block
/wp-content/uploads/2024/06/TTP_BrandIllustrations_DayAnd...186.2 KiB175.8 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:3190.313 label:Time to first byte subpart:timeToFirstByte] map[duration:25.106 label:Resource load delay subpart:resourceLoadDelay] map[duration:374.664 label:Resource load duration subpart:resourceLoadDuration] map[duration:448.631 label:Element render delay subpart:elementRenderDelay]]
lhId: page-4-IMG
nodeLabel: An LGBTQ+ young person lies forward on a couch.
path: 1,HTML,1,BODY,12,MAIN,0,HEADER,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,4,DIV,0,IMG
selector: div.page-header-img-wrap > div.page-header-images > div.page-header-image > img.block
snippet: <img aria-hidden="true" src="https://www.thetrevorproject.org/wp-content/uploads/2024/10/TTP_Individual…" class="block mx-auto" alt="An LGBTQ+ young person lies forward on a couch.">

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-4-IMG
nodeLabel: An LGBTQ+ young person lies forward on a couch.
path: 1,HTML,1,BODY,12,MAIN,0,HEADER,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,4,DIV,0,IMG
selector: div.page-header-img-wrap > div.page-header-images > div.page-header-image > img.block
snippet: <img aria-hidden="true" src="https://www.thetrevorproject.org/wp-content/uploads/2024/10/TTP_Individual…" class="block mx-auto" alt="An LGBTQ+ young person lies forward on a couch.">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 269 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 3.0 s
URLTime Spent
www.thetrevorproject.org/3.1 s

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 210 ms 158.8 KiB
URLTransfer SizeEst Savings
/wp-content/themes/trevor/static/js/frontend.js?ver=1.0.0...606.3 KiB158.8 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 460 ms 344.7 KiB

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

Why this matters

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

Learn more

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

Source: Google web.dev / Lighthouse

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation1.1 s
Other437 ms
Style & Layout267 ms
Script Parsing & Compilation252 ms
Parse HTML & CSS76 ms
Garbage Collection23 ms
Rendering11 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
Indigo line art illustration of a bill and 2 coins. div.org-mission__cards > div.org-mission__card > div.org-mission__image > img
/wp-content/uploads/2024/07/TTP_Icons_Indigo_Fundraising.svg
Indigo line art illustration of a megaphone. div.org-mission__cards > div.org-mission__card > div.org-mission__image > img
/wp-content/uploads/2024/07/TTP_Icons_Indigo_Program-Advo...
Indigo line art illustration of a hand holding a heart above it. div.org-mission__cards > div.org-mission__card > div.org-mission__image > img
/wp-content/uploads/2024/07/TTP_Icons_Indigo_Volunteer.svg
Indigo line art illustration of the Trevor star with a comet trail. div.org-mission__cards > div.org-mission__card > div.org-mission__image > img
/wp-content/uploads/2024/07/TTP_Icons_Indigo_Work-at-Trev...

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

Max Potential First Input Delay 90 ms
Layout shift culprits
Optimize DOM size
Modern HTTP
Optimize viewport for mobile
Minify CSS
User Timing marks and measures 20 user timings
JavaScript execution time 1.0 s
Avoid long main-thread tasks 12 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 100 ms
Server Backend Latencies 170 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid large layout shifts 1 layout shift found
INP breakdown
Avoid non-composited animations
96

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
And so do the people you care about. Here you can reach out to a counselor if y… div.page-header > div.page-header-inner > div.page-header-content-wrap > p.page-header-desc
day or night. div.messaging > div.messaging__container > p.messaging__title > tilt

These are opportunities to improve the legibility of your content.

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

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

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Mixed content
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
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Mitigate clickjacking with XFO or CSP
92

SEO

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

Content Best Practices

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.

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
Document has a meta description
Page has successful HTTP status code
Links are crawlable
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`
Image elements have `[alt]` attributes

Send Feedback