Tools & Wizards About Us
customerly.io screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    59% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 90% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    82% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

customerly.io

Customerly | The Best Customer Service Software in the World

Page Load Speed

3.9 sec in total

First Response

50 ms

Resources Loaded

2.2 sec

Page Rendered

1.6 sec

customerly.io screenshot

About Website

Visit customerly.io now to see the best up-to-date Customerly content for India and also check out these interesting facts you probably never knew about customerly.io

Acquire, Support and Satisfy your SaaS Customers. Top Live Chat Software in the World. Discover why...

Visit customerly.io

Key Findings

We analyzed Customerly.io page load time and found that the first response time was 50 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

customerly.io performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

72/100

25%

SI (Speed Index)

Value16.7 s

0/100

10%

TBT (Total Blocking Time)

Value19,800 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value28.1 s

0/100

10%

Network Requests Diagram

customerly.io

50 ms

index.html

271 ms

gtm.js

574 ms

stub.js

677 ms

iubenda_cs.js

679 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 85% of them (35 requests) were addressed to the original Customerly.io, 10% (4 requests) were made to Cdn.iubenda.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (679 ms) relates to the external source Cdn.iubenda.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 199.2 kB (81%)

Content Size

247.2 kB

After Optimization

48.0 kB

  • HTML
  • JavaScript

In fact, the total size of Customerly.io main page is 247.2 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. 70% of websites need less resources to load. HTML takes 246.7 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 199.2 kB

  • Original 246.7 kB
  • After minification 246.3 kB
  • After compression 47.5 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 199.2 kB or 81% of the original size.

JavaScript Optimization

-8%

Potential reduce by 34 B

  • Original 447 B
  • After minification 447 B
  • After compression 413 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. This website has mostly compressed JavaScripts.

Requests Breakdown

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

Requests Now

39

After Optimization

23

  • AJAX
  • Images
  • JavaScript

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

Network Requests Diagram

customerly.io

customerly.io

50 ms

index.html

index.html

271 ms

gtm.js

gtm.js

574 ms

stub.js

stub.js

677 ms

iubenda_cs.js

iubenda_cs.js

679 ms

polyfill-f090a3ff160b37c2886b.js

polyfill-f090a3ff160b37c2886b.js

174 ms

component---src-pages-index-tsx-4e13b7f95743f7fdb014.js

component---src-pages-index-tsx-4e13b7f95743f7fdb014.js

453 ms

d6b9e9a829b4d5e7e6c436a621cee9bff66619a5-4bd805fd85e40265273f.js

d6b9e9a829b4d5e7e6c436a621cee9bff66619a5-4bd805fd85e40265273f.js

455 ms

c01d6696ea311b76f9df7d826e50bdc4a73c066f-ade9694859c8bec75550.js

c01d6696ea311b76f9df7d826e50bdc4a73c066f-ade9694859c8bec75550.js

456 ms

f542847b049a9365e669db376dda5d5339209a17-d4039fe102a6733f7c2d.js

f542847b049a9365e669db376dda5d5339209a17-d4039fe102a6733f7c2d.js

452 ms

c53ae2d756475db1979134de4bfafda60276027c-717270739bffe328aeba.js

c53ae2d756475db1979134de4bfafda60276027c-717270739bffe328aeba.js

452 ms

59b0a05ed5c4bcb42ecbcb4c33d43dadb285a940-e98bb6e61240912b965a.js

59b0a05ed5c4bcb42ecbcb4c33d43dadb285a940-e98bb6e61240912b965a.js

454 ms

55be9819945c8cb6b2df2016f0151505e811efb3-2f3f0b8b3d60da9ed6f1.js

55be9819945c8cb6b2df2016f0151505e811efb3-2f3f0b8b3d60da9ed6f1.js

535 ms

app-8b65df591829f4b5bc38.js

app-8b65df591829f4b5bc38.js

550 ms

framework-b2cbef5027fd1b2ebdbd.js

framework-b2cbef5027fd1b2ebdbd.js

550 ms

webpack-runtime-ed8bcd6c812962ebef87.js

webpack-runtime-ed8bcd6c812962ebef87.js

549 ms

wide-blue.svg

wide-blue.svg

549 ms

attention-seeker-arrow.svg

attention-seeker-arrow.svg

545 ms

square-white.svg

square-white.svg

624 ms

facebook.svg

facebook.svg

627 ms

linkedin.svg

linkedin.svg

624 ms

twitter.svg

twitter.svg

622 ms

youtube.svg

youtube.svg

625 ms

get-app-best-live-chat-2020.svg

get-app-best-live-chat-2020.svg

626 ms

g2crowd-best-live-chat-2019.svg

g2crowd-best-live-chat-2019.svg

658 ms

g2crowd-best-live-chat-2020.svg

g2crowd-best-live-chat-2020.svg

656 ms

g2crowd-best-live-chat-2021.svg

g2crowd-best-live-chat-2021.svg

660 ms

g2crowd-best-live-chat-spring-2021.svg

g2crowd-best-live-chat-spring-2021.svg

662 ms

optimize.js

optimize.js

323 ms

core-en.js

core-en.js

176 ms

app-data.json

app-data.json

215 ms

page-data.json

page-data.json

217 ms

tcf-v2-0.18.1.js

tcf-v2-0.18.1.js

136 ms

1271460761.json

1271460761.json

460 ms

1335423543.json

1335423543.json

458 ms

2346570661.json

2346570661.json

437 ms

2854521131.json

2854521131.json

330 ms

2940964782.json

2940964782.json

434 ms

3280999885.json

3280999885.json

457 ms

3414066678.json

3414066678.json

604 ms

4131050129.json

4131050129.json

462 ms

Accessibility Review

customerly.io accessibility score

96

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

Heading elements are not in a sequentially-descending order

Best Practices

customerly.io best practices score

92

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

Page has valid source maps

SEO Factors

customerly.io SEO score

93

Search Engine Optimization Advices

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 Customerly.io 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 Customerly.io 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

customerly.io

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