Website review, no card needed
client-solutions-group.com website review
Visit site (opens in a new tab)Reviewed 6 November 202624 issues · 76 checks
This review found 24 issues worth fixing on client-solutions-group.com, 3 of them high impact, across 76 checks. The most urgent: render-blocking requests. 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
79CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.6 s
1.3 s
1.9 s
2.5 s
3.1 s
3.8 s
4.4 s
5.0 s
Speed
Render-blocking requests
2.9 s39 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.9 s.
Mobile performance score: 76
76/100Your mobile performance score is 76. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
450 ms · 82 KiBAbout 82 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Improve image delivery
206 KiB3 images could be 206 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 177 ms. During a long task the page ignores taps.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Minify CSS
12 KiB12 KiB could be saved by minifying CSS.
1 third-party service on the page
1 third-party service load with your homepage (Google Fonts), adding 88 KiB and 1 ms of main-thread time.
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.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 224 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 4.7 s
4.7 sYour largest element takes 4.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “The Ark Shop!”.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Speed Index: 5.0 s
5.0 sVisually, the page fills in at 5.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 4.7 s
4.7 sThe page becomes fully interactive after 4.7 s. Good is under 3.8 s.
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: 27 ms
27 msScripts block the page for only 27 ms while loading. Good is under 200 ms.
Images and page weight
2 images far larger than shown
92 KiB2 images are downloaded at several times the size a phone draws them, for example CSG_PSSlider_1600x600.jpg at 1,600 px wide, shown at 390 px. Resized copies would save about 92 KiB.
2 images in older formats
2 images (274 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.
About 0.2 g of CO₂ per visit
0.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.24 g of CO₂e: 29.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 884 KiB in 48 requests
884 KiBYour homepage downloads 884 KiB in 48 requests on a phone: images 465 KiB (4), fonts 156 KiB (3) and stylesheets 152 KiB (21). That is a lean page.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
2 links without text
2 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 skip levels
Headings skip levels (h3 → h6, h2 → h4 and h2 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 8 images in the HTML carry an alt attribute.
34 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is long (68 characters)
Your title is 68 characters, so Google will cut it off around 60: “Merchant Services | Credit Card Processing | Small Business Services”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
10 links crawlers can't follow
10 links have no real href, so search engines can't follow them.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
42 internal links, 31 external
The homepage links to 42 pages on client-solutions-group.com and 31 external pages.
5 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “Client Solutions Group provides small business services - credit card processing, business cash advance, POS, gift & lo…”.
Canonical URL set
The canonical URL is https://www.client-solutions-group.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and 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.client-solutions-group.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.client-solutions-group.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.
3 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (712 words), so crawlers that don't run JavaScript still read it.
Other pages
10 pages without a meta description
https://www.client-solutions-group.com/business-cash-advance, https://www.client-solutions-group.com/credit-card-processing, https://www.client-solutions-group.com/gift-loyalty-programs, https://www.client-solutions-group.com/bulletsinthebathtub, https://www.client-solutions-group.com/blog and https://www.client-solutions-group.com/our-story and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.
10 pages without an H1
https://www.client-solutions-group.com/business-cash-advance, https://www.client-solutions-group.com/credit-card-processing, https://www.client-solutions-group.com/gift-loyalty-programs, https://www.client-solutions-group.com/bulletsinthebathtub, https://www.client-solutions-group.com/blog and https://www.client-solutions-group.com/our-story and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.client-solutions-group.com/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.
8 pages slow to respond
https://www.client-solutions-group.com/business-cash-advance, https://www.client-solutions-group.com/gift-loyalty-programs, https://www.client-solutions-group.com/bulletsinthebathtub, https://www.client-solutions-group.com/blog, https://www.client-solutions-group.com/our-story and https://www.client-solutions-group.com/sister-companies and 2 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 22 found) and read each the way a search engine does.
5 checks passed
Linked pages load
10 pages of 15 loaded without an error (the rest turned automated requests away).
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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 10 pages that loaded have a <title>.
Best practices
2 small tap targets
2 of 10 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
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 273 words of copy
The homepage carries about 273 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: “The Ark Shop” and “Learn More”.
3 calls to action
The homepage has 3 calls to action, for example “Contact Us”, “The Ark Shop” and “Learn More”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 4 testimonial or review blocks and 4 customer or partner logos.
Direct contact links
Visitors can reach you directly: 1 phone link and 4 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 client-solutions-group.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
- Hosting
- GoDaddy
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 24 issues on client-solutions-group.com, including 7 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.