Website review, no card needed
co.delaware.oh.us website review
Visit site (opens in a new tab)Reviewed 29 October 202628 issues · 82 checks
This review found 28 issues worth fixing on co.delaware.oh.us, 11 of them high impact, across 82 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 1.9 s |
| Jun 20, 2026 | 1.9 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 95 ms |
| May 16, 2026 | 96 ms |
| May 23, 2026 | 99 ms |
| May 30, 2026 | 97 ms |
| Jun 6, 2026 | 94 ms |
| Jun 13, 2026 | 96 ms |
| Jun 20, 2026 | 96 ms |
| Jun 27, 2026 | 103 ms |
| Jul 4, 2026 | 119 ms |
| Jul 11, 2026 | 125 ms |
| Jul 18, 2026 | 121 ms |
| Jul 25, 2026 | 125 ms |
| Aug 1, 2026 | 117 ms |
| Aug 8, 2026 | 112 ms |
| Aug 15, 2026 | 128 ms |
| Aug 22, 2026 | 138 ms |
| Aug 29, 2026 | 127 ms |
| Sep 5, 2026 | 128 ms |
| Sep 12, 2026 | 105 ms |
| Sep 19, 2026 | 96 ms |
| Sep 26, 2026 | 94 ms |
| Oct 3, 2026 | 87 ms |
| Oct 10, 2026 | 92 ms |
| Oct 17, 2026 | 95 ms |
| Oct 24, 2026 | 104 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Use efficient cache lifetimes
14.3 s · 2.8 MB43 files are served with short cache lifetimes, so returning visitors download them again (2.8 MB).
Reduce unused JavaScript
5.8 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.8 s faster on a phone.
Reduce unused CSS
3.1 s · 539 KiBAbout 539 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.1 s faster on a phone.
Mobile performance score: 47
47/100Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
800 ms · 201 KiB4 images could be 201 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.
Minify JavaScript
690 ms · 160 KiB160 KiB could be saved by minifying JavaScript.
Render-blocking requests
700 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.
Legacy JavaScript
500 ms · 104 KiBPolyfills for old browsers add 104 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 500 ms faster on a phone.
Minify CSS
450 ms · 71 KiB71 KiB could be saved by minifying CSS.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, userway.org and Amazon Web Services and others), adding 811 KiB and 218 ms of main-thread time.
Font display
200 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 200 ms).
Document request latency
93 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 77 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 447 ms of it running JavaScript. That is comfortably low.
Server response: 78 ms
78 msYour server sent the HTML in 78 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 21.7 s
21.7 sYour largest element takes 21.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 21.7 s
21.7 sThe page becomes fully interactive after 21.7 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.738
0.738The layout shifts by 0.738 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Speed Index: 3.9 s
3.9 sVisually, the page fills in at 3.9 s (Speed Index). Good is under 3.4 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 95 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 111 ms
111 msReal visitors wait 111 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.2 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 32 ms
32 msScripts block the page for only 32 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.7 MB in 74 requests
3.7 MBYour homepage downloads 3.7 MB in 74 requests on a phone: scripts 1.7 MB (30), fonts 694 KiB (5) and images 612 KiB (8). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (86 KiB) 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.
2 images below the first screen load straight away
2 images further down the page (86 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.1 g of CO₂ per visit
1.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.06 g of CO₂e: 127.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 5 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (22 characters)
Your title is only 22 characters: “Home - Delaware County”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (38 characters)
Your meta description is only 38 characters: “Delaware County Ohio County Government”. 70 to 160 characters is enough to sell the click.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
33 internal links, 27 external
The homepage links to 33 pages on co.delaware.oh.us and 27 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Delaware County, Ohio – It’s where you should be”.
Canonical URL set
The canonical URL is https://co.delaware.oh.us/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://co.delaware.oh.us/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
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.
No llms.txt
There is no https://co.delaware.oh.us/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 (801 words), so crawlers that don't run JavaScript still read it.
Other pages
10 pages without a meta description
https://co.delaware.oh.us/contactus, https://co.delaware.oh.us/cities, https://co.delaware.oh.us/media-room/forms, https://co.delaware.oh.us/media-room/bids, https://co.delaware.oh.us/delaware-county-public-records-requests and https://co.delaware.oh.us/media-room and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 18 found) and read each the way a search engine does.
6 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.
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 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://co.delaware.oh.us/.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
12 of 13 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 323 words of copy
The homepage carries about 323 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT US”.
4 calls to action
The homepage has 4 calls to action, for example “Contact Us”, “Contact” and “CONTACT US”.
1 short form
A short form (2 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
2 trackers load before any consent
2Before 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.
7 cookies set on arrival
7Opening the homepage sets 7 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.
14 other companies contacted
Loading the homepage contacts 14 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 co.delaware.oh.us, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- Oarnet
Company
- Founded
- 1808
- Headquarters
- Delaware
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on co.delaware.oh.us, including 17 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.