Website review, no card needed
harrisgovern.com website review
Visit site (opens in a new tab)Reviewed 25 October 202636 issues · 83 checks
This review found 36 issues worth fixing on harrisgovern.com, 18 of them high impact, across 83 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
72CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
1.1 s
2.2 s
3.3 s
4.4 s
5.5 s
6.6 s
7.7 s
8.8 s
Speed
Use efficient cache lifetimes
8.0 s · 1.8 MB50 files are served with short cache lifetimes, so returning visitors download them again (1.8 MB).
Improve image delivery
4.1 s · 897 KiB6 images could be 897 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 4.1 s faster on a phone.
Render-blocking requests
2.3 s23 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Font display
1.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).
Mobile performance score: 58
58/100Your mobile performance score is 58 (desktop: 81). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
610 ms · 135 KiBAbout 135 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 610 ms faster on a phone.
Reduce unused JavaScript
450 ms · 100 KiBAbout 100 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Minify JavaScript
160 ms · 10 KiB10 KiB could be saved by minifying JavaScript.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, Google Fonts and Cloudflare CDN and others), adding 313 KiB and 121 ms of main-thread time.
Document request latency
89 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 89 ms. During a long task the page ignores taps.
Minify CSS
10 ms · 6 KiB6 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.
2 checks passed
Main-thread work: 0.8 s
A phone's processor spends 0.8 s on main-thread work while loading, 262 ms of it running JavaScript. That is comfortably low.
Server response: 254 ms
254 msYour server sent the HTML in 254 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 14.3 s
14.3 sYour largest element takes 14.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Harris Govern Modern Software for a Smarter, More Efficient…”. Most of its time is resource load delay (7.1 s).
Speed Index: 13.8 s
13.8 sVisually, the page fills in at 13.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 14.3 s
14.3 sThe page becomes fully interactive after 14.3 s. Good is under 3.8 s.
First Contentful Paint: 3.9 s
3.9 sThe first text or image appears after 3.9 s on a phone. Good is under 1.8 s.
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
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.
2 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 45 ms
45 msScripts block the page for only 45 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.2 MB in 59 requests
2.2 MBYour homepage downloads 2.2 MB in 59 requests on a phone: images 1.1 MB (7), fonts 498 KiB (5) and scripts 349 KiB (23). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (37 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.
About 0.6 g of CO₂ per visit
0.62 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.62 g of CO₂e: 74.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
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.
ARIA attributes must conform to valid values (1 element)
ARIA attributes must conform to valid values: 1 element on the page fails 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.
ARIA input fields must have an accessible name (4 elements)
ARIA input fields must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.
ARIA toggle fields must have an accessible name (4 elements)
ARIA toggle fields must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Hidden but focusable
3 elements hidden from screen readers can still receive keyboard focus.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h4 and h3 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 22 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 60 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 12 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (20 characters)
Your title is only 20 characters: “Home - Harris Govern”. Between 30 and 65 characters leaves room to say what you do and for whom.
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.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
159 internal links, 158 external
The homepage links to 159 pages on harrisgovern.com and 158 external pages.
6 checks passed
Meta description: 134 characters
Your meta description is 134 characters: “The Industry Leader in Property Appraisal and Tax Software. Trusted by more than 300 counties and municipalities around…”.
One H1 headline
Your main headline reads: “Harris Govern”.
Canonical URL set
The canonical URL is https://www.harrisgovern.com/.
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://www.harrisgovern.com/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://www.harrisgovern.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,302 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.harrisgovern.com/business-tax-billing-and-collection-software and https://www.harrisgovern.com/mobile-software all use the title “Business Tax Software | Intelligent Tax Automation for Government”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages slow to respond
https://www.harrisgovern.com/gis-deeds-services and https://www.harrisgovern.com/harris-govern-online 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
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://www.harrisgovern.com/.
4 small tap targets
4 of 11 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 6 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
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 791 words of copy
The homepage carries about 791 words of visible text.
3 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact Us” and “Contact”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
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.
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.
5 other companies contacted
Loading the homepage contacts 5 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 harrisgovern.com, 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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on harrisgovern.com, including 12 speed issues, 3 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.