Tools & Wizards About Us
support.gardena.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

support.gardena.com

Login to the Gardena sales company support site

Page Load Speed

2.1 sec in total

First Response

210 ms

Resources Loaded

1.7 sec

Page Rendered

119 ms

support.gardena.com screenshot

About Website

Welcome to support.gardena.com homepage info - get ready to check Support Gardena best content for Germany right away, or after learning these important things about support.gardena.com

Visit support.gardena.com

Key Findings

We analyzed Support.gardena.com page load time and found that the first response time was 210 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

support.gardena.com performance score

0

Network Requests Diagram

support.gardena.com

210 ms

node2739.aspx

110 ms

node2796.aspx

121 ms

jquery-1.2.2.min.js

301 ms

swfobject.js

21 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 94% of them (59 requests) were addressed to the original Support.gardena.com, 5% (3 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (597 ms) belongs to the original domain Support.gardena.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 184.4 kB (72%)

Content Size

254.6 kB

After Optimization

70.2 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Support.gardena.com main page is 254.6 kB. 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. CSS take 133.0 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 4.2 kB

  • Original 6.1 kB
  • After minification 5.5 kB
  • After compression 1.9 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 4.2 kB or 69% of the original size.

JavaScript Optimization

-63%

Potential reduce by 72.5 kB

  • Original 115.5 kB
  • After minification 101.3 kB
  • After compression 43.0 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 72.5 kB or 63% of the original size.

CSS Optimization

-81%

Potential reduce by 107.7 kB

  • Original 133.0 kB
  • After minification 91.6 kB
  • After compression 25.3 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. Support.gardena.com needs all CSS files to be minified and compressed as it can save up to 107.7 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 54 (90%)

Requests Now

60

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

support.gardena.com

support.gardena.com

210 ms

node2739.aspx

node2739.aspx

110 ms

node2796.aspx

node2796.aspx

121 ms

jquery-1.2.2.min.js

jquery-1.2.2.min.js

301 ms

swfobject.js

swfobject.js

21 ms

jquery-impromptu.1.8.js

jquery-impromptu.1.8.js

191 ms

login.css

login.css

190 ms

inc_product_list.js

inc_product_list.js

189 ms

inc_menu.js

inc_menu.js

200 ms

inc_basket.js

inc_basket.js

204 ms

common.js

common.js

285 ms

keyPress.js

keyPress.js

284 ms

equalheights.js

equalheights.js

282 ms

stockbalance.js

stockbalance.js

309 ms

lightbox.js

lightbox.js

310 ms

login.css

login.css

103 ms

imp_text.css

imp_text.css

108 ms

imp_pagebase.css

imp_pagebase.css

105 ms

imp_pagebase.css

imp_pagebase.css

96 ms

default.css

default.css

118 ms

imp_menu.css

imp_menu.css

104 ms

imp_news.css

imp_news.css

96 ms

imp_text.css

imp_text.css

99 ms

imp_form.css

imp_form.css

98 ms

imp_basket.css

imp_basket.css

106 ms

imp_shoppingcart.css

imp_shoppingcart.css

107 ms

imp_pc_table.css

imp_pc_table.css

187 ms

imp_panel.css

imp_panel.css

190 ms

imp_product_details.css

imp_product_details.css

190 ms

imp_product_xref.css

imp_product_xref.css

205 ms

imp_tabs.css

imp_tabs.css

200 ms

imp_text.css

imp_text.css

200 ms

imp_form.css

imp_form.css

276 ms

imp_menu.css

imp_menu.css

279 ms

imp_news.css

imp_news.css

277 ms

imp_dealers.css

imp_dealers.css

295 ms

imp_dealerlocator2.css

imp_dealerlocator2.css

298 ms

imp_google.css

imp_google.css

300 ms

imp_vibcalc.css

imp_vibcalc.css

368 ms

imp_product_list.css

imp_product_list.css

369 ms

imp_product_details.css

imp_product_details.css

372 ms

imp_product_compare.css

imp_product_compare.css

393 ms

imp_product_overview.css

imp_product_overview.css

395 ms

imp_product_guide.css

imp_product_guide.css

400 ms

imp_weborder.css

imp_weborder.css

459 ms

inc_articles_list.css

inc_articles_list.css

460 ms

imp_toolguide.css

imp_toolguide.css

461 ms

imp_webec.css

imp_webec.css

490 ms

imp_messageboard.css

imp_messageboard.css

491 ms

imp_dam_basket.css

imp_dam_basket.css

500 ms

imp_dam.css

imp_dam.css

549 ms

imp_pcprogress.css

imp_pcprogress.css

551 ms

jquery.treeview.css

jquery.treeview.css

552 ms

imp_tabs.css

imp_tabs.css

586 ms

imp_pcform.css

imp_pcform.css

588 ms

imp_pc_table.css

imp_pc_table.css

597 ms

imp_shoppingcart.css

imp_shoppingcart.css

561 ms

login_to_the_gardena_sales_company_support_site_f12f21ca.gif

login_to_the_gardena_sales_company_support_site_f12f21ca.gif

102 ms

header_bottom_grade.gif

header_bottom_grade.gif

105 ms

panel.gif

panel.gif

95 ms

ga.js

ga.js

29 ms

inpage_linkid.js

inpage_linkid.js

12 ms

__utm.gif

__utm.gif

25 ms

SEO Factors

support.gardena.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Support.gardena.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Support.gardena.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

support.gardena.com

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