Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

chorus.ai

Conversation Intelligence for Sales | ZoomInfo + Chorus

Page Load Speed

1.5 sec in total

First Response

10 ms

Resources Loaded

969 ms

Page Rendered

493 ms

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 10 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

chorus.ai performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value20.8 s

0/100

10%

TBT (Total Blocking Time)

Value9,950 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value34.7 s

0/100

10%

Network Requests Diagram

chorus.ai

10 ms

chorus

399 ms

autopilot_sdk.js

45 ms

gtm.js

71 ms

07d46f61fbe6a6bf.css

57 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Chorus.ai, 57% (50 requests) were made to Zoominfo.com and 38% (33 requests) were made to Content.zoominfo.com. The less responsive or slowest element that took the longest time to load (399 ms) relates to the external source Zoominfo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 114.8 kB (39%)

Content Size

293.8 kB

After Optimization

179.1 kB

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

HTML Optimization

-82%

Potential reduce by 114.8 kB

  • Original 139.7 kB
  • After minification 138.9 kB
  • After compression 24.9 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 114.8 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 23.2 kB
  • After minification 23.2 kB
  • After compression 23.2 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 56 (67%)

Requests Now

84

After Optimization

28

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 25 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

chorus.ai accessibility score

76

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

92

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

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: