Tools & Wizards About Us
dexly.pro screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

dexly.pro

Dexly • Trade Forex, Crypto, CFD with cryptocurrencies

Page Load Speed

2.5 sec in total

First Response

340 ms

Resources Loaded

1.7 sec

Page Rendered

458 ms

dexly.pro screenshot

About Website

Welcome to dexly.pro homepage info - get ready to check Dexly best content right away, or after learning these important things about dexly.pro

Dexly is a cryptocurrency trading platform that allows you to trade global markets including Crypto, Forex, Indices, and Commodities.

Visit dexly.pro

Key Findings

We analyzed Dexly.pro page load time and found that the first response time was 340 ms and then it took 2.2 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

dexly.pro performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

64/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

6/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value3,920 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value18.7 s

3/100

10%

Network Requests Diagram

dexly.pro

340 ms

dexly.pro

66 ms

frontend.css

39 ms

eae.min.css

51 ms

peel.css

65 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 92% of them (98 requests) were addressed to the original Dexly.pro, 3% (3 requests) were made to S3.tradingview.com and 2% (2 requests) were made to Cdn.lordicon.com. The less responsive or slowest element that took the longest time to load (725 ms) belongs to the original domain Dexly.pro.

Page Optimization Overview & Recommendations

Page size can be reduced by 191.1 kB (15%)

Content Size

1.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Dexly.pro main page is 1.3 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. 65% of websites need less resources to load. Images take 711.8 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 156.0 kB

  • Original 186.5 kB
  • After minification 178.9 kB
  • After compression 30.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. 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 156.0 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 14.3 kB

  • Original 711.8 kB
  • After minification 697.5 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. Dexly images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 9.6 kB

  • Original 205.2 kB
  • After minification 205.2 kB
  • After compression 195.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. This website has mostly compressed JavaScripts.

CSS Optimization

-6%

Potential reduce by 11.2 kB

  • Original 196.6 kB
  • After minification 196.4 kB
  • After compression 185.4 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. Dexly.pro has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 73 (84%)

Requests Now

87

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dexly.pro

dexly.pro

340 ms

dexly.pro

dexly.pro

66 ms

frontend.css

frontend.css

39 ms

eae.min.css

eae.min.css

51 ms

peel.css

peel.css

65 ms

v4-shims.min.css

v4-shims.min.css

41 ms

all.min.css

all.min.css

60 ms

vegas.min.css

vegas.min.css

42 ms

header-footer-elementor.css

header-footer-elementor.css

64 ms

elementor-icons.min.css

elementor-icons.min.css

63 ms

frontend.min.css

frontend.min.css

84 ms

swiper.min.css

swiper.min.css

78 ms

e-swiper.min.css

e-swiper.min.css

77 ms

post-2287.css

post-2287.css

86 ms

fadeInDown.min.css

fadeInDown.min.css

77 ms

widget-text-editor.min.css

widget-text-editor.min.css

73 ms

fadeIn.min.css

fadeIn.min.css

93 ms

fadeInRight.min.css

fadeInRight.min.css

86 ms

widget-image.min.css

widget-image.min.css

102 ms

fadeInUp.min.css

fadeInUp.min.css

92 ms

widget-heading.min.css

widget-heading.min.css

94 ms

zoomInUp.min.css

zoomInUp.min.css

98 ms

fadeInLeft.min.css

fadeInLeft.min.css

95 ms

widget-icon-list.min.css

widget-icon-list.min.css

109 ms

post-2.css

post-2.css

107 ms

post-926.css

post-926.css

106 ms

style.css

style.css

110 ms

dashicons.min.css

dashicons.min.css

129 ms

style-min.css

style-min.css

118 ms

responsive-min.css

responsive-min.css

118 ms

style.css

style.css

122 ms

iconfont-min.css

iconfont-min.css

123 ms

widget-icon-list.min.css

widget-icon-list.min.css

121 ms

widget-social-icons.min.css

widget-social-icons.min.css

