Tools & Wizards About Us
chorus.ai screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

chorus.ai

Conversation Intelligence for Sales | ZoomInfo + Chorus

Page Load Speed

13.4 sec in total

First Response

40 ms

Resources Loaded

11.9 sec

Page Rendered

1.5 sec

chorus.ai screenshot

About Website

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

Make every interaction count! Leverage Chorus' conversation intelligence backed by ZoomInfo's leading B2B data to distill premium insights from sales calls.

Visit chorus.ai

Key Findings

We analyzed Chorus.ai page load time and found that the first response time was 40 ms and then it took 13.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

chorus.ai performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value38.8 s

0/100

10%

TBT (Total Blocking Time)

Value60,930 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value80.9 s

0/100

10%

Network Requests Diagram

chorus.ai

40 ms

www.chorus.ai

2439 ms

main-1d42912fb2.css

76 ms

forms2.min.js

710 ms

main-7d7d3e5965.bundle.js

479 ms

Our browser made a total of 95 requests to load all elements on the main page. We found that 11% of them (10 requests) were addressed to the original Chorus.ai, 36% (34 requests) were made to D1zp01vk4nyewr.cloudfront.net and 11% (10 requests) were made to Dev.visualwebsiteoptimizer.com. The less responsive or slowest element that took the longest time to load (4.2 sec) relates to the external source D1zp01vk4nyewr.cloudfront.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 315.8 kB (51%)

Content Size

618.8 kB

After Optimization

303.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Chorus.ai main page is 618.8 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 268.6 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 206.5 kB

  • Original 268.6 kB
  • After minification 268.5 kB
  • After compression 62.1 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 206.5 kB or 77% of the original size.

Image Optimization

-12%

Potential reduce by 3.7 kB

  • Original 31.0 kB
  • After minification 27.3 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. Obviously, Chorus needs image optimization as it can save up to 3.7 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-42%

Potential reduce by 61.5 kB

  • Original 145.1 kB
  • After minification 144.8 kB
  • After compression 83.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 61.5 kB or 42% of the original size.

CSS Optimization

-25%

Potential reduce by 44.0 kB

  • Original 174.1 kB
  • After minification 174.1 kB
  • After compression 130.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. Chorus.ai needs all CSS files to be minified and compressed as it can save up to 44.0 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (45%)

Requests Now

84

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

chorus.ai

chorus.ai

40 ms

www.chorus.ai

www.chorus.ai

2439 ms

main-1d42912fb2.css

main-1d42912fb2.css

76 ms

forms2.min.js

forms2.min.js

710 ms

main-7d7d3e5965.bundle.js

main-7d7d3e5965.bundle.js

479 ms

j.php

j.php

2840 ms

gtm.js

gtm.js

3753 ms

Chorus-Main_web.svg

Chorus-Main_web.svg

3400 ms

Docusign-Logo_dark_2021-08-16-201749.svg

Docusign-Logo_dark_2021-08-16-201749.svg

3710 ms

hudl-logo-black_2021-11-16-173100.svg

hudl-logo-black_2021-11-16-173100.svg

3728 ms

adobe-gray-2020_200601_224437.svg

adobe-gray-2020_200601_224437.svg

3732 ms

mongodb-gray-2020_200601_224432.svg

mongodb-gray-2020_200601_224432.svg

3733 ms

qualtrics-gray-2020_200601_224429.svg

qualtrics-gray-2020_200601_224429.svg

3715 ms

cision-gray-2020_200601_224440.svg

cision-gray-2020_200601_224440.svg

3728 ms

ZoomInfo-mark.svg

ZoomInfo-mark.svg

3857 ms

Best_Software_Products_2022.svg

Best_Software_Products_2022.svg

3850 ms

Year2022-v2.svg

Year2022-v2.svg

3853 ms

Fastest_Growing_Products_2022.svg

Fastest_Growing_Products_2022.svg

3833 ms

Highest_Satisfaction_Products_2022.svg

Highest_Satisfaction_Products_2022.svg

3838 ms

adobe.svg

adobe.svg

3845 ms

mongodb.svg

mongodb.svg

3861 ms

marketo.svg

marketo.svg

3859 ms

cision.svg

cision.svg

3869 ms

asana.svg

asana.svg

