4.7 sec in total
441 ms
4.2 sec
85 ms
Click here to check amazing Trade Map content for Iran. Otherwise, check out these important facts you probably never knew about trademap.org
Trade Map - free access to world trade data (on a monthly, quarterly and yearly basis) by country, product and service, to the most detailed level
Visit trademap.orgWe analyzed Trademap.org page load time and found that the first response time was 441 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
trademap.org performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value7.1 s
6/100
25%
Value5.5 s
54/100
10%
Value100 ms
98/100
30%
Value0
100/100
15%
Value6.8 s
55/100
10%
441 ms
429 ms
123 ms
296 ms
290 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 71% of them (47 requests) were addressed to the original Trademap.org, 17% (11 requests) were made to Platform.twitter.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (886 ms) belongs to the original domain Trademap.org.
Page size can be reduced by 114.8 kB (53%)
216.3 kB
101.6 kB
In fact, the total size of Trademap.org main page is 216.3 kB. 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. HTML takes 118.6 kB which makes up the majority of the site volume.
Potential reduce by 100.9 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 100.9 kB or 85% of the original size.
Potential reduce by 9.4 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, Trade Map needs image optimization as it can save up to 9.4 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 2.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. This website has mostly compressed JavaScripts.
Potential reduce by 1.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. Trademap.org needs all CSS files to be minified and compressed as it can save up to 1.7 kB or 23% of the original size.
Number of requests can be reduced by 36 (57%)
63
27
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Trade Map. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
trademap.org
441 ms
www.trademap.org
429 ms
Index.aspx
123 ms
Default.css
296 ms
Menus.css
290 ms
HomePage.css
296 ms
Styles.css
314 ms
js
46 ms
Ajax.js
330 ms
Popup.js
330 ms
ScrollableNewsParams.js
602 ms
ScrollableNewsMessages_EN.txt
580 ms
WebResource.axd
613 ms
ScrollableNews.js
627 ms
js
40 ms
analytics.js
20 ms
ITC_Logo.gif
315 ms
TM_logo.gif
315 ms
title-TradeMap.png
574 ms
close.gif
381 ms
imprim.gif
599 ms
maximize.gif
590 ms
lockLogin.gif
487 ms
DropArrow.gif
594 ms
delete.png
631 ms
meta_red.png
630 ms
social_media_twitter_follow.png
686 ms
social_media_round_icons_darkblue_32x32_facebook.png
737 ms
social_media_round_icons_lightblue_32x32_twitter.png
737 ms
social_media_round_icons_darkblue_32x32_linkedin.png
782 ms
social_media_round_icons_lightblue_32x32_youtube.png
842 ms
logo-EU.png
843 ms
logo-UNCTAD.png
877 ms
logo-WTO.png
886 ms
collect
44 ms
collect
24 ms
SilentLogin.aspx
591 ms
widgets.js
90 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
57 ms
settings
97 ms
timeline.e108540dddc96e4b707f5cf259a582d7.js
22 ms
ITC_MktAnalysis
76 ms
polyfills-3b821eda8863adcc4a4b.js
22 ms
runtime-a697c5a1ae32bd7e4d42.js
48 ms
modules.20f98d7498a59035a762.js
91 ms
main-fd9ef5eb169057cda26d.js
70 ms
_app-88bf420a57d49e33be53.js
77 ms
%5BscreenName%5D-c33f0b02841cffc3e9b4.js
86 ms
_buildManifest.js
92 ms
_ssgManifest.js
90 ms
authorize
563 ms
Print.css
107 ms
ajax-loader.gif
108 ms
DistanceConcentrationCountriesBubbleGraph.aspx
142 ms
LeadingMarketsMap.aspx
154 ms
GrowthCountriesBubbleGraph.aspx
151 ms
TM_DA_News_en_100.png
448 ms
Default.css
324 ms
DisplayToolTips.js
299 ms
ChartPic_000226.png
188 ms
ChartPic_000227.png
280 ms
DisplayToolTips.js
275 ms
DundasMap8.js
589 ms
MapPic_000165.png
298 ms
Empty.gif
106 ms
Rendering.gif
106 ms
trademap.org accessibility score
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
Links do not have a discernible name
trademap.org 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
trademap.org SEO score
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 Trademap.org 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 Trademap.org 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.
trademap.org
Open Graph description is not detected on the main page of Trade Map. 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: