4.1 sec in total
150 ms
3.3 sec
713 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 150 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
Value4.0 s
23/100
10%
Value6.5 s
9/100
25%
Value4.5 s
73/100
10%
Value190 ms
91/100
30%
Value0
100/100
15%
Value6.3 s
61/100
10%
150 ms
18 ms
348 ms
242 ms
261 ms
Our browser made a total of 62 requests to load all elements on the main page. We found that 90% of them (56 requests) were addressed to the original L24.lt, 3% (2 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain L24.lt.
Page size can be reduced by 209.6 kB (35%)
592.2 kB
382.6 kB
In fact, the total size of L24.lt main page is 592.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. HTML takes 226.6 kB which makes up the majority of the site volume.
Potential reduce by 198.4 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 80.6 kB, which is 36% 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 198.4 kB or 88% of the original size.
Potential reduce by 0 B
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 6.3 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. This website has mostly compressed JavaScripts.
Potential reduce by 5.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 5.0 kB or 21% of the original size.
Number of requests can be reduced by 31 (54%)
57
26
The browser has sent 57 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 25 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
l24.lt
150 ms
18 ms
348 ms
components,_com_k2,_css,_k2.css+,_modules,_mod_so_k2slider,_assets,_style.css+,_modules,_mod_so_k2slider,_assets,_general.css.pagespeed.cc.kwZiwICExE.css
242 ms
jcemediabox.css
261 ms
style.css
262 ms
template.css
257 ms
ticker.css
260 ms
css
35 ms
mootools-core.js
451 ms
core.js
250 ms
jquery-1.9.1.min.js
591 ms
k2.js
482 ms
ytc.jquery-1.5.min.js
493 ms
general.js
483 ms
slider.js
496 ms
jquery.dimensions.js
680 ms
jquery.simpletip-1.3.1.js
721 ms
stickytooltip.js
717 ms
jcemediabox.js
724 ms
mootools-more.js
937 ms
menu.js
822 ms
banner.js
964 ms
jquery.marquee.min.js
963 ms
jquery.lazyload.min.js
965 ms
ticker.js
975 ms
hplayer.js
1050 ms
excanvas.js
1170 ms
coolclock.js
1167 ms
moreskins.js
1063 ms
ct-functions.js
1190 ms
A.font-awesome.min.css.pagespeed.cf.ZQRvzBRhjx.css
1001 ms
css
32 ms
gtm.js
176 ms
background.png
252 ms
xlogo.png.pagespeed.ic.MrTKzW7oWZ.png
72 ms
all.js
170 ms
top_back.png
250 ms
menu_back.png
280 ms
menu_bar_back.png
246 ms
x21e281cf343d4029f9a1e6321d3696f3_Generic.jpg.pagespeed.ic.ZyQu1cqFAF.jpg
353 ms
xf7f77f3927a83113aa4bc88bc8a7a496_Generic.jpg.pagespeed.ic.zzmypHPFTo.jpg
360 ms
x9f238b8c2ecda49d60286114a3419bdf_S.jpg.pagespeed.ic.Qj6q1ZkLP4.jpg
459 ms
x4bd849795465891d5ff1d2380d790483_S.jpg.pagespeed.ic.aYv-wewmxW.jpg
482 ms
x0c755b271fc276651f8aad61368d3a45_S.jpg.pagespeed.ic.6kxHo9s8BB.jpg
471 ms
xe55f4d00517f1f1ecc307a494abdc28c_S.jpg.pagespeed.ic.iy3aYHwGqA.jpg
492 ms
x65a49865f2ebd6876d6599cca2d11039_S.jpg.pagespeed.ic.U2HKSLHgf_.jpg
480 ms
xa6bb8e99c3f0194cf4639e859bab5815_S.jpg.pagespeed.ic.inaqI6wQ7N.jpg
587 ms
x31b161b0798674ccf7dfbffcf9b3eb69_S.jpg.pagespeed.ic.zhlMoanvGZ.jpg
658 ms
xe9cb67f17453c770a0d56659315a7daa_S.jpg.pagespeed.ic.XnXRbQuDU2.jpg
664 ms
x311cf38086612986df2db2d80a2585de_S.jpg.pagespeed.ic.Vs_R1X0iBN.jpg
669 ms
x1128104723aad471c138060b5a58a0ed_S.jpg.pagespeed.ic.clkbYyL6lo.jpg
670 ms
xbd368c7a62c1da6cac274066cce276c4_S.jpg.pagespeed.ic.jUCePCUvzi.jpg
684 ms
x232939721b5f66ad6c3ec6038803cf9a_S.jpg.pagespeed.ic.t1QiWWLcyR.jpg
770 ms
x9a504470723562983cb83112604c56b3_S.jpg.pagespeed.ic.toGF46fSKn.jpg
890 ms
x68444504c1089f29c5371c3cd0c52047_S.jpg.pagespeed.ic.oDjEMOCM9h.jpg
895 ms
1080 ms
popup.html
815 ms
tooltip.html
820 ms
fontawesome-webfont.woff
1126 ms
OpNJno4VhNfK-RgpwWWxlilVXg.ttf
76 ms
all.js
23 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: