Tools & Wizards About Us
eneco.be screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

eneco.be

Energieleverancier voor duurzame energie | Eneco België

Page Load Speed

4.8 sec in total

First Response

651 ms

Resources Loaded

2.8 sec

Page Rendered

1.3 sec

eneco.be screenshot

About Website

Welcome to eneco.be homepage info - get ready to check Eneco best content for Belgium right away, or after learning these important things about eneco.be

Eneco kiest als energieleverancier voor 100% groene elektriciteit uit eigen land. Bereken jouw voordelig energietarief.

Visit eneco.be

Key Findings

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

Performance Metrics

eneco.be performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

88/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

58/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value4,750 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value17.6 s

4/100

10%

Network Requests Diagram

eneco.be

651 ms

nl

715 ms

gtm.js

194 ms

app.min.css

135 ms

slick.css

58 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 88% of them (53 requests) were addressed to the original Eneco.be, 5% (3 requests) were made to Dev.visualwebsiteoptimizer.com and 3% (2 requests) were made to Energy.eneco.be. The less responsive or slowest element that took the longest time to load (715 ms) belongs to the original domain Eneco.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 713.2 kB (43%)

Content Size

1.6 MB

After Optimization

934.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eneco.be main page is 1.6 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. Javascripts take 573.3 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 93.4 kB

  • Original 117.1 kB
  • After minification 96.0 kB
  • After compression 23.7 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 21.1 kB, which is 18% 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 93.4 kB or 80% of the original size.

Image Optimization

-10%

Potential reduce by 55.8 kB

  • Original 570.6 kB
  • After minification 514.8 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. Eneco images are well optimized though.

JavaScript Optimization

-41%

Potential reduce by 234.4 kB

  • Original 573.3 kB
  • After minification 496.4 kB
  • After compression 338.9 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 234.4 kB or 41% of the original size.

CSS Optimization

-85%

Potential reduce by 329.6 kB

  • Original 386.9 kB
  • After minification 378.2 kB
  • After compression 57.3 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. Eneco.be needs all CSS files to be minified and compressed as it can save up to 329.6 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (47%)

Requests Now

49

After Optimization

26

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eneco.be

eneco.be

651 ms

nl

nl

715 ms

gtm.js

gtm.js

194 ms

app.min.css

app.min.css

135 ms

slick.css

slick.css

58 ms

main.css

main.css

18 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

119 ms

jquery.matchHeight-min.js

jquery.matchHeight-min.js

52 ms

jquery.validate.min.js

jquery.validate.min.js

63 ms

jquery.validate.unobtrusive.min.js

jquery.validate.unobtrusive.min.js

123 ms

jquery.unobtrusive-ajax.min.js

jquery.unobtrusive-ajax.min.js

90 ms

jquery.validate.unobtrusive.errorhandling.js

jquery.validate.unobtrusive.errorhandling.js

190 ms

slick.min.js

slick.min.js

188 ms

js.cookie.min.js

js.cookie.min.js

198 ms

util.js

util.js

198 ms

modal.js

modal.js

197 ms

stickyfill.js

stickyfill.js

196 ms

popper.js

popper.js

279 ms

dropdown.js

dropdown.js

197 ms

jquery.nav.js

jquery.nav.js

321 ms

pagination.min.js

pagination.min.js

324 ms

chart.min.js

chart.min.js

471 ms

main.js

main.js

387 ms

map.js

map.js

400 ms

app.min.js

app.min.js

319 ms

custom.js

custom.js

398 ms

j.php

j.php

80 ms

sprites.png

sprites.png

279 ms

evd0005286-1.jpg

evd0005286-1.jpg

169 ms

eneco-gradient-rgb-80x80-smartphone-01.png

eneco-gradient-rgb-80x80-smartphone-01.png

169 ms

eneco-gradient-rgb-80x80-solar-panel.svg

eneco-gradient-rgb-80x80-solar-panel.svg

172 ms

eneco-iconen-windmolens.svg

eneco-iconen-windmolens.svg

180 ms

eneco-oneplanet-icoon-rgb.svg

eneco-oneplanet-icoon-rgb.svg

187 ms

evd0005269-min.jpg

evd0005269-min.jpg

207 ms

evd0005271-min.jpg

evd0005271-min.jpg

216 ms

evd0005331-min.jpg

evd0005331-min.jpg

265 ms

two-men-checking-information-on-laptop.jpg

two-men-checking-information-on-laptop.jpg

220 ms

koppel-op-groene-background.jpg

koppel-op-groene-background.jpg

227 ms

mobile-backdrop.png

mobile-backdrop.png

248 ms

dk-caroussel-img-2.jpg

dk-caroussel-img-2.jpg

292 ms

292338473-3227937557471129-7068480814826580887-n-1-2.jpeg

292338473-3227937557471129-7068480814826580887-n-1-2.jpeg

256 ms

eneco-besparen-case-1.jpg

eneco-besparen-case-1.jpg

274 ms

eneco-ohl.jpg

eneco-ohl.jpg

328 ms

evd0005294.jpg

evd0005294.jpg

329 ms

dpgmadia-eneco-david-16.jpg

dpgmadia-eneco-david-16.jpg

289 ms

moving.jpg

moving.jpg

329 ms

evd0005273-min.jpg

evd0005273-min.jpg

331 ms

etelkamedium-webfont.woff

etelkamedium-webfont.woff

362 ms

v.gif

v.gif

62 ms

va-20f437c77e8177d40efc102933b96327.js

va-20f437c77e8177d40efc102933b96327.js

9 ms

etelkaMedium.woff

etelkaMedium.woff

292 ms

etelkatextpro.woff

etelkatextpro.woff

226 ms

etelkaLight.woff

etelkaLight.woff

257 ms

etelkatextprobold.woff

etelkatextprobold.woff

519 ms

etelkalight-webfont.woff

etelkalight-webfont.woff

228 ms

etelkablack-webfont.woff

etelkablack-webfont.woff

257 ms

etelkatext-bold-webfont.woff

etelkatext-bold-webfont.woff

290 ms

elqCfg.min.js

elqCfg.min.js

71 ms

svrGP

svrGP

609 ms

svrGP

svrGP

147 ms

Accessibility Review

eneco.be accessibility score

81

Accessibility Issues

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

eneco.be best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

eneco.be SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    NL

  • Language Claimed

    NL

  • Encoding

    UTF-8

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

eneco.be

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