Tools & Wizards About Us
vorweggehen.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

vorweggehen.com

innogy - Home

Page Load Speed

6.8 sec in total

First Response

1.2 sec

Resources Loaded

4.7 sec

Page Rendered

894 ms

vorweggehen.com screenshot

About Website

Visit vorweggehen.com now to see the best up-to-date Vorweggehen content and also check out these interesting facts you probably never knew about vorweggehen.com

Wir wollen das erste Land sein, das komplett auf neue Energien setzt. Sind wir Deutschen eigentlich verrückt geworden?

Visit vorweggehen.com

Key Findings

We analyzed Vorweggehen.com page load time and found that the first response time was 1.2 sec and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

vorweggehen.com performance score

0

Network Requests Diagram

vorweggehen.com

1177 ms

www.vorweggehen.de

894 ms

style.css

288 ms

doc_head.js

192 ms

public.css

191 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Vorweggehen.com, 58% (36 requests) were made to Vorweggehen.de and 8% (5 requests) were made to Etracker.de. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Vorweggehen.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 804.7 kB (25%)

Content Size

3.2 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vorweggehen.com main page is 3.2 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. 55% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 50.5 kB

  • Original 63.6 kB
  • After minification 56.4 kB
  • After compression 13.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 7.2 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 50.5 kB or 79% of the original size.

Image Optimization

-6%

Potential reduce by 133.6 kB

  • Original 2.2 MB
  • After minification 2.1 MB

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. Vorweggehen images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 435.8 kB

  • Original 687.8 kB
  • After minification 686.8 kB
  • After compression 252.0 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 435.8 kB or 63% of the original size.

CSS Optimization

-89%

Potential reduce by 184.8 kB

  • Original 208.3 kB
  • After minification 207.7 kB
  • After compression 23.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. Vorweggehen.com needs all CSS files to be minified and compressed as it can save up to 184.8 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (45%)

Requests Now

60

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

vorweggehen.com

vorweggehen.com

1177 ms

www.vorweggehen.de

www.vorweggehen.de

894 ms

style.css

style.css

288 ms

doc_head.js

doc_head.js

192 ms

public.css

public.css

191 ms

bootstrap.js

bootstrap.js

506 ms

e.js

e.js

431 ms

de4e62e752ae53fb6a6eebd0f6146aa702.js

de4e62e752ae53fb6a6eebd0f6146aa702.js

391 ms

wp-embed.min.js

wp-embed.min.js

187 ms

webfont.js

webfont.js

114 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

212 ms

body-bg.jpg

body-bg.jpg

209 ms

logo-campaign-de.png

logo-campaign-de.png

212 ms

zukunftswochen.jpg

zukunftswochen.jpg

662 ms

Fledermaus_bearbeitet-774x413.jpg

Fledermaus_bearbeitet-774x413.jpg

211 ms

Taucher-WKW-Fankel-5127-620x413.jpg

Taucher-WKW-Fankel-5127-620x413.jpg

662 ms

Ausschnitt-Titel-Brosch%C3%BCre-Es-geht-auch-elektrisch-774x413.jpg

Ausschnitt-Titel-Brosch%C3%BCre-Es-geht-auch-elektrisch-774x413.jpg

663 ms

EnergyAppAward_Head_21-978x364.jpg

EnergyAppAward_Head_21-978x364.jpg

661 ms

IMG_0325-551x413.jpg

IMG_0325-551x413.jpg

719 ms

EnergyApp_OM2-978x355.png

EnergyApp_OM2-978x355.png

1110 ms

govecs_lifestyle_couple_stairs_clean-222x80.jpg

govecs_lifestyle_couple_stairs_clean-222x80.jpg

740 ms

IMG_1814-222x80.png

IMG_1814-222x80.png

834 ms

servicepreis-222x80.png

servicepreis-222x80.png

856 ms

Beitragsbild1-978x355.jpg

Beitragsbild1-978x355.jpg

1033 ms

Horx-978x356.png

Horx-978x356.png

1760 ms

120905_RWE_Teaser_Master_File.jpg

120905_RWE_Teaser_Master_File.jpg

1012 ms

all.js

all.js

496 ms

sprite-tabnavi.png

sprite-tabnavi.png

982 ms

sprite-tabnavi-aktion.png

sprite-tabnavi-aktion.png

987 ms

sprite-main.png

sprite-main.png

1343 ms

sidebar-bg.jpg

sidebar-bg.jpg

1162 ms

bg_question_teaser.png

bg_question_teaser.png

1165 ms

rweheadline-lightcondens-webfont.woff

rweheadline-lightcondens-webfont.woff

1254 ms

rweheadline-regularcondens-webfont.woff

rweheadline-regularcondens-webfont.woff

1336 ms

rweheadline-mediumcondens-webfont.woff

rweheadline-mediumcondens-webfont.woff

1443 ms

marginalteaser_energie_app.png

marginalteaser_energie_app.png

1293 ms

smarthome_marginalteaser_255x487.png

smarthome_marginalteaser_255x487.png

1847 ms

thermo_marginalteaser_255x487.png

thermo_marginalteaser_255x487.png

1912 ms

teaserbig-ladesaulenfinder.png

teaserbig-ladesaulenfinder.png

1468 ms

footer-bg.jpg

footer-bg.jpg

1521 ms

footer-shadow.png

footer-shadow.png

1635 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

423 ms

266 ms

t.js

t.js

414 ms

pct

pct

232 ms

ga.js

ga.js

37 ms

player_api

player_api

171 ms

opentag-66627-1135195.js

opentag-66627-1135195.js

306 ms

__utm.gif

__utm.gif

65 ms

103 ms

www-widgetapi.js

www-widgetapi.js

32 ms

xd_arbiter.php

xd_arbiter.php

224 ms

xd_arbiter.php

xd_arbiter.php

478 ms

__utm.gif

__utm.gif

35 ms

cnt_js.php

cnt_js.php

870 ms

cntcc

cntcc

200 ms

qtracker-v3-min.js

qtracker-v3-min.js

31 ms

ActivityServer.bs

ActivityServer.bs

114 ms

t2

t2

192 ms

ebAttribution.js

ebAttribution.js

9 ms

tag2

tag2

165 ms

eventcnt.php

eventcnt.php

201 ms

SEO Factors

vorweggehen.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vorweggehen.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Vorweggehen.com 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.

Social Sharing Optimization

vorweggehen.com

Open Graph data is detected on the main page of Vorweggehen. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: