Tools & Wizards About Us
trademoremobile.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

trademoremobile.com

Buy Devices or Trade-in Phones, Tablets & More | Trademore

Page Load Speed

3.2 sec in total

First Response

1.1 sec

Resources Loaded

1.9 sec

Page Rendered

268 ms

trademoremobile.com screenshot

About Website

Welcome to trademoremobile.com homepage info - get ready to check Trademore Mobile best content for United States right away, or after learning these important things about trademoremobile.com

Buy and sell used phones and pre-owned electronics like tablets, watches and more with Trademore. Browse our wide selection of devices to buy and sell today.

Visit trademoremobile.com

Key Findings

We analyzed Trademoremobile.com page load time and found that the first response time was 1.1 sec and then it took 2.1 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.

Performance Metrics

trademoremobile.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value1,820 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.5 s

8/100

10%

Network Requests Diagram

www.trademore.com

1088 ms

airgap.js

68 ms

trademore-vendor-lite-1039763172.js

22 ms

trademore-init-home-758805306.js

38 ms

api.js

43 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Trademoremobile.com, 11% (4 requests) were made to Bat.bing.com and 8% (3 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Trademore.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 52.3 kB (10%)

Content Size

531.5 kB

After Optimization

479.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Trademoremobile.com main page is 531.5 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. 60% of websites need less resources to load. Javascripts take 351.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 50.1 kB

  • Original 63.5 kB
  • After minification 53.8 kB
  • After compression 13.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 9.7 kB, which is 15% 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 50.1 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 856 B

  • Original 85.0 kB
  • After minification 84.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. Trademore Mobile images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.1 kB

  • Original 351.2 kB
  • After minification 351.1 kB
  • After compression 350.1 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.

CSS Optimization

-1%

Potential reduce by 263 B

  • Original 31.8 kB
  • After minification 31.8 kB
  • After compression 31.5 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. Trademoremobile.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 23 (68%)

Requests Now

34

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 34 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Trademore Mobile. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

www.trademore.com

www.trademore.com

1088 ms

airgap.js

airgap.js

68 ms

trademore-vendor-lite-1039763172.js

trademore-vendor-lite-1039763172.js

22 ms

trademore-init-home-758805306.js

trademore-init-home-758805306.js

38 ms

api.js

api.js

43 ms

js

js

280 ms

kenshoo.js

kenshoo.js

48 ms

trademore-feedback-58386545.js

trademore-feedback-58386545.js

37 ms

trademore-home-1571962794.js

trademore-home-1571962794.js

52 ms

platform.js

platform.js

54 ms

email-subscription-2108494065.js

email-subscription-2108494065.js

41 ms

trademore-vendor-427275139.css

trademore-vendor-427275139.css

252 ms

trademore-home-1632019603.css

trademore-home-1632019603.css

62 ms

bat.js

bat.js

315 ms

ktag.js

ktag.js

307 ms

v1

v1

357 ms

trademore_logo.svg

trademore_logo.svg

279 ms

loading.gif

loading.gif

200 ms

home-top-banner.jpg

home-top-banner.jpg

280 ms

privacyoptions.svg

privacyoptions.svg

277 ms

trademore-sprite.svg

trademore-sprite.svg

99 ms

left-directional-arrow.svg

left-directional-arrow.svg

97 ms

right-directional-arrow.svg

right-directional-arrow.svg

173 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

102 ms

Lato-Regular.woff

Lato-Regular.woff

106 ms

activity;src=8396909;cost=%2F;npa=0;auiddc=1024902173.1725615725;pscdl=noapi;frm=0;gtm=45fe4940v9181635138za200;gcd=13l3l3l3l1l1;dma=0;tag_exp=0;epver=2;~oref=https%3A%2F%2Fwww.trademore.com%2F

activity;src=8396909;cost=%2F;npa=0;auiddc=1024902173.1725615725;pscdl=noapi;frm=0;gtm=45fe4940v9181635138za200;gcd=13l3l3l3l1l1;dma=0;tag_exp=0;epver=2;~oref=https%3A%2F%2Fwww.trademore.com%2F

115 ms

5976027.js

5976027.js

63 ms

badge

badge

117 ms

5976027

5976027

43 ms

m=_b,_tp

m=_b,_tp

15 ms

js

js

66 ms

gray_stars_large.png

gray_stars_large.png

66 ms

orange_stars_large.png

orange_stars_large.png

105 ms

gcr_logo_stacked.png

gcr_logo_stacked.png

129 ms

0.7.45

0.7.45

52 ms

m=vhDjqd

m=vhDjqd

64 ms

Accessibility Review

trademoremobile.com accessibility score

68

Accessibility Issues

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

High

[aria-hidden="true"] elements contain focusable descendents

High

[role] values are not valid

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

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Some elements have a [tabindex] value greater than 0

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

trademoremobile.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

trademoremobile.com SEO score

79

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Trademoremobile.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 Trademoremobile.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.

Social Sharing Optimization

trademoremobile.com

Open Graph data is detected on the main page of Trademore Mobile. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: