Website review, no card needed

kalsoft.com logo

kalsoft.com website review

Visit site (opens in a new tab)Reviewed 27 October 202634 issues · 76 checks

This review found 34 issues worth fixing on kalsoft.com, 15 of them high impact, across 76 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
5.9 s2.4 sMay 9Oct 244.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.9 s
May 16, 20263.2 s
May 23, 20263.2 s
May 30, 20263.3 s
Jun 6, 20263.1 s
Jun 13, 20262.8 s
Jun 20, 20263.5 s
Jun 27, 20263.2 s
Jul 11, 20263.2 s
Jul 18, 20263.2 s
Jul 25, 20263.5 s
Aug 1, 20264.1 s
Aug 8, 20265.3 s
Aug 15, 20265.5 s
Aug 22, 20264.8 s
Aug 29, 20264.0 s
Sep 5, 20263.7 s
Sep 12, 20263.7 s
Sep 19, 20263.7 s
Sep 26, 20263.7 s
Oct 3, 20263.7 s
Oct 10, 20263.9 s
Oct 17, 20263.9 s
Oct 24, 20264.0 s
Real-visitor tap response (INP)75th percentile, phones
230 ms97 msMay 16Oct 17194 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026112 ms
May 23, 2026113 ms
May 30, 2026114 ms
Aug 22, 2026195 ms
Aug 29, 2026195 ms
Sep 5, 2026178 ms
Sep 12, 2026176 ms
Sep 19, 2026194 ms
Sep 26, 2026194 ms
Oct 3, 2026208 ms
Oct 10, 2026215 ms
Oct 17, 2026194 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 kalsoft.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kalsoft.com at 0.4 s0.4 s
  2. kalsoft.com at 0.8 s0.8 s
  3. kalsoft.com at 1.1 s1.1 s
  4. kalsoft.com at 1.5 s1.5 s
  5. kalsoft.com at 1.9 s1.9 s
  6. kalsoft.com at 2.3 s2.3 s
  7. kalsoft.com at 2.6 s2.6 s
  8. kalsoft.com at 3.0 s3.0 s

Speed

6 to fix62
  • Use efficient cache lifetimes

    40.5 s · 23.6 MB

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

  • Improve image delivery

    32.5 s · 20.5 MB

    14 images could be 20.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 32.5 s faster on a phone.

  • Reduce unused JavaScript

    1.7 s · 312 KiB

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

  • Mobile performance score: 62

    62/100

    Your mobile performance score is 62 (desktop: 65). Pages that score under 90 lose visitors before the first paint.

  • Render-blocking requests

    700 ms

    15 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.

  • Google CDN adds 61 ms

    61 ms

    Google CDN costs a phone 61 ms of main-thread work and 349 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.

  • Reduce unused CSS

    150 ms · 54 KiB

    About 54 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google CDN, Cloudflare CDN and Other Google APIs/SDKs and others), adding 376 KiB and 73 ms of main-thread time.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 74 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 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.

  • Minify CSS

    5 KiB

    5 KiB could be saved by minifying CSS.

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 0.6 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

11 to fix50
  • 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: 4.0 s

    4.0 s

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

  • Real-user FCP: 3.4 s

    3.4 s

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

  • Largest Contentful Paint: 83.0 s

    83.0 s

    Your largest element takes 83.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Enterprise TechnologyServices & SolutionsIntegrator”.

  • Time to Interactive: 87.1 s

    87.1 s

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

  • Speed Index: 15.2 s

    15.2 s

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

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

    +82%

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

  • Largest content (LCP) got 30% slower for real visitors

    +30%

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • 2 images without width and height

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

3 checks passed
  • Real-user CLS: 0.00

    0.00

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 12 ms

    12 ms

    Scripts block the page for only 12 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix18
  • Page weight: 23.9 MB in 68 requests

    23.9 MB

    Your homepage downloads 23.9 MB in 68 requests on a phone: images 23.1 MB (18), scripts 726 KiB (31) and stylesheets 107 KiB (18). Under 2 MB keeps phones on slow connections fast.

  • 9 images over 500 KB

    9 images weigh 15.5 MB together. On a phone connection a single image that size takes seconds.

  • 9 images far larger than shown

    9.3 MB

    9 images are downloaded at several times the size a phone draws them, for example Industry_solutions_1.png at 1,536 px wide, shown at 346 px. Resized copies would save about 9.3 MB.

  • 9 images in older formats

    9 images (15.5 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.

  • 9 images below the first screen load straight away

    9 images further down the page (15.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 6.8 g of CO₂ per visit

    6.79 g

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

Accessibility

2 to fixGoogle 9196
  • 4 tap targets too small

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

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 12 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

2 to fixGoogle 10091
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (178 characters)

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

  • 30 internal links, 2 external

    The homepage links to 30 pages on kalsoft.com and 2 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Enterprise TechnologyServices & SolutionsIntegrator”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Global Technology Services & Solutions Integrator | KalSoft”.

  • Canonical URL set

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

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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.kalsoft.com/sitemap.xml.

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.kalsoft.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 (400 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without an H1

    https://www.kalsoft.com/industry-solutions has no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.kalsoft.com/industry-solutions 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage 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.

  • 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 10087
  • 6 small tap targets

    6 of 14 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://kit-free.fontawesome.com/releases/latest/css/free-v4-shims.min.css' from origin 'h…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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: “800+ Clients”. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 390 words of visible text.

1 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact Us” and “Contact UsContact”.

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.

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

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 kalsoft.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
Next.js
Hosting
Wolfpawservices

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on kalsoft.com, including 17 speed issues, 2 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