4 sec in total
468 ms
3.4 sec
157 ms
Welcome to wemag.com homepage info - get ready to check WEMAG best content for Germany right away, or after learning these important things about wemag.com
Ökostrom, Erdgas und Glasfaser-Internet von der WEMAG, dem Ökoenergie-Anbieter aus dem Norden. Wechseln Sie jetzt!
Visit wemag.comWe analyzed Wemag.com page load time and found that the first response time was 468 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
wemag.com performance score
name
value
score
weighting
Value14.0 s
0/100
10%
Value15.0 s
0/100
25%
Value20.0 s
0/100
10%
Value1,370 ms
16/100
30%
Value0.2
62/100
15%
Value17.4 s
4/100
10%
468 ms
103 ms
197 ms
199 ms
201 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 96% of them (48 requests) were addressed to the original Wemag.com, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Wemag.com.
Page size can be reduced by 191.3 kB (11%)
1.7 MB
1.5 MB
In fact, the total size of Wemag.com main page is 1.7 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 1.5 MB which makes up the majority of the site volume.
Potential reduce by 20.1 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 6.0 kB, which is 24% 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 20.1 kB or 80% of the original size.
Potential reduce by 51.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. WEMAG images are well optimized though.
Potential reduce by 90.6 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 90.6 kB or 58% of the original size.
Potential reduce by 29.0 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. Wemag.com needs all CSS files to be minified and compressed as it can save up to 29.0 kB or 84% of the original size.
Number of requests can be reduced by 21 (43%)
49
28
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WEMAG. 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 7 to 1 for CSS and as a result speed up the page load time.
wemag.com
468 ms
style.css
103 ms
content.css
197 ms
news_feed.css
199 ms
keyvisual.css
201 ms
autocomplete.css
203 ms
startseite_landingpage.css
202 ms
jquery.fancybox-1.3.4.css
203 ms
jquery-1.5.min.js
399 ms
jquery.easing.1.3.js
294 ms
jquery.autocomplete.pack.js
302 ms
liScroll.js
303 ms
slides.min.jquery.js
304 ms
startseite_landingpage.js
309 ms
jquery_fancybox_1.3.4.pack.js
393 ms
main.js
422 ms
wemiorechner_klein_neu.jpg
895 ms
bg_mainnavi_blau.png
103 ms
bg_mainnavi_grau.png
104 ms
wemag_header1.jpg
1013 ms
wemag_header2.jpg
301 ms
wemag_header3.jpg
605 ms
bg_teaser_linksAktiv.png
100 ms
slide_prev.png
197 ms
slide_next.png
199 ms
Fotolia_84129446_Subscription_Monthly_M.jpg
303 ms
Hausnotruf-klein.jpg
2503 ms
teaser-jugend-forscht-101.jpg
498 ms
oekotest_teaser.jpg
401 ms
startseite_klein_oekostrategie.jpg
402 ms
teaser_startseite_oekokraftwerke.jpg
502 ms
teaser_startseite_kundenmagazin.jpg
504 ms
teaser_startseite_facebook.png
599 ms
service_lineontop.gif
602 ms
service_button_stoerungsannahme.gif
604 ms
service_button_presse.gif
698 ms
service_button_kontakt.gif
701 ms
service_button_facebook.gif
702 ms
wem_web_service_button_google_plus.gif
703 ms
service_button_wemagblog.gif
797 ms
service_button_youtube.gif
800 ms
service_button_wemio.gif
801 ms
bg_footer_content.gif
800 ms
icon_wemag_netz.gif
898 ms
icon_edat.gif
900 ms
icon_wemacom.gif
902 ms
icon_mea.gif
901 ms
ga.js
28 ms
stars.png
955 ms
__utm.gif
11 ms
wemag.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
wemag.com 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
Missing source maps for large first-party JavaScript
wemag.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wemag.com 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 Wemag.com 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.
wemag.com
Open Graph description is not detected on the main page of WEMAG. 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: