5 sec in total
412 ms
4.3 sec
319 ms
Visit infolex.lt now to see the best up-to-date INFOLEX content for Lithuania and also check out these interesting facts you probably never knew about infolex.lt
Lietuvos teis?s naujienos, spaudos ap?valga
Visit infolex.ltWe analyzed Infolex.lt page load time and found that the first response time was 412 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
infolex.lt performance score
412 ms
2604 ms
531 ms
551 ms
278 ms
Our browser made a total of 80 requests to load all elements on the main page. We found that 50% of them (40 requests) were addressed to the original Infolex.lt, 26% (21 requests) were made to Static.xx.fbcdn.net and 6% (5 requests) were made to Scontent-iad3-1.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Infolex.lt.
Page size can be reduced by 113.4 kB (33%)
345.9 kB
232.5 kB
In fact, the total size of Infolex.lt main page is 345.9 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. 50% of websites need less resources to load. Images take 209.4 kB which makes up the majority of the site volume.
Potential reduce by 67.9 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 12.9 kB, which is 16% 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 67.9 kB or 82% of the original size.
Potential reduce by 24.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. Obviously, INFOLEX needs image optimization as it can save up to 24.4 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 11.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 11.2 kB or 27% of the original size.
Potential reduce by 9.9 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. Infolex.lt needs all CSS files to be minified and compressed as it can save up to 9.9 kB or 82% of the original size.
Number of requests can be reduced by 37 (48%)
77
40
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of INFOLEX. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
infolex.lt
412 ms
start.asp
2604 ms
funcs.js
531 ms
Logo_small_2.png
551 ms
en2.gif
278 ms
lt2.gif
279 ms
on_left.png
290 ms
on_right.png
282 ms
off_left.png
283 ms
off_right.png
300 ms
hor.gif
278 ms
portal_nn.css
283 ms
count.php
248 ms
rss.gif
152 ms
teises_mokymai.png
305 ms
nta_baneris.gif
272 ms
advocatu.gif
279 ms
antstoliu.gif
299 ms
notaru.gif
411 ms
policijos.gif
415 ms
teismai.gif
418 ms
prokuraturos.jpg
567 ms
logo_ERPF1.jpg
440 ms
portal_ie.css
404 ms
smweb_Advokatas_Tomas_Bagdanskis.jpg
685 ms
smweb_02-72dpi.jpg
423 ms
smweb_ds_sabelija.jpg
436 ms
smweb_aaalflogo.jpg
534 ms
smweb_Bitalogo.jpg
537 ms
smweb_STRATEGUM.jpg
687 ms
smweb_TF%20logo.jpg
561 ms
smweb_1.jpg
715 ms
smweb_Jaroslav_Pavlovskij_Varul_2016.jpg
663 ms
smweb_cobalt.JPG
671 ms
smweb_julija_viktorija.jpg
693 ms
smweb_0_642030001358509820.jpg
667 ms
smweb_MRU_logotipas_spalvotas.jpg
677 ms
smweb_advoco_logo_new.png
834 ms
smweb_Triniti-LT-logo.jpg
698 ms
on_bg.png
696 ms
off_bg.png
715 ms
ga.js
31 ms
xgemius.js
580 ms
__utm.gif
12 ms
collect
67 ms
all.js
29 ms
69 ms
xd_arbiter.php
58 ms
xd_arbiter.php
82 ms
fpdata.js
114 ms
lsget.html
256 ms
like_box.php
251 ms
rexdot.js
116 ms
FbUd6dZS1Af.css
51 ms
dGJLq38YL-C.css
59 ms
f7m6HODnCDd.css
68 ms
i5_N_HL0uEJ.css
78 ms
MU2r9HyY0UU.css
77 ms
Msuaq9yC6iC.css
88 ms
_rx8naC75Dy.js
107 ms
VeFaH1CwyWY.js
134 ms
ICDbTSzjQEg.js
75 ms
TTCre3391I0.js
102 ms
njO1TPvGzoR.js
101 ms
b_6HNn_J2BZ.js
104 ms
7cm7D75Y0Sf.js
150 ms
rFmE1g6Dkoz.js
160 ms
336JejShbZp.js
145 ms
10928835_10153060751875559_8463130707448701268_n.png
135 ms
safe_image.php
144 ms
992986_10151692433230559_443128090_n.jpg
24 ms
12799221_10154018227845559_925835669636088372_n.jpg
28 ms
268626_388888474510274_254854447_n.jpg
26 ms
12507232_10153931861430559_1732368659193746537_n.jpg
28 ms
wL6VQj7Ab77.png
23 ms
s7jcwEQH7Sx.png
24 ms
QDwYpIaRyfG.png
23 ms
a-ZN6WoEOje.png
23 ms
I6-MnjEovm5.js
12 ms
vlXaquuXMrr.js
17 ms
infolex.lt SEO score
LT
N/A
WINDOWS-1257
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Infolex.lt can be misinterpreted by Google and other search engines. Our service has detected that Lithuanian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Infolex.lt main page’s claimed encoding is windows-1257. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
infolex.lt
Open Graph description is not detected on the main page of INFOLEX. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: