5.7 sec in total
426 ms
5 sec
246 ms
Click here to check amazing LEW content for Germany. Otherwise, check out these important facts you probably never knew about lew.de
Wir bieten Ihnen Strom und attraktive Angebote rund um die Energieerzeugung, - speicherung und Elektromobilität. Mehr erfahren!
Visit lew.deWe analyzed Lew.de page load time and found that the first response time was 426 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
lew.de performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value14.2 s
0/100
25%
Value13.6 s
2/100
10%
Value6,340 ms
0/100
30%
Value0.005
100/100
15%
Value19.2 s
2/100
10%
426 ms
324 ms
1904 ms
432 ms
318 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 90% of them (55 requests) were addressed to the original Lew.de, 3% (2 requests) were made to Pong.qubitproducts.com and 2% (1 request) were made to Grmtech.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Lew.de.
Page size can be reduced by 1.7 MB (53%)
3.3 MB
1.5 MB
In fact, the total size of Lew.de main page is 3.3 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. 45% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 114.8 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 44.7 kB, which is 35% 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 114.8 kB or 89% of the original size.
Potential reduce by 80.6 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. LEW images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 80% of the original size.
Potential reduce by 409.7 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. Lew.de needs all CSS files to be minified and compressed as it can save up to 409.7 kB or 89% of the original size.
Number of requests can be reduced by 30 (55%)
55
25
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LEW. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
lew.de
426 ms
www.lew.de
324 ms
www.lew.de
1904 ms
Global-RWE-Scripts_rcr.js
432 ms
jquery.tabSlideOut.v1.3.js
318 ms
bootstrap.min.js
532 ms
customValidation.js
324 ms
foundation.css
546 ms
lewStyles-2014.css
554 ms
slider.css
420 ms
buttons.css
476 ms
startup-pf-slider.js
524 ms
jquery.js
542 ms
foundation.min.js
658 ms
foundation.offcanvas.js
657 ms
decd4bb35c75ba84b4f39e547b1416fd35.js
625 ms
back.jpg
222 ms
lew-slider-regionfuerrio-u-bild-02_2016.png
544 ms
e-mobility-schnellladestation.png
763 ms
switch-bg.png
222 ms
pager-bg.png
923 ms
switch-bt.png
924 ms
icon-link-8x5.png
925 ms
QuickSearch-Lupe.png
927 ms
mainnav-back.png
926 ms
logo.png
929 ms
sprites.png
1122 ms
mann-und-frau-am-tablet.jpg
1132 ms
bt-kat2-bg.png
1028 ms
mainnav-trenner.png
1030 ms
f_mechaniker_283x178.png
1037 ms
t_lewmagazin.jpg
1142 ms
karriere.jpg
1138 ms
t_bewegteslicht.jpg
1351 ms
kundenkonto_frau_hand-am-laptop_navigation.jpg
1146 ms
subnav-backul.png
1227 ms
icosteckerblau.png
1238 ms
gasweiss.png
1243 ms
icoheizungweiss.png
1246 ms
sprite-finder-lew.png
1253 ms
fb.png
1335 ms
youtube.png
1346 ms
xing.png
1352 ms
webcam.png
1354 ms
icon_partnerportal_2.png
1362 ms
rweheadline-regularcondens-webfont.woff
1513 ms
rweheadline-lightcondens-webfont.woff
1562 ms
sub_nav.png
1397 ms
sub_nav_back.png
1402 ms
print.png
1402 ms
totop-l.png
1388 ms
totop-r.png
1509 ms
piwik.js
789 ms
totop-m.png
1377 ms
opentag-66627-1115049.js
36 ms
sprite-finder.png
1374 ms
qtracker-v3-min.js
26 ms
t2
344 ms
quicksearch-lupe.png
675 ms
tag2
131 ms
print-2014.css
109 ms
lew.de 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
[aria-*] attributes are not valid or misspelled
ARIA IDs are not unique
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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
lew.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
lew.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lew.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 Lew.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.
lew.de
Open Graph description is not detected on the main page of LEW. 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: