Tools & Wizards About Us
gevit.at screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

gevit.at

Vitalpilz - Reishi | Vitamin C - Camu Camu | Gevit

Page Load Speed

2.8 sec in total

First Response

332 ms

Resources Loaded

2.3 sec

Page Rendered

207 ms

gevit.at screenshot

About Website

Welcome to gevit.at homepage info - get ready to check Gevit best content right away, or after learning these important things about gevit.at

Bei Gevit finden Sie Reishi, den „Koenig der Heilpilze“ und die Beerenfrucht Camu Camu, „Vitamin C Weltmeister“. Bei Fragen beraten wir Sie sehr gern.

Visit gevit.at

Key Findings

We analyzed Gevit.at page load time and found that the first response time was 332 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

gevit.at performance score

0

Network Requests Diagram

gevit.at

332 ms

www.gevit.at

468 ms

style-e5aacd82.css

264 ms

jquery-1.4.min.js

361 ms

jquery-ui-1.7.2.min.js

273 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 78% of them (52 requests) were addressed to the original Gevit.at, 7% (5 requests) were made to Ecx.images-amazon.com and 6% (4 requests) were made to Rcm-de.amazon.de. The less responsive or slowest element that took the longest time to load (731 ms) belongs to the original domain Gevit.at.

Page Optimization Overview & Recommendations

Page size can be reduced by 331.5 kB (63%)

Content Size

527.1 kB

After Optimization

195.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gevit.at main page is 527.1 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. 30% of websites need less resources to load. Javascripts take 396.6 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 14.2 kB

  • Original 18.9 kB
  • After minification 18.1 kB
  • After compression 4.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 14.2 kB or 75% of the original size.

Image Optimization

-24%

Potential reduce by 20.1 kB

  • Original 84.3 kB
  • After minification 64.2 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. Obviously, Gevit needs image optimization as it can save up to 20.1 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-70%

Potential reduce by 276.1 kB

  • Original 396.6 kB
  • After minification 388.1 kB
  • After compression 120.5 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 276.1 kB or 70% of the original size.

CSS Optimization

-77%

Potential reduce by 21.2 kB

  • Original 27.3 kB
  • After minification 26.7 kB
  • After compression 6.2 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. Gevit.at needs all CSS files to be minified and compressed as it can save up to 21.2 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (68%)

Requests Now

65

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gevit.at

gevit.at

332 ms

www.gevit.at

www.gevit.at

468 ms

style-e5aacd82.css

style-e5aacd82.css

264 ms

jquery-1.4.min.js

jquery-1.4.min.js

361 ms

jquery-ui-1.7.2.min.js

jquery-ui-1.7.2.min.js

273 ms

jquery.easing.1.3.min.js

jquery.easing.1.3.min.js

185 ms

jquery.bgiframe.min.js

jquery.bgiframe.min.js

188 ms

jquery.cluetip.min.js

jquery.cluetip.min.js

188 ms

jquery.toolTip.js

jquery.toolTip.js

277 ms

jquery.overlabel.min.js

jquery.overlabel.min.js

277 ms

jquery.scrollTo-min.js

jquery.scrollTo-min.js

275 ms

jquery.localscroll-min.js

jquery.localscroll-min.js

347 ms

jquery.fancybox-1.2.6.pack.js

jquery.fancybox-1.2.6.pack.js

370 ms

jquery.validate.min.js

jquery.validate.min.js

373 ms

hoverIntent.min.js

hoverIntent.min.js

374 ms

superfish.min.js

superfish.min.js

374 ms

supersubs.min.js

supersubs.min.js

432 ms

cufon-yui.js

cufon-yui.js

448 ms

demo.js

demo.js

453 ms

cufon-font-all.js

cufon-font-all.js

731 ms

plusone.js

plusone.js

68 ms

skin-1.css

skin-1.css

92 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

56 ms

cm

cm

376 ms

cm

cm

343 ms

cm

cm

368 ms

cm

cm

343 ms

bodyBg.gif

bodyBg.gif

100 ms

pageBg-top.png

pageBg-top.png

106 ms

pageBg-repeat.png

pageBg-repeat.png

102 ms

mainMenu-left.png

mainMenu-left.png

106 ms

mainMenu-repeat.png

mainMenu-repeat.png

101 ms

mainMenu-divider.gif

mainMenu-divider.gif

102 ms

facebook.png

facebook.png

192 ms

twitter2.png

twitter2.png

193 ms

mainMenu-right.png

mainMenu-right.png

194 ms

logo_reishi.png

logo_reishi.png

194 ms

ribbon-wrap.png

ribbon-wrap.png

194 ms

ribbon.png

ribbon.png

195 ms

hr-bg.gif

hr-bg.gif

282 ms

footerBg-top.png

footerBg-top.png

278 ms

footerBg-repeat.png

footerBg-repeat.png

285 ms

footerBg-verticalRule.gif

footerBg-verticalRule.gif

284 ms

dot_gray.gif

dot_gray.gif

292 ms

logoSymbol-small_reishi.png

logoSymbol-small_reishi.png

380 ms

footerBg-bottom.png

footerBg-bottom.png

365 ms

xhtml_valid.png

xhtml_valid.png

370 ms

css_valid.png

css_valid.png

377 ms

piwik.js

piwik.js

427 ms

51VzL9ToMBL._SL110_.jpg

51VzL9ToMBL._SL110_.jpg

50 ms

159 ms

buy-from-tan.gif

buy-from-tan.gif

8 ms

170 ms

41oAQBGZOuL._SL110_.jpg

41oAQBGZOuL._SL110_.jpg

156 ms

165 ms

51Iw5n2Ox0L._SL110_.jpg

51Iw5n2Ox0L._SL110_.jpg

9 ms

163 ms

51m2u4S645L._SL110_.jpg

51m2u4S645L._SL110_.jpg

12 ms

piwik.php

piwik.php

329 ms

fancy_shadow_n.png

fancy_shadow_n.png

98 ms

fancy_shadow_ne.png

fancy_shadow_ne.png

98 ms

fancy_shadow_e.png

fancy_shadow_e.png

102 ms

fancy_shadow_se.png

fancy_shadow_se.png

91 ms

fancy_shadow_s.png

fancy_shadow_s.png

100 ms

fancy_shadow_sw.png

fancy_shadow_sw.png

180 ms

fancy_shadow_w.png

fancy_shadow_w.png

187 ms

fancy_shadow_nw.png

fancy_shadow_nw.png

190 ms

SEO Factors

gevit.at SEO score

0

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

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

gevit.at

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