Tools & Wizards About Us
canary.exchange screenshot

Report Summary

  • 79

    Performance

    Renders faster than
    85% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

canary.exchange

Canary DeFi | Decentralized Finance (DeFi) | Let's change the world!

Page Load Speed

2 sec in total

First Response

250 ms

Resources Loaded

1.3 sec

Page Rendered

369 ms

canary.exchange screenshot

About Website

Visit canary.exchange now to see the best up-to-date Canary content for Turkey and also check out these interesting facts you probably never knew about canary.exchange

Canary DeFi is a decentralized finance (DeFi) which runs on Avalanche,the most promising and the fastest blockchain

Visit canary.exchange

Key Findings

We analyzed Canary.exchange page load time and found that the first response time was 250 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

canary.exchange performance score

79

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

62/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value3.5 s

88/100

10%

TBT (Total Blocking Time)

Value200 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.8 s

89/100

10%

Network Requests Diagram

canary.exchange

250 ms

canary.exchange

215 ms

main.css

218 ms

email-decode.min.js

9 ms

jquery-3.5.1.min.js

204 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 67% of them (20 requests) were addressed to the original Canary.exchange, 23% (7 requests) were made to Fonts.gstatic.com and 10% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (580 ms) belongs to the original domain Canary.exchange.

Page Optimization Overview & Recommendations

Page size can be reduced by 30.1 kB (7%)

Content Size

460.5 kB

After Optimization

430.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Canary.exchange main page is 460.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. 35% of websites need less resources to load. Images take 287.4 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 6.5 kB

  • Original 8.3 kB
  • After minification 5.5 kB
  • After compression 1.8 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 2.8 kB, which is 34% 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 6.5 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 287.4 kB
  • After minification 287.4 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. Canary images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 2.1 kB

  • Original 84.5 kB
  • After minification 84.5 kB
  • After compression 82.4 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

-27%

Potential reduce by 21.5 kB

  • Original 80.3 kB
  • After minification 80.3 kB
  • After compression 58.8 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. Canary.exchange needs all CSS files to be minified and compressed as it can save up to 21.5 kB or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (78%)

Requests Now

18

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

canary.exchange

canary.exchange

250 ms

canary.exchange

canary.exchange

215 ms

main.css

main.css

218 ms

email-decode.min.js

email-decode.min.js

9 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

204 ms

popper.min.js

popper.min.js

203 ms

bootstrap.min.js

bootstrap.min.js

208 ms

jquery.easing.min.js

jquery.easing.min.js

203 ms

owl.carousel.min.js

owl.carousel.min.js

201 ms

countdown.min.js

countdown.min.js

391 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

396 ms

jquery.rcounterup.js

jquery.rcounterup.js

395 ms

magnific-popup.min.js

magnific-popup.min.js

396 ms

validator.min.js

validator.min.js

400 ms

app.js

app.js

407 ms

logo.svg

logo.svg

580 ms

css

css

44 ms

css

css

60 ms

css

css

65 ms

bgimg.jpg

bgimg.jpg

295 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

18 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

23 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

30 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

33 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

34 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

40 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

39 ms

fa-solid-900.woff

fa-solid-900.woff

522 ms

fa-regular-400.woff

fa-regular-400.woff

334 ms

fa-brands-400.woff

fa-brands-400.woff

513 ms

Accessibility Review

canary.exchange accessibility score

93

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

canary.exchange best practices score

83

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

canary.exchange SEO score

100

Search Engine Optimization Advices

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 Canary.exchange 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 Canary.exchange 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

canary.exchange

Open Graph description is not detected on the main page of Canary. 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: