4.2 sec in total
532 ms
3.5 sec
161 ms
Welcome to graf.fr homepage info - get ready to check Graf best content for France right away, or after learning these important things about graf.fr
Graf propose des réservoirs, cuves et citernes pour la récupération d'eau de pluie, des systèmes d'épurations et des systèmes d'infiltration
Visit graf.frWe analyzed Graf.fr page load time and found that the first response time was 532 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
graf.fr performance score
name
value
score
weighting
Value4.4 s
17/100
10%
Value10.7 s
0/100
25%
Value9.0 s
14/100
10%
Value700 ms
43/100
30%
Value0.022
100/100
15%
Value11.1 s
20/100
10%
532 ms
502 ms
423 ms
26 ms
968 ms
Our browser made a total of 35 requests to load all elements on the main page. We found that 83% of them (29 requests) were addressed to the original Graf.fr, 9% (3 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Graf.fr.
Page size can be reduced by 511.2 kB (26%)
1.9 MB
1.4 MB
In fact, the total size of Graf.fr main page is 1.9 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. 25% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 7.4 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 7.4 kB or 69% of the original size.
Potential reduce by 17.1 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. Graf images are well optimized though.
Potential reduce by 426.3 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 426.3 kB or 71% of the original size.
Potential reduce by 60.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. Graf.fr needs all CSS files to be minified and compressed as it can save up to 60.4 kB or 81% of the original size.
Number of requests can be reduced by 7 (24%)
29
22
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Graf. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
graf.fr
532 ms
www.graf.fr
502 ms
head-b3db5d9d0436fb1e306325aab60b3e78.merged.gz.css
423 ms
css
26 ms
head-2c87b1a97fe3eecccc3fced1cced43d5.merged.gz.js
968 ms
graf.png
115 ms
mini-world.png
109 ms
arrow-nav-grey.gif
108 ms
en.gif
198 ms
aus.gif
212 ms
es.gif
220 ms
bg-search.gif
216 ms
search-icon.gif
222 ms
merkzettel-arrow.png
224 ms
DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf
15 ms
cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf
16 ms
MTP_ySUJH_bn48VBG8sNSpS3E-kSBmtLoNJPDtbj2Pk.ttf
16 ms
segmentseite_rwn_oberirdisch_03.jpg
1396 ms
segmentseite_rwn_unterirdisch_03.jpg
1161 ms
segmentseite_versickerung_06.jpg
733 ms
kleinklaeranlagen_03.jpg
1249 ms
faesser_lagerung_03.jpg
973 ms
rainwater-above-no.jpg
409 ms
rainwater-underground-no.jpg
626 ms
stormwater-no.jpg
839 ms
wastewater-no.jpg
835 ms
drinking-water-no.jpg
942 ms
xxl_tanks-no.jpg
1066 ms
citernes-souples-no.jpg
1051 ms
storage-no.jpg
1076 ms
blue-arrow-teaser.png
1156 ms
footer-divider.gif
1171 ms
analytics.js
576 ms
collect
14 ms
head-457ef4ea3ce290520fa0bd9dc7235d9e.merged.gz.css
111 ms
graf.fr 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.
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
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
graf.fr 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
Missing source maps for large first-party JavaScript
graf.fr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
Tap targets are not sized appropriately
FR
FR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Graf.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 Graf.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.
graf.fr
Open Graph description is not detected on the main page of Graf. 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: