Tools & Wizards About Us
web4.ecolo.be screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

web4.ecolo.be

Ecolo - Le parti vert belge francophone - ecolo.be

Page Load Speed

3.4 sec in total

First Response

313 ms

Resources Loaded

2.5 sec

Page Rendered

562 ms

web4.ecolo.be screenshot

About Website

Welcome to web4.ecolo.be homepage info - get ready to check Web 4 Ecolo best content for Belgium right away, or after learning these important things about web4.ecolo.be

Retrouvez l'actualité, le programme, les élus et l'histoire du parti politique écologiste belge francophone !

Visit web4.ecolo.be

Key Findings

We analyzed Web4.ecolo.be page load time and found that the first response time was 313 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

web4.ecolo.be performance score

0

Network Requests Diagram

web4.ecolo.be

313 ms

www.ecolo.be

474 ms

main.css

94 ms

extensions.css

180 ms

css

22 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 Web4.ecolo.be, 71% (37 requests) were made to Ecolo.be and 8% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Ecolo.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 925.5 kB (16%)

Content Size

5.7 MB

After Optimization

4.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Web4.ecolo.be main page is 5.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. 50% of websites need less resources to load. Images take 4.6 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 59.0 kB

  • Original 78.0 kB
  • After minification 66.7 kB
  • After compression 19.0 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 11.3 kB, which is 14% 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 59.0 kB or 76% of the original size.

Image Optimization

-4%

Potential reduce by 182.2 kB

  • Original 4.6 MB
  • After minification 4.5 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. Web 4 Ecolo images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 644.3 kB

  • Original 895.3 kB
  • After minification 740.8 kB
  • After compression 251.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 644.3 kB or 72% of the original size.

CSS Optimization

-80%

Potential reduce by 40.0 kB

  • Original 49.8 kB
  • After minification 45.1 kB
  • After compression 9.8 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. Web4.ecolo.be needs all CSS files to be minified and compressed as it can save up to 40.0 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (41%)

Requests Now

46

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

web4.ecolo.be

web4.ecolo.be

313 ms

www.ecolo.be

www.ecolo.be

474 ms

main.css

main.css

94 ms

extensions.css

extensions.css

180 ms

css

css

22 ms

modernizr-2.6.2.min.js

modernizr-2.6.2.min.js

184 ms

jquery.min.js

jquery.min.js

5 ms

colorbox.css

colorbox.css

223 ms

jquery.js

jquery.js

484 ms

jquery.form.js

jquery.form.js

223 ms

jquery.autosave.js

jquery.autosave.js

223 ms

jquery.placeholder-label.js

jquery.placeholder-label.js

268 ms

ajaxCallback.js

ajaxCallback.js

273 ms

jquery.cookie.js

jquery.cookie.js

274 ms

jquery.colorbox.js

jquery.colorbox.js

278 ms

spip.mediabox.js

spip.mediabox.js

277 ms

jquery-ui.min.js

jquery-ui.min.js

5 ms

main.js

main.js

448 ms

addthis_widget.js

addthis_widget.js

13 ms

analytics.js

analytics.js

9 ms

bgHead.jpg

bgHead.jpg

145 ms

logo_creonsdemain.png

logo_creonsdemain.png

149 ms

menuSprite.png

menuSprite.png

152 ms

socialBottomSprite.jpg

socialBottomSprite.jpg

152 ms

arton6462.png

arton6462.png

982 ms

arton6463.jpg

arton6463.jpg

603 ms

arton6464.jpg

arton6464.jpg

1242 ms

arton6460.jpg

arton6460.jpg

1435 ms

arton6457.jpg

arton6457.jpg

1340 ms

arton6392.png

arton6392.png

450 ms

arton6148.jpg

arton6148.jpg

635 ms

breveon149.jpg

breveon149.jpg

693 ms

breveon99.jpg

breveon99.jpg

728 ms

loading.gif

loading.gif

785 ms

collect

collect

11 ms

toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf

toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf

8 ms

ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf

ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf

10 ms

piwik.js

piwik.js

396 ms

viewSprite.png

viewSprite.png

538 ms

dossierSprite.png

dossierSprite.png

595 ms

plusSprite.png

plusSprite.png

632 ms

shareSprite.png

shareSprite.png

687 ms

bottomSprite.png

bottomSprite.png

725 ms

M2Jd71oPJhLKp0zdtTvoM0DauxaEVho0aInXGvhmB4k.ttf

M2Jd71oPJhLKp0zdtTvoM0DauxaEVho0aInXGvhmB4k.ttf

96 ms

fpTVHK8qsXbIeTHTrnQH6Edtd7Dq2ZflsctMEexj2lw.ttf

fpTVHK8qsXbIeTHTrnQH6Edtd7Dq2ZflsctMEexj2lw.ttf

97 ms

boost

boost

15 ms

300lo.json

300lo.json

37 ms

overlay.png

overlay.png

658 ms

border.png

border.png

667 ms

controls.png

controls.png

698 ms

sh.07f0d9bf220d07a763adad1e.html

sh.07f0d9bf220d07a763adad1e.html

25 ms

bg_direction_nav.png

bg_direction_nav.png

91 ms

SEO Factors

web4.ecolo.be SEO score

0

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Web4.ecolo.be can be misinterpreted by Google and other search engines. Our service has detected that French 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 Web4.ecolo.be 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

web4.ecolo.be

Open Graph description is not detected on the main page of Web 4 Ecolo. 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: