3.5 sec in total
290 ms
3 sec
172 ms
Welcome to dragonex.io homepage info - get ready to check Dragonex best content for Ukraine right away, or after learning these important things about dragonex.io
DragonEx团队拥有7年的区块链领域开发、运营经验。全站采用DC(Dragon Cash)代币衡量、利益共享收入100%按日分红、7*24小时优质服务。DragonEx specialized in development and operation of Blockchain with seven years experience. It boasts the following compe...
Visit dragonex.ioWe analyzed Dragonex.io page load time and found that the first response time was 290 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
dragonex.io performance score
name
value
score
weighting
Value7.1 s
1/100
10%
Value9.0 s
1/100
25%
Value38.5 s
0/100
10%
Value420 ms
65/100
30%
Value0
100/100
15%
Value8.8 s
36/100
10%
290 ms
82 ms
145 ms
275 ms
901 ms
Our browser made a total of 28 requests to load all elements on the main page. We found that 43% of them (12 requests) were addressed to the original Dragonex.io, 21% (6 requests) were made to Static.zdassets.com and 11% (3 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Dragonex.io.
Page size can be reduced by 213.4 kB (60%)
354.5 kB
141.1 kB
In fact, the total size of Dragonex.io main page is 354.5 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. 65% of websites need less resources to load. CSS take 183.3 kB which makes up the majority of the site volume.
Potential reduce by 4.7 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 4.7 kB or 60% of the original size.
Potential reduce by 95.6 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 95.6 kB or 59% of the original size.
Potential reduce by 113.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. Dragonex.io needs all CSS files to be minified and compressed as it can save up to 113.2 kB or 62% of the original size.
Number of requests can be reduced by 21 (78%)
27
6
The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dragonex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and as a result speed up the page load time.
{{url}}
{{time}} ms
dragonex.io 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.
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
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
dragonex.io best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
dragonex.io SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
Document doesn't have a valid hreflang
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 uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dragonex.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 Dragonex.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.
{{og_description}}
dragonex.io
Open Graph description is not detected on the main page of Dragonex. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: