Website review, no card needed

egov.com logo

egov.com website review

Visit site (opens in a new tab)Reviewed 4 November 202641 issues · 88 checks

This review found 41 issues worth fixing on egov.com, 19 of them high impact, across 88 checks. The most urgent: render-blocking requests. 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.5 s2.8 sMay 16Oct 312.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.3 s
May 23, 20263.4 s
May 30, 20263.3 s
Jun 6, 20263.2 s
Jun 13, 20263.3 s
Jun 20, 20263.2 s
Jun 27, 20263.3 s
Jul 4, 20263.3 s
Jul 11, 20263.3 s
Jul 18, 20263.3 s
Jul 25, 20263.3 s
Aug 1, 20263.3 s
Aug 8, 20263.2 s
Aug 15, 20263.2 s
Aug 22, 20263.0 s
Aug 29, 20262.9 s
Sep 5, 20262.9 s
Sep 12, 20262.9 s
Sep 19, 20262.9 s
Sep 26, 20263.0 s
Oct 3, 20263.0 s
Oct 10, 20263.0 s
Oct 17, 20262.9 s
Oct 24, 20262.9 s
Oct 31, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
163 ms134 msMay 16Oct 31142 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026160 ms
May 23, 2026160 ms
May 30, 2026158 ms
Jun 6, 2026157 ms
Jun 13, 2026158 ms
Jun 20, 2026156 ms
Jun 27, 2026157 ms
Jul 4, 2026155 ms
Jul 11, 2026150 ms
Jul 18, 2026147 ms
Jul 25, 2026146 ms
Aug 1, 2026144 ms
Aug 8, 2026144 ms
Aug 15, 2026142 ms
Aug 22, 2026139 ms
Aug 29, 2026137 ms
Sep 5, 2026137 ms
Sep 12, 2026138 ms
Sep 19, 2026141 ms
Sep 26, 2026143 ms
Oct 3, 2026141 ms
Oct 10, 2026142 ms
Oct 17, 2026142 ms
Oct 24, 2026144 ms
Oct 31, 2026142 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 egov.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. egov.com at 0.5 s0.5 s
  2. egov.com at 1.0 s1.0 s
  3. egov.com at 1.5 s1.5 s
  4. egov.com at 2.1 s2.1 s
  5. egov.com at 2.6 s2.6 s
  6. egov.com at 3.1 s3.1 s
  7. egov.com at 3.6 s3.6 s
  8. egov.com at 4.1 s4.1 s

Speed

10 to fix23
  • Render-blocking requests

    5.8 s

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

  • Use efficient cache lifetimes

    1.9 s · 1.6 MB

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

  • Reduce unused CSS

    1.8 s · 385 KiB

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

  • Reduce unused JavaScript

    1.2 s · 707 KiB

    About 707 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.

  • Mobile performance score: 23

    23/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Accessibe Accessibility Overlay and others), adding 1.4 MB and 1.1 s of main-thread time.

  • Improve image delivery

    799 KiB

    2 images could be 799 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Google Tag Manager adds 383 ms

    383 ms

    Google Tag Manager costs a phone 383 ms of main-thread work and 380 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.5 s

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

  • 1,876 HTML elements

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

  • Legacy JavaScript

    200 ms · 50 KiB

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

  • 11 long tasks on the main thread

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

  • Minify JavaScript

    56 KiB

    56 KiB could be saved by minifying JavaScript.

  • Minify CSS

    18 KiB

    18 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: 4 ms

    4 ms

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

Core Web Vitals

12 to fix33
  • 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.

  • Real-user LCP: 5.0 s

    5.0 s

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

  • Real-user CLS: 0.27

    0.27

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

  • Real-user FCP: 4.1 s

    4.1 s

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

  • Real-user TTFB: 2.2 s

    2.2 s

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

  • Cumulative Layout Shift: 1.216

    1.216

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

  • Largest Contentful Paint: 8.9 s

    8.9 s

    Your largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Tyler AI: Built for the Mission of Government”.

  • First Contentful Paint: 5.7 s

    5.7 s

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

  • Time to Interactive: 15.5 s

    15.5 s

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

  • Speed Index: 6.6 s

    6.6 s

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

  • Total Blocking Time: 492 ms

    492 ms

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

  • 3 images without width and height

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

3 checks passed
  • Real-user INP: 160 ms

    160 ms

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

  • Tap response (INP) got 11% faster for real visitors

    -11%

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

  • Largest content (LCP) got 14% faster for real visitors

    -14%

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

Images and page weight

3 to fix45
  • Page weight: 6.4 MB in 148 requests

    6.4 MB

    Your homepage downloads 6.4 MB in 148 requests on a phone: images 4.1 MB (41), scripts 1.6 MB (52) and stylesheets 426 KiB (18). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

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

  • 25 images in older formats

    25 images (3.9 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.

  • About 1.8 g of CO₂ per visit

    1.82 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.82 g of CO₂e: 218.1 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

3 to fixGoogle 9395
  • 7 tap targets too small

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

  • 6 text elements with low contrast

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

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

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

2 checks passed
  • Every image has alt text

    All 27 images in the HTML carry an alt attribute.

  • 44 automated accessibility rules passed

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

SEO

8 to fixGoogle 8575
  • 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 (“Tyler AI: Built for the Mission of Government”, “Modern Governments Live in the Cloud” and “We Empower the Public Sector to Create Smarter, S…”). One clear main headline is easier for people and search engines.

  • Meta description is long (164 characters)

    Your meta description is 164 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 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://www.tylertech.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.

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

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

  • 442 internal links, 11 external

    The homepage links to 442 pages on egov.com and 11 external pages.

3 checks passed
  • Title: 62 characters

    Your title is a healthy 62 characters: “Software & Services for the Public Sector | Tyler Technologies”.

  • Canonical URL set

    The canonical URL is https://www.tylertech.com/.

  • 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://www.tylertech.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,903 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

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

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

  • 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

2 to fixGoogle 7791
  • 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.”).

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “hover is not defined”.

2 checks passed
  • Tap targets are thumb-sized

    42 of 44 tappable elements near the top are at least 24 px.

  • 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 customer or partner logos. 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 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 617 words of copy

    The homepage carries about 617 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: “REGISTER”.

  • 2 calls to action

    The homepage has 2 calls to action, for example “Register” and “Learn More”.

  • 1 short form

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 22 cookies set on arrival

    22

    Opening the homepage sets 22 cookies (measured from a US location before any click).

  • 29 other companies contacted

    Loading the homepage contacts 29 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 egov.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 Tag Manager
Hosting
Tylertech Nic1

Company

Founded
1991
Headquarters
Olathe

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on egov.com, including 22 speed issues, 8 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