3.8 sec in total
464 ms
3.1 sec
253 ms
Welcome to greenika.com homepage info - get ready to check Greenika best content for India right away, or after learning these important things about greenika.com
Greenka
Visit greenika.comWe analyzed Greenika.com page load time and found that the first response time was 464 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
greenika.com performance score
name
value
score
weighting
Value2.7 s
60/100
10%
Value3.1 s
75/100
25%
Value4.9 s
66/100
10%
Value1,600 ms
12/100
30%
Value0
100/100
15%
Value8.9 s
34/100
10%
464 ms
460 ms
276 ms
188 ms
282 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 72% of them (42 requests) were addressed to the original Greenika.com, 12% (7 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Greenika.com.
Page size can be reduced by 852.3 kB (17%)
5.0 MB
4.1 MB
In fact, the total size of Greenika.com main page is 5.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. 50% of websites need less resources to load. Images take 4.0 MB which makes up the majority of the site volume.
Potential reduce by 15.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. This page needs HTML code to be minified as it can gain 3.1 kB, which is 15% 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 15.4 kB or 77% of the original size.
Potential reduce by 136.0 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. Greenika images are well optimized though.
Potential reduce by 327.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 327.0 kB or 66% of the original size.
Potential reduce by 373.9 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. Greenika.com needs all CSS files to be minified and compressed as it can save up to 373.9 kB or 84% of the original size.
Number of requests can be reduced by 21 (46%)
46
25
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greenika. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
greenika.com
464 ms
bootstrap.min.css
460 ms
bootstrap-theme.min.css
276 ms
customstyles.css
188 ms
font-awesome.css
282 ms
theme.css
190 ms
prettyPhoto.css
359 ms
style.css
370 ms
ie-emulation-modes-warning.js
371 ms
style5.css
483 ms
style_common.css
484 ms
ajax.js
546 ms
jquery.min2.js
745 ms
jquery.isotope.min.js
573 ms
jquery.prettyPhoto.js
648 ms
bootstrap.min.js
659 ms
docs.min.js
707 ms
ie10-viewport-bug-workaround.js
646 ms
jquery.min.js
941 ms
css
26 ms
shopping_cart_64.png
428 ms
logo.png
429 ms
gmplogo.jpg
430 ms
video_ad_03.png
509 ms
RLZ24J.jpg
1121 ms
MZfryA.jpg
1191 ms
329WbV.jpg
1198 ms
MWs2Jy.jpg
1225 ms
kQ48bC.jpg
1313 ms
b76ftE.jpg
1352 ms
promologo.jpg
1304 ms
xF3ghz.jpg
1565 ms
1Jc0mf.jpg
1382 ms
VpywB7.jpg
1591 ms
UwgnPsXJ.jpg
1946 ms
grupee.jpg
1496 ms
rupee.jpg
1569 ms
V2SIkgq5.jpg
2045 ms
rk3wpILW.jpg
2153 ms
blink.gif
1931 ms
MHl8YIly198
115 ms
titbg.gif
1732 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
48 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
51 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
51 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
52 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
66 ms
fontawesome-webfont.woff
1936 ms
glyphicons-halflings-regular.woff
1958 ms
www-embed-player-vflfNyN_r.css
88 ms
www-embed-player.js
108 ms
base.js
205 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
38 ms
ad_status.js
39 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
65 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
64 ms
analytics.js
26 ms
collect
25 ms
greenika.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
greenika.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
Missing source maps for large first-party JavaScript
greenika.com 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 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 Greenika.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 Greenika.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.
greenika.com
Open Graph description is not detected on the main page of Greenika. 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: