6.1 sec in total
1.5 sec
4.1 sec
549 ms
Visit greshma.com now to see the best up-to-date GRESHMA content for India and also check out these interesting facts you probably never knew about greshma.com
Visit greshma.comWe analyzed Greshma.com page load time and found that the first response time was 1.5 sec and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
greshma.com performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value3.9 s
51/100
25%
Value7.0 s
32/100
10%
Value920 ms
30/100
30%
Value0.31
38/100
15%
Value4.4 s
84/100
10%
1509 ms
652 ms
436 ms
842 ms
435 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that all of those requests were addressed to Greshma.com and no external sources were called. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Greshma.com.
Page size can be reduced by 926.2 kB (79%)
1.2 MB
250.9 kB
In fact, the total size of Greshma.com 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. 25% of websites need less resources to load. Javascripts take 832.4 kB which makes up the majority of the site volume.
Potential reduce by 162.7 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 30.3 kB, which is 16% 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 162.7 kB or 85% of the original size.
Potential reduce by 21 B
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. GRESHMA images are well optimized though.
Potential reduce by 742.9 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 742.9 kB or 89% of the original size.
Potential reduce by 20.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. Greshma.com needs all CSS files to be minified and compressed as it can save up to 20.6 kB or 85% of the original size.
Number of requests can be reduced by 46 (77%)
60
14
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GRESHMA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
greshma.com
1509 ms
style.css
652 ms
js-image-slider.css
436 ms
js-image-slider.js
842 ms
jquery-1.9.0.min.js
435 ms
WebResource.axd
469 ms
ScriptResource.axd
907 ms
ScriptResource.axd
840 ms
ScriptResource.axd
430 ms
ScriptResource.axd
676 ms
ScriptResource.axd
676 ms
ScriptResource.axd
640 ms
ScriptResource.axd
654 ms
ScriptResource.axd
848 ms
ScriptResource.axd
865 ms
ScriptResource.axd
887 ms
ScriptResource.axd
886 ms
ScriptResource.axd
1070 ms
Home.js
1062 ms
CommonJs.js
1074 ms
spacer.gif
808 ms
logo.gif
806 ms
gt_lt.gif
809 ms
loading.gif
845 ms
get_go.gif
850 ms
gt_rt.gif
873 ms
tg_arr.gif
876 ms
tdiv.gif
881 ms
tr_arr.gif
917 ms
banner1.jpg
1299 ms
banner2.jpg
1279 ms
banner3.jpg
1267 ms
backoffice.gif
1065 ms
b_div.gif
1081 ms
trade_now.gif
1095 ms
business_partner.gif
1276 ms
open_account.gif
1292 ms
marr.gif
1312 ms
n_arr.gif
1464 ms
tc_tlt.gif
1473 ms
tc_trt.gif
1476 ms
tc_blt.gif
1487 ms
tc_brt.gif
1499 ms
to_lt.gif
1354 ms
to_ua.gif
1483 ms
to_da.gif
1472 ms
to_rt.gif
1474 ms
tcg.gif
1326 ms
tcr.gif
1329 ms
tc_but.gif
1347 ms
bbg.gif
1272 ms
logo_bg.gif
1203 ms
gt_bg.gif
1206 ms
Menu_On_BG.gif
1236 ms
loading.gif
1236 ms
but_bg.gif
1186 ms
gdot.gif
1311 ms
tc_tbg.gif
1320 ms
RupeeFont.ttf
1323 ms
tc_lt.gif
1329 ms
tc_rt.gif
1324 ms
tc_bt.gif
1334 ms
to_bg.gif
1450 ms
bullet.png
1469 ms
greshma.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.
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
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
Image elements do not have [alt] attributes
<input type="image"> elements do not have [alt] text
Form elements do not have associated labels
Links do not have a discernible name
greshma.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
greshma.com 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
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greshma.com 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 Greshma.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.
greshma.com
Open Graph description is not detected on the main page of GRESHMA. 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: