1.7 sec in total
138 ms
1.4 sec
179 ms
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.reportWe 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.
dex.report performance score
name
value
score
weighting
Value3.4 s
36/100
10%
Value3.5 s
63/100
25%
Value3.8 s
84/100
10%
Value440 ms
63/100
30%
Value0
100/100
15%
Value8.5 s
38/100
10%
138 ms
421 ms
195 ms
287 ms
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 size can be reduced by 237.7 kB (78%)
304.1 kB
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.
Potential reduce by 2.5 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 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.
Potential reduce by 59.0 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.
Potential reduce by 176.2 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.
Number of requests can be reduced by 13 (87%)
15
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.
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
css
46 ms
css
59 ms
css
60 ms
device-mockups.min.css
279 ms
new-age.min.css
283 ms
styles.css
281 ms
bundle.js
636 ms
jquery.min.js
465 ms
bootstrap.bundle.min.js
464 ms
jquery.easing.min.js
370 ms
new-age.js
372 ms
js
78 ms
css
14 ms
dex.report 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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
dex.report best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
dex.report SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document doesn't use 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 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.
dex.report
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: