Report Summary

  • 19

    Performance

    Renders faster than
    37% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

gdax.io

Cryptocurrency Prices, Charts And Market Capitalizations | CoinMarketCap

Page Load Speed

6.6 sec in total

First Response

115 ms

Resources Loaded

3.5 sec

Page Rendered

2.9 sec

gdax.io screenshot

About Website

Welcome to gdax.io homepage info - get ready to check Gdax best content right away, or after learning these important things about gdax.io

Top cryptocurrency prices and charts, listed by market capitalization. Free access to current and historic data for Bitcoin and thousands of altcoins.

Visit gdax.io

Key Findings

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

Performance Metrics

gdax.io performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value13.8 s

0/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value7,080 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value17.5 s

4/100

10%

Network Requests Diagram

gdax.io

115 ms

www.coinmarketcap.com

89 ms

coinmarketcap.com

176 ms

sensorsdata.min.js

886 ms

bundle.tracing.min.js

917 ms

Our browser made a total of 130 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Gdax.io, 82% (107 requests) were made to S2.coinmarketcap.com and 12% (15 requests) were made to S3.coinmarketcap.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source S3.coinmarketcap.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 598.7 kB (43%)

Content Size

1.4 MB

After Optimization

807.6 kB

In fact, the total size of Gdax.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 830.6 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 428.2 kB

  • Original 524.1 kB
  • After minification 523.0 kB
  • After compression 95.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 428.2 kB or 82% of the original size.

Image Optimization

-19%

Potential reduce by 156.1 kB

  • Original 830.6 kB
  • After minification 674.6 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, Gdax needs image optimization as it can save up to 156.1 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-32%

Potential reduce by 14.4 kB

  • Original 44.5 kB
  • After minification 44.5 kB
  • After compression 30.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 14.4 kB or 32% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 7.0 kB
  • After minification 7.0 kB
  • After compression 7.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. Gdax.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 79 (65%)

Requests Now

121

After Optimization

42

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

Accessibility Review

gdax.io accessibility score

64

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-*] attributes do not match their roles

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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

gdax.io best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

gdax.io SEO score

78

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

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Gdax.io 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 Gdax.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

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