Website review, no card needed
geocareinc.com website review
Visit site (opens in a new tab)Reviewed 31 October 202629 issues · 78 checks
This review found 29 issues worth fixing on geocareinc.com, 9 of them high impact, across 78 checks. The most urgent: required ARIA attributes must be provided (3 elements). 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
85BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.3 s |
| May 16, 2026 | 1.3 s |
| May 23, 2026 | 1.3 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.2 s |
| Jun 13, 2026 | 1.2 s |
| Jun 20, 2026 | 1.2 s |
| Jun 27, 2026 | 1.2 s |
| Jul 4, 2026 | 1.2 s |
| Jul 11, 2026 | 1.2 s |
| Jul 18, 2026 | 1.2 s |
| Jul 25, 2026 | 1.2 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.1 s |
| Aug 15, 2026 | 1.1 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.1 s |
| Oct 24, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 111 ms |
| May 16, 2026 | 111 ms |
| May 23, 2026 | 118 ms |
| May 30, 2026 | 118 ms |
| Jun 6, 2026 | 120 ms |
| Jun 13, 2026 | 123 ms |
| Jun 20, 2026 | 121 ms |
| Jun 27, 2026 | 122 ms |
| Jul 4, 2026 | 121 ms |
| Jul 11, 2026 | 121 ms |
| Jul 18, 2026 | 119 ms |
| Jul 25, 2026 | 119 ms |
| Aug 1, 2026 | 119 ms |
| Aug 8, 2026 | 112 ms |
| Aug 15, 2026 | 115 ms |
| Aug 22, 2026 | 119 ms |
| Aug 29, 2026 | 119 ms |
| Sep 5, 2026 | 127 ms |
| Sep 12, 2026 | 127 ms |
| Sep 19, 2026 | 128 ms |
| Sep 26, 2026 | 127 ms |
| Oct 3, 2026 | 131 ms |
| Oct 10, 2026 | 122 ms |
| Oct 17, 2026 | 122 ms |
| Oct 24, 2026 | 129 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
Speed
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 154 ms. During a long task the page ignores taps.
Reduce unused JavaScript
49 KiBAbout 49 KiB of JavaScript is downloaded but never used on this page.
1 third-party service on the page
1 third-party service load with your homepage (cloudflare.com), adding 28 KiB and 19 ms of main-thread time.
3 checks passed
Mobile performance score: 98
98/100Your mobile performance score is 98. That is in Google's “good” band (90 and up).
Main-thread work: 0.7 s
A phone's processor spends 0.7 s on main-thread work while loading, 515 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 111 ms to 129 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 1.3 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
12 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 112 ms
112 msReal visitors wait 112 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.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 452 ms
452 msReal visitors wait 452 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 169 ms
169 msScripts block the page for only 169 ms while loading. Good is under 200 ms.
Time to Interactive: 3.0 s
3.0 sThe page is fully interactive after 3.0 s.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
First Contentful Paint: 0.8 s
0.8 sThe first text or image appears after 0.8 s, inside the 1.8 s “good” threshold.
Largest Contentful Paint: 0.8 s
0.8 sYour largest element renders in 0.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “This website uses a security service to protect against mal…”.
Speed Index: 1.3 s
1.3 sVisually, the page fills in at 1.3 s (Speed Index), inside the 3.4 s “good” threshold.
Images and page weight
1 image far larger than shown
387 KiB1 image is downloaded at several times the size a phone draws it, for example americas-most-patriotic-companies-2026-04.png at 2,619 px wide, shown at 56 px. Resized copies would save about 387 KiB.
2 images in older formats
2 images (495 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 (408 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.3 g of CO₂ per visit
0.32 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.32 g of CO₂e: 38.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1.1 MB in 9 requests
1.1 MBYour homepage downloads 1.1 MB in 9 requests on a phone: other files 730 KiB (4), scripts 217 KiB (2) and HTML 199 KiB (2). That is a lean page.
Accessibility
Required ARIA attributes must be provided (3 elements)
Required ARIA attributes must be provided: 3 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.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
The document uses <meta http-equiv="refresh">
The document uses <meta http-equiv="refresh"> (1 element).
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (5 elements)
ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.
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.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Blocked from indexing
Google's crawler is blocked from indexing this page.
Error status code
The page answers with an error status, so search engines may drop it.
Title is short (8 characters)
Your title is only 8 characters: “GEO Care”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
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:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://geogroup.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at geogroup.com/robots.txt, the first file search crawlers ask for.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
86 internal links, 23 external
The homepage links to 86 pages on geocareinc.com and 23 external pages.
1 checks passed
One H1 headline
Your main headline reads: “Thank you for subscribing!”.
AI search readiness
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://geogroup.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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (515 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages share 2 titles
https://geogroup.com/about-us and https://geogroup.com/about-us/who-we-are all use the title “Who We Are”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
14 pages without a meta description
https://geogroup.com/geo-world, https://geogroup.com/news/newsletters, https://geogroup.com/about-us, https://geogroup.com/about-us/who-we-are, https://geogroup.com/partnerships and https://geogroup.com/about-us/history-timeline and 8 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 49 found) and read each the way a search engine does.
5 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 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 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://cdn-images.mailchimp.com/embedcode/classic-10_7.css' from origin 'https://geogroup…”.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
8 of 9 tappable elements near the top are at least 24 px.
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.
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 333 words of copy
The homepage carries about 333 words of visible text.
5 checks passed
1 call to action
The homepage has 1 call to action, for example “SIGN UP”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 6 customer or partner logos and 1 trust badge.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
7 other companies contacted
Loading the homepage contacts 7 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 geocareinc.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 Analytics
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on geocareinc.com, including 9 SEO issues and 1 conversion gap. 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.