9.7 sec in total
248 ms
9 sec
476 ms
Welcome to whentotrade.com homepage info - get ready to check Whento Trade best content right away, or after learning these important things about whentotrade.com
WTT Homepage
Visit whentotrade.comWe analyzed Whentotrade.com page load time and found that the first response time was 248 ms and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
whentotrade.com performance score
name
value
score
weighting
Value5.6 s
5/100
10%
Value9.8 s
0/100
25%
Value8.0 s
22/100
10%
Value650 ms
46/100
30%
Value0.006
100/100
15%
Value9.8 s
28/100
10%
248 ms
2057 ms
380 ms
642 ms
507 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 88% of them (72 requests) were addressed to the original Whentotrade.com, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Whentotrade.com.
Page size can be reduced by 1.1 MB (35%)
3.0 MB
2.0 MB
In fact, the total size of Whentotrade.com main page is 3.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. 65% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 75.2 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 75.2 kB or 84% of the original size.
Potential reduce by 22.7 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. Whento Trade images are well optimized though.
Potential reduce by 292.8 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 292.8 kB or 62% of the original size.
Potential reduce by 668.0 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. Whentotrade.com needs all CSS files to be minified and compressed as it can save up to 668.0 kB or 86% of the original size.
Number of requests can be reduced by 55 (70%)
79
24
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whento Trade. 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 24 to 1 for CSS and as a result speed up the page load time.
whentotrade.com
248 ms
www.whentotrade.com
2057 ms
wp-emoji-release.min.js
380 ms
vplayer.css
642 ms
woocommerce-mod.css
507 ms
frond-end.css
311 ms
bbpress-mod.css
435 ms
szstyles.css
415 ms
sidebar-login.css
474 ms
srr-css.css
524 ms
frontend.css
527 ms
grid.css
544 ms
base.css
568 ms
layout.css
706 ms
shortcodes.css
852 ms
magnific-popup.css
631 ms
mediaelementplayer.css
653 ms
enfold_child_by_lvt.css
944 ms
custom.css
735 ms
style.css
690 ms
layerslider.css
717 ms
css
54 ms
ytprefs.min.css
758 ms
jetpack.css
906 ms
addtoany.min.css
793 ms
jquery.js
1039 ms
jquery-migrate.min.js
859 ms
jquery.blockUI.min.js
918 ms
sidebar-login.min.js
918 ms
srr-js.js
962 ms
avia-compat.js
989 ms
greensock.js
1099 ms
layerslider.kreaturamedia.jquery.js
1098 ms
layerslider.transitions.js
1022 ms
ytprefs.min.js
1064 ms
woocommerce-mod.js
736 ms
editor.js
824 ms
wc-aelia-currency-switcher.js
831 ms
add-to-cart.min.js
831 ms
woocommerce.min.js
908 ms
devicepx-jetpack.js
27 ms
e-201611.js
31 ms
jquery.cookie.min.js
906 ms
cart-fragments.min.js
903 ms
avia.js
997 ms
shortcodes.js
1064 ms
jquery.magnific-popup.min.js
841 ms
mediaelement-and-player.min.js
962 ms
wp-mediaelement.js
851 ms
comment-reply.min.js
839 ms
angelleye-frontend.js
886 ms
fitvids.min.js
841 ms
wp-embed.min.js
845 ms
iframe_api
111 ms
analytics.js
108 ms
wttlogo5.png
629 ms
wttbackground.jpg
631 ms
decoding-book9.png
632 ms
wttbackground3.jpg
1056 ms
ChartingPlatform4.png
633 ms
videoarchivebackground3.jpg
854 ms
vid1l.png
629 ms
vid5l.png
635 ms
vid2l.png
634 ms
vid8l.png
633 ms
vid3l.png
636 ms
vid6l.png
639 ms
vid4l.png
639 ms
vid9l.png
654 ms
vid10l.png
673 ms
videoarchive.png
826 ms
forum.png
841 ms
dna2.png
765 ms
entypo-fontello.woff
746 ms
page.js
58 ms
www-widgetapi.js
37 ms
collect
26 ms
skin.css
408 ms
www.whentotrade.com
2369 ms
g.gif
43 ms
DXI1ORHCpsQm3Vp6mXoaTdqQynqKV_9Plp7mupa0S4g.ttf
58 ms
print.css
366 ms
whentotrade.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.
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
whentotrade.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
Page has valid source maps
whentotrade.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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whentotrade.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 Whentotrade.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.
whentotrade.com
Open Graph data is detected on the main page of Whento Trade. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: