lrt.lt website review

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

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

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

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

Google Tag Manager costs a phone 1.2 s of main-thread work and 498 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, cookiebot.eu and Google/Doubleclick Ads and others), adding 1.3 MB and 3.0 s of main-thread time.

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

cookiebot.eu costs a phone 741 ms of main-thread work and 32 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.

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

Google/Doubleclick Ads costs a phone 345 ms of main-thread work and 321 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.

Facebook costs a phone 282 ms of main-thread work and 195 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.

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

8 KiB could be saved by minifying JavaScript.

5 KiB could be saved by minifying CSS.

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.

Your largest element takes 10.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Valdas Adamkus susitikime su studentais 1997 metų prezident…”.

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

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

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

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

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

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

Your homepage downloads 4.9 MB in 153 requests on a phone: scripts 2.2 MB (51), images 1.9 MB (55) and stylesheets 378 KiB (7). Under 2 MB keeps phones on slow connections fast.

2524883-680935-1287x836.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

2 images are downloaded at several times the size a phone draws them, for example 2524883-680935-1287x836.jpg at 1,254 px wide, shown at 374 px. Resized copies would save about 105 KiB.

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

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

Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

Your title is 86 characters, so Google will cut it off around 60: “Lietuvos nacionalinis radijas ir televizija. Naujienos, įrašai ir transliacijos. - LRT”.

Structured data found (NewsMediaOrganization and WebSite) but with 1 problem, for example “WebSite: missing name”.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 342 pages on lrt.lt and 24 external pages.

Your robots.txt shuts out ChatGPT search (OAI-SearchBot), ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

There is no https://www.lrt.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.

robots.txt blocks GPTBot, ClaudeBot, Google-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

https://www.lrt.lt/mediateka and https://www.lrt.lt/radioteka have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.lrt.lt/mediateka, https://www.lrt.lt/radioteka and https://www.lrt.lt/projektai/eurovision-sport have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.lrt.lt/radioteka, https://www.lrt.lt/naujienos/lrt-paprastai and https://www.lrt.lt/projektai/eurovision-sport have 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.

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

Large scripts ship without source maps.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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 2,334 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

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

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