Website review, no card needed

solutionanalysts.com logo

solutionanalysts.com website review

Visit site (opens in a new tab)Reviewed 19 November 202639 issues · 69 checks

This review found 39 issues worth fixing on solutionanalysts.com, 16 of them high impact, across 69 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
2.9 s2.2 sMay 30Nov 142.5 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.6 s
Jun 6, 20262.4 s
Jun 13, 20262.2 s
Jun 20, 20262.2 s
Jun 27, 20262.3 s
Jul 4, 20262.5 s
Jul 11, 20262.4 s
Jul 18, 20262.3 s
Jul 25, 20262.4 s
Aug 1, 20262.3 s
Aug 8, 20262.8 s
Aug 15, 20262.8 s
Aug 22, 20262.6 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.5 s
Sep 26, 20262.7 s
Oct 3, 20262.7 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Oct 24, 20262.4 s
Oct 31, 20262.4 s
Nov 7, 20262.7 s
Nov 14, 20262.5 s
Real-visitor tap response (INP)75th percentile, phones
244 ms101 msMay 30Nov 14227 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026163 ms
Jun 6, 2026128 ms
Jun 13, 2026123 ms
Jun 20, 2026119 ms
Jun 27, 2026117 ms
Jul 4, 2026144 ms
Jul 11, 2026144 ms
Jul 18, 2026153 ms
Jul 25, 2026163 ms
Aug 1, 2026160 ms
Aug 8, 2026172 ms
Aug 15, 2026183 ms
Aug 22, 2026182 ms
Aug 29, 2026184 ms
Sep 5, 2026184 ms
Sep 12, 2026159 ms
Sep 19, 2026178 ms
Sep 26, 2026180 ms
Oct 3, 2026165 ms
Oct 10, 2026180 ms
Oct 17, 2026170 ms
Oct 31, 2026166 ms
Nov 14, 2026227 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 solutionanalysts.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. solutionanalysts.com at 0.8 s0.8 s
  2. solutionanalysts.com at 1.5 s1.5 s
  3. solutionanalysts.com at 2.3 s2.3 s
  4. solutionanalysts.com at 3.1 s3.1 s
  5. solutionanalysts.com at 3.8 s3.8 s
  6. solutionanalysts.com at 4.6 s4.6 s
  7. solutionanalysts.com at 5.4 s5.4 s
  8. solutionanalysts.com at 6.1 s6.1 s

Speed

5 to fix55
  • Use efficient cache lifetimes

    3.6 s · 2.3 MB

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

  • Reduce unused JavaScript

    2.2 s · 449 KiB

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

  • Mobile performance score: 55

    55/100

    Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Clarity and lfeeder.com and others), adding 920 KiB and 708 ms of main-thread time.

  • Google Tag Manager adds 593 ms

    593 ms

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

  • 9 long tasks on the main thread

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

  • Improve image delivery

    55 KiB

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

  • Legacy JavaScript

    13 KiB

    Polyfills for old browsers add 13 KiB JavaScript that modern phones do not need.

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

2 checks passed
  • Main-thread work: 1.9 s

    A phone's processor spends 1.9 s on main-thread work while loading, 1.2 s of it running JavaScript. That is comfortably low.

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

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

  • Largest Contentful Paint: 14.5 s

    14.5 s

    Your largest element takes 14.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Your product, further. Your team, stronger.”.

  • Time to Interactive: 14.6 s

    14.6 s

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

  • Speed Index: 7.5 s

    7.5 s

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

  • Real-user LCP: 2.6 s

    2.6 s

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

  • Real-user INP: 228 ms

    228 ms

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

  • Tap response (INP) got 35% slower for real visitors

    +35%

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • 73 images without width and height

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

  • Total Blocking Time: 446 ms

    446 ms

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

3 checks passed
  • Real-user CLS: 0.10

    0.10

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

  • Cumulative Layout Shift: 0.074

    0.074

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

  • First Contentful Paint: 0.8 s

    0.8 s

    The first text or image appears after 0.8 s, inside the 1.8 s “good” threshold.

Images and page weight

3 to fix50
  • 1 image over 500 KB

    p__3.svg weighs 545 KiB. On a phone connection a single image that size takes seconds.

  • 4 images far larger than shown

    925 KiB

    4 images are downloaded at several times the size a phone draws them, for example p__3.svg at 247 px wide, shown at 42 px. Resized copies would save about 925 KiB.

  • Page weight: 3.3 MB in 85 requests

    3.3 MB

    Your homepage downloads 3.3 MB in 85 requests on a phone: images 1.6 MB (23), scripts 1.1 MB (26) and fonts 583 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (60 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.

  • 2 images below the first screen load straight away

    2 images further down the page (58 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.9 g of CO₂ per visit

    0.94 g

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

Accessibility

6 to fixGoogle 9191
  • 11 text elements with low contrast

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

  • 3 tap targets too small

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

  • Heading levels should only increase by one (4 elements)

    Heading levels should only increase by one: 4 elements on the page fail this check, rated moderate by axe-core.

  • Main landmark should not be contained in another landmark (1 element)

    Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one main landmark (1 element)

    Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (3 elements).

1 checks passed
  • 41 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: 41 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

7 to fixGoogle 9260
  • No meta description

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

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (17 characters)

    Your title is only 17 characters: “Solution Analysts”. 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:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • Only 0 internal links

    The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

2 checks passed
  • 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.solutionanalysts.com/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    0%

    A phone browser shows 1,984 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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

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

Best practices

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix30
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 1,984 words of visible text.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Microsoft Clarity (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.

  • 10 cookies set on arrival

    10

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

  • 24 other companies contacted

    Loading the homepage contacts 24 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 solutionanalysts.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 | Google Tag Manager
Hosting
AWS

Company

Headquarters
Ahmedabad

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on solutionanalysts.com, including 16 speed issues, 7 SEO issues and 4 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