trcp.org website review

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

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

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

3.0 MB JavaScript is shipped twice across bundles. Google estimates it would make the page about 2.5 s faster on a phone.

710 KiB could be saved by minifying JavaScript.

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

Google CDN costs a phone 1.8 s of main-thread work and 4.9 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.

YouTube costs a phone 1.5 s of main-thread work and 4.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.

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

cloudfront.net costs a phone 1.3 s of main-thread work and 695 KiB 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.

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

The page has 4,454 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (Google CDN, YouTube and cloudfront.net and others), adding 11.1 MB and 6.1 s of main-thread time.

About 277 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 740 ms faster on a phone.

Other Google APIs/SDKs costs a phone 352 ms of main-thread work and 537 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.

csidetm.com costs a phone 339 ms of main-thread work and 15 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.

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

17 KiB could be saved by minifying CSS.

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

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

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

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

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.

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

Your largest element takes 53.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “…”.

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

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

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

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

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

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

3 images have no width and height attributes, so the layout jumps as each one loads.

Your homepage downloads 29.9 MB in 422 requests on a phone: images 13.9 MB (139), scripts 10.7 MB (85) and other files 2.3 MB (91). Under 2 MB keeps phones on slow connections fast.

26 images (1.8 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 further down the page (295 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image is downloaded at several times the size a phone draws it, for example Steven-Rinella-ITA-2.png at 420 px wide, shown at 137 px. Resized copies would save about 4 KiB.

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

31 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

Some lists contain elements other than list items, which screen readers announce wrongly.

4 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 25 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

13 visible links have no text or label, so screen readers cannot say where they go.

2 frames have no title, so screen-reader users cannot tell what they contain.

Headings skip levels (h1 → h3, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.

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

Your title is 87 characters, so Google will cut it off around 60: “Theodore Roosevelt Conservation Partnership - Guaranteeing You a Place to Hunt and Fish”.

There are 4 <h1> headlines (“Farm Bill Conservation”, “Step Into The Arena” and “Conservation Economy”). One clear main headline is easier for people and search engines.

The homepage links to 178 pages on trcp.org and 26 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

There is no https://www.trcp.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.

https://www.trcp.org/action-alert/hunters-and-anglers-need-a-strong-bipartisan-farm-bill-in-2025 and https://www.trcp.org/action-alert/hunters-and-anglers-need-a-strong-bipartisan-farm-bill-in-2026 all use the title “Hunters and anglers need a strong, bipartisan Farm Bill in 2026 | The…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.trcp.org/what/hunting-fishing-access, https://www.trcp.org/unlocking-public-lands, https://www.trcp.org/public-land-access, https://www.trcp.org/chronic-wasting-disease, https://www.trcp.org/sage-grouse-conservation and https://www.trcp.org/2024/10/15/in-the-arena-ryan-sparks and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.trcp.org/action-alert/hunters-and-anglers-need-a-strong-bipartisan-farm-bill-in-2025, whose canonical is https://www.trcp.org/action-alert/hunters-and-anglers-need-a-strong-bipartisan-farm-bill-in-2026. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.trcp.org/2023/11/08/in-the-arena-brian-flynn-two-wolf-foundation, https://www.trcp.org/2024/10/15/in-the-arena-ryan-sparks, https://www.trcp.org/2025/09/17/in-the-arena-david-mangum, https://www.trcp.org/action-alert/hunters-and-anglers-need-a-strong-bipartisan-farm-bill-in-2025 and https://www.trcp.org/action-alert/hunters-and-anglers-need-a-strong-bipartisan-farm-bill-in-2026 have no <h1> headline, so visitors and search engines get no clear main topic.

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

9 of 23 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

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

Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

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

There is no form on the homepage, so every lead has to click through to another page first.

The homepage carries about 633 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight and 2 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.

Opening the homepage sets 10 cookies, 1 of them by other companies (measured from a US location before any click).

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.

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