7.5 sec in total
321 ms
6.9 sec
289 ms
Click here to check amazing GRDF content for France. Otherwise, check out these important facts you probably never knew about grdf.fr
GRDF, distribution de gaz naturel en France. GRDF est au service des particuliers, des fournisseurs, entreprises, des installateurs, des prestataires, des acteurs du biométhane et des collectivités lo...
Visit grdf.frWe analyzed Grdf.fr page load time and found that the first response time was 321 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
grdf.fr performance score
name
value
score
weighting
Value12.8 s
0/100
10%
Value32.4 s
0/100
25%
Value14.5 s
1/100
10%
Value2,650 ms
4/100
30%
Value0.066
97/100
15%
Value36.2 s
0/100
10%
321 ms
510 ms
322 ms
535 ms
564 ms
Our browser made a total of 136 requests to load all elements on the main page. We found that 59% of them (80 requests) were addressed to the original Grdf.fr, 10% (13 requests) were made to Pixel.mathtag.com and 4% (5 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (5 sec) belongs to the original domain Grdf.fr.
Page size can be reduced by 2.8 MB (51%)
5.6 MB
2.7 MB
In fact, the total size of Grdf.fr main page is 5.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. 65% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 111.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. 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 111.7 kB or 86% of the original size.
Potential reduce by 65.6 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. GRDF images are well optimized though.
Potential reduce by 1.3 MB
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 1.3 MB or 70% of the original size.
Potential reduce by 1.3 MB
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. Grdf.fr needs all CSS files to be minified and compressed as it can save up to 1.3 MB or 89% of the original size.
Number of requests can be reduced by 98 (78%)
126
28
The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GRDF. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
grdf.fr
321 ms
www.grdf.fr
510 ms
jquery.min.js
322 ms
jquery-plugins.js
535 ms
primefaces.js
564 ms
jsf.js
343 ms
aui.css
479 ms
main.css
351 ms
barebone.jsp
901 ms
vert-deau.css
448 ms
common.css
609 ms
contenu.css
608 ms
contactFormulaire.css
709 ms
home.css
761 ms
liferay.css
660 ms
rebond.css
657 ms
specific.css
687 ms
particuliers
787 ms
particuliers
803 ms
particuliers
823 ms
moteur.js
827 ms
particuliers
1036 ms
particuliers
1033 ms
gazmap.js
942 ms
pgmapstools-min.js
941 ms
particuliers
940 ms
particuliers
940 ms
particuliers
939 ms
main.js
938 ms
bootstrap.min.js
969 ms
jquery.fitvids.js
983 ms
jquery.bxslider.min.js
1000 ms
js
91 ms
conversion.js
36 ms
gtm.js
42 ms
analytics.js
20 ms
collect
12 ms
collect
58 ms
6812d0ec-df0c-4acc-89e1-1493d3e8712e
329 ms
68f7fe08-4515-4c2a-9af8-db2f6b74759e
142 ms
e9632793-05ac-4153-bbb1-c8bfb6e57e77
328 ms
b605ca9d-de79-4ce2-8953-5af6ae7a4eeb
317 ms
272f3cf5-92ae-4849-86a4-82f89ecc7e3a
1153 ms
3daed025-3441-475a-b859-fca60f788b3e
4957 ms
e9a73e8e-035c-49f6-bbb2-47d9a37f4b57
915 ms
c1665f07-aed6-4f03-84be-d899a545bc8a
1186 ms
c684eb21-f3f1-45ed-873a-2374e96f31f4
446 ms
8d434145-947d-4126-8fa0-23f616e51c9b
430 ms
dc09ff11-9937-496b-ad56-e7b09ea876f9
534 ms
6ff40cc0-1a7c-41d1-be55-fafe88ace78c
894 ms
b25baa3f-a17d-4b02-bcf9-072c03567070
1553 ms
ed34c9cc-c729-4c35-9aed-e78e1adb4811
1013 ms
a53b5e45-068d-4047-bb4f-b741d5939e5f
1029 ms
382678eb-6d7e-49b1-8c95-34e36aacce32
1132 ms
75aee58f-3735-4183-a828-0570cdba6d97
1377 ms
f03f369d-c17c-479f-ab8f-d02d290292d3
1243 ms
73423c71-e5b6-46b7-a834-4fb8847cdddd
1267 ms
8738b190-5c4b-45b5-ab1e-854b160a1c69
1305 ms
631be0a7-dcb9-4285-8fc6-326092ddd826
1349 ms
48071c2f-9ce6-4b4e-a6c9-209c46feb819
1390 ms
AvenirLTW01_55Roman1475520.woff
1401 ms
ico_menu_2.png
1446 ms
ico_recherche_2.png
1486 ms
ico_contact_email.png
1487 ms
collect
21 ms
affadvc.aspx
410 ms
AntagometricaBTW01-Regu.woff
1512 ms
accordeon_ferme.png
1575 ms
trait_jaune.png
1577 ms
accordeon_ouvert.png
1605 ms
AntagometricaBTW01-Ligh.woff
1798 ms
deco_gauche.png
1581 ms
deco_droite.png
1601 ms
AvenirLTW01_95Black1475556.woff
1577 ms
barre.png
1600 ms
deroulant.png
1616 ms
btn_plus.png
1635 ms
hotjar-139682.js
200 ms
149 ms
1510 ms
1024_sup.png
1600 ms
separateur_twitter-md.png
1600 ms
52 ms
modules-1f5c71aea63f8df71401422ed80fbe5f.js
31 ms
icon-twitter.png
1489 ms
bx_loader.gif
1508 ms
nav_carrousel_gauche.png
1452 ms
affact.aspx
297 ms
s.aspx
343 ms
si.aspx
347 ms
nav_carrousel_droit.png
1091 ms
js
38 ms
i.js
125 ms
js
63 ms
img
15 ms
164 ms
iframe
23 ms
img
20 ms
img
29 ms
122 ms
available_languages.jsp
118 ms
146 ms
pixel
22 ms
img
17 ms
common.js
33 ms
util.js
93 ms
controls.js
123 ms
places_impl.js
102 ms
img
54 ms
Pug
99 ms
u.php
122 ms
rtset
104 ms
UserMatch.ashx
72 ms
rum
67 ms
match.aspx
99 ms
sync
73 ms
match
63 ms
138 ms
user-registering
115 ms
86 ms
GenericUserSync.ashx
70 ms
2948
105 ms
68 ms
4448
99 ms
img
103 ms
img
99 ms
img
105 ms
img
110 ms
img
101 ms
sd
20 ms
mapuser
23 ms
merge
23 ms
xrefid.xgi
37 ms
spacer.gif
44 ms
sync
38 ms
rum
43 ms
grdf.fr accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a valid value for its [lang] attribute.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
grdf.fr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grdf.fr can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Grdf.fr 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.
grdf.fr
Open Graph description is not detected on the main page of GRDF. 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: