Website review, no card needed

hcdistrictclerk.com logo

hcdistrictclerk.com website review

Visit site (opens in a new tab)Reviewed 11 October 202644 issues · 88 checks

This review found 44 issues worth fixing on hcdistrictclerk.com, 13 of them high impact, across 88 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
1.6 s1.2 sApr 18Oct 31.3 s
Show as table
DateReal-visitor load time (LCP)
Apr 18, 20261.3 s
Apr 25, 20261.3 s
May 2, 20261.3 s
May 9, 20261.3 s
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.5 s
Jun 13, 20261.5 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.4 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.4 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
152 ms87 msApr 18Oct 3138 ms
Show as table
DateReal-visitor tap response (INP)
Apr 18, 202694 ms
Apr 25, 202694 ms
May 2, 202694 ms
May 9, 202695 ms
May 16, 202697 ms
May 23, 2026103 ms
May 30, 2026104 ms
Jun 6, 2026123 ms
Jun 13, 2026132 ms
Jun 20, 2026131 ms
Jun 27, 2026138 ms
Jul 4, 2026125 ms
Jul 11, 2026119 ms
Jul 18, 2026129 ms
Jul 25, 2026126 ms
Aug 1, 2026129 ms
Aug 8, 2026130 ms
Aug 15, 2026121 ms
Aug 22, 2026127 ms
Aug 29, 2026125 ms
Sep 5, 2026130 ms
Sep 12, 2026137 ms
Sep 19, 2026137 ms
Sep 26, 2026144 ms
Oct 3, 2026138 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 hcdistrictclerk.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hcdistrictclerk.com at 0.4 s0.4 s
  2. hcdistrictclerk.com at 0.8 s0.8 s
  3. hcdistrictclerk.com at 1.1 s1.1 s
  4. hcdistrictclerk.com at 1.5 s1.5 s
  5. hcdistrictclerk.com at 1.9 s1.9 s
  6. hcdistrictclerk.com at 2.3 s2.3 s
  7. hcdistrictclerk.com at 2.6 s2.6 s
  8. hcdistrictclerk.com at 3.0 s3.0 s

Speed

10 to fix59
  • Use efficient cache lifetimes

    4.8 s · 4.5 MB

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

  • Improve image delivery

    2.2 s · 809 KiB

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

  • Reduce unused JavaScript

    2.3 s · 535 KiB

    About 535 KiB 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.

  • Render-blocking requests

    2.0 s

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

  • Mobile performance score: 59

    59/100

    Your mobile performance score is 59 (desktop: 72). Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Maps, Other Google APIs/SDKs and Google Tag Manager and others), adding 1,012 KiB and 739 ms of main-thread time.

  • Reduce unused CSS

    300 ms · 74 KiB

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

  • Google Maps adds 303 ms

    303 ms

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

  • Other Google APIs/SDKs adds 227 ms

    227 ms

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

  • Main-thread work: 2.4 s

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

  • Legacy JavaScript

    200 ms · 11 KiB

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

  • Font display

    200 ms

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

  • Minify CSS

    150 ms · 16 KiB

    16 KiB could be saved by minifying CSS.

  • Minify JavaScript

    150 ms · 10 KiB

    10 KiB could be saved by minifying JavaScript.

  • 9 long tasks on the main thread

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

  • 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.

1 checks passed
  • Server response: 40 ms

    40 ms

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

Core Web Vitals

8 to fix100
  • Largest Contentful Paint: 13.5 s

    13.5 s

    Your largest element takes 13.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Fraud Alert. The District Clerk's Office will never text or…”.

  • Time to Interactive: 19.3 s

    19.3 s

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

  • First Contentful Paint: 3.4 s

    3.4 s

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

  • Tap response (INP) got 50% slower for real visitors

    +50%

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

  • Speed Index: 4.7 s

    4.7 s

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

  • 15 images without width and height

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

  • Cumulative Layout Shift: 0.105

    0.105

    The layout shifts by 0.105 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 206 ms

    206 ms

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

  • Largest content (LCP) held steady for real visitors

    0%

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

6 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.5 s

    1.5 s

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

  • Real-user INP: 88 ms

    88 ms

    Real visitors wait 88 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.

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 546 ms

    546 ms

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

Images and page weight

5 to fix18
  • Page weight: 5.5 MB in 95 requests

    5.5 MB

    Your homepage downloads 5.5 MB in 95 requests on a phone: images 4.2 MB (36), scripts 1.1 MB (36) and fonts 152 KiB (2). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 1.7 MB together. On a phone connection a single image that size takes seconds.

  • 6 images far larger than shown

    659 KiB

    6 images are downloaded at several times the size a phone draws them, for example fraudalert.jpg at 4,219 px wide, shown at 390 px. Resized copies would save about 659 KiB.

  • 14 images in older formats

    14 images (4.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.

  • 5 images below the first screen load straight away

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

  • About 1.6 g of CO₂ per visit

    1.57 g

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

Accessibility

3 to fixGoogle 9795
  • 10 tap targets too small

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

  • 1 image without alt text

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

  • All page content should be contained by landmarks (3 elements)

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

9 to fixGoogle 8360
  • No meta description

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

  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “Office of Harris County District Clerk - Marilyn Burgess | Home Page”.

  • No structured data

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

  • 3 H1 headlines

    There are 3 <h1> headlines (“Header”, “Main content” and “Footer”). One clear main headline is easier for people and search engines.

  • No canonical URL

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

  • No social preview image

    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

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

  • No favicon declared

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

  • 1 link with vague text

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

  • No X (Twitter) card tag

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

  • 107 internal links, 11 external

    The homepage links to 107 pages on hcdistrictclerk.com and 11 external pages.

1 checks passed
  • robots.txt in place

    robots.txt is in place.

AI search readiness

1 to fix88
  • No Organization structured data

    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.

  • No llms.txt

    There is no https://hcdistrictclerk.com/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.

2 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.

  • Text is in the HTML

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://hcdistrictclerk.com/jury/juror.html has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://hcdistrictclerk.com/jury/juror.html has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://hcdistrictclerk.com/jury/juror.html has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

5 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 1 page that loaded have a <title>.

Best practices

3 to fixGoogle 7785
  • 15 small tap targets

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

  • Deprecated browser APIs

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

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://www.google.com/cse/static/element/f71e4ed980f4c082/default+en.css' from origin 'ht…”.

  • 8 low-resolution images

    8 images are served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • Local business without LocalBusiness data

    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.

  • Thin social proof

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

  • No opening hours

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

  • 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 1,302 words of copy

    The homepage carries about 1,302 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us” and “Contact Information”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact Us” and “Contact Information”.

  • 1 short form

    A short form (2 fields at most) is right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link and 2 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    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.

  • 4 cookies set on arrival

    4

    Opening the homepage sets 4 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.

  • 17 other companies contacted

    Loading the homepage contacts 17 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 hcdistrictclerk.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on hcdistrictclerk.com, including 18 speed issues, 9 SEO issues and 2 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