15.4 sec in total
222 ms
13.8 sec
1.4 sec
Visit greenpips.whotrades.com now to see the best up-to-date Greenpips Whotrades content for India and also check out these interesting facts you probably never knew about greenpips.whotrades.com
Trader Profile Nilaish Kumar
Visit greenpips.whotrades.comWe analyzed Greenpips.whotrades.com page load time and found that the first response time was 222 ms and then it took 15.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
greenpips.whotrades.com performance score
name
value
score
weighting
Value3.7 s
29/100
10%
Value17.8 s
0/100
25%
Value13.6 s
2/100
10%
Value4,770 ms
0/100
30%
Value0.77
5/100
15%
Value26.0 s
0/100
10%
222 ms
1828 ms
707 ms
871 ms
800 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 11% of them (10 requests) were addressed to the original Greenpips.whotrades.com, 49% (43 requests) were made to D28amqw7zbvhq.cloudfront.net and 5% (4 requests) were made to Content.adriver.ru. The less responsive or slowest element that took the longest time to load (4.2 sec) relates to the external source Googletagmanager.com.
Page size can be reduced by 823.5 kB (60%)
1.4 MB
548.3 kB
In fact, the total size of Greenpips.whotrades.com main page is 1.4 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. 60% of websites need less resources to load. CSS take 589.8 kB which makes up the majority of the site volume.
Potential reduce by 277.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 77.7 kB, which is 24% 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 277.4 kB or 85% of the original size.
Potential reduce by 17.1 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. Greenpips Whotrades images are well optimized though.
Potential reduce by 44.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 44.4 kB or 41% of the original size.
Potential reduce by 484.7 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. Greenpips.whotrades.com needs all CSS files to be minified and compressed as it can save up to 484.7 kB or 82% of the original size.
Number of requests can be reduced by 55 (71%)
78
23
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Greenpips Whotrades. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
greenpips.whotrades.com
222 ms
greenpips.whotrades.com
1828 ms
swfobject.js
707 ms
site-on-platforma.css
871 ms
whotrades.css
800 ms
cached
2307 ms
layout+layout-personal.css
774 ms
comments.css
791 ms
masonry.css
825 ms
blog-posts-list-masonry.css
837 ms
widget_personalsiteheader_99914b932bd37a50b983c5e7c90ae93b.css
846 ms
widget_recommendedaction_99914b932bd37a50b983c5e7c90ae93b.css
867 ms
widget_blogposts_99914b932bd37a50b983c5e7c90ae93b.css
946 ms
cached
423 ms
modernizr.js
952 ms
environment.js
945 ms
wt_light.css
480 ms
newsplugin.js
486 ms
tv.js
589 ms
javascript_includes_new_final.js
1757 ms
site-on-platforma.js
1150 ms
whotrades.js
949 ms
layout+layout-personal.js
947 ms
masonry.js
964 ms
blog-posts-list-masonry.js
964 ms
widget_personalsiteheader_99914b932bd37a50b983c5e7c90ae93b.js
1194 ms
widget_recommendedaction_99914b932bd37a50b983c5e7c90ae93b.js
983 ms
widget_blogposts_99914b932bd37a50b983c5e7c90ae93b.js
1008 ms
widget_socialsubscribers_99914b932bd37a50b983c5e7c90ae93b.js
1064 ms
analytics.js
1373 ms
blank_male_small.gif
3344 ms
20039756609
1362 ms
20660441148
1362 ms
20695138754
1358 ms
blank_male_med.gif
3336 ms
gtm.js
4211 ms
logotype.svg
333 ms
sprite.png
332 ms
OpenSans-Light.ttf
3038 ms
OpenSans-Regular.ttf
3155 ms
OpenSans-Semibold.ttf
3153 ms
blogs-icons.png
986 ms
flags.png
2963 ms
default-cover.jpg
2960 ms
autoUpdate.adriver.js
4066 ms
icons-Regular.woff
2127 ms
watch.js
1568 ms
2573 ms
messages-popup.js
2491 ms
messages-popup.css
2503 ms
sdk.js
2860 ms
lens.png
1009 ms
just2trade.png
1010 ms
1174 ms
dialoggy.css
259 ms
collect
452 ms
conversion_async.js
1377 ms
target.js
1840 ms
guest-messages-popup.js
475 ms
collect
442 ms
forecast-preview.css
168 ms
869 ms
xd_arbiter.php
1099 ms
old.adriver.js
1527 ms
dialoggy.js
554 ms
favicon.ico
479 ms
favicon.ico
522 ms
favicon.ico
817 ms
favicon.ico
699 ms
spinner-new.gif
208 ms
registration
347 ms
share-block.js
94 ms
buttons.js
450 ms
335 ms
widget_registration_99914b932bd37a50b983c5e7c90ae93b.css
166 ms
fbds.js
126 ms
246 ms
70 ms
countdown-core.js
74 ms
164 ms
forecast-preview.js
63 ms
632 ms
checkFlash.adriver.js
564 ms
functions.adriver.js
586 ms
981 ms
getAllAppDefault.esi
564 ms
203 ms
xd_arbiter.php
347 ms
greenpips.whotrades.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
ARIA tooltip elements do not have accessible names.
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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
greenpips.whotrades.com 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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
greenpips.whotrades.com 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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greenpips.whotrades.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Greenpips.whotrades.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.
greenpips.whotrades.com
Open Graph description is not detected on the main page of Greenpips Whotrades. 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: