Tools & Wizards About Us
canary.tools screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

canary.tools

Thinkst Canary

Page Load Speed

2.1 sec in total

First Response

139 ms

Resources Loaded

1.4 sec

Page Rendered

532 ms

canary.tools screenshot

About Website

Welcome to canary.tools homepage info - get ready to check Canary best content for United States right away, or after learning these important things about canary.tools

Most companies discover they've been breached way too late. Thinkst Canary fixes this: just 2 minutes of setup; nearly 0 false positives, no ongoing overhead, and you can detect attackers long before ...

Visit canary.tools

Key Findings

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

Performance Metrics

canary.tools performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

37/100

25%

SI (Speed Index)

Value5.3 s

59/100

10%

TBT (Total Blocking Time)

Value800 ms

36/100

30%

CLS (Cumulative Layout Shift)

Value0.032

100/100

15%

TTI (Time to Interactive)

Value16.8 s

5/100

10%

Network Requests Diagram

canary.tools

139 ms

canary.tools

287 ms

app.css

141 ms

player.js

53 ms

widgets.js

25 ms

Our browser made a total of 61 requests to load all elements on the main page. We found that 66% of them (40 requests) were addressed to the original Canary.tools, 15% (9 requests) were made to Player.vimeo.com and 7% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (758 ms) belongs to the original domain Canary.tools.

Page Optimization Overview & Recommendations

Page size can be reduced by 516.8 kB (40%)

Content Size

1.3 MB

After Optimization

760.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Canary.tools 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. 55% of websites need less resources to load. Javascripts take 585.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 44.9 kB

  • Original 56.3 kB
  • After minification 44.5 kB
  • After compression 11.3 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 11.7 kB, which is 21% 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 44.9 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 14.0 kB

  • Original 572.3 kB
  • After minification 558.2 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

-74%

Potential reduce by 435.1 kB

  • Original 585.5 kB
  • After minification 585.5 kB
  • After compression 150.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 435.1 kB or 74% of the original size.

CSS Optimization

-36%

Potential reduce by 22.7 kB

  • Original 62.8 kB
  • After minification 62.8 kB
  • After compression 40.1 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.tools needs all CSS files to be minified and compressed as it can save up to 22.7 kB or 36% of the original size.

Requests Breakdown

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

Requests Now

46

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 46 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 7 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

canary.tools

canary.tools

139 ms

canary.tools

canary.tools

287 ms

app.css

app.css

141 ms

player.js

player.js

53 ms

widgets.js

widgets.js

25 ms

app.js

app.js

613 ms

site.js

site.js

206 ms

api.js

api.js

28 ms

css

css

30 ms

matomo.js

matomo.js

517 ms

337352561

337352561

190 ms

712336054

712336054

398 ms

731308710

731308710

248 ms

974103584

974103584

226 ms

logo-full--light.svg

logo-full--light.svg

127 ms

canary-console-long.svg

canary-console-long.svg

484 ms

twitter.svg

twitter.svg

136 ms

1GwB0p7m_400x400.png

1GwB0p7m_400x400.png

501 ms

dSC6oVHz_400x400.jpg

dSC6oVHz_400x400.jpg

338 ms

qkujxLMS_400x400.jpg

qkujxLMS_400x400.jpg

272 ms

jNj0exyI_400x400.jpg

jNj0exyI_400x400.jpg

205 ms

tbzv5wRP_normal.jpg

tbzv5wRP_normal.jpg

273 ms

jonathanlevine_400x400.jpg

jonathanlevine_400x400.jpg

340 ms

why_canary_1.jpg

why_canary_1.jpg

409 ms

why_canary_2.jpg

why_canary_2.jpg

502 ms

why_canary_3.jpg

why_canary_3.jpg

408 ms

how_it_works_1.gif

how_it_works_1.gif

678 ms

canary-console-medium.svg

canary-console-medium.svg

544 ms

c81TqWog_400x400.jpg

c81TqWog_400x400.jpg

524 ms

default_profile_400x400.png

default_profile_400x400.png

525 ms

canary_logo_alert.gif

canary_logo_alert.gif

541 ms

login.svg

login.svg

541 ms

Exit.svg

Exit.svg

559 ms

reset-passsword.svg

reset-passsword.svg

563 ms

Minus.svg

Minus.svg

608 ms

Plus.svg

Plus.svg

610 ms

Heart.svg

Heart.svg

613 ms

Unlimited.svg

Unlimited.svg

626 ms

AWS.svg

AWS.svg

630 ms

Year.svg

Year.svg

675 ms

Next.svg

Next.svg

676 ms

Quote-Check.svg

Quote-Check.svg

680 ms

Previous.svg

Previous.svg

693 ms

quote_loading.svg

quote_loading.svg

698 ms

quote_done.svg

quote_done.svg

753 ms

quote-fail.svg

quote-fail.svg

750 ms

message.svg

message.svg

756 ms

contact-soon.svg

contact-soon.svg

758 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

16 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

21 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

44 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

45 ms

canary-landing.woff

canary-landing.woff

652 ms

api.js

api.js

14 ms

337352561

337352561

293 ms

712336054

712336054

242 ms

731308710

731308710

237 ms

974103584

974103584

215 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

41 ms

settings

settings

95 ms

matomo.php

matomo.php

109 ms

Accessibility Review

canary.tools accessibility score

81

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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.

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.tools best practices score

75

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

Browser errors were logged to the console

SEO Factors

canary.tools SEO score

82

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

Links do not have descriptive text

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

High

Tap targets are not sized appropriately

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.tools 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.tools 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.tools

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