11.2 sec in total
290 ms
9.4 sec
1.6 sec
Welcome to groovyveg.de homepage info - get ready to check Groovyveg best content right away, or after learning these important things about groovyveg.de
Visit groovyveg.deWe analyzed Groovyveg.de page load time and found that the first response time was 290 ms and then it took 10.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
groovyveg.de performance score
name
value
score
weighting
Value0.9 s
100/100
10%
Value0.9 s
100/100
25%
Value2.0 s
100/100
10%
Value190 ms
91/100
30%
Value0.219
57/100
15%
Value3.1 s
95/100
10%
290 ms
1805 ms
400 ms
300 ms
2701 ms
Our browser made a total of 144 requests to load all elements on the main page. We found that 43% of them (62 requests) were addressed to the original Groovyveg.de, 19% (28 requests) were made to Google.com and 18% (26 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Groovyveg.de.
Page size can be reduced by 1.3 MB (47%)
2.7 MB
1.4 MB
In fact, the total size of Groovyveg.de 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. 65% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 52.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 52.4 kB or 80% of the original size.
Potential reduce by 3.6 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. Groovyveg images are well optimized though.
Potential reduce by 739.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 739.0 kB or 68% of the original size.
Potential reduce by 472.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. Groovyveg.de needs all CSS files to be minified and compressed as it can save up to 472.6 kB or 76% of the original size.
Number of requests can be reduced by 65 (49%)
133
68
The browser has sent 133 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Groovyveg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
groovyveg.de
290 ms
www.groovyveg.de
1805 ms
form.css
400 ms
calendarview.css
300 ms
mobile.css
2701 ms
9f1957f5_ai1ec_parsed_css.css
1084 ms
font-awesome.css
404 ms
frontend.css
680 ms
jquery.bxslider.css
656 ms
css
48 ms
menu-image.css
697 ms
wpmenucart-icons.css
716 ms
wpmenucart-main.css
944 ms
woocommerce-layout.css
1089 ms
woocommerce.css
1175 ms
woocommerce-gzd-layout.min.css
1036 ms
bootstrap-groovy-veg.css
1609 ms
theme-base.css
1523 ms
css
59 ms
style.css
1367 ms
style.css
1437 ms
css
59 ms
jquery.js
1919 ms
jquery-migrate.min.js
1719 ms
jquery.bxslider.min.js
1820 ms
jquery.marquee.min.js
2055 ms
frontend.js
2313 ms
fixed-menu-anchor.js
2099 ms
jq-sticky-anything.min.js
2232 ms
external-tracking.min.js
2367 ms
stickThis.js
2230 ms
add-to-cart.min.js
2220 ms
jquery.blockUI.min.js
2525 ms
woocommerce.min.js
2527 ms
jquery.cookie.min.js
2527 ms
cart-fragments.min.js
2647 ms
bootstrap.min.js
2756 ms
theme.js
2739 ms
q2w3-fixed-widget.min.js
2894 ms
scripts.js
2837 ms
wp-embed.min.js
2897 ms
printForm.css
166 ms
wp-emoji-release.min.js
520 ms
colors.css
552 ms
analytics.js
260 ms
embed
551 ms
embed
805 ms
embed
862 ms
embed
858 ms
groovy-vegetables-logo-top.jpg
1558 ms
hello-yummy.jpg
513 ms
background-heading-medium.jpg
509 ms
green-line.gif
1550 ms
veggie-way-seeding.jpg
1595 ms
background-heading-circle.png
513 ms
veggie-way-growing.jpg
1661 ms
veggie-way-harvesting.jpg
1594 ms
veggie-way-box-on-wheels-195x300.jpg
2057 ms
veggie-way-road.jpg
2538 ms
veggie-way-house-group.jpg
2538 ms
veggie-way-box-delivery.jpg
2537 ms
button-place-an-order.jpg
2270 ms
rapeseed-line.jpg
2540 ms
background-heading-short.jpg
2920 ms
box-tiny@2x.jpg
3367 ms
box-mini@2x.jpg
3469 ms
box-proper@2x.jpg
3470 ms
box-giant@2x.jpg
3558 ms
background-heading-medium-white.jpg
3199 ms
www.groovyveg.de
3325 ms
-KZsao_xwBpcExaHoPH8_w.ttf
62 ms
5DVGWnz9Skaq1amwwwGZEw.ttf
128 ms
8YIp-EIJXA6NJdTPxy9qiQ.ttf
143 ms
_sVKdO-TLWvaH-ptGimJBaCWcynf_cDxXwCLxiixG1c.ttf
143 ms
collect
74 ms
js
43 ms
init_embed.js
71 ms
js
4 ms
common.js
95 ms
map.js
94 ms
google4.png
566 ms
overlay.js
507 ms
util.js
504 ms
onion.js
618 ms
search_impl.js
618 ms
StaticMapService.GetMapImage
718 ms
stats.js
666 ms
openhand_8_8.cur
589 ms
ViewportInfoService.GetViewportInfo
585 ms
ViewportInfoService.GetViewportInfo
585 ms
kh
852 ms
transparent.png
538 ms
StaticMapService.GetMapImage
498 ms
StaticMapService.GetMapImage
496 ms
ViewportInfoService.GetViewportInfo
497 ms
ViewportInfoService.GetViewportInfo
492 ms
kh
602 ms
ViewportInfoService.GetViewportInfo
488 ms
ViewportInfoService.GetViewportInfo
474 ms
kh
668 ms
kh
990 ms
StaticMapService.GetMapImage
554 ms
controls.js
266 ms
ViewportInfoService.GetViewportInfo
338 ms
ViewportInfoService.GetViewportInfo
656 ms
kh
339 ms
vt
248 ms
vt
220 ms
vt
219 ms
vt
553 ms
vt
550 ms
vt
444 ms
vt
590 ms
vt
591 ms
vt
585 ms
vt
625 ms
vt
625 ms
vt
726 ms
vt
739 ms
vt
726 ms
vt
726 ms
vt
726 ms
vt
723 ms
vt
771 ms
vt
744 ms
css
372 ms
entity11.png
354 ms
mapcnt6.png
413 ms
sv9.png
412 ms
vt
445 ms
vt
446 ms
vt
447 ms
vt
446 ms
tmapctrl.png
246 ms
vt
186 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
85 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
85 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
84 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
89 ms
AuthenticationService.Authenticate
83 ms
AuthenticationService.Authenticate
64 ms
AuthenticationService.Authenticate
48 ms
AuthenticationService.Authenticate
42 ms
woocommerce-smallscreen.css
514 ms
groovyveg.de 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
<frame> or <iframe> elements do not have a title
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.
groovyveg.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Issues were logged in the Issues panel in Chrome Devtools
groovyveg.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 doesn't use legible font sizes
DE
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Groovyveg.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Groovyveg.de 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.
groovyveg.de
Open Graph description is not detected on the main page of Groovyveg. 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: