3.1 sec in total
970 ms
2 sec
151 ms
Click here to check amazing Green content. Otherwise, check out these important facts you probably never knew about green.in
Store for small producers who produces hand made products, or it is home made with lot of love.
Visit green.inWe analyzed Green.in page load time and found that the first response time was 970 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
green.in performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value12.5 s
0/100
25%
Value8.9 s
15/100
10%
Value2,570 ms
4/100
30%
Value0.593
11/100
15%
Value21.5 s
1/100
10%
970 ms
185 ms
203 ms
115 ms
109 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 79% of them (31 requests) were addressed to the original Green.in, 13% (5 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (970 ms) belongs to the original domain Green.in.
Page size can be reduced by 674.4 kB (66%)
1.0 MB
341.3 kB
In fact, the total size of Green.in main page is 1.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. 30% of websites need less resources to load. Javascripts take 591.4 kB which makes up the majority of the site volume.
Potential reduce by 11.0 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. This page needs HTML code to be minified as it can gain 2.0 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 11.0 kB or 78% of the original size.
Potential reduce by 2.9 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. Green images are well optimized though.
Potential reduce by 450.3 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 450.3 kB or 76% of the original size.
Potential reduce by 210.1 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. Green.in needs all CSS files to be minified and compressed as it can save up to 210.1 kB or 88% of the original size.
Number of requests can be reduced by 25 (76%)
33
8
The browser has sent 33 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Green. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and as a result speed up the page load time.
www.green.in
970 ms
prototype.js
185 ms
jquery-1.10.2.min.js
203 ms
noconflict.js
115 ms
ccard.js
109 ms
validation.js
144 ms
builder.js
112 ms
effects.js
169 ms
dragdrop.js
173 ms
controls.js
172 ms
slider.js
180 ms
js.js
237 ms
form.js
239 ms
translate.js
225 ms
cookies.js
226 ms
modernizr.custom.min.js
269 ms
selectivizr.js
272 ms
matchMedia.js
277 ms
matchMedia.addListener.js
277 ms
enquire.js
276 ms
app.js
306 ms
jquery.cycle2.min.js
302 ms
jquery.cycle2.swipe.min.js
302 ms
slideshow.js
304 ms
imagesloaded.js
305 ms
minicart.js
318 ms
css
22 ms
styles.css
411 ms
madisonisland.css
338 ms
ga.js
28 ms
greenstore_logo.png
79 ms
icon_sprite.png
80 ms
farmer.jpg
180 ms
IczWvq5y_Cwwv_rBjOtT0w.woff
60 ms
CcKI4k9un7TZVWzRVT-T8xsxEYwM7FgeyaSgU71cLG0.woff
62 ms
-_Ctzj9b56b8RgXW8FAriRsxEYwM7FgeyaSgU71cLG0.woff
60 ms
xkvoNo9fC8O2RDydKj12bxsxEYwM7FgeyaSgU71cLG0.woff
60 ms
JbtMzqLaYbbbCL9X6EvaIxsxEYwM7FgeyaSgU71cLG0.woff
60 ms
__utm.gif
22 ms
green.in 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
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
Links do not have a discernible name
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.
green.in 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
green.in SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Green.in 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 Green.in 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.
green.in
Open Graph description is not detected on the main page of Green. 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: