3.8 sec in total
386 ms
3.1 sec
263 ms
Welcome to e-energy.de homepage info - get ready to check E Energy best content right away, or after learning these important things about e-energy.de
Visit e-energy.deWe analyzed E-energy.de page load time and found that the first response time was 386 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
e-energy.de performance score
name
value
score
weighting
Value2.7 s
60/100
10%
Value5.6 s
17/100
25%
Value5.0 s
64/100
10%
Value10 ms
100/100
30%
Value0.032
100/100
15%
Value5.5 s
71/100
10%
386 ms
991 ms
112 ms
325 ms
331 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original E-energy.de, 92% (48 requests) were made to Digitale-technologien.de and 4% (2 requests) were made to Etracker.de. The less responsive or slowest element that took the longest time to load (991 ms) relates to the external source Digitale-technologien.de.
Page size can be reduced by 47.3 kB (86%)
55.3 kB
7.9 kB
In fact, the total size of E-energy.de main page is 55.3 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. HTML takes 55.1 kB which makes up the majority of the site volume.
Potential reduce by 47.3 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 15.6 kB, which is 28% 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 47.3 kB or 86% of the original size.
Potential reduce by 14 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 40 (85%)
47
7
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E Energy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
e-energy.de
386 ms
991 ms
bmwi_theme.css
112 ms
styles.css
325 ms
jquery-1.8.3.min.js
331 ms
jquery.tools.min.js
220 ms
jquery.easing.1.3.js
218 ms
slides.min.jquery.js
223 ms
MediaMatcher.js
239 ms
mdd.lib.js
347 ms
usage.js
352 ms
preusage.js
395 ms
bmwi_logo_de.png;jsessionid=FBDFF8AE1117EC1542D1D725B230CFED
117 ms
icon_rss.gif
112 ms
bg_btn_quicksearch.gif
114 ms
bg_navigation.gif
113 ms
bg_navi_0.gif
113 ms
icon_breadcrumb.gif
117 ms
list_icon.gif
221 ms
navi_0_0.gif
232 ms
navi_0_2.gif
230 ms
navi_1_2.gif
223 ms
banner-animation.jpg;jsessionid=FBDFF8AE1117EC1542D1D725B230CFED
351 ms
abschlussbroschuere-e-energy.jpg;jsessionid=FBDFF8AE1117EC1542D1D725B230CFED
269 ms
icon_linkedin.gif
329 ms
icon_facebook.gif
332 ms
icon_g_plus.gif
349 ms
icon_twitter.gif
343 ms
icon_xing.gif
377 ms
icon_print.gif
440 ms
t.js
586 ms
bundessansweb-regular.woff
730 ms
bundesserifweb-regular.woff
751 ms
bundessansweb-bold.woff
649 ms
cnt_js.php
264 ms
cntcc
261 ms
screen-small.css
118 ms
screen-medium.css
118 ms
jquery-ui-1.9.2.custom.min.css
116 ms
jquery-ui-1.9.2.custom.min.css
152 ms
pplayer.bmwi.js
430 ms
pplayer.bmwi.bitv.js
219 ms
superfish.js
111 ms
jquery.bxSlider.min.js
114 ms
jquery.horizontaltouchwipe.min.js
112 ms
jquery-ui-1.9.2.custom.min.js
138 ms
jquery.syncHeight.min.js
184 ms
pagination.png
113 ms
arrow-prev_l.png
120 ms
arrow-next_xs.png
114 ms
screen-small.css
114 ms
screen-medium.css
112 ms
e-energy.de accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
e-energy.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
e-energy.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
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise E-energy.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that E-energy.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.
e-energy.de
Open Graph description is not detected on the main page of E Energy. 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: