Tools & Wizards About Us
guillebert.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

guillebert.com

Matériel élagage et outillage espaces verts pour pros | Guillebert

Page Load Speed

5.4 sec in total

First Response

321 ms

Resources Loaded

4.4 sec

Page Rendered

683 ms

guillebert.com screenshot

About Website

Click here to check amazing Guillebert content. Otherwise, check out these important facts you probably never knew about guillebert.com

Guillebert : site de vente en ligne de matériel espaces verts et outillage espaces verts à destination des professionnels.

Visit guillebert.com

Key Findings

We analyzed Guillebert.com page load time and found that the first response time was 321 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

guillebert.com performance score

0

Network Requests Diagram

guillebert.com

321 ms

www.guillebert.com

606 ms

www.guillebert.fr

1181 ms

dashboard.css

190 ms

style.css

381 ms

Our browser made a total of 120 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original Guillebert.com, 95% (114 requests) were made to Guillebert.fr and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Guillebert.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 963.7 kB (36%)

Content Size

2.7 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Guillebert.com main page is 2.7 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. 60% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 119.7 kB

  • Original 140.4 kB
  • After minification 133.4 kB
  • After compression 20.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 119.7 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 38.0 kB

  • Original 1.5 MB
  • After minification 1.5 MB

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. Guillebert images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 632.0 kB

  • Original 826.6 kB
  • After minification 641.6 kB
  • After compression 194.6 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 632.0 kB or 76% of the original size.

CSS Optimization

-85%

Potential reduce by 174.1 kB

  • Original 205.0 kB
  • After minification 167.6 kB
  • After compression 30.9 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. Guillebert.com needs all CSS files to be minified and compressed as it can save up to 174.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (36%)

Requests Now

116

After Optimization

74

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Guillebert. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

guillebert.com

guillebert.com

321 ms

www.guillebert.com

www.guillebert.com

606 ms

www.guillebert.fr

www.guillebert.fr

1181 ms

dashboard.css

dashboard.css

190 ms

style.css

style.css

381 ms

default_style.css

default_style.css

191 ms

custom.css

custom.css

192 ms

jquery.fancybox.css

jquery.fancybox.css

193 ms

jquery.jqzoom.css

jquery.jqzoom.css

276 ms

tooltipster.css

tooltipster.css

283 ms

tooltipster-light.css

tooltipster-light.css

283 ms

tooltipster-shadow.css

tooltipster-shadow.css

284 ms

prototype.js

prototype.js

477 ms

ccard.js

ccard.js

369 ms

validation.js

validation.js

468 ms

builder.js

builder.js

375 ms

effects.js

effects.js

468 ms

dragdrop.js

dragdrop.js

464 ms

controls.js

controls.js

563 ms

slider.js

slider.js

470 ms

js.js

js.js

559 ms

form.js

form.js

561 ms

menu.js

menu.js

562 ms

translate.js

translate.js

562 ms

cookies.js

cookies.js

567 ms

review.js

review.js

651 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

752 ms

jquery-ui-1.8.21.custom.min.js

jquery-ui-1.8.21.custom.min.js

754 ms

jquery.carousel.min.js

jquery.carousel.min.js

654 ms

jquery.ddslick.js

jquery.ddslick.js

655 ms

jquery.fancybox.js

jquery.fancybox.js

660 ms

jquery.complexify.js

jquery.complexify.js

744 ms

jquery.jqzoom-core.js

jquery.jqzoom-core.js

748 ms

jquery.limit-1.2.source.js

jquery.limit-1.2.source.js

748 ms

jquery.inputlabels.js

jquery.inputlabels.js

753 ms

jquery.autocomplete.js

jquery.autocomplete.js

837 ms

jquery.ba-dotimeout.min.js

jquery.ba-dotimeout.min.js

842 ms

tools.js

tools.js

842 ms

site.js

site.js

675 ms

jquery.tooltipster.js

jquery.tooltipster.js

670 ms

reset.css

reset.css

481 ms

text.css

text.css

564 ms

960.css

960.css

568 ms

MyFontsWebfontsKit.css

MyFontsWebfontsKit.css

569 ms

jquery-ui-1.8.21.custom.css

jquery-ui-1.8.21.custom.css

571 ms

css

css

24 ms

bg-winter.jpg

bg-winter.jpg

845 ms

analytics.js

analytics.js

9 ms

logo.jpg

logo.jpg

133 ms

