Tools & Wizards About Us
interactive.twilio.com screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

interactive.twilio.com

Communication APIs for SMS, Voice, Video & Authentication | Twilio

Page Load Speed

2.4 sec in total

First Response

104 ms

Resources Loaded

904 ms

Page Rendered

1.4 sec

interactive.twilio.com screenshot

About Website

Welcome to interactive.twilio.com homepage info - get ready to check Interactive Twilio best content for United States right away, or after learning these important things about interactive.twilio.com

Connect with customers on their preferred channels—anywhere in the world. Quickly integrate powerful communication APIs to start building solutions for SMS and WhatsApp messaging, voice, video, and em...

Visit interactive.twilio.com

Key Findings

We analyzed Interactive.twilio.com page load time and found that the first response time was 104 ms and then it took 2.3 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

interactive.twilio.com performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value6.7 s

8/100

25%

SI (Speed Index)

Value7.8 s

23/100

10%

TBT (Total Blocking Time)

Value5,000 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.904

3/100

15%

TTI (Time to Interactive)

Value22.1 s

1/100

10%

Network Requests Diagram

interactive.twilio.com

104 ms

interactive.twilio.com

51 ms

www.twilio.com

42 ms

en-us

31 ms

fonts.css

229 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Interactive.twilio.com, 78% (25 requests) were made to Twilio.com and 3% (1 request) were made to Cloud.typography.com. The less responsive or slowest element that took the longest time to load (262 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 274.1 kB (77%)

Content Size

353.9 kB

After Optimization

79.8 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Interactive.twilio.com main page is 353.9 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. HTML takes 334.3 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 258.7 kB

  • Original 334.3 kB
  • After minification 300.3 kB
  • After compression 75.6 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 258.7 kB or 77% of the original size.

JavaScript Optimization

-47%

Potential reduce by 900 B

  • Original 1.9 kB
  • After minification 1.9 kB
  • After compression 998 B

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 900 B or 47% of the original size.

CSS Optimization

-82%

Potential reduce by 14.5 kB

  • Original 17.8 kB
  • After minification 16.9 kB
  • After compression 3.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. Interactive.twilio.com needs all CSS files to be minified and compressed as it can save up to 14.5 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (41%)

Requests Now

27

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

interactive.twilio.com

interactive.twilio.com

104 ms

interactive.twilio.com

interactive.twilio.com

51 ms

www.twilio.com

www.twilio.com

42 ms

en-us

en-us

31 ms

fonts.css

fonts.css

229 ms

css2

css2

31 ms

clientlib-site.lc-75da14ff65d2b3c910a8fbdd7cfffcce-lc.min.css

clientlib-site.lc-75da14ff65d2b3c910a8fbdd7cfffcce-lc.min.css

36 ms

homepage.min.css

homepage.min.css

71 ms

parameters.lc-775c9eb7ff4c48025fbe3d707bcf5f55-lc.min.js

parameters.lc-775c9eb7ff4c48025fbe3d707bcf5f55-lc.min.js

54 ms

jquery.lc-7842899024219bcbdb5e72c946870b79-lc.min.js

jquery.lc-7842899024219bcbdb5e72c946870b79-lc.min.js

30 ms

commons.lc-5370019fd157d93202ac2d6f771f04b8-lc.min.js

commons.lc-5370019fd157d93202ac2d6f771f04b8-lc.min.js

53 ms

atjs-integration.lc-401aa9ea1dd109fe7762186a74ae6c2b-lc.min.js

atjs-integration.lc-401aa9ea1dd109fe7762186a74ae6c2b-lc.min.js

54 ms

atjs.lc-b3979f0fb6fb659f264f69f53f1d5824-lc.min.js

atjs.lc-b3979f0fb6fb659f264f69f53f1d5824-lc.min.js

57 ms

utils.lc-e7bf340a353e643d198b25d0c8ccce47-lc.min.js

utils.lc-e7bf340a353e643d198b25d0c8ccce47-lc.min.js

57 ms

clientlib-site.lc-8447b086d1933e9c0eee6edd8cdf5387-lc.min.js

clientlib-site.lc-8447b086d1933e9c0eee6edd8cdf5387-lc.min.js

76 ms

homepage.min.js

homepage.min.js

81 ms

97CE8DA419CE4B000.css

97CE8DA419CE4B000.css

145 ms

gtm.js

gtm.js

262 ms

check-black.svg

check-black.svg

120 ms

compressed-1600.webp

compressed-1600.webp

62 ms

compressed-original.webp

compressed-original.webp

68 ms

compressed-original.webp

compressed-original.webp

64 ms

compressed-original.webp

compressed-original.webp

63 ms

compressed-original.webp

compressed-original.webp

67 ms

compressed-original.webp

compressed-original.webp

87 ms

twilio_mark.svg

twilio_mark.svg

80 ms

compressed-original.webp

compressed-original.webp

88 ms

compressed-original.webp

compressed-original.webp

94 ms

personas-bkgd.svg

personas-bkgd.svg

80 ms

compressed-original.webp

compressed-original.webp

93 ms

compressed-1600.webp

compressed-1600.webp

184 ms

json

json

31 ms

Accessibility Review

interactive.twilio.com accessibility score

83

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

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA IDs are not unique

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.

Best Practices

interactive.twilio.com best practices score

83

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

Page has valid source maps

SEO Factors

interactive.twilio.com SEO score

93

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

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 Interactive.twilio.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 Interactive.twilio.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

interactive.twilio.com

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