126 ms

brands.css

brands.css

135 ms

fontawesome.css

fontawesome.css

145 ms

solid.css

solid.css

134 ms

js

js

86 ms

lcw-widget.js

lcw-widget.js

91 ms

embed-widget-market-overview.js

embed-widget-market-overview.js

33 ms

embed-widget-technical-analysis.js

embed-widget-technical-analysis.js

112 ms

embed-widget-timeline.js

embed-widget-timeline.js

70 ms

mt7.js

mt7.js

69 ms

lordicon-1.1.0.js

lordicon-1.1.0.js

48 ms

general.min.css

general.min.css

127 ms

fontawesome.min.css

fontawesome.min.css

106 ms

brands.min.css

brands.min.css

110 ms

regular.min.css

regular.min.css

110 ms

solid.min.css

solid.min.css

99 ms

owl.carousel.css

owl.carousel.css

91 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

107 ms

animate.css

animate.css

103 ms

lordicon.js

lordicon.js

6 ms

iconHelper.js

iconHelper.js

215 ms

jquery.min.js

jquery.min.js

211 ms

jquery-migrate.min.js

jquery-migrate.min.js

217 ms

email-decode.min.js

email-decode.min.js

85 ms

eae.min.js

eae.min.js

373 ms

index.min.js

index.min.js

274 ms

v4-shims.min.js

v4-shims.min.js

275 ms

animated-main.min.js

animated-main.min.js

317 ms

particles.min.js

particles.min.js

340 ms

magnific.min.js

magnific.min.js

341 ms

vegas.min.js

vegas.min.js

355 ms

site-jquery-min.js

site-jquery-min.js

378 ms

comment-reply.min.js

comment-reply.min.js

439 ms

general.min.js

general.min.js

437 ms

hoverIntent.min.js

hoverIntent.min.js

624 ms

maxmegamenu.js

maxmegamenu.js

461 ms

fn.js

fn.js

466 ms

ue-remote-controls.js

ue-remote-controls.js

472 ms

owl.carousel.min.js

owl.carousel.min.js

549 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

549 ms

webpack.runtime.min.js

webpack.runtime.min.js

575 ms

frontend-modules.min.js

frontend-modules.min.js

621 ms

core.min.js

core.min.js

599 ms

frontend.min.js

frontend.min.js

710 ms

cropped-dexly2.png

cropped-dexly2.png

378 ms

world-map-background-dark.webp

world-map-background-dark.webp

389 ms

dexly_image2.png

dexly_image2.png

628 ms

dexly3-768x481.png

dexly3-768x481.png

511 ms

cropped-dexly2-300x79.png

cropped-dexly2-300x79.png

443 ms

trustpilot.png

trustpilot.png

444 ms

ssl-secure-1.png

ssl-secure-1.png

454 ms

1-768x439.webp

1-768x439.webp

412 ms

2-768x512.webp

2-768x512.webp

398 ms

3-768x439.webp

3-768x439.webp

421 ms

4-768x439.webp

4-768x439.webp

417 ms

5-768x512.webp

5-768x512.webp

435 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf

455 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

441 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

513 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

477 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

478 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

514 ms

wARDj0u

wARDj0u

22 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexQ.ttf

472 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkWVAexQ.ttf

497 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkWVAexQ.ttf

462 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjWVAexQ.ttf

482 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexQ.ttf

478 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVAexQ.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjWVAexQ.ttf

479 ms

fa-brands-400.woff

fa-brands-400.woff

526 ms

fa-regular-400.woff

fa-regular-400.woff

522 ms

fa-solid-900.woff

fa-solid-900.woff

725 ms

page-builder-framework.woff

page-builder-framework.woff

476 ms

main.js

main.js

21 ms

Accessibility Review

dexly.pro accessibility score

96

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

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

Links do not have a discernible name

Best Practices

dexly.pro best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

dexly.pro SEO score

93

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

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 Dexly.pro 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 Dexly.pro 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

dexly.pro

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