opc-ajax-loader.gif

opc-ajax-loader.gif

133 ms

port-offert-overhead.png

port-offert-overhead.png

133 ms

outillages_4.png

outillages_4.png

134 ms

11985__.jpg

11985__.jpg

134 ms

taille_coupe_3.png

taille_coupe_3.png

190 ms

8018___.jpg

8018___.jpg

190 ms

fournitures_horticoles_3.png

fournitures_horticoles_3.png

190 ms

7159___.jpg

7159___.jpg

192 ms

arrosage_3.png

arrosage_3.png

193 ms

11351__.jpg

11351__.jpg

283 ms

atelier_3.png

atelier_3.png

283 ms

10107__.jpg

10107__.jpg

285 ms

equipement_3.png

equipement_3.png

286 ms

2578___.jpg

2578___.jpg

287 ms

proprete_voirie_3.png

proprete_voirie_3.png

376 ms

10985__.jpg

10985__.jpg

376 ms

protection_securite_3.png

protection_securite_3.png

377 ms

small_image.png

small_image.png

379 ms

elagage_3.png

elagage_3.png

378 ms

1404___.jpg

1404___.jpg

469 ms

tronconneuse-picto.png

tronconneuse-picto.png

468 ms

11880__.jpg

11880__.jpg

469 ms

catalogue-2016-hpV2.jpg

catalogue-2016-hpV2.jpg

564 ms

chaussures-216538.jpg

chaussures-216538.jpg

563 ms

outforce-2r.jpg

outforce-2r.jpg

656 ms

carter-216466.jpg

carter-216466.jpg

748 ms

manches-216422.jpg

manches-216422.jpg

656 ms

12120__.jpg

12120__.jpg

656 ms

12901__.jpg

12901__.jpg

658 ms

13083__.jpg

13083__.jpg

747 ms

13097__.jpg

13097__.jpg

749 ms

13022__.jpg

13022__.jpg

751 ms

12930__.jpg

12930__.jpg

751 ms

12357__.jpg

12357__.jpg

840 ms

collect

collect

27 ms

collect

collect

104 ms

230CF1_4_0.woff

230CF1_4_0.woff

723 ms

12981__.jpg

12981__.jpg

723 ms

12851__.jpg

12851__.jpg

741 ms

comm-1.jpg

comm-1.jpg

741 ms

comm-2.jpg

comm-2.jpg

793 ms

230CF1_5_0.woff

230CF1_5_0.woff

757 ms

230CF1_2_0.woff

230CF1_2_0.woff

760 ms

230CF1_7_0.woff

230CF1_7_0.woff

760 ms

comm-9.jpg

comm-9.jpg

759 ms

comm-8.jpg

comm-8.jpg

758 ms

comm-3.jpg

comm-3.jpg

736 ms

comm-4.jpg

comm-4.jpg

756 ms

fiches-de-vie-HP.png

fiches-de-vie-HP.png

758 ms

decouvrir-arbo.png

decouvrir-arbo.png

757 ms

expert.jpg

expert.jpg

758 ms

quality.jpg

quality.jpg

668 ms

service.jpg

service.jpg

736 ms

payement-modes.png

payement-modes.png

754 ms

bg-home-search-keyword.gif

bg-home-search-keyword.gif

757 ms

bg-home-search-ok.gif

bg-home-search-ok.gif

759 ms

cart-icon.png

cart-icon.png

668 ms

blue-arrow-down.png

blue-arrow-down.png

668 ms

page-shadow.png

page-shadow.png

737 ms

main-menu.gif

main-menu.gif

662 ms

bg-h2-home.png

bg-h2-home.png

665 ms

button.png

button.png

574 ms

home-commercial-section.jpg

home-commercial-section.jpg

573 ms

bouton-devis.png

bouton-devis.png

574 ms

bigSliderControle.png

bigSliderControle.png

641 ms

bigSliderPagin.png

bigSliderPagin.png

571 ms

links-separator.png

links-separator.png

572 ms

orange-block-bg.png

orange-block-bg.png

572 ms

footer-halo.jpg

footer-halo.jpg

572 ms

get-catalog.gif

get-catalog.gif

572 ms

print.css

print.css

96 ms

SEO Factors

guillebert.com SEO score

0

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Guillebert.com 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 Guillebert.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.

Social Sharing Optimization

guillebert.com

Open Graph description is not detected on the main page of Guillebert. 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: