2.5 sec in total
192 ms
2.1 sec
226 ms
Visit trader.me now to see the best up-to-date Trader content and also check out these interesting facts you probably never knew about trader.me
Visit trader.meWe analyzed Trader.me page load time and found that the first response time was 192 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
trader.me performance score
name
value
score
weighting
Value3.3 s
39/100
10%
Value4.5 s
36/100
25%
Value4.1 s
79/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value3.3 s
93/100
10%
192 ms
829 ms
126 ms
123 ms
129 ms
Our browser made a total of 33 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Trader.me, 58% (19 requests) were made to Cdn.sedo.com and 9% (3 requests) were made to Sedo.com. The less responsive or slowest element that took the longest time to load (829 ms) relates to the external source Sedo.com.
Page size can be reduced by 1.2 MB (65%)
1.8 MB
612.7 kB
In fact, the total size of Trader.me main page is 1.8 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. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 145 B
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 145 B or 37% of the original size.
Potential reduce by 0 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. Trader images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 75% of the original size.
Potential reduce by 80.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. Trader.me needs all CSS files to be minified and compressed as it can save up to 80.7 kB or 77% of the original size.
Number of requests can be reduced by 23 (77%)
30
7
The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Trader. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
trader.me
192 ms
details.php4
829 ms
reset.css
126 ms
font-awesome-4.css
123 ms
jquery-ui.css
129 ms
details.parking.css
130 ms
magicsuggest.css
132 ms
tld-dialog.css
132 ms
jquery.js
151 ms
jquery-ui.js
169 ms
jquery.getUrlParam.js
150 ms
magicsuggest.js
150 ms
tld-dialog.js
150 ms
jquery.thickbox.js
167 ms
cookie.js
226 ms
etracker.js
229 ms
jquery-ui.js
237 ms
selectric.js
226 ms
details.js
227 ms
font-awesome.min.css
116 ms
e.js
522 ms
gpt.js
48 ms
ga.js
23 ms
pubads_impl_82.js
69 ms
__utm.gif
15 ms
container.html
28 ms
jquery.js
183 ms
534 ms
t.js
560 ms
search.details.parking.png
175 ms
loader.gif
227 ms
fontawesome-webfont.woff
3 ms
fontawesome-webfont.woff
94 ms
trader.me 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
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.
trader.me best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
trader.me 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Trader.me 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 Trader.me 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.
trader.me
Open Graph description is not detected on the main page of Trader. 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: