Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

docs.authy.com

Authy: 2FA and Passwordless Login | Twilio

Page Load Speed

351 ms in total

First Response

27 ms

Resources Loaded

324 ms

Page Rendered

0 ms

docs.authy.com screenshot

About Website

Welcome to docs.authy.com homepage info - get ready to check Docs Authy best content for United States right away, or after learning these important things about docs.authy.com

Easily add two-factor authentication and passwordless logins via API or with our Helper Libraries. Protect logins and step-up transactions with SMS, Voice, PushAuthentications, and TOTP through a simp...

Visit docs.authy.com

Key Findings

We analyzed Docs.authy.com page load time and found that the first response time was 27 ms and then it took 324 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

docs.authy.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

86/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value2,880 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value13.1 s

12/100

10%

Network Requests Diagram

docs.authy.com

27 ms

authy

68 ms

authy

127 ms

notice

108 ms

12418e876151f57e.css

16 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Docs.authy.com, 89% (17 requests) were made to Twilio.com and 5% (1 request) were made to Consent.trustarc.com. The less responsive or slowest element that took the longest time to load (127 ms) relates to the external source Twilio.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 125.9 kB (80%)

Content Size

157.6 kB

After Optimization

31.8 kB

In fact, the total size of Docs.authy.com main page is 157.6 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 146.5 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 125.7 kB

  • Original 146.5 kB
  • After minification 146.5 kB
  • After compression 20.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. 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 125.7 kB or 86% of the original size.

JavaScript Optimization

-1%

Potential reduce by 145 B

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

Requests Breakdown

Number of requests can be reduced by 12 (75%)

Requests Now

16

After Optimization

4

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

Accessibility Review

docs.authy.com accessibility score

98

Accessibility Issues

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

docs.authy.com 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

docs.authy.com SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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 Docs.authy.com 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 Docs.authy.com 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

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