Website review, no card needed

dentoncounty.gov logo

dentoncounty.gov website review

Visit site (opens in a new tab)Reviewed 27 October 202653 issues · 103 checks

This review found 53 issues worth fixing on dentoncounty.gov, 24 of them high impact, across 103 checks. The most urgent: improve image delivery. 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
2.2 s1.9 sMay 9Oct 242.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.0 s
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.1 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.1 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.1 s
Aug 1, 20262.0 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.1 s
Sep 5, 20262.1 s
Sep 12, 20262.1 s
Sep 19, 20262.1 s
Sep 26, 20262.2 s
Oct 3, 20262.1 s
Oct 10, 20262.1 s
Oct 17, 20262.1 s
Oct 24, 20262.1 s
Real-visitor tap response (INP)75th percentile, phones
114 ms107 msMay 9Oct 24108 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026108 ms
May 16, 2026111 ms
May 23, 2026112 ms
May 30, 2026112 ms
Jun 6, 2026111 ms
Jun 13, 2026111 ms
Jun 20, 2026112 ms
Jun 27, 2026112 ms
Jul 4, 2026113 ms
Jul 11, 2026112 ms
Jul 18, 2026110 ms
Jul 25, 2026110 ms
Aug 1, 2026110 ms
Aug 8, 2026110 ms
Aug 15, 2026112 ms
Aug 22, 2026112 ms
Aug 29, 2026112 ms
Sep 5, 2026113 ms
Sep 12, 2026113 ms
Sep 19, 2026112 ms
Sep 26, 2026113 ms
Oct 3, 2026112 ms
Oct 10, 2026112 ms
Oct 17, 2026110 ms
Oct 24, 2026108 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 dentoncounty.gov (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. dentoncounty.gov at 0.8 s0.8 s
  2. dentoncounty.gov at 1.6 s1.6 s
  3. dentoncounty.gov at 2.4 s2.4 s
  4. dentoncounty.gov at 3.3 s3.3 s
  5. dentoncounty.gov at 4.1 s4.1 s
  6. dentoncounty.gov at 4.9 s4.9 s
  7. dentoncounty.gov at 5.7 s5.7 s
  8. dentoncounty.gov at 6.5 s6.5 s

Speed

14 to fix38
  • Improve image delivery

    11.1 s · 2.4 MB

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

  • Render-blocking requests

    2.0 s

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

  • Use efficient cache lifetimes

    1.1 s · 545 KiB

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

  • audioeye.com adds 1.2 s

    1.2 s

    audioeye.com costs a phone 1.2 s of main-thread work and 363 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.

  • Mobile performance score: 38

    38/100

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

  • Main-thread work: 9.2 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (audioeye.com, YouTube and Google Tag Manager and others), adding 2.3 MB and 2.8 s of main-thread time.

  • Reduce unused JavaScript

    750 ms · 1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

  • Reduce unused CSS

    600 ms · 239 KiB

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

  • YouTube adds 696 ms

    696 ms

    YouTube costs a phone 696 ms of main-thread work and 972 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 adds 548 ms

    548 ms

    Google Tag Manager costs a phone 548 ms of main-thread work and 470 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 on the main thread

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

  • 2,105 HTML elements

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

  • docaccess.com adds 107 ms

    107 ms

    docaccess.com costs a phone 107 ms of main-thread work and 389 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.

  • Minify JavaScript

    84 KiB

    84 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    44 KiB

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

  • Forced reflow

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

1 checks passed
  • Server response: 66 ms

    66 ms

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

Core Web Vitals

8 to fix100
  • Fails Core Web Vitals for real visitors

    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.

  • Largest Contentful Paint: 19.1 s

    19.1 s

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

  • Speed Index: 15.8 s

    15.8 s

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

  • Time to Interactive: 28.3 s

    28.3 s

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

  • Total Blocking Time: 1.2 s

    1.2 s

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

  • Real-user TTFB: 1.0 s

    1.0 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • 22 images without width and height

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

5 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 139 ms

    139 ms

    Real visitors wait 139 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.01

    0.01

    For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.6 s

    1.6 s

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

  • Cumulative Layout Shift: 0.005

    0.005

    The layout barely moves while loading (CLS 0.005, good is under 0.1).

Images and page weight

4 to fix25
  • Page weight: 6.4 MB in 118 requests

    6.4 MB

    Your homepage downloads 6.4 MB in 118 requests on a phone: images 3.1 MB (34), scripts 2.4 MB (42) and other files 419 KiB (17). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Document weighs 2.4 MB. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    1.5 MB

    2 images are downloaded at several times the size a phone draws them, for example Document at 1,920 px wide, shown at 390 px. Resized copies would save about 1.5 MB.

  • 2 images in older formats

    2 images (2.4 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.

  • 1 image below the first screen load straight away

    1 image further down the page (79 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.8 g of CO₂ per visit

    1.81 g

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

Accessibility

11 to fixGoogle 7887
  • ARIA attributes must conform to valid values (9 elements)

    ARIA attributes must conform to valid values: 9 elements on the page fail this check, rated critical by axe-core.

  • Certain ARIA roles must be contained by particular parents (4 elements)

    Certain ARIA roles must be contained by particular parents: 4 elements on the page fail this check, rated critical by axe-core.

  • 5 text elements with low contrast

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

  • 5 tap targets too small

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

  • Links must have discernible text (2 elements)

    Links must have discernible text: 2 elements on the page fail this check, rated serious by axe-core.

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

    Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (1 element).

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • 5 form fields without a label

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

  • Elements marked as presentational should be consistently ignored (9 elements)

    Elements marked as presentational should be consistently ignored: 9 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 20 images in the HTML carry an alt attribute.

  • 57 automated accessibility rules passed

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

SEO

4 to fixGoogle 9284
  • No structured data

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

  • 4 H1 headlines

    There are 4 <h1> headlines (“HOW CAN I…”, “News & Events” and “Calendar of Events”). 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 X (Twitter) card tag

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

  • 144 internal links, 33 external

    The homepage links to 144 pages on dentoncounty.gov and 33 external pages.

4 checks passed
  • Meta description: 131 characters

    Your meta description is 131 characters: “Denton County will be recognized as the leader in local government through its excellent service to citizens and qualit…”.

  • Title: 36 characters

    Your title is a healthy 36 characters: “Denton County, TX | Official Website”.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.dentoncounty.gov/sitemap.xml.

AI search readiness

2 to fix70
  • 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.

  • Parts of the site are closed to 3 AI crawlers

    Your robots.txt lets ChatGPT search (OAI-SearchBot), Claude search (Claude-SearchBot) and Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.

  • No llms.txt

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

1 checks passed
  • Text is in the HTML

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

Other pages

1 to fix95
  • 2 pages without a meta description

    https://www.dentoncounty.gov/agendacenter and https://www.dentoncounty.gov/list.aspx have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page with very little text

    https://www.dentoncounty.gov/1021/Elections 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 81 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    13 pages of 15 loaded without an error (the rest turned automated requests away).

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

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

5 to fixGoogle 5469
  • 3 broken images

    3 images failed to load on a phone, for example https://www.dentoncounty.gov/Common/images/ajax-loader.gif.

  • 8 small tap targets

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

  • 5 third-party cookies

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

  • Deprecated browser APIs

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

  • 2 JavaScript errors while loading

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

  • 2 low-resolution images

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

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix64
  • No call to action on the first screen

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

  • No social proof

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

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

  • No opening hours

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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

4 checks passed
  • 11 calls to action

    The homepage has 11 calls to action, for example “Apply for”, “Register for” and “Request”.

  • 2 short forms

    2 short forms (0 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

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.

  • 20 cookies set on arrival

    20

    Opening the homepage sets 20 cookies, 1 of them by other companies (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.

  • 19 other companies contacted

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

Upkeep, stack and company

Stack

Hosting
Cloudflare

Company

Founded
1846

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 53 issues on dentoncounty.gov, including 22 speed issues, 4 SEO issues and 3 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