712 ms in total
72 ms
406 ms
234 ms
Click here to check amazing Gebo content. Otherwise, check out these important facts you probably never knew about gebo.fr
Raccords à compression en fonte malléable / à compression en polypropylène.Rubans d’étanchéisation inox en.Siphons et caniveaux de sol pour douche à l’italienne.
Visit gebo.frWe analyzed Gebo.fr page load time and found that the first response time was 72 ms and then it took 640 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.
gebo.fr performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value12.2 s
0/100
25%
Value10.2 s
9/100
10%
Value1,210 ms
20/100
30%
Value0.766
5/100
15%
Value12.5 s
14/100
10%
72 ms
24 ms
52 ms
79 ms
41 ms
Our browser made a total of 40 requests to load all elements on the main page. We found that 95% of them (38 requests) were addressed to the original Gebo.fr, 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (213 ms) belongs to the original domain Gebo.fr.
Page size can be reduced by 182.8 kB (10%)
1.9 MB
1.7 MB
In fact, the total size of Gebo.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. 20% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 6.5 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 2.0 kB, which is 21% 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 6.5 kB or 70% of the original size.
Potential reduce by 80.0 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. Gebo images are well optimized though.
Potential reduce by 79.8 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 79.8 kB or 67% of the original size.
Potential reduce by 16.6 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. Gebo.fr needs all CSS files to be minified and compressed as it can save up to 16.6 kB or 86% of the original size.
Number of requests can be reduced by 9 (23%)
39
30
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gebo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
gebo.fr
72 ms
facebox.css
24 ms
algemein1.css
52 ms
jquery.js
79 ms
facebox.js
41 ms
load.js
28 ms
analytics.js
44 ms
hintergrund.jpg
29 ms
close.png
30 ms
fittings_splashscreen.png
119 ms
oben_blau.png
30 ms
oben002.png
46 ms
assort_oben_1.jpg
74 ms
verlauf.png
30 ms
aktuelles.png
31 ms
nipple_klein.png
90 ms
neu_drain_klein.png
78 ms
backgr_inhalt_neue.png
41 ms
logo_titel.png
71 ms
stern.png
57 ms
koenig.jpg
88 ms
koenig_gros.jpg
174 ms
koenig_over.jpg
85 ms
macke_up.jpg
104 ms
macke_up_gros.jpg
183 ms
macke_up_over.jpg
101 ms
schach.jpg
103 ms
schach_gros.jpg
213 ms
schach_over.jpg
118 ms
schirm.jpg
148 ms
schirm_gros.jpg
174 ms
schirm_over.jpg
146 ms
closelabel.gif
169 ms
loading.gif
170 ms
b.png
183 ms
bl.png
183 ms
br.png
184 ms
tl.png
184 ms
tr.png
192 ms
collect
14 ms
gebo.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
Document doesn't have a <title> element
Image elements do not have [alt] attributes
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.
gebo.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
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
gebo.fr SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gebo.fr can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Gebo.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.
gebo.fr
Open Graph description is not detected on the main page of Gebo. 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: