tid.org website review

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

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

7 files are served with short cache lifetimes, so returning visitors download them again (387 KiB).

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

6 images could be 931 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

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

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

YouTube costs a phone 429 ms of main-thread work and 990 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.

Google Tag Manager costs a phone 319 ms of main-thread work and 523 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.

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

Google Maps costs a phone 173 ms of main-thread work and 397 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.

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

Polyfills for old browsers add 11 KiB JavaScript that modern phones do not need.

9 KiB could be saved by minifying CSS.

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

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

Your largest element takes 20.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Bucket truck with power plant and corn field in the backgro…”.

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

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

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

4 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-31, real Chrome visitors' tap response (inp) went from 99 ms to 101 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

DSF4898-2-scaled.jpg weighs 645 KiB. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example DSF4898-2-scaled.jpg at 2,560 px wide, shown at 374 px. Resized copies would save about 757 KiB.

Your homepage downloads 3.6 MB in 109 requests on a phone: scripts 2.1 MB (34), images 1.1 MB (22) and stylesheets 242 KiB (22). Under 2 MB keeps phones on slow connections fast.

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

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

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

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

Your title is only 24 characters: “Home - TID Water & Power”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is only 24 characters: “Home - TID Water & Power”. 70 to 160 characters is enough to sell the click.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link has no real href, so search engines can't follow it.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 172 pages on tid.org and 19 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

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

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

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

5 errors were logged to the browser console while the page loaded, for example “gform is not defined”.

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

Social proof on the homepage: 4 trust badges. 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.

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 271 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, 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 4 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 26 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.