4.5 sec in total
1.1 sec
3.2 sec
270 ms
Click here to check amazing Gis content for Lithuania. Otherwise, check out these important facts you probably never knew about gis.lt
Maps.lt yra Interneto žemėlapių svetainė, skirta interaktyviai navigacijai teritorijoje, geografinės vietos paieškai žemėlapiuose, susipažinimui su geografinėmis duomenų bazėmis bei skaitmeniniais žem...
Visit gis.ltWe analyzed Gis.lt page load time and found that the first response time was 1.1 sec and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
gis.lt performance score
1107 ms
235 ms
238 ms
233 ms
169 ms
Our browser made a total of 129 requests to load all elements on the main page. We found that 27% of them (35 requests) were addressed to the original Gis.lt, 9% (11 requests) were made to Rtb-csync.smartadserver.com and 6% (8 requests) were made to Dsum.casalemedia.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Gis.lt.
Page size can be reduced by 227.9 kB (53%)
429.5 kB
201.7 kB
In fact, the total size of Gis.lt main page is 429.5 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. Javascripts take 268.5 kB which makes up the majority of the site volume.
Potential reduce by 35.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 11.1 kB, which is 24% 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 35.8 kB or 79% of the original size.
Potential reduce by 17.9 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, Gis needs image optimization as it can save up to 17.9 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 160.4 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 160.4 kB or 60% of the original size.
Potential reduce by 13.8 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. Gis.lt needs all CSS files to be minified and compressed as it can save up to 13.8 kB or 85% of the original size.
Number of requests can be reduced by 83 (72%)
115
32
The browser has sent 115 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gis. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and as a result speed up the page load time.
gis.lt
1107 ms
main.css
235 ms
form.css
238 ms
default.css
233 ms
config.js
169 ms
form_checker.js
240 ms
window.js
238 ms
swfobject.js
343 ms
jquery-1.4.2.min.js
571 ms
mapsltPlugins.js
345 ms
ads_demo
346 ms
smart.js
163 ms
ads_demo
240 ms
init-for-BBEposCodes-withExtra.js
634 ms
bb_one2n.js
505 ms
xgemius.js
577 ms
bk_2.png
144 ms
menu-1.png
146 ms
icon-1.gif
144 ms
icon-2.gif
143 ms
icon-3.gif
145 ms
maps_lt_logo.png
142 ms
menu-2-sep.png
235 ms
get.php
251 ms
get.php
270 ms
button-1.gif
235 ms
arrow-3.gif
309 ms
get.php
497 ms
get.php
397 ms
get.php
583 ms
get.php
425 ms
menu-2-bg.png
417 ms
analytics.js
23 ms
128 ms
arrow-1.gif
447 ms
all.js
18 ms
arrow-2.gif
510 ms
get.php
528 ms
linkid.js
46 ms
get.php
463 ms
get.php
480 ms
get.php
522 ms
get.php
547 ms
get.php
593 ms
get.php
587 ms
156 ms
sep-1.gif
567 ms
bb_one2n.113.65.77.1.js
562 ms
ac
195 ms
xd_arbiter.php
57 ms
xd_arbiter.php
80 ms
pixel.gif
190 ms
fpdata.js
130 ms
lsget.html
374 ms
CookieSync.html
13 ms
main.js.php
153 ms
233 ms
296 ms
299 ms
231 ms
bootstrapScript.js
232 ms
main.js.php
262 ms
mainScript.jpg
227 ms
quant.js
9 ms
CookieSync.min.js
6 ms
pixel.htm
51 ms
usermatch
28 ms
pixelpush
25 ms
p68r
73 ms
generic
14 ms
pixel
39 ms
sync
30 ms
93 ms
generic
26 ms
91 ms
usermatch
41 ms
90 ms
pixel
39 ms
ddc.htm
48 ms
pixel;r=1911529086;a=p-T1nhLcmCjVzQS;fpan=1;fpa=P0-792261746-1458495329695;ns=1;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458495329695;tzo=-180;ref=http%3A%2F%2Fgis.lt%2F;url=http%3A%2F%2Fcdn1.smartadserver.com%2Fdiff%2Frtb%2Fcsync%2FCookieSync.html%3Fnwid%3D1211%26dcid%3D6;ogl=
50 ms
gr
47 ms
68 ms
pixel.htm
50 ms
60 ms
66 ms
81 ms
98 ms
95 ms
Pug
57 ms
pixel
56 ms
rtset
63 ms
rum
53 ms
u.php
115 ms
um
186 ms
setuid
73 ms
74 ms
pixel
116 ms
crum
63 ms
ddc.htm
58 ms
sd
53 ms
crum
59 ms
xrefid.xgi
48 ms
match
72 ms
mapuser
49 ms
bd
86 ms
tap.php
61 ms
rum
40 ms
crum
35 ms
rum
107 ms
rum
33 ms
bd
54 ms
crum
27 ms
merge
58 ms
pixel.gif
39 ms
42 ms
m
47 ms
sync
98 ms
lr.gif
22 ms
crum
12 ms
29 ms
NAX6858289048739944195
47 ms
rexdot.js
119 ms
bbnaut-lib-1.7.5.min.js
333 ms
co
255 ms
like.php
79 ms
qeKvIRsJabD.js
51 ms
LVx-xkvaJ0b.png
42 ms
mainScript.js
285 ms
sale.api
105 ms
gis.lt SEO score
LT
LT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gis.lt can be misinterpreted by Google and other search engines. Our service has detected that Lithuanian is used on the page, and it matches the claimed language. Our system also found out that Gis.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.
gis.lt
Open Graph description is not detected on the main page of Gis. 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: