Programmable

Website review, no card needed

kasolution.com.br logo

kasolution.com.br website review

Visit site (opens in a new tab)Reviewed 2 November 202648 issues · 76 checks

This review found 48 issues worth fixing on kasolution.com.br, 15 of them high impact, across 76 checks. The most urgent: reduce unused JavaScript. 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

Site score

57F

Closest competitors among reviewed websites

Compare side by side
Real-visitor load time (LCP)75th percentile, phones
3.5 s1.7 sMay 16Oct 32.2 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.0 s
May 23, 20261.9 s
May 30, 20261.9 s
Jun 6, 20261.9 s
Jun 13, 20262.8 s
Jun 20, 20262.9 s
Jun 27, 20263.3 s
Jul 4, 20262.9 s
Jul 11, 20262.9 s
Jul 18, 20262.6 s
Jul 25, 20262.4 s
Aug 1, 20262.7 s
Aug 8, 20262.4 s
Aug 15, 20262.4 s
Aug 22, 20262.5 s
Aug 29, 20262.3 s
Sep 5, 20262.4 s
Sep 12, 20262.2 s
Sep 19, 20262.2 s
Sep 26, 20262.3 s
Oct 3, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
201 ms80 msMay 16Sep 26145 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026131 ms
May 23, 2026126 ms
May 30, 2026113 ms
Jun 6, 2026121 ms
Jun 13, 202697 ms
Jun 20, 202695 ms
Jun 27, 2026102 ms
Jul 4, 202694 ms
Jul 11, 202699 ms
Jul 18, 2026111 ms
Jul 25, 2026139 ms
Aug 1, 2026156 ms
Aug 8, 2026187 ms
Aug 15, 2026187 ms
Aug 22, 2026163 ms
Aug 29, 2026163 ms
Sep 5, 2026148 ms
Sep 12, 2026140 ms
Sep 19, 2026134 ms
Sep 26, 2026145 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

kasolution.com.br (opens in a new tab)
Full-page screenshot of kasolution.com.br (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. kasolution.com.br at 0.4 s0.4 s
  2. kasolution.com.br at 0.8 s0.8 s
  3. kasolution.com.br at 1.3 s1.3 s
  4. kasolution.com.br at 1.7 s1.7 s
  5. kasolution.com.br at 2.1 s2.1 s
  6. kasolution.com.br at 2.5 s2.5 s
  7. kasolution.com.br at 2.9 s2.9 s
  8. kasolution.com.br at 3.4 s3.4 s

Speed

11 to fix41

  • Reduce unused JavaScript

    1.5 s · 641 KiB

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

  • Render-blocking requests

    1.3 s

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

  • Mobile performance score: 41

    41/100

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

  • Improve image delivery

    150 ms · 1.7 MB

    8 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Other Google APIs/SDKs and others), adding 1.4 MB and 1.4 s of main-thread time.

  • Use efficient cache lifetimes

    750 ms · 570 KiB

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

  • Google Tag Manager adds 961 ms

    961 ms

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

  • Legacy JavaScript

    300 ms · 60 KiB

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

  • 10 long tasks on the main thread

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

  • Facebook adds 254 ms

    254 ms

    Facebook costs a phone 254 ms of main-thread work and 267 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.6 s

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

  • Minify JavaScript

    9 KiB

    9 KiB could be saved by minifying JavaScript.

  • 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

    2 KiB

    2 KiB could be saved by minifying CSS.

1 checks passed

  • Server response: 1 ms

    1 ms

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

Core Web Vitals

6 to fix35

  • Largest Contentful Paint: 11.2 s

    11.2 s

    Your largest element takes 11.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 19.2 s

    19.2 s

    The page becomes fully interactive after 19.2 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.

  • Cumulative Layout Shift: 0.238

    0.238

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

  • Total Blocking Time: 550 ms

    550 ms

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

  • 28 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +9%

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

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

    +17%

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

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

1 checks passed

  • First Contentful Paint: 1.8 s

    1.8 s

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

Images and page weight

2 to fix75

  • Page weight: 3.6 MB in 85 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 85 requests on a phone: images 2.1 MB (40), scripts 1.5 MB (30) and stylesheets 15 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • 4 images in older formats

    4 images (990 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 1.0 g of CO₂ per visit

    1.02 g

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

8 to fixGoogle 7282

  • Unlabelled dropdowns

    1 dropdown has no label.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 9 images without alt text

    9 images have no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 18 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.

  • 9 form fields without a label

    9 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 5 links without text

    5 visible links have no text or label, so screen readers cannot say where they go.

1 checks passed

  • 23 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 30 WCAG 2.2 A/AA and best-practice rules on the phone render: 23 passed and 7 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 9259

  • No H1 headline

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

  • Title is long (273 characters)

    Your title is 273 characters, so Google will cut it off around 60: “Ka Solution | Academias SAP e Cursos SAP Cursos Microsoft Cursos Azure Cursos AWS Cursos …”.

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

  • Meta description is long (193 characters)

    Your meta description is 193 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://kasolution.com.br/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at kasolution.com.br/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.

  • 11 internal links, 2 external

    The homepage links to 11 pages on kasolution.com.br and 2 external pages.

AI search readiness

1 to fix69

  • 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://kasolution.com.br/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.

Other pages

3 to fix75

  • 6 pages without a title

    https://kasolution.com.br/social/whatsapp.html, https://kasolution.com.br/social/Linkedin.html, https://kasolution.com.br/social/instagram.html, https://kasolution.com.br/social/Youtube.html, https://kasolution.com.br/social/facebook.html and https://kasolution.com.br/social/twitter.html have no <title>, so Google invents the link text in results.

  • 7 pages without a meta description

    https://kasolution.com.br/social/whatsapp.html, https://kasolution.com.br/social/Linkedin.html, https://kasolution.com.br/social/instagram.html, https://kasolution.com.br/social/Youtube.html, https://kasolution.com.br/social/facebook.html and https://kasolution.com.br/social/twitter.html and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages without an H1

    https://kasolution.com.br/Paginas/SegurancaEPrivacidade, https://kasolution.com.br/social/whatsapp.html, https://kasolution.com.br/social/Linkedin.html, https://kasolution.com.br/social/instagram.html, https://kasolution.com.br/social/Youtube.html and https://kasolution.com.br/social/facebook.html and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 11 internal pages checked

    We fetched 11 pages linked from your homepage and read each the way a search engine does.

4 checks passed

  • Linked pages load

    All 11 pages we checked loaded without an error.

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

Best practices

4 to fixGoogle 9645

  • No mobile viewport

    No viewport meta tag, so phones render the desktop layout zoomed out.

  • 4 broken images

    4 images failed to load on a phone, for example https://kasolution.com.br/Content/themes/Ka/Imagens.Mobile.EN/Home/Home_Banner06_Mobile.jpg.

  • 11 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.

  • 12 low-resolution images

    12 images are served at too low a resolution for sharp phone screens.

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.

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

  • Thin social proof

    Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 108 words

    The homepage has only about 108 words of visible text; thin pages give Google and first-time buyers little to go on.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

2 checks passed

  • 2 short forms

    2 short forms (4 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix

  • 5 trackers load before any consent

    5

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

  • 14 cookies set on arrival

    14

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

  • 20 other companies contacted

    Loading the homepage contacts 20 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 kasolution.com.br, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2000.

Stack

Framework
jQuery
Analytics
Google Tag Manager
Hosting
Azure

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 48 issues on kasolution.com.br, including 17 speed issues, 8 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