8 sec in total
904 ms
6.9 sec
270 ms
Click here to check amazing EDT content for French Polynesia. Otherwise, check out these important facts you probably never knew about edt.pf
Retrouvez toutes les informations et les services réservés aux particuliers. Gérer l'électricité de votre maison et votre consommation électrique en ligne avec EDT ENGIE.
Visit edt.pfWe analyzed Edt.pf page load time and found that the first response time was 904 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
edt.pf performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value11.1 s
0/100
25%
Value20.0 s
0/100
10%
Value820 ms
35/100
30%
Value0.003
100/100
15%
Value39.2 s
0/100
10%
904 ms
155 ms
180 ms
179 ms
266 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 87% of them (69 requests) were addressed to the original Edt.pf, 5% (4 requests) were made to Agence.edt.pf and 3% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Edt.pf.
Page size can be reduced by 555.2 kB (27%)
2.1 MB
1.5 MB
In fact, the total size of Edt.pf main page is 2.1 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. 45% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 55.2 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 55.2 kB or 79% of the original size.
Potential reduce by 34.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. EDT images are well optimized though.
Potential reduce by 199.7 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 199.7 kB or 67% of the original size.
Potential reduce by 265.4 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. Edt.pf needs all CSS files to be minified and compressed as it can save up to 265.4 kB or 84% of the original size.
Number of requests can be reduced by 46 (61%)
75
29
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of EDT. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
www.edt.pf
904 ms
wp-emoji-release.min.js
155 ms
imgmap_style.css
180 ms
styles.css
179 ms
front.css
266 ms
bootstrap.css
459 ms
font-awesome.min.css
274 ms
jquery.fancybox-1.3.7.min.css
240 ms
style.css
524 ms
jquery.js
537 ms
jquery-migrate.min.js
326 ms
utils.min.js
353 ms
jquery.imagemapster.min.js
457 ms
imagemapper_script.js
413 ms
bootstrap.min.js
536 ms
front.js
499 ms
chosen.jquery.min.js
549 ms
swfobject.js
549 ms
sam-layout.min.js
585 ms
frontend.js
609 ms
nivo-slider.js
623 ms
style.css
622 ms
style-frontpage.css
581 ms
style-mobile.css
580 ms
core.min.js
641 ms
widget.min.js
642 ms
mouse.min.js
649 ms
resizable.min.js
649 ms
draggable.min.js
678 ms
button.min.js
678 ms
position.min.js
727 ms
dialog.min.js
728 ms
editor.min.js
734 ms
ajax.js
778 ms
jquery.form.min.js
782 ms
scripts.js
782 ms
jquery.fancybox-1.3.7.min.js
813 ms
jquery.easing.pack.js
727 ms
jquery.mousewheel.min.js
711 ms
jquery.metadata.pack.js
754 ms
fontfaces.css
418 ms
content-style.css
417 ms
newsletter.css
443 ms
ga.js
66 ms
agenceedtiframe.php
2580 ms
brand-colours-14_v2.png
135 ms
brand-colours-red-14.png
159 ms
brand-colours-violet-14.png
135 ms
240x108_EDT-ENGIE.jpg
159 ms
site-EDT-bandeau-acceuil-FACTURE-1440x400.jpg
312 ms
slider3.png
483 ms
slider2.png
559 ms
slider1.png
507 ms
slider4.png
517 ms
Affiche-Village-de-lEau-2016-300x300.jpg
424 ms
Actu-site-Val%C3%A9rie-HARE-300x300.jpg
588 ms
Photo-conf%C3%A9rence-de-presse-1-450x253.jpg
672 ms
kitsecurite.jpg
693 ms
centralehydroelentrique.jpg
794 ms
productionentempsreel.jpg
834 ms
agence.png
750 ms
newsletter.png
763 ms
en_bref.png
790 ms
sdk.js
44 ms
loading.gif
816 ms
nimbussannov-reg-webfont.woff
827 ms
elusive.woff
858 ms
nimbussannov-lig-webfont.woff
868 ms
__utm.gif
98 ms
sam-ajax.php
933 ms
sam-ajax.php
991 ms
arrows.png
818 ms
182 ms
xd_arbiter.php
19 ms
xd_arbiter.php
49 ms
jquery.js
1560 ms
jquery.jqplot.js
1760 ms
jqplot.pieRenderer.js
907 ms
jquery.jqplot.css
905 ms
edt.pf 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.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
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
<frame> or <iframe> elements do not have a title
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
edt.pf 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
edt.pf SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
FR
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Edt.pf can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed English language. Our system also found out that Edt.pf 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.
edt.pf
Open Graph description is not detected on the main page of EDT. 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: