Tools & Wizards About Us
tradepay.io screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% 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

  • 84

    SEO

    Google-friendlier than
    52% of websites

tradepay.io

Tradepay B2b Payments Using Part Cash and Part Trade | Trade Pay

Page Load Speed

4 sec in total

First Response

424 ms

Resources Loaded

3.2 sec

Page Rendered

437 ms

tradepay.io screenshot

About Website

Click here to check amazing Tradepay content. Otherwise, check out these important facts you probably never knew about tradepay.io

Tradepay is a B2B payment platform for businesses using partial cash and partial trade. Get the best deals for your business from Tradepay!

Visit tradepay.io

Key Findings

We analyzed Tradepay.io page load time and found that the first response time was 424 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

tradepay.io performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value12.7 s

0/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.3 s

32/100

10%

Network Requests Diagram

tradepay.io

424 ms

gtm.js

51 ms

normalize.css

84 ms

webflow.css

110 ms

trade-pay.webflow.css

104 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 76% of them (57 requests) were addressed to the original Tradepay.io, 13% (10 requests) were made to Use.typekit.net and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (483 ms) belongs to the original domain Tradepay.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 304.5 kB (21%)

Content Size

1.4 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tradepay.io 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. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 47.4 kB

  • Original 57.2 kB
  • After minification 55.1 kB
  • After compression 9.8 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 47.4 kB or 83% of the original size.

Image Optimization

-18%

Potential reduce by 187.3 kB

  • Original 1.0 MB
  • After minification 850.0 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, Tradepay needs image optimization as it can save up to 187.3 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-19%

Potential reduce by 42.9 kB

  • Original 227.2 kB
  • After minification 227.2 kB
  • After compression 184.3 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 42.9 kB or 19% of the original size.

CSS Optimization

-28%

Potential reduce by 26.9 kB

  • Original 97.5 kB
  • After minification 96.3 kB
  • After compression 70.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. Tradepay.io needs all CSS files to be minified and compressed as it can save up to 26.9 kB or 28% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (47%)

Requests Now

64

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tradepay.io

tradepay.io

424 ms

gtm.js

gtm.js

51 ms

normalize.css

normalize.css

84 ms

webflow.css

webflow.css

110 ms

trade-pay.webflow.css

trade-pay.webflow.css

104 ms

pwp1qnn.js

pwp1qnn.js

221 ms

modernizr.js

modernizr.js

108 ms

style.css

style.css

108 ms

styles.css

styles.css

216 ms

menu-image.css

menu-image.css

177 ms

dashicons.min.css

dashicons.min.css

202 ms

style.css

style.css

179 ms

swpm.common.css

swpm.common.css

198 ms

front-legacy.css

front-legacy.css

194 ms

wpbaw-public.css

wpbaw-public.css

261 ms

wp-custom-register-login-public.css

wp-custom-register-login-public.css

261 ms

bootstrap.min.css

bootstrap.min.css

296 ms

formValidation.min.css

formValidation.min.css

283 ms

addtoany.min.css

addtoany.min.css

283 ms

page.js

page.js

48 ms

jquery.js

jquery.js

303 ms

addtoany.min.js

addtoany.min.js

332 ms

popup.js

popup.js

343 ms

anything-popup.js

anything-popup.js

378 ms

wp-custom-register-login-public.js

wp-custom-register-login-public.js

377 ms

bootstrap.min.js

bootstrap.min.js

378 ms

formValidation.min.js

formValidation.min.js

415 ms

bootstrap-validator.min.js

bootstrap-validator.min.js

407 ms

jquery.min.js

jquery.min.js

27 ms

webflow.js

webflow.js

483 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

341 ms

eso.m4v434v2.js

eso.m4v434v2.js

14 ms

analytics.js

analytics.js

170 ms

Logo3x_1.png

Logo3x_1.png

165 ms

Money-bag3x.png

Money-bag3x.png

167 ms

Share3x.png

Share3x.png

165 ms

Shoping-cart3x.png

Shoping-cart3x.png

166 ms

List-icon3x.png

List-icon3x.png

164 ms

Submit-icon3x-150x141.png

Submit-icon3x-150x141.png

167 ms

Communicate3x.png

Communicate3x.png

169 ms

People-23x.png

People-23x.png

168 ms

icon-login.png

icon-login.png

168 ms

Hero-1.jpg

Hero-1.jpg

197 ms

Arrow.png

Arrow.png

196 ms

Illustration-p-500.png

Illustration-p-500.png

219 ms

icon-.png

icon-.png

230 ms

Icon-2.png

Icon-2.png

244 ms

Icon-3.png

Icon-3.png

242 ms

Mockup-1.png

Mockup-1.png

244 ms

Check.png

Check.png

245 ms

Group-5.png

Group-5.png

295 ms

Wall-203x300.png

Wall-203x300.png

301 ms

Illustration_1.png

Illustration_1.png

319 ms

Cube-260x300.png

Cube-260x300.png

311 ms

Logo3x.png

Logo3x.png

313 ms

Facebook3x-24x24.png

Facebook3x-24x24.png

317 ms

Twitter3x.png

Twitter3x.png

359 ms

Linkedin@3x-24x24.png

Linkedin@3x-24x24.png

376 ms

logo.png

logo.png

388 ms

Icon-2-150x150.png

Icon-2-150x150.png

384 ms

List-icon3x-1.png

List-icon3x-1.png

389 ms

Share3x-24x24.png

Share3x-24x24.png

394 ms

Communicate3x-24x24.png

Communicate3x-24x24.png

435 ms

d

d

23 ms

d

d

40 ms

d

d

41 ms

d

d

50 ms

d

d

42 ms

d

d

88 ms

d

d

50 ms

d

d

117 ms

d

d

57 ms

collect

collect

19 ms

js

js

59 ms

p.gif

p.gif

28 ms

Accessibility Review

tradepay.io accessibility score

68

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

tradepay.io best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

tradepay.io SEO score

84

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

tradepay.io

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