Tools & Wizards About Us
ruby.com screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

ruby.com

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

Page Load Speed

1.6 sec in total

First Response

142 ms

Resources Loaded

1 sec

Page Rendered

459 ms

ruby.com screenshot

About Website

Click here to check amazing Ruby content for United States. Otherwise, check out these important facts you probably never knew about ruby.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 ruby.com

Key Findings

We analyzed Ruby.com page load time and found that the first response time was 142 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

ruby.com performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

24/100

25%

SI (Speed Index)

Value2.7 s

96/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.7 s

90/100

10%

Network Requests Diagram

ruby.com

142 ms

www.ruby.com

100 ms

www.ruby.com

221 ms

cqp5kgb.css

27 ms

style.min.css

37 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 92% of them (69 requests) were addressed to the original Ruby.com, 5% (4 requests) were made to Use.typekit.net and 1% (1 request) were made to P.typekit.net. The less responsive or slowest element that took the longest time to load (221 ms) belongs to the original domain Ruby.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 212.9 kB (30%)

Content Size

704.8 kB

After Optimization

491.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ruby.com main page is 704.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. 60% of websites need less resources to load. Images take 266.2 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 209.7 kB

  • Original 246.3 kB
  • After minification 238.8 kB
  • After compression 36.7 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 209.7 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-0%

Potential reduce by 5 B

  • Original 3.1 kB
  • After minification 3.1 kB
  • After compression 3.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.

CSS Optimization

-2%

Potential reduce by 3.2 kB

  • Original 189.1 kB
  • After minification 187.1 kB
  • After compression 185.9 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. Ruby.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 39 (60%)

Requests Now

65

After Optimization

26

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ruby.com

ruby.com

142 ms

www.ruby.com

www.ruby.com

100 ms

www.ruby.com

www.ruby.com

221 ms

cqp5kgb.css

cqp5kgb.css

27 ms

style.min.css

style.min.css

37 ms

theme.min.css

theme.min.css

30 ms

header-footer.min.css

header-footer.min.css

43 ms

frontend-lite.min.css

frontend-lite.min.css

38 ms

post-57249.css

post-57249.css

26 ms

jet-elements.css

jet-elements.css

60 ms

jet-elements-skin.css

jet-elements-skin.css

41 ms

elementor-icons.min.css

elementor-icons.min.css

47 ms

swiper.min.css

swiper.min.css

58 ms

frontend-lite.min.css

frontend-lite.min.css

57 ms

all.min.css

all.min.css

81 ms

v4-shims.min.css

v4-shims.min.css

79 ms

post-52957.css

post-52957.css

70 ms

post-57248.css

post-57248.css

73 ms

post-57301.css

post-57301.css

77 ms

post-58440.css

post-58440.css

92 ms

animate.min.css

animate.min.css

89 ms

ruby.css

ruby.css

93 ms

swiper-bundle.min.css

swiper-bundle.min.css

93 ms

forms.css

forms.css

99 ms

ruby-image.css

ruby-image.css

117 ms

nice-select.css

nice-select.css

113 ms

customer-stories.css

customer-stories.css

117 ms

widget-styles.css

widget-styles.css

127 ms

responsive.css

responsive.css

109 ms

general.min.css

general.min.css

111 ms

ecs-style.css

ecs-style.css

144 ms

fontawesome.min.css

fontawesome.min.css

145 ms

solid.min.css

solid.min.css

148 ms

brands.min.css

brands.min.css

144 ms

widget-nav-menu.min.css

widget-nav-menu.min.css

143 ms

widget-theme-elements.min.css

widget-theme-elements.min.css

172 ms

widget-posts.min.css

widget-posts.min.css

146 ms

post-60661.css

post-60661.css

174 ms

elementor.css

elementor.css

171 ms

p.css

p.css

45 ms

leadin.css

leadin.css

158 ms

ruby-frontend.css

ruby-frontend.css

163 ms

animations.min.css

animations.min.css

154 ms

lazyload.min.js

lazyload.min.js

147 ms

143 ms

logo-dark.svg

logo-dark.svg

60 ms

Ruby-App-Home-1-558x1200.png

Ruby-App-Home-1-558x1200.png

62 ms

VirtualReceptionist.svg

VirtualReceptionist.svg

79 ms

LiveChat.svg

LiveChat.svg

77 ms

TeamYouCanTrust.svg

TeamYouCanTrust.svg

74 ms

ChatCallConnection.svg

ChatCallConnection.svg

81 ms

Legal.svg

Legal.svg

80 ms

HomeServices.svg

HomeServices.svg

74 ms

BusinessServices.svg

BusinessServices.svg

81 ms

Healthcare.svg

Healthcare.svg

86 ms

Finance.svg

Finance.svg

83 ms

SmallBusinesses.svg

SmallBusinesses.svg

86 ms

clipboard-665x800.png

clipboard-665x800.png

88 ms

WinBackWorkDay-1.svg

WinBackWorkDay-1.svg

88 ms

IncreaseCustomerLoyalty-1.svg

IncreaseCustomerLoyalty-1.svg

92 ms

GrowBusiness-1.svg

GrowBusiness-1.svg

90 ms

Frame-32.png

Frame-32.png

89 ms

Group-2772.svg

Group-2772.svg

92 ms

Integrations_Lockup-copy-1.png

Integrations_Lockup-copy-1.png

93 ms

CC_AdobeStock_244031424-copy-1.webp

CC_AdobeStock_244031424-copy-1.webp

97 ms

RubyLogo_Nelson-1200x541.jpg

RubyLogo_Nelson-1200x541.jpg

96 ms

Google-Play-Badge-1-1.png

Google-Play-Badge-1-1.png

95 ms

App-Store-Badge-2.png

App-Store-Badge-2.png

97 ms

d

d

46 ms

d

d

77 ms

d

d

77 ms

d

d

95 ms

fa-solid-900.woff

fa-solid-900.woff

45 ms

fa-regular-400.woff

fa-regular-400.woff

190 ms

fa-brands-400.woff

fa-brands-400.woff

17 ms

Accessibility Review

ruby.com accessibility score

79

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

SEO Factors

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ruby.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 Ruby.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

ruby.com

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