Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

dex.report

List of Decentralized Exchanges - Best DEX Decentralized exchanges

Page Load Speed

1.7 sec in total

First Response

138 ms

Resources Loaded

1.4 sec

Page Rendered

179 ms

About Website

Click here to check amazing DEX content. Otherwise, check out these important facts you probably never knew about dex.report

List of decentralized crypto exchanges. A decentralized exchange (DEX) is a cryptocurrency exchange which operates in a decentralized way, without a central ...

Visit dex.report

Key Findings

We analyzed Dex.report page load time and found that the first response time was 138 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

dex.report performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

63/100

25%

SI (Speed Index)

Value3.8 s

84/100

10%

TBT (Total Blocking Time)

Value440 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

dex.report

138 ms

rays.network

421 ms

bootstrap.min.css

195 ms

font-awesome.min.css

287 ms

simple-line-icons.css

286 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original Dex.report, 67% (12 requests) were made to Rays.network and 22% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (636 ms) relates to the external source Rays.network.

Page Optimization Overview & Recommendations

Page size can be reduced by 237.7 kB (78%)

Content Size

304.1 kB

After Optimization

66.4 kB

In fact, the total size of Dex.report main page is 304.1 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. 20% of websites need less resources to load. CSS take 210.1 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 2.5 kB

  • Original 3.3 kB
  • After minification 2.9 kB
  • After compression 825 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. This page needs HTML code to be minified as it can gain 351 B, which is 11% 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 2.5 kB or 75% of the original size.

JavaScript Optimization

-65%

Potential reduce by 59.0 kB

  • Original 90.8 kB
  • After minification 90.2 kB
  • After compression 31.7 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 59.0 kB or 65% of the original size.

CSS Optimization

-84%

Potential reduce by 176.2 kB

  • Original 210.1 kB
  • After minification 201.9 kB
  • After compression 33.9 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. Dex.report needs all CSS files to be minified and compressed as it can save up to 176.2 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (87%)

Requests Now

15

After Optimization

2

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

Accessibility Review

dex.report accessibility score

73

Accessibility Issues

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

Heading elements are not in a sequentially-descending order

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

dex.report best practices score

83

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

Page has valid source maps

SEO Factors

dex.report SEO score

86

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

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 doesn't use legible font sizes

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 Dex.report 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 Dex.report 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 DEX. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: