trinityra.org website review

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

16 images could be 803 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.7 s faster on a phone.

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

7 third-party services load with your homepage (Google Tag Manager, Other Google APIs/SDKs and Google CDN and others), adding 22.0 MB and 116 ms of main-thread time.

revize.com costs a phone 0 ms of main-thread work and 21.6 MB 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.

Your mobile performance score is 68. Pages that score under 90 lose visitors before the first paint.

About 188 KiB of JavaScript is downloaded but never used on this page.

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

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

33 KiB could be saved by minifying JavaScript.

About 18 KiB of CSS is downloaded but never applied on this page.

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.

4 KiB could be saved by minifying CSS.

Your largest element takes 121.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 22.5 MB in 157 requests on a phone: images 21.4 MB (44), scripts 564 KiB (26) and other files 382 KiB (68). Under 2 MB keeps phones on slow connections fast.

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

1 button has no accessible name, so screen readers announce just “button”.

9 tap targets are too small or too close together to hit reliably with a finger.

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

1 image has no alt text, which hurts accessibility and image search.

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

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

ARIA role should be appropriate for the element: 15 elements on the page fail this check, rated minor by axe-core.

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 2 <h1> headlines (“Trinity River Authority, TX” and “RZ.module = 'global'; RZ.nexturl = 'editforms/hea…”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your meta description is 246 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://trinityra.org/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at trinityra.org/robots.txt, the first file search crawlers ask for.

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

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 125 pages on trinityra.org and 25 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://trinityra.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://trinityra.org/services/report_odors.php, https://trinityra.org/contact_us/index.php, https://trinityra.org/career_opportunities/index.php, https://trinityra.org/about_us.php, https://trinityra.org/our_history.php and https://trinityra.org/our_mission_and_vision.php and 9 others all use the title “Trinity River Authority, TX”. Search engines can't tell which page to show for a search, so each competes with the others.

https://trinityra.org/services/report_odors.php, https://trinityra.org/contact_us/index.php, https://trinityra.org/career_opportunities/index.php, https://trinityra.org/about_us.php, https://trinityra.org/our_history.php and https://trinityra.org/our_mission_and_vision.php and 9 others use the same meta description. A description written for each page earns more clicks.

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

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

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 ()”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage shows no opening hours. If customers visit or call, show when.

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

The homepage carries about 392 words of visible text.

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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 2 cookies (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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.