kalba.lt website review

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

About 1.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.7 s faster on a phone.

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

About 646 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.3 s faster on a phone.

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

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

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 1.9 MB and 1.6 s of main-thread time.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 750 ms).

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

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

The page has 1,534 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

7 images could be 148 KiB 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.

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

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

13 KiB could be saved by minifying JavaScript.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB could be saved by minifying CSS.

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 visitors wait 4.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

Your largest element takes 49.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Šiame tinklalapyje naudojame slapukus siekiant užtikrinti p…”.

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

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

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

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

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

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

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

Your homepage downloads 9.1 MB in 346 requests on a phone: images 4.6 MB (62), scripts 2.4 MB (103) and stylesheets 851 KiB (80). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.1 MB together. On a phone connection a single image that size takes seconds.

4 images (912 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 are downloaded at several times the size a phone draws them, for example studijos-be-streso.png at 1,605 px wide, shown at 308 px. Resized copies would save about 215 KiB.

1 image further down the page (261 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

All page content should be contained by landmarks: 52 elements on the page fail this check, rated moderate by axe-core.

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 on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

24 links have no real href, so search engines can't follow them.

The homepage links to 149 pages on kalba.lt and 11 external pages.

There is no https://kalba.lt/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.

https://kalba.lt/en and https://kalba.lt/ru declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

https://kalba.lt/anglu-kalba-mokyklose-ir-darzeliuose, https://kalba.lt/kalba-paslaugos-moksleiviams/pasiruosimas-brandos-egzaminams-grupese, https://kalba.lt/kalba-paslaugos-moksleiviams/pasiruosimas-penktai-klasei and https://kalba.lt/kalba-paslaugos-moksleiviams/kalbu-kursai-moksleiviams-grupese are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

/ and https://kalba.lt/ru all use the title “Kalba.Lt - edukacinės rinkos lyderis. Dirbame daugiau nei 30 metų”. Search engines can't tell which page to show for a search, so each competes with the others.

https://kalba.lt/kalba-paslaugos-suaugusiems/kalbu-kursai/anglu-kalbos-kursai-suaugusiems-grupese, https://kalba.lt/kalba-paslaugos-moksleiviams/kalbu-kursai-moksleiviams-grupese/anglu-kalbos-kursai-grupese-moksleiviams, https://kalba.lt/kalba-paslaugos-moksleiviams/kalbu-kursai-moksleiviams-grupese, https://kalba.lt/snekamosios-anglu-kalbos-kursai, https://kalba.lt/finansuojami-kalbu-kursai and https://kalba.lt/kalba-paslaugos-suaugusiems/kalbu-kursai/lietuviu-kalbos-kursai-suaugusiems have no meta description, so Google writes the search snippet from whatever text it finds.

https://kalba.lt/en and https://kalba.lt/ru use the same meta description. A description written for each page earns more clicks.

https://kalba.lt/ru, https://kalba.lt/kalba-paslaugos-moksleiviams/pasiruosimas-brandos-egzaminams-grupese and https://kalba.lt/kalba-paslaugos-moksleiviams/korepetitoriavimas have no <h1> headline, so visitors and search engines get no clear main topic.

https://kalba.lt/kalba-paslaugos-suaugusiems/kalbu-kursai/anglu-kalbos-kursai-suaugusiems-grupese, https://kalba.lt/kalba-paslaugos-suaugusiems/kalbu-kursai, https://kalba.lt/en, https://kalba.lt/ru, https://kalba.lt/kalba-paslaugos-moksleiviams/kalbu-kursai-moksleiviams-grupese/anglu-kalbos-kursai-grupese-moksleiviams and https://kalba.lt/anglu-kalba-mokyklose-ir-darzeliuose and 4 others took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 57 found) and read each the way a search engine does.

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

6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

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

Chrome logged issues while loading the page (“Mixed content”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 805 words of visible text.

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

Opening the homepage sets 14 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.