6.4 sec in total
441 ms
4.8 sec
1.2 sec
Welcome to sillygreens.com homepage info - get ready to check Silly Greens best content right away, or after learning these important things about sillygreens.com
Visit sillygreens.comWe analyzed Sillygreens.com page load time and found that the first response time was 441 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
sillygreens.com performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value16.2 s
0/100
25%
Value9.0 s
14/100
10%
Value1,620 ms
12/100
30%
Value0.571
12/100
15%
Value17.8 s
4/100
10%
441 ms
65 ms
172 ms
256 ms
303 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 60% of them (54 requests) were addressed to the original Sillygreens.com, 24% (22 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Sillygreens.com.
Page size can be reduced by 666.2 kB (8%)
8.0 MB
7.4 MB
In fact, the total size of Sillygreens.com main page is 8.0 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. Only a small number of websites need less resources to load. Images take 7.6 MB which makes up the majority of the site volume.
Potential reduce by 57.2 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 57.2 kB or 82% of the original size.
Potential reduce by 603.4 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. Silly Greens images are well optimized though.
Potential reduce by 3.4 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. This website has mostly compressed JavaScripts.
Potential reduce by 2.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. Sillygreens.com has all CSS files already compressed.
Number of requests can be reduced by 28 (42%)
67
39
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Silly Greens. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
sillygreens.com
441 ms
css
65 ms
style-static.min.css
172 ms
green-styles.css
256 ms
style.css
303 ms
jquery.min.js
314 ms
jquery-migrate.min.js
312 ms
js
107 ms
js
148 ms
lo.js
57 ms
tp.widget.bootstrap.min.js
53 ms
font-awesome.min.css
58 ms
css
63 ms
et-core-unified-28507.min.css
446 ms
custom-child.js
309 ms
scripts.min.js
630 ms
jquery.fitvids.js
625 ms
comment-reply.min.js
624 ms
jquery.mobile.js
625 ms
magnific-popup.js
624 ms
easypiechart.js
622 ms
salvattore.js
632 ms
instant_click.min.js
629 ms
common.js
631 ms
motion-effects.js
769 ms
sticky-elements.js
768 ms
gtm.js
298 ms
fbevents.js
299 ms
lo.legacy.js
194 ms
SG_black-300x73.png
306 ms
6.png
3662 ms
22-2.png
419 ms
23-4-e1686921439575.png
419 ms
3-e1676134562847.png
418 ms
23-1.png
418 ms
27-1.png
417 ms
FINAL-POT-GROW-1-2.png
993 ms
FINAL-POT-GROW-2-2-e1698327722337.png
757 ms
FINAL-NO-POT-1-3.png
992 ms
FINAL-NO-POT-2-2-e1698327806237.png
657 ms
FINAL-STEAM-POT-1-2.png
993 ms
FINAL-STEAM-POT-2-2-e1698327401749.png
841 ms
FINAL-DISPOSABLE-GROW-BOX-1-2.png
1077 ms
FINAL-DISPOSABLE-GROW-BOX-2-2-e1698327767378.png
912 ms
tear.png
996 ms
water-e1540495255510.png
1078 ms
flavour.png
1077 ms
Copy-of-Untitled-7.png
1077 ms
Copy-of-Untitled-6.png
1163 ms
4-per-Box-2-e1540221382208.png
1243 ms
Home-page-banner-2.png
1251 ms
32A9842.jpg
1334 ms
Finished.png
1161 ms
11.png
1093 ms
8.png
1094 ms
5.png
1172 ms
10.png
1177 ms
Copy-of-How-to-eat.png
1179 ms
4.png
1179 ms
2.png
1252 ms
9.png
1256 ms
3.png
1253 ms
255 ms
1.png
1118 ms
6.png
1119 ms
LhWlMVbYOfASNfNUVFk1Yvdd.ttf
272 ms
iJWHBXyXfDDVXbFqj2md8WX07oB-.ttf
297 ms
iJWHBXyXfDDVXbFqj1ma-2fW7A.ttf
333 ms
iJWHBXyXfDDVXbEOjFma-2fW7A.ttf
369 ms
iJWKBXyXfDDVXbnBrXmw023e.ttf
273 ms
iJWKBXyXfDDVXYnGp3uS0Q.ttf
334 ms
iJWHBXyXfDDVXbEyjlma-2fW7A.ttf
334 ms
iJWHBXyXfDDVXbEeiWmd8WX07oB-.ttf
317 ms
iJWHBXyXfDDVXbEeiVma-2fW7A.ttf
345 ms
iJWHBXyXfDDVXbF6iGmd8WX07oB-.ttf
335 ms
iJWHBXyXfDDVXbF6iFma-2fW7A.ttf
393 ms
iJWHBXyXfDDVXbFmi1ma-2fW7A.ttf
365 ms
uK_z4rqWc-Eoo9J0Kjc9OPec.ttf
366 ms
uK_z4rqWc-Eoo7Z1Kjc9OPec.ttf
393 ms
uK_z4rqWc-Eoo5pyKjc9OPec.ttf
426 ms
uK_84rqWc-Eom25bCD8X.ttf
394 ms
uK_z4rqWc-Eoo8JzKjc9OPec.ttf
394 ms
zYXwKUwuEqdVGqM8tPDdAA_Y-_bMKo1EhQd2tWxo8Tx2TaP4L4ppfPSB.ttf
447 ms
zYXwKUwuEqdVGqM8tPDdAA_Y-_bMKo1EhQd2tWxo8TwRTaP4L4ppfPSB.ttf
427 ms
zYXwKUwuEqdVGqM8tPDdAA_Y-_bMKo1EhQd2tWxo8TxPTaP4L4ppfPSB.ttf
409 ms
zYXwKUwuEqdVGqM8tPDdAA_Y-_bMKo1EhQd2tWxo8TyjSqP4L4ppfPSB.ttf
464 ms
zYXwKUwuEqdVGqM8tPDdAA_Y-_bMKo1EhQd2tWxo8TyRSqP4L4ppfPSB.ttf
445 ms
bat.js
262 ms
116 ms
5b8f3fd7
42 ms
sillygreens.com 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
sillygreens.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
sillygreens.com SEO score
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sillygreens.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 Sillygreens.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.
sillygreens.com
Open Graph description is not detected on the main page of Silly Greens. 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: