11.1 sec in total
1.1 sec
8.7 sec
1.3 sec
Visit greengully.in now to see the best up-to-date Greengully content for India and also check out these interesting facts you probably never knew about greengully.in
GreenGully-One of the largest Vertical Garden providers from India. We are specialized in designing Vertical Gardens or Green Walls
Visit greengully.inWe analyzed Greengully.in page load time and found that the first response time was 1.1 sec and then it took 10 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
greengully.in performance score
name
value
score
weighting
Value5.4 s
6/100
10%
Value24.6 s
0/100
25%
Value15.8 s
0/100
10%
Value7,190 ms
0/100
30%
Value0.145
77/100
15%
Value20.2 s
2/100
10%
1136 ms
1355 ms
253 ms
591 ms
638 ms
Our browser made a total of 124 requests to load all elements on the main page. We found that 63% of them (78 requests) were addressed to the original Greengully.in, 14% (17 requests) were made to Fonts.gstatic.com and 10% (13 requests) were made to T.commonsupport.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Greengully.in.
Page size can be reduced by 351.5 kB (30%)
1.2 MB
807.1 kB
In fact, the total size of Greengully.in main page is 1.2 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 701.6 kB which makes up the majority of the site volume.
Potential reduce by 171.8 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 27.1 kB, which is 13% 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 171.8 kB or 84% of the original size.
Potential reduce by 164.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. Obviously, Greengully needs image optimization as it can save up to 164.6 kB or 23% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 10.1 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 5.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. Greengully.in has all CSS files already compressed.
Number of requests can be reduced by 46 (47%)
98
52
The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greengully. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
greengully.in
1136 ms
greengully.in
1355 ms
bootstrap.css
253 ms
settings.css
591 ms
layers.css
638 ms
navigation.css
713 ms
style.css
911 ms
responsive.css
937 ms
color-switcher-design.css
939 ms
default-theme.css
927 ms
jquery.js
1308 ms
jquery.themepunch.revolution.min.js
1277 ms
jquery.themepunch.tools.min.js
1363 ms
revolution.extension.actions.min.js
1276 ms
revolution.extension.carousel.min.js
1277 ms
revolution.extension.kenburn.min.js
1307 ms
revolution.extension.layeranimation.min.js
1460 ms
revolution.extension.migration.min.js
1464 ms
revolution.extension.navigation.min.js
1459 ms
revolution.extension.parallax.min.js
1456 ms
revolution.extension.slideanims.min.js
1456 ms
revolution.extension.video.min.js
1610 ms
main-slider-script.js
1716 ms
bootstrap.min.js
1726 ms
jquery.mCustomScrollbar.concat.min.js
1736 ms
jquery.fancybox.pack.js
1721 ms
jquery.fancybox-media.js
1719 ms
owl.js
1827 ms
wow.js
1913 ms
appear.js
1950 ms
isotope.js
1946 ms
script.js
1936 ms
color-settings.js
1944 ms
addthis_widget.js
62 ms
logo.png
2440 ms
slider1.jpg
2763 ms
slider2.jpg
2536 ms
slider3.jpg
2547 ms
slider6.jpg
2889 ms
slider7.jpg
2390 ms
p1.jpg
2545 ms
p2.jpg
2488 ms
p3.jpg
2591 ms
css
47 ms
font-awesome.css
123 ms
flaticon.css
103 ms
animate.css
127 ms
owl.css
99 ms
jquery.fancybox.css
121 ms
jquery.mCustomScrollbar.min.css
131 ms
p4.jpg
2211 ms
p5.jpg
2466 ms
1.jpg
3367 ms
2.jpg
2705 ms
counter.php
293 ms
bg-logo.png
188 ms
pattern-1.png
224 ms
4.png
186 ms
tick.png
172 ms
4.jpg
2361 ms
5.jpg
2079 ms
3.jpg
2304 ms
6.jpg
2558 ms
7.jpg
2519 ms
5aU69_a8oxmIdGl4AQ.ttf
252 ms
5aU19_a8oxmIfJpbERySiA.ttf
318 ms
5aU19_a8oxmIfMJaERySiA.ttf
319 ms
5aU19_a8oxmIfLZcERySiA.ttf
318 ms
5aU19_a8oxmIfNJdERySiA.ttf
320 ms
flaticon.svg
312 ms
flaticon.woff
156 ms
fontawesome-webfont.woff
205 ms
7Au7p_IgjDKdCRWuR1azplQKGFk.ttf
318 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJ6bQl2xMB.ttf
322 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJ0LQl2xMB.ttf
322 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJt7Ql2xMB.ttf
303 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJBbMl2xMB.ttf
302 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJN7Ml2xMB.ttf
305 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJabMl2xMB.ttf
305 ms
8.jpg
2429 ms
9.jpg
2598 ms
10.jpg
2811 ms
11.jpg
2680 ms
12.jpg
2674 ms
bulb.jpg
3064 ms
AJ.jpeg
3072 ms
DSP.jpeg
2903 ms
VM.jpeg
3133 ms
SS.jpeg
2961 ms
ISRAR.jpeg
3070 ms
author-1.jpg
3017 ms
1.jpg
3035 ms
2.png
2983 ms
3.png
3030 ms
10.jpg
3069 ms
6.png
3186 ms
moatframe.js
245 ms
_ate.track.config_resp
423 ms
300lo.json
179 ms
revicons-5510888.woff
2668 ms
sh.f48a1a04fe8dbf021b4cda1d.html
45 ms
8.png
3005 ms
livechat2.aspx
233 ms
7.jfif
2591 ms
10.jfif
2645 ms
footer-logo.png
2710 ms
css
37 ms
chatinline.css
38 ms
resources2.aspx
161 ms
post-thumb-1.png
2617 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
7 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
9 ms
pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf
10 ms
pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf
10 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
11 ms
layers.fa6cd1947ce26e890d3d.js
60 ms
livechatinit2.js
172 ms
post-thumb-2.png
2334 ms
5.jpg
3095 ms
2.jpg
2557 ms
shares-post.json
498 ms
shares.json
153 ms
shares.json
190 ms
3.jpg
2939 ms
greengully.in accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
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
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
greengully.in best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
greengully.in SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greengully.in can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Greengully.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.
greengully.in
Open Graph description is not detected on the main page of Greengully. 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: