4.2 sec in total
271 ms
3.2 sec
729 ms
Visit l24.lt now to see the best up-to-date L 24 content for Lithuania and also check out these interesting facts you probably never knew about l24.lt
Skaityk tikras ir bešališkas žinias apie Lietuvos ir pasaulio gyvenimą - lietuviškai, lenkiškai rusiškai ir angliškai - tik www.l24.lt. Tikslinė mūsų skaitytojų auditorija – visa Lietuva. Be to, inter...
Visit l24.ltWe analyzed L24.lt page load time and found that the first response time was 271 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
l24.lt performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value6.4 s
9/100
25%
Value7.7 s
24/100
10%
Value80 ms
99/100
30%
Value0
100/100
15%
Value5.3 s
73/100
10%
271 ms
317 ms
286 ms
191 ms
291 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 64% of them (61 requests) were addressed to the original L24.lt, 10% (10 requests) were made to Static.xx.fbcdn.net and 9% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain L24.lt.
Page size can be reduced by 771.4 kB (56%)
1.4 MB
603.9 kB
In fact, the total size of L24.lt main page is 1.4 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Javascripts take 643.7 kB which makes up the majority of the site volume.
Potential reduce by 199.8 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 84.4 kB, which is 38% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 199.8 kB or 90% of the original size.
Potential reduce by 16.4 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. L 24 images are well optimized though.
Potential reduce by 447.2 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 447.2 kB or 69% of the original size.
Potential reduce by 108.0 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. L24.lt needs all CSS files to be minified and compressed as it can save up to 108.0 kB or 86% of the original size.
Number of requests can be reduced by 50 (54%)
92
42
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of L 24. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
271 ms
k2.css
317 ms
style.css
286 ms
general.css
191 ms
template.css
291 ms
ticker.css
192 ms
css
26 ms
artclock.css
192 ms
style6.css
280 ms
mod_sp_weather.css
286 ms
template.css
284 ms
mootools-core.js
685 ms
core.js
510 ms
jquery-1.9.1.min.js
707 ms
k2.js
513 ms
ytc.jquery-1.5.min.js
720 ms
general.js
405 ms
slider.js
635 ms
jquery.dimensions.js
734 ms
jquery.simpletip-1.3.1.js
742 ms
stickytooltip.js
862 ms
mootools-more.js
1280 ms
menu.js
926 ms
banner.js
796 ms
jquery.marquee.min.js
830 ms
jquery.lazyload.min.js
969 ms
ticker.js
892 ms
excanvas.js
1056 ms
coolclock.js
1088 ms
moreskins.js
1120 ms
ty2udate.js
1021 ms
engine.mootools.js
1196 ms
font-awesome.min.css
1247 ms
css
29 ms
ga.js
16 ms
28d-100567.png
13 ms
26d-100567.png
14 ms
39d-100567.png
77 ms
34d-100567.png
14 ms
30d-100567.png
13 ms
background.png
286 ms
logo.png
454 ms
lt.gif
103 ms
pl.gif
104 ms
ru.gif
103 ms
en.gif
101 ms
300x150-Milana_en.gif
457 ms
300x100-solidarnosc-ENG.gif
323 ms
all.js
77 ms
top_back.png
193 ms
menu_back.png
194 ms
menu_bar_back.png
281 ms
3463c20e162a3c9d19c8da68f64c9ca2_Generic.jpg
449 ms
ecba4220ec415d57a30312ce2a2240b4_Generic.jpg
601 ms
67989414784a25789140336605f4611f_S.jpg
510 ms
518233aae8e9b1441cc458cb91fe8dd8_S.jpg
542 ms
626a3c7c6948945237ae3af06fa0970c_S.jpg
602 ms
1937a373b0c3d8a11c3da1bfdd0bc3b0_S.jpg
631 ms
1c76c6f59a5683652d7d856a4cc3b24c_S.jpg
649 ms
a03cf4a04abfb41b975b2013b49a4fa3_S.jpg
737 ms
__utm.gif
28 ms
fe31ea379cfc1d356a68f1a4ed6e1821_S.jpg
704 ms
b787fa7994345346761493bbbf1a7fed_S.jpg
763 ms
c63bc1e3a249a0d6d1101680fe4cb935_S.jpg
764 ms
253e3aa2eda5ab2c5c00230ac4170a3c_S.jpg
789 ms
de606818a0e09008382010c0dfc5cf01_S.jpg
811 ms
ed6145f3c2f6c22309526b955af45897_S.jpg
898 ms
67de1c98d53945f2f78f34549cb9b8e8_S.jpg
930 ms
84cd636197e1cf2d6a7d42dfe2ebf492_S.jpg
990 ms
953 ms
fontawesome-webfont.woff
1196 ms
collect
78 ms
55 ms
g_U08WmVcCfOwPUBpEKV5C3USBnSvpkopQaUR-2r7iU.ttf
30 ms
xd_arbiter.php
46 ms
xd_arbiter.php
95 ms
like_box.php
66 ms
FbUd6dZS1Af.css
46 ms
dGJLq38YL-C.css
53 ms
_rx8naC75Dy.js
73 ms
x5F9OMjKyLw.js
95 ms
ICDbTSzjQEg.js
93 ms
TTCre3391I0.js
94 ms
969536_597546330278404_1378652784_n.jpg
68 ms
1236062_650197008346669_739907472_n.jpg
35 ms
12039230_783649621744711_1493303078110249060_n.jpg
37 ms
12108241_1682622345307305_6624560537075593605_n.jpg
36 ms
12650889_133175603732438_5418809277761385075_n.jpg
35 ms
10516776_689231437818236_3821588570406501125_n.jpg
36 ms
154797_103437103061337_5670788_n.jpg
42 ms
12512562_920649171323373_3921830976833813156_n.jpg
41 ms
1959636_508331502617573_69868630_n.jpg
60 ms
wL6VQj7Ab77.png
14 ms
s7jcwEQH7Sx.png
14 ms
I6-MnjEovm5.js
9 ms
vlXaquuXMrr.js
10 ms
l24.lt accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
Links do not have a discernible name
l24.lt best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
l24.lt SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise L24.lt can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that L24.lt main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
l24.lt
Open Graph data is detected on the main page of L 24. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: