4.5 sec in total
348 ms
3.9 sec
313 ms
Welcome to eneco.com homepage info - get ready to check Eneco best content for Netherlands right away, or after learning these important things about eneco.com
We must act now to leave future generations a liveable planet. We take our responsibility. Together with our customers, we take steps towards becoming climate neutral in 2035.
Visit eneco.comWe analyzed Eneco.com page load time and found that the first response time was 348 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
eneco.com performance score
name
value
score
weighting
Value2.7 s
61/100
10%
Value3.9 s
52/100
25%
Value5.7 s
52/100
10%
Value2,310 ms
5/100
30%
Value0
100/100
15%
Value14.6 s
8/100
10%
348 ms
687 ms
431 ms
446 ms
482 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 89% of them (102 requests) were addressed to the original Eneco.com, 3% (3 requests) were made to S.ytimg.com and 2% (2 requests) were made to Projects.elitechnology.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Eneco.com.
Page size can be reduced by 1.3 MB (58%)
2.3 MB
974.0 kB
In fact, the total size of Eneco.com main page is 2.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. 55% of websites need less resources to load. Javascripts take 809.0 kB which makes up the majority of the site volume.
Potential reduce by 34.3 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 34.3 kB or 74% of the original size.
Potential reduce by 58.9 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.
Potential reduce by 610.4 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 610.4 kB or 75% of the original size.
Potential reduce by 623.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. Eneco.com needs all CSS files to be minified and compressed as it can save up to 623.8 kB or 85% of the original size.
Number of requests can be reduced by 84 (79%)
106
22
The browser has sent 106 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 82 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
348 ms
687 ms
dtagent625_gbjnpt_1006.js
431 ms
default.min.FD4D8CC89BDA464AD83CBC75B76789F8.css
446 ms
default2.min.3A9617C3B42AE15DCF71FFEE315CE39D.css
482 ms
responsive_modernizr_26EED6A076E03E6CFB6D3723F85B8A89.js
359 ms
VisitorIdentification.js
186 ms
eneco3_9679572F9E970AF7238DE113FAE0E78F.js
530 ms
2a3a6c
19 ms
enecologo
135 ms
bannernieuwegein.ashx
1146 ms
telraam
138 ms
icon_nieuws_320x180.ashx
136 ms
icon_nieuws_320x180
138 ms
icon_financieel_320x180.ashx
373 ms
icon_financieel_320x180
374 ms
icon_contact_320x180.ashx
373 ms
icon_contact_320x180
374 ms
scroll_down.png
373 ms
icon_facebook
561 ms
icon_twitter
563 ms
icon_linkedin
564 ms
icon_youtube
562 ms
iconforum
562 ms
wwflogo_205
595 ms
init.js
343 ms
MVDKl5TreXA
99 ms
2A3A6C_0_0.ttf
896 ms
2A3A6C_1_0.ttf
827 ms
2A3A6C_2_0.ttf
843 ms
fontello.ttf
663 ms
www-embed-player-vflfNyN_r.css
258 ms
www-embed-player.js
302 ms
base.js
340 ms
sprite.png
333 ms
sides.png
437 ms
scroll-more-primary.png
438 ms
slide.animation.js
544 ms
selectbutton.directive.js
544 ms
submitbutton.directive.js
609 ms
togglebutton.directive.js
618 ms
fieldrenderer.directive.js
631 ms
disabledinput.directive.js
637 ms
dropdown.directive.js
662 ms
formfield.directive.js
706 ms
badge.directive.js
707 ms
tooltip.directive.js
718 ms
productOfferColumn.directive.js
723 ms
loader.directive.js
748 ms
qubitclick.directive.js
795 ms
qubitscroll.directive.js
798 ms
qubitsocial.directive.js
805 ms
qubittracking.directive.js
813 ms
collapse.directive.js
836 ms
sameheight.directive.js
862 ms
showsection.directive.js
872 ms
numericValidator.directive.js
875 ms
postalCodeValidator.directive.js
880 ms
badge.filter.js
888 ms
jquery.min.js
35 ms
dcx.default.va.js
17 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
37 ms
ad_status.js
40 ms
ecommerce.filters.js
726 ms
currencydecimal.filter.js
761 ms
currencysplit.filter.js
771 ms
todecimal.filter.js
779 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
32 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
34 ms
isempty.filter.js
785 ms
math.filters.js
757 ms
orempty.filter.js
696 ms
ecommerce.controller.js
704 ms
replacementProduct.controller.js
634 ms
productorder.controller.js
643 ms
packagechooser.controller.js
563 ms
producttiles.controller.js
546 ms
quickbox.controller.js
571 ms
heatfailure.controller.js
603 ms
question.controller.js
563 ms
toontest.controller.js
558 ms
toontest.directives.js
554 ms
angular.min.js
546 ms
app.js
572 ms
utility.service.js
579 ms
formhelper.service.js
535 ms
tracking.app.js
456 ms
qubitbase.service.js
472 ms
base.service.js
450 ms
quickbox.service.js
476 ms
ecommerce.service.js
407 ms
utility.app.js
345 ms
usage.service.js
285 ms
tariff.service.js
322 ms
productorder.app.js
308 ms
productorder.service.js
309 ms
productoffer.service.js
360 ms
packagechooser.service.js
362 ms
productquestion.service.js
359 ms
aansluiting.service.js
391 ms
heatfailure.service.js
355 ms
ng-table.min.js
361 ms
question.app.js
397 ms
toontest.service.js
389 ms
cookie.service.js
388 ms
angular-locale_nl-nl.js
392 ms
angular-resource.min.js
392 ms
angular-animate.js
393 ms
sitehelper.service.js
409 ms
encryption.service.js
400 ms
querystring.service.js
402 ms
productorder.model.js
359 ms
collection.service.js
280 ms
domReady.js
126 ms
eneco.com accessibility score
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
eneco.com 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
eneco.com SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eneco.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Eneco.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.
eneco.com
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: