4.7 sec in total
432 ms
4 sec
202 ms
Welcome to lpp.si homepage info - get ready to check Lpp best content for Slovenia right away, or after learning these important things about lpp.si
Visit lpp.siWe analyzed Lpp.si page load time and found that the first response time was 432 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
lpp.si performance score
name
value
score
weighting
Value10.5 s
0/100
10%
Value13.3 s
0/100
25%
Value16.4 s
0/100
10%
Value7,000 ms
0/100
30%
Value0.001
100/100
15%
Value19.1 s
3/100
10%
432 ms
805 ms
223 ms
221 ms
268 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 87% of them (97 requests) were addressed to the original Lpp.si, 5% (6 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Lpp.si.
Page size can be reduced by 910.1 kB (53%)
1.7 MB
794.8 kB
In fact, the total size of Lpp.si main page is 1.7 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. 40% of websites need less resources to load. CSS take 553.5 kB which makes up the majority of the site volume.
Potential reduce by 95.7 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 95.7 kB or 75% of the original size.
Potential reduce by 30.7 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. Lpp images are well optimized though.
Potential reduce by 308.7 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 308.7 kB or 65% of the original size.
Potential reduce by 475.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. Lpp.si needs all CSS files to be minified and compressed as it can save up to 475.0 kB or 86% of the original size.
Number of requests can be reduced by 57 (55%)
103
46
The browser has sent 103 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lpp. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
lpp.si
432 ms
www.lpp.si
805 ms
system.base.css
223 ms
system.menus.css
221 ms
system.messages.css
268 ms
system.theme.css
269 ms
date.css
316 ms
datepicker.1.7.css
318 ms
domain_nav.css
364 ms
field.css
372 ms
node.css
413 ms
poll.css
414 ms
search.css
461 ms
user.css
465 ms
views.css
511 ms
colorbox_stockholmsyndrome.css
518 ms
ctools.css
560 ms
field_slideshow.css
561 ms
normalize.css
609 ms
tabs.css
611 ms
style.css
1214 ms
jplayer-jhl.css
665 ms
css
47 ms
stylesheet.css
927 ms
jquery.min.js
79 ms
jquery.once.js
708 ms
drupal.js
927 ms
cookieControl-5.1.min.js
977 ms
sl_lBnuPBAmsUwCFFMGzR7GFUxsnMgp9tC6ROYRBTnCr5A.js
977 ms
jquery.colorbox-min.js
814 ms
colorbox.js
975 ms
colorbox_stockholmsyndrome.js
1032 ms
modernizr.min.js
1036 ms
googleanalytics.js
1083 ms
jquery.cycle.all.js
1198 ms
field_slideshow.js
1140 ms
js
93 ms
jrespond.min.js
1142 ms
jquery.placeholder.min.js
1184 ms
jquery.sharrre-1.3.3.min.js
1192 ms
jquery.bxslider.min.js
1174 ms
jquery.mcustomscrollbar.min.js
1162 ms
jhl.js
1210 ms
plugins.js
1054 ms
clientside_validation_html5.js
1099 ms
body-bg.png
112 ms
logo-lpp.png
117 ms
holding-logo-circle.png
112 ms
night-overcast-moderate-rain.png
168 ms
info-phone-lpp.png
111 ms
search-bg.gif
212 ms
search-button.png
166 ms
slider-title-lpp.png
262 ms
arrow-white.png
221 ms
1-1foto_tamara_deu.jpg
324 ms
zpe-drsnik.jpeg
385 ms
prevoz-na-klic_0.jpg
378 ms
parkiraj-in-pelji-z-busom.jpg
326 ms
tehnicni_pregledi.jpg
411 ms
img_4561.jpg
378 ms
informativni_dnevi_2016.jpg
467 ms
napovedi-prihodov-busov.jpg
436 ms
varno-na-bus.jpg
510 ms
s-kolesom-na-bus.jpg
490 ms
elektromobilnost.jpg
562 ms
spremembe-linij.jpg
522 ms
lpp-slider.png
1057 ms
company-icon-logos.png
581 ms
rss.png
772 ms
arrow-white-up.png
620 ms
left-menu-arrows-lpp.png
784 ms
front-top-region-lpp.jpg
673 ms
arrow-white-right.png
826 ms
urbana.jpg
730 ms
arrow-red.png
833 ms
urbana-arrow.png
840 ms
avtobusno-oglasevanje.jpg
881 ms
najemi-bus.jpg
892 ms
lpp-video-background.png
941 ms
M59TomUAmyw.jpg
945 ms
EbWYl5TL4PY.jpg
951 ms
01t4vGu3AFM.jpg
904 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
31 ms
MTP_ySUJH_bn48VBG8sNStqQynqKV_9Plp7mupa0S4g.ttf
56 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
69 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
70 ms
stik-arrow-lpp.png
896 ms
stik-plus-lpp.png
949 ms
faq-arrows-lpp.png
945 ms
M59TomUAmyw
104 ms
k008.jpg
899 ms
k060.jpg
926 ms
9001_1.gif
906 ms
14001_1.gif
949 ms
www-embed-player-vflZsBgOl.css
70 ms
www-embed-player.js
94 ms
18001_1.gif
914 ms
footer-icons.png
847 ms
footer-ask-us-text-bg.png
848 ms
1eJU4PjErWSV5LNTKFXcze5UHikZLg3viIH581vcHWA.js
39 ms
ad_status.js
55 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
67 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
80 ms
footer-forms-arrow.png
841 ms
websi-jhl.png
847 ms
mol-logo-footer.png
895 ms
kom-zpe-logo.png
870 ms
bg_tab.png
848 ms
lpp-active-video.png
823 ms
slider-lpp-dragger-bg.png
116 ms
slider-lpp-dragger.png
112 ms
lpp.si accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
lpp.si 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
General
Impact
Issue
Detected JavaScript libraries
lpp.si SEO score
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
SL
SL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lpp.si can be misinterpreted by Google and other search engines. Our service has detected that Slovenian is used on the page, and it matches the claimed language. Our system also found out that Lpp.si 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.
lpp.si
Open Graph description is not detected on the main page of Lpp. 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: