Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

hearingchats.com

Ruby: #1 Virtual Receptionist & Live Chat Solution for Small Businesses

Page Load Speed

4.2 sec in total

First Response

162 ms

Resources Loaded

3.5 sec

Page Rendered

531 ms

hearingchats.com screenshot

About Website

Welcome to hearingchats.com homepage info - get ready to check Hearing Chat S best content right away, or after learning these important things about hearingchats.com

14,000+ small businesses trust the virtual receptionists at Ruby to create meaningful connections over the phone and through live chat, 24/7.

Visit hearingchats.com

Key Findings

We analyzed Hearingchats.com page load time and found that the first response time was 162 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

hearingchats.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value25.5 s

0/100

25%

SI (Speed Index)

Value25.4 s

0/100

10%

TBT (Total Blocking Time)

Value47,860 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value63.6 s

0/100

10%

Network Requests Diagram

hearingchats.com

162 ms

www.ruby.com

269 ms

p.css

112 ms

YyhlLmNvbmNhdGVtb2ppKTplLndwZW1vamkmJmUudHdlbW9qaSYmKGMoZS50d2Vtb2ppKSxjKGUud3BlbW9qaSkpKX0od2luZG93LGRvY3VtZW50LHdpbmRvdy5fd3BlbW9qaVNldHRpbmdzKTsK

1 ms

cqp5kgb.css

277 ms

Our browser made a total of 180 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Hearingchats.com, 41% (74 requests) were made to Ruby.com and 9% (17 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (899 ms) relates to the external source In.hotjar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 701 B (0%)

Content Size

322.8 kB

After Optimization

322.1 kB

In fact, the total size of Hearingchats.com main page is 322.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. 85% 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. Javascripts take 271.0 kB which makes up the majority of the site volume.

HTML Optimization

-0%

Potential reduce by -8 B

  • Original 0 B

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 web page is already compressed.

Image Optimization

-1%

Potential reduce by 384 B

  • Original 51.9 kB
  • After minification 51.5 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. Hearing Chat S images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 325 B

  • Original 271.0 kB
  • After minification 271.0 kB
  • After compression 270.7 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 92 (65%)

Requests Now

142

After Optimization

50

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

Accessibility Review

hearingchats.com accessibility score

77

Accessibility Issues

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

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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 IDs are not unique

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

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

hearingchats.com SEO score

79

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

High

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hearingchats.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Hearingchats.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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