Website review, no card needed

thetrevorproject.org logo

thetrevorproject.org website review

Visit site (opens in a new tab)Reviewed 28 October 202641 issues · 83 checks

This review found 41 issues worth fixing on thetrevorproject.org, 23 of them high impact, across 83 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
5.3 s4.1 sMay 9Oct 244.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.7 s
May 16, 20264.5 s
May 23, 20264.4 s
May 30, 20264.4 s
Jun 6, 20264.3 s
Jun 13, 20264.3 s
Jun 20, 20264.5 s
Jun 27, 20264.8 s
Jul 4, 20265.1 s
Jul 11, 20265.1 s
Jul 18, 20264.9 s
Jul 25, 20264.5 s
Aug 1, 20264.4 s
Aug 8, 20264.3 s
Aug 15, 20264.4 s
Aug 22, 20264.6 s
Aug 29, 20264.6 s
Sep 5, 20264.8 s
Sep 12, 20264.7 s
Sep 19, 20264.6 s
Sep 26, 20264.5 s
Oct 3, 20264.4 s
Oct 10, 20264.2 s
Oct 17, 20264.3 s
Oct 24, 20264.3 s
Real-visitor tap response (INP)75th percentile, phones
222 ms199 msMay 9Oct 24216 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026202 ms
May 16, 2026203 ms
May 23, 2026205 ms
May 30, 2026206 ms
Jun 6, 2026205 ms
Jun 13, 2026204 ms
Jun 20, 2026204 ms
Jun 27, 2026204 ms
Jul 4, 2026206 ms
Jul 11, 2026208 ms
Jul 18, 2026210 ms
Jul 25, 2026212 ms
Aug 1, 2026212 ms
Aug 8, 2026215 ms
Aug 15, 2026215 ms
Aug 22, 2026214 ms
Aug 29, 2026215 ms
Sep 5, 2026213 ms
Sep 12, 2026217 ms
Sep 19, 2026217 ms
Sep 26, 2026217 ms
Oct 3, 2026219 ms
Oct 10, 2026219 ms
Oct 17, 2026218 ms
Oct 24, 2026216 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of thetrevorproject.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thetrevorproject.org at 0.5 s0.5 s
  2. thetrevorproject.org at 1.0 s1.0 s
  3. thetrevorproject.org at 1.6 s1.6 s
  4. thetrevorproject.org at 2.1 s2.1 s
  5. thetrevorproject.org at 2.6 s2.6 s
  6. thetrevorproject.org at 3.1 s3.1 s
  7. thetrevorproject.org at 3.6 s3.6 s
  8. thetrevorproject.org at 4.2 s4.2 s

Speed

13 to fix33
  • Use efficient cache lifetimes

    12.9 s · 3.1 MB

    38 files are served with short cache lifetimes, so returning visitors download them again (3.1 MB).

  • Improve image delivery

    8.3 s · 2.1 MB

    7 images could be 2.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.3 s faster on a phone.

  • Render-blocking requests

    5.8 s

    12 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.8 s.

  • Reduce unused JavaScript

    2.3 s · 1.4 MB

    About 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

  • Reduce unused CSS

    1.8 s · 383 KiB

    About 383 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.8 s faster on a phone.

  • Google Tag Manager adds 1.1 s

    1.1 s

    Google Tag Manager costs a phone 1.1 s of main-thread work and 1.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 33

    33/100

    Your mobile performance score is 33 (desktop: 37). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 5.2 s

    A phone's processor spends 5.2 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and TikTok and others), adding 2.5 MB and 2.1 s of main-thread time.

  • Minify JavaScript

    750 ms · 159 KiB

    159 KiB could be saved by minifying JavaScript.

  • Google CDN adds 455 ms

    455 ms

    Google CDN costs a phone 455 ms of main-thread work and 736 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Legacy JavaScript

    350 ms · 70 KiB

    Polyfills for old browsers add 70 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 271 ms. During a long task the page ignores taps.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Chained critical requests

    Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 2 ms

    2 ms

    Your server sent the HTML in 2 ms, well inside Google's 600 ms guideline.

Core Web Vitals

9 to fix67
  • Fails Core Web Vitals for real visitors

    Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

  • Real-user LCP: 5.1 s

    5.1 s

    Real visitors wait 5.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 4.9 s

    4.9 s

    Real visitors see the first content after 4.9 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 3.2 s

    3.2 s

    Real visitors wait 3.2 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest Contentful Paint: 18.0 s

    18.0 s

    Your largest element takes 18.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “And so do the people you care about. Here you can reach out…”.

  • Time to Interactive: 35.7 s

    35.7 s

    The page becomes fully interactive after 35.7 s. Good is under 3.8 s.

  • First Contentful Paint: 6.0 s

    6.0 s

    The first text or image appears after 6.0 s on a phone. Good is under 1.8 s.

  • Speed Index: 11.2 s

    11.2 s

    Visually, the page fills in at 11.2 s (Speed Index). Good is under 3.4 s.

  • Total Blocking Time: 1.1 s

    1.1 s

    Scripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.

  • Tap response (INP) held steady for real visitors

    +7%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 202 ms to 216 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    -7%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.7 s to 4.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

3 checks passed
  • Real-user INP: 198 ms

    198 ms

    Real visitors wait 198 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Cumulative Layout Shift: 0.001

    0.001

    The layout barely moves while loading (CLS 0.001, good is under 0.1).

Images and page weight

3 to fix40
  • Page weight: 6.4 MB in 138 requests

    6.4 MB

    Your homepage downloads 6.4 MB in 138 requests on a phone: scripts 3.2 MB (42), images 2.3 MB (31) and stylesheets 397 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 7 images far larger than shown

    2.0 MB

    7 images are downloaded at several times the size a phone draws them, for example TTP_Individual_Julia1_Homepage-scaled.jpg at 2,168 px wide, shown at 207 px. Resized copies would save about 2.0 MB.

  • 7 images in older formats

    7 images (2.0 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 2 images below the first screen load straight away

    2 images further down the page (234 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.8 g of CO₂ per visit

    1.81 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.81 g of CO₂e: 217.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

3 to fixGoogle 9694
  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

2 checks passed
  • Every image has alt text

    All 12 images in the HTML carry an alt attribute.

  • 31 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 32 WCAG 2.2 A/AA and best-practice rules on the phone render: 31 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9298
  • 4 links with vague text

    4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 106 internal links, 24 external

    The homepage links to 106 pages on thetrevorproject.org and 24 external pages.

8 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “The Trevor Project is a non-profit suicide prevention organization that provides 24/7 crisis support services, research…”.

  • One H1 headline

    Your main headline reads: “You deserve a welcoming, loving world.”.

  • Title: 63 characters

    Your title is a healthy 63 characters: “The Trevor Project - Suicide Prevention for LGBTQ+ Young People”.

  • Canonical URL set

    The canonical URL is https://www.thetrevorproject.org/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.thetrevorproject.org/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.thetrevorproject.org/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

3 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,356 words), so crawlers that don't run JavaScript still read it.

Other pages

5 to fix67
  • 1 page without a title

    https://www.thetrevorproject.org/financial-reports has no <title>, so Google invents the link text in results.

  • 2 pages share a title

    https://www.thetrevorproject.org/get-help and https://www.thetrevorproject.org/crisis-services all use the title “24/7 Suicide Hotline for LGBTQ Youth - We’re here for you Now”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://www.thetrevorproject.org/be-the-one has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://www.thetrevorproject.org/get-help and https://www.thetrevorproject.org/crisis-services use the same meta description. A description written for each page earns more clicks.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.thetrevorproject.org/crisis-services, whose canonical is https://www.thetrevorproject.org/get-help. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages slow to respond

    https://www.thetrevorproject.org/pride, https://www.thetrevorproject.org/be-the-one and https://www.thetrevorproject.org/circle-of-light-archive took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 31 found) and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

3 to fixGoogle 5476
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=17525614&Ver=2&mid=1afd6115-4762-4b21-aa1b-5a76c0833b31&bo=1&sid=56267ec0d30d11f184b189ec2c7c9b9d&vid=56267c30d30d11f1b83fdf184e953ebf&vids=1&msclkid=N&pi=918639831&lg.

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://api-sr.amplitude.com/sessions/v2/track?device_id=8a16a68c-4372-4b39-917f-a87284b372a2&sessi…”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

2 checks passed
  • Tap targets are thumb-sized

    7 of 7 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • Thin social proof

    Social proof on the homepage: 8 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No risk reducer

    No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

  • About 483 words of copy

    The homepage carries about 483 words of visible text.

3 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Learn More”, “Subscribe” and “Contact Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager, Microsoft Clarity and Amplitude.

Privacy and tracking

1 to fix
  • 14 trackers load before any consent

    14

    Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and Hotjar and 9 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

  • 28 cookies set on arrival

    28

    Opening the homepage sets 28 cookies (measured from a US location before any click).

  • No consent tool detected

    No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

  • 46 other companies contacted

    Loading the homepage contacts 46 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at thetrevorproject.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager | Amplitude | Microsoft Clarity
Hosting
Cloudflare

Hiring

Hiring
8 open roles
Teams
Crisis Services (2), Community Philanthropy (1), Development Ops (1), Finance (1)
Job board
lever

Company

Employees
781
Founded
1998
Headquarters
West Hollywood

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on thetrevorproject.org, including 22 speed issues, 1 SEO issue and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25