5.7 sec in total
344 ms
5.2 sec
147 ms
Visit lzo.de now to see the best up-to-date LzO content for Germany and also check out these interesting facts you probably never knew about lzo.de
Unsere Nähe bringt Sie weiter. Seit 1786. Und auch in Zukunft. Unser KundenServiceCenter erreichen Sie montags bis freitags von 8 bis 20 Uhr: 0441 2300.
Visit lzo.deWe analyzed Lzo.de page load time and found that the first response time was 344 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
lzo.de performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value5.7 s
16/100
25%
Value7.1 s
31/100
10%
Value1,060 ms
25/100
30%
Value0.379
28/100
15%
Value7.9 s
43/100
10%
344 ms
1176 ms
569 ms
702 ms
947 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lzo.de, 98% (98 requests) were made to Banking.lzo.com and 1% (1 request) were made to Sparkasse.de. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Banking.lzo.com.
Page size can be reduced by 519.7 kB (46%)
1.1 MB
621.0 kB
In fact, the total size of Lzo.de main page is 1.1 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. 25% of websites need less resources to load. Images take 549.1 kB which makes up the majority of the site volume.
Potential reduce by 50.5 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 50.5 kB or 83% of the original size.
Potential reduce by 70.3 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, LzO needs image optimization as it can save up to 70.3 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 241.1 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 241.1 kB or 71% of the original size.
Potential reduce by 157.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. Lzo.de needs all CSS files to be minified and compressed as it can save up to 157.8 kB or 82% of the original size.
Number of requests can be reduced by 56 (57%)
98
42
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LzO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
lzo.de
344 ms
StartenIPSTANDARD
1176 ms
std.js
569 ms
jquery.min.js
702 ms
jquery.ui.min.js
947 ms
jquery.easing.min.js
387 ms
opttan4_0_3.css
393 ms
suche.js
194 ms
oph.js
294 ms
if5_raster.css
292 ms
if5_container.css
98 ms
banking.css
196 ms
if5_oph_navi.css
103 ms
if5_oph.css
100 ms
if5_raster_project.css
100 ms
if5_raster_individuell.css
96 ms
buttons.css
101 ms
if5_ie.css
102 ms
setTrackingCookie.html
528 ms
lzo_logo_208x85.gif
100 ms
op_gen.jpg
97 ms
weiter_button.gif
100 ms
metanavi_verlauf_1px.gif
100 ms
ksc_telefon_rot.jpg
97 ms
ksc_telefon_grau.jpg
97 ms
bg.jpg
197 ms
weiter_button.gif
192 ms
beraterchat_rot.jpg
192 ms
beraterchat_grau.jpg
197 ms
co_00080.jpg
293 ms
videoberatung_rot.jpg
199 ms
videoberatung_grau.jpg
287 ms
beraterchat_sitenavi.jpg
287 ms
emailkontakt_rot.jpg
293 ms
emailkontakt_grau.jpg
294 ms
check.jpg
298 ms
filialezeiten_rot.jpg
381 ms
filialezeiten_grau.jpg
383 ms
co_00042.jpg
491 ms
onlineterminvereinbarung_rot.jpg
393 ms
onlineterminvereinbarung_grau.jpg
394 ms
navigation_border.gif
396 ms
en.gif
479 ms
ned.gif
478 ms
metanavi_weiter_button.gif
487 ms
if5_anmelden.png
491 ms
nur_im_internet.png
495 ms
charts
636 ms
charts
640 ms
charts
641 ms
charts
639 ms
charts
636 ms
charts
637 ms
charts
733 ms
charts
718 ms
charts
652 ms
charts
659 ms
charts
646 ms
charts
676 ms
beratung.png
740 ms
videoberatung.png
739 ms
icon_nachoben.gif
652 ms
icon_druck.gif
656 ms
facebook.png
658 ms
icon_twitter.png
670 ms
ecke0.png
736 ms
hinweis.png
647 ms
hol.gif
653 ms
hor.gif
654 ms
hbgo.gif
661 ms
hro.gif
670 ms
hbgu.gif
730 ms
hru.gif
649 ms
hul.gif
654 ms
hur.gif
651 ms
nol.gif
656 ms
nor.gif
661 ms
nbg.gif
643 ms
no.gif
644 ms
nc.gif
649 ms
nul_windows.gif
653 ms
nur.gif
655 ms
is.gif
657 ms
iar.gif
579 ms
ir.gif
580 ms
rbg.gif
594 ms
mail.png
600 ms
finden.png
603 ms
berater_aktiv.png
606 ms
notfall.png
577 ms
if5_druck.css
99 ms
op_oph_scardplus_ts99536956.png
287 ms
ppl.gif
100 ms
pu.gif
101 ms
bg_gen.png
97 ms
bg_gen.png
99 ms
weiter_button.gif
182 ms
bg_gen.png
196 ms
bg_gen.png
195 ms
ppr.gif
197 ms
lzo.de 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.
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
lzo.de 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
lzo.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
DE
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lzo.de can be misinterpreted by Google and other search engines. Our service has detected that German 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 Lzo.de 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.
lzo.de
Open Graph description is not detected on the main page of LzO. 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: