Tools & Wizards About Us
lza.de screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    67% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

lza.de

Lebenszentrum Adelshofen

Page Load Speed

3.4 sec in total

First Response

314 ms

Resources Loaded

3 sec

Page Rendered

158 ms

lza.de screenshot

About Website

Visit lza.de now to see the best up-to-date Lza content for Germany and also check out these interesting facts you probably never knew about lza.de

Ein freies Missionswerk innerhalb der evangelischen Landeskirche. Eine theologische Ausbildungsstätte. Ein christliches Schulungszentrum. Eine Lebensgemeinschaft von Christen.

Visit lza.de

Key Findings

We analyzed Lza.de page load time and found that the first response time was 314 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

lza.de performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.422

23/100

15%

TTI (Time to Interactive)

Value4.7 s

80/100

10%

Network Requests Diagram

lza.de

314 ms

www.lza.de

563 ms

accesskey.js

121 ms

screen.css

237 ms

v04.css

257 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 46% of them (23 requests) were addressed to the original Lza.de, 26% (13 requests) were made to Scontent.xx.fbcdn.net and 20% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (732 ms) relates to the external source Scontent.xx.fbcdn.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 38.9 kB (20%)

Content Size

198.4 kB

After Optimization

159.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lza.de main page is 198.4 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. 15% of websites need less resources to load. Images take 144.4 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 8.6 kB

  • Original 12.5 kB
  • After minification 11.2 kB
  • After compression 4.0 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 1.4 kB, which is 11% 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 8.6 kB or 68% of the original size.

Image Optimization

-2%

Potential reduce by 2.7 kB

  • Original 144.4 kB
  • After minification 141.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. Lza images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 15.4 kB

  • Original 25.7 kB
  • After minification 25.3 kB
  • After compression 10.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 15.4 kB or 60% of the original size.

CSS Optimization

-78%

Potential reduce by 12.2 kB

  • Original 15.7 kB
  • After minification 10.0 kB
  • After compression 3.5 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. Lza.de needs all CSS files to be minified and compressed as it can save up to 12.2 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (52%)

Requests Now

48

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lza. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

lza.de

lza.de

314 ms

www.lza.de

www.lza.de

563 ms

accesskey.js

accesskey.js

121 ms

screen.css

screen.css

237 ms

v04.css

v04.css

257 ms

tables_addin.css

tables_addin.css

260 ms

navigation.css

navigation.css

244 ms

badge_code_v2.gne

badge_code_v2.gne

81 ms

lza-start.jpg

lza-start.jpg

349 ms

drucker.gif

drucker.gif

228 ms

16-Oasentag.gif

16-Oasentag.gif

400 ms

3503271615_73ae108a7a_m.jpg

3503271615_73ae108a7a_m.jpg

56 ms

p

p

40 ms

bg-header.jpg

bg-header.jpg

262 ms

c-white.gif

c-white.gif

142 ms

bg-menu.gif

bg-menu.gif

182 ms

c-blue-active.gif

c-blue-active.gif

198 ms

c-blue.gif

c-blue.gif

257 ms

c-blue-2.gif

c-blue-2.gif

298 ms

listicon.gif

listicon.gif

311 ms

tr.gif

tr.gif

312 ms

piwik.js

piwik.js

390 ms

likebox.php

likebox.php

238 ms

410ucuAGgaJ.css

410ucuAGgaJ.css

281 ms

tSbl8xBI27R.css

tSbl8xBI27R.css

352 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

488 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

618 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

487 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

485 ms

piwik.php

piwik.php

576 ms

946328_10153061937775144_477641375_n.jpg

946328_10153061937775144_477641375_n.jpg

419 ms

12049740_10156401682590144_8506884611790956623_n.jpg

12049740_10156401682590144_8506884611790956623_n.jpg

486 ms

11214328_105182889853498_7658103035442225007_n.jpg

11214328_105182889853498_7658103035442225007_n.jpg

557 ms

11755147_10207558145258263_1701569426573322317_n.jpg

11755147_10207558145258263_1701569426573322317_n.jpg

621 ms

12715659_183633225340662_2725470504865265414_n.jpg

12715659_183633225340662_2725470504865265414_n.jpg

629 ms

12728788_180425645663633_1804040386952129544_n.jpg

12728788_180425645663633_1804040386952129544_n.jpg

626 ms

11988288_10205539352785919_7737281551268631657_n.jpg

11988288_10205539352785919_7737281551268631657_n.jpg

624 ms

1899922_720697701359391_693847245658532010_n.jpg

1899922_720697701359391_693847245658532010_n.jpg

630 ms

12814057_230153737332439_6925053753416511023_n.jpg

12814057_230153737332439_6925053753416511023_n.jpg

626 ms

1380498_466398846806852_1496759327_n.jpg

1380498_466398846806852_1496759327_n.jpg

689 ms

10403606_947877831896322_1260834924100490915_n.jpg

10403606_947877831896322_1260834924100490915_n.jpg

691 ms

12745533_236127846720491_2579560216233812172_n.jpg

12745533_236127846720491_2579560216233812172_n.jpg

732 ms

970669_1385792874979695_1814613567_n.jpg

970669_1385792874979695_1814613567_n.jpg

692 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

74 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

73 ms

print.css

print.css

119 ms

v04-ie.css

v04-ie.css

116 ms

v04-ie5.css

v04-ie5.css

116 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

69 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

137 ms

Accessibility Review

lza.de accessibility score

77

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

lza.de best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

lza.de SEO score

91

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lza.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 Lza.de main page’s claimed encoding is iso-8859-1. 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.

Social Sharing Optimization

lza.de

Open Graph description is not detected on the main page of Lza. 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: