Website review, no card needed

cravencountync.gov logo

cravencountync.gov website review

Visit site (opens in a new tab)Reviewed 2 November 202652 issues · 100 checks

This review found 52 issues worth fixing on cravencountync.gov, 19 of them high impact, across 100 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
3.0 s2.4 sMay 16Oct 312.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.8 s
May 23, 20262.7 s
May 30, 20262.6 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.6 s
Jul 11, 20262.6 s
Jul 18, 20262.6 s
Jul 25, 20262.6 s
Aug 1, 20262.6 s
Aug 8, 20262.6 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.6 s
Sep 12, 20262.7 s
Sep 19, 20262.7 s
Sep 26, 20262.8 s
Oct 3, 20262.8 s
Oct 10, 20262.8 s
Oct 17, 20262.8 s
Oct 24, 20262.9 s
Oct 31, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
157 ms125 msMay 16Oct 31139 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026135 ms
May 23, 2026140 ms
May 30, 2026138 ms
Jun 6, 2026138 ms
Jun 13, 2026139 ms
Jun 20, 2026134 ms
Jun 27, 2026131 ms
Jul 4, 2026130 ms
Jul 11, 2026129 ms
Jul 18, 2026132 ms
Jul 25, 2026133 ms
Aug 1, 2026136 ms
Aug 8, 2026142 ms
Aug 15, 2026141 ms
Aug 22, 2026139 ms
Aug 29, 2026144 ms
Sep 5, 2026141 ms
Sep 12, 2026144 ms
Sep 19, 2026153 ms
Sep 26, 2026149 ms
Oct 3, 2026147 ms
Oct 10, 2026146 ms
Oct 17, 2026140 ms
Oct 24, 2026139 ms
Oct 31, 2026139 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 cravencountync.gov (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cravencountync.gov at 1.2 s1.2 s
  2. cravencountync.gov at 2.3 s2.3 s
  3. cravencountync.gov at 3.5 s3.5 s
  4. cravencountync.gov at 4.7 s4.7 s
  5. cravencountync.gov at 5.9 s5.9 s
  6. cravencountync.gov at 7.0 s7.0 s
  7. cravencountync.gov at 8.2 s8.2 s
  8. cravencountync.gov at 9.4 s9.4 s

Speed

15 to fix35
  • Use efficient cache lifetimes

    18.6 s · 3.6 MB

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

  • Reduce unused JavaScript

    16.7 s · 3.3 MB

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

  • Render-blocking requests

    1.4 s

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

  • audioeye.com adds 1.3 s

    1.3 s

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

  • Reduce unused CSS

    1.1 s · 160 KiB

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

  • Mobile performance score: 35

    35/100

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

  • Main-thread work: 7.5 s

    A phone's processor spends 7.5 s on main-thread work while loading, 3.8 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, Google Tag Manager and polimorphic.com and others), adding 5.6 MB and 2.5 s of main-thread time.

  • Legacy JavaScript

    650 ms · 60 KiB

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

  • Google Tag Manager adds 598 ms

    598 ms

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

  • polimorphic.com adds 303 ms

    303 ms

    polimorphic.com costs a phone 303 ms of main-thread work and 3.5 MB 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.

  • Improve image delivery

    500 ms · 150 KiB

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

  • 19 long tasks on the main thread

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

  • Minify JavaScript

    450 ms · 82 KiB

    82 KiB could be saved by minifying JavaScript.

  • docaccess.com adds 52 ms

    52 ms

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

  • 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: 25 ms

    25 ms

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

Core Web Vitals

9 to fix67
  • 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: 39.0 s

    39.0 s

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

  • Speed Index: 22.2 s

    22.2 s

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

  • Time to Interactive: 46.4 s

    46.4 s

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

  • Total Blocking Time: 1.5 s

    1.5 s

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

  • Real-user LCP: 3.1 s

    3.1 s

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

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

    2.9 s

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

  • 31 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) held steady for real visitors

    +6%

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

4 checks passed
  • Real-user INP: 140 ms

    140 ms

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

    0.01

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

Images and page weight

5 to fix28
  • Page weight: 8.8 MB in 159 requests

    8.8 MB

    Your homepage downloads 8.8 MB in 159 requests on a phone: scripts 5.4 MB (73), images 2.3 MB (35) and fonts 505 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    Document weighs 960 KiB. On a phone connection a single image that size takes seconds.

  • 7 images in older formats

    7 images (2.1 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 (1.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 3 images far larger than shown

    478 KiB

    3 images are downloaded at several times the size a phone draws them, for example Document at 940 px wide, shown at 280 px. Resized copies would save about 478 KiB.

  • About 2.5 g of CO₂ per visit

    2.49 g

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

Accessibility

8 to fixGoogle 8991
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • Hidden but focusable

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

  • Links must have discernible text (1 element)

    Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

  • [role]s are not contained by their required parent element

    [role]s are not contained by their required parent element (2 elements).

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

    All page content should be contained by landmarks: 12 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 (3 elements)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 elements on the page fail 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.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails 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.

  • Elements with role="none" or role="presentation" have conflicts

    Elements with role="none" or role="presentation" have conflicts (2 elements).

2 checks passed
  • Every image has alt text

    All 30 images in the HTML carry an alt attribute.

  • 56 automated accessibility rules passed

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

SEO

5 to fixGoogle 8374
  • No meta description

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

  • 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 (“COMMON SERVICES”, “CRAVEN COUNTY NEWS” and “UPCOMING 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.

  • 112 internal links, 6 external

    The homepage links to 112 pages on cravencountync.gov and 6 external pages.

3 checks passed
  • Title: 32 characters

    Your title is a healthy 32 characters: “Craven County | 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.cravencountync.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.cravencountync.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,060 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 6 pages without a meta description

    https://www.cravencountync.gov/list.aspx, https://www.cravencountync.gov/billpay, https://www.cravencountync.gov/2406/Health, https://www.cravencountync.gov/2405/Social-Services, https://www.cravencountync.gov/303/register-of-deeds and https://www.cravencountync.gov/CivicAlerts.aspx have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page with very little text

    https://www.cravencountync.gov/142/Contact-Us 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.

  • 7 pages slow to respond

    https://www.cravencountync.gov/35/Departments, https://www.cravencountync.gov/list.aspx, https://www.cravencountync.gov/142/Contact-Us, https://www.cravencountync.gov/billpay, https://www.cravencountync.gov/357/Permitting-Process and https://www.cravencountync.gov/2404/Sheriffs-Office and 1 other took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 25 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

4 to fixGoogle 5086
  • 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.”).

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://wsv3cdn.audioeye.com/static-scripts/v2/2026-10-30/compliance.css' from origin 'htt…”.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Missing source maps

    Large scripts ship without source maps.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    93 of 94 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix86
  • 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: 1 trust badge. 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.

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

    The homepage carries about 1,367 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: “Submit Service Request | Report Issue” and “Contact Us”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Submit Service Request | Report Issue”, “Contact Us” and “Register of Deeds”.

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

  • 21 cookies set on arrival

    21

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

  • 26 other companies contacted

    Loading the homepage contacts 26 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 cravencountync.gov, 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 | Google Tag Manager
Hosting
Cloudflare

Company

Founded
1712

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 52 issues on cravencountync.gov, including 24 speed issues, 5 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