3.5 sec in total
494 ms
2.9 sec
138 ms
Welcome to ezag.de homepage info - get ready to check Ez AG best content right away, or after learning these important things about ezag.de
Visit ezag.deWe analyzed Ezag.de page load time and found that the first response time was 494 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
ezag.de performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value4.8 s
30/100
25%
Value7.6 s
25/100
10%
Value90 ms
99/100
30%
Value0
100/100
15%
Value8.1 s
41/100
10%
494 ms
94 ms
184 ms
276 ms
186 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Ezag.de, 10% (4 requests) were made to Charts25.equitystory.com and 2% (1 request) were made to Code.etracker.com. The less responsive or slowest element that took the longest time to load (721 ms) relates to the external source Ezag.com.
Page size can be reduced by 560.6 kB (62%)
903.8 kB
343.2 kB
In fact, the total size of Ezag.de main page is 903.8 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. 30% of websites need less resources to load. Javascripts take 587.3 kB which makes up the majority of the site volume.
Potential reduce by 22.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. This page needs HTML code to be minified as it can gain 3.4 kB, which is 12% 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 22.7 kB or 78% of the original size.
Potential reduce by 4.1 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. Ez AG images are well optimized though.
Potential reduce by 450.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 450.4 kB or 77% of the original size.
Potential reduce by 83.3 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. Ezag.de needs all CSS files to be minified and compressed as it can save up to 83.3 kB or 85% of the original size.
Number of requests can be reduced by 24 (60%)
40
16
The browser has sent 40 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ez AG. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
startseite.html
494 ms
style.css
94 ms
stylesheet_c2d4ae6342.css
184 ms
basic_01.css
276 ms
style.css
186 ms
extensions_01.css
374 ms
jquery-1.7.x-1.8.x-1.2.x.js
652 ms
jquery.cycle.all-2.9999.8.min.js
280 ms
prototype.js
631 ms
scriptaculous.js
277 ms
javascript_0b12553063.js
367 ms
slightbox.css
371 ms
slimbox.2.0.4.yui.js
377 ms
builder.js
97 ms
effects.js
104 ms
dragdrop.js
189 ms
controls.js
101 ms
slider.js
101 ms
sound.js
99 ms
logo_01_d.png
96 ms
icon_lupe.png
96 ms
0e6ded3f7f.jpg
98 ms
89d4b8108e.jpg
93 ms
547c26da82.jpg
94 ms
6c29ed1c69.jpg
96 ms
1305_mainpic.jpg
182 ms
03961bf766.gif
721 ms
isotope_02.jpg
378 ms
05f2eb3306.png
187 ms
t.js
322 ms
cnt_js.php
214 ms
teaser2.php
403 ms
hg_ezag.png
95 ms
schatten_small.png
96 ms
lines3.png
98 ms
red_box.png
100 ms
unten_kachel.png
97 ms
caption_slider.png
188 ms
teaser2.css
209 ms
png_teaser.php
310 ms
aktie.png
209 ms
ezag.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
<frame> or <iframe> elements do not have a title
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
ezag.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
ezag.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ezag.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Ezag.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.
ezag.de
Open Graph description is not detected on the main page of Ez AG. 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: