hcfcd.org website review

About 799 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.3 s faster on a phone.

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

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

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

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

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

8 third-party services load with your homepage (Google Tag Manager, curator.io and Other Google APIs/SDKs and others), adding 1.2 MB and 705 ms of main-thread time.

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

57 KiB could be saved by minifying JavaScript.

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

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

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

8 KiB could be saved by minifying CSS.

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

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.

Your largest element takes 23.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “⏸ Pause carousel”.

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

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

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

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

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

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 6.3 MB in 142 requests on a phone: images 3.3 MB (44), scripts 1.6 MB (37) and other files 991 KiB (36). Under 2 MB keeps phones on slow connections fast.

17 images are downloaded at several times the size a phone draws them, for example 72185251-3207-4775-ba4c-4ba092889797_resized.jpg at 3,200 px wide, shown at 320 px. Resized copies would save about 2.1 MB.

18 images further down the page (2.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

1 image (385 KiB) is 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.

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

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

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

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

Heading levels should only increase by one: 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.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

The robots meta tag says “NOINDEX, NOFOLLOW”: Google is told not to list this page at all.

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Google's crawler is blocked from indexing this page.

Your title is only 5 characters: “HCFCD”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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

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

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

Open Graph is missing og:title and og:description, so shared links fall back to guesses.

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

The homepage links to 326 pages on hcfcd.org and 17 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 /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.

/About and /About/About-the-Flood-Control-District all use the title “About the Flood Control District”. Search engines can't tell which page to show for a search, so each competes with the others.

/About/Harris-Countys-Flooding-History/Hurricane-Harvey, /About/Harris-Countys-Flooding-History/Countywide-Impacts and /About/Harris-Countys-Flooding-History/Roles-Responsibilities have no meta description, so Google writes the search snippet from whatever text it finds.

/About and /About/About-the-Flood-Control-District use the same meta description. A description written for each page earns more clicks.

/Community/Contact-Us/Service-Request, /About/Flood-Damage-Reduction-Tools, /About/Flood-Damage-Reduction-Tools/Structural-Tools and /About/Harris-Countys-Flooding-History/Countywide-Impacts took over 3 s to send their HTML from our server.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn.curator.io/5.0/curator.embed.css' from origin 'https://www.hcfcd.org' has been…”.

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

Large scripts ship without source maps.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

hcfcd.org has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

hcfcd.org's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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.

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

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

hcfcd.org has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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