3872 ms

procore.svg

procore.svg

3864 ms

6sense.svg

6sense.svg

4103 ms

invision.svg

invision.svg

4087 ms

trip-actions.svg

trip-actions.svg

4088 ms

segment.svg

segment.svg

4118 ms

lucidchart.svg

lucidchart.svg

4124 ms

talkdesk-2020.svg

talkdesk-2020.svg

4121 ms

user-testing.svg

user-testing.svg

4157 ms

qualtrics.svg

qualtrics.svg

4130 ms

gitlab.svg

gitlab.svg

4151 ms

themuse.svg

themuse.svg

4154 ms

Docusign-Logo_black_2021-08-16-201747.svg

Docusign-Logo_black_2021-08-16-201747.svg

4148 ms

sendoso.svg

sendoso.svg

4152 ms

mongodb-white.svg

mongodb-white.svg

4167 ms

housecall-pro-white.svg

housecall-pro-white.svg

4179 ms

bugcrowd-white.svg

bugcrowd-white.svg

4183 ms

chorus-zoominfo-white.png

chorus-zoominfo-white.png

4162 ms

SharpSans-normal.otf

SharpSans-normal.otf

2651 ms

SharpSans-medium.otf

SharpSans-medium.otf

2651 ms

SharpSans-light.otf

SharpSans-light.otf

3217 ms

SharpSans-thin.otf

SharpSans-thin.otf

3221 ms

SharpSans-bold.otf

SharpSans-bold.otf

3215 ms

SharpSans-extra_bold.otf

SharpSans-extra_bold.otf

3214 ms

getForm

getForm

2489 ms

v.gif

v.gif

331 ms

tag-90d1c59b328d9c90a45785e87c70a86f.js

tag-90d1c59b328d9c90a45785e87c70a86f.js

598 ms

forms2.css

forms2.css

594 ms

forms2-theme-simple.css

forms2-theme-simple.css

664 ms

6si.min.js

6si.min.js

1767 ms

pixel

pixel

1317 ms

uwt.js

uwt.js

1979 ms

analytics.js

analytics.js

2323 ms

hotjar-1209417.js

hotjar-1209417.js

2324 ms

conversion_async.js

conversion_async.js

1941 ms

insight.min.js

insight.min.js

2710 ms

fbevents.js

fbevents.js

2633 ms

bizible.js

bizible.js

3005 ms

1389.js

1389.js

3004 ms

613f967b73005a001a5a92b1

613f967b73005a001a5a92b1

3003 ms

munchkin.js

munchkin.js

2695 ms

tag-834fdc77ea0a775f5f74f5321b5a87b7.js

tag-834fdc77ea0a775f5f74f5321b5a87b7.js

1221 ms

formcomplete.js

formcomplete.js

1978 ms

settings.js

settings.js

636 ms

XDFrame

XDFrame

613 ms

worker-70faafffa0475802f5ee03ca5ff74179.js

worker-70faafffa0475802f5ee03ca5ff74179.js

1218 ms

1602 ms

1834 ms

adsct

adsct

1190 ms

adsct

adsct

1189 ms

collect

collect

607 ms

modules.61e17720cf639c3e96a7.js

modules.61e17720cf639c3e96a7.js

1142 ms

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

box-69edcc3187336f9b0a3fbb4c73be9fe6.html

1012 ms

1744016142293951

1744016142293951

374 ms

munchkin.js

munchkin.js

309 ms

collect

collect

905 ms

ipv

ipv

178 ms

u

u

750 ms

getMapping

getMapping

526 ms

visitWebPage

visitWebPage

793 ms

xdc.js

xdc.js

721 ms

377 ms

entitlementCheck

entitlementCheck

146 ms

visit-data

visit-data

509 ms

69 ms

ga-audiences

ga-audiences

36 ms

22 ms

insent

insent

864 ms

l.gif

l.gif

488 ms

settings.js

settings.js

115 ms

s.gif

s.gif

118 ms

e.gif

e.gif

118 ms

Accessibility Review

chorus.ai accessibility score

93

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-hidden="true"] elements contain focusable descendents

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

Best Practices

chorus.ai 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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

chorus.ai SEO score

86

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Chorus.ai 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 Chorus.ai 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

chorus.ai

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