1.8 sec in total
11 ms
1.3 sec
476 ms
Welcome to customer.io homepage info - get ready to check Customer best content for United States right away, or after learning these important things about customer.io
Leverage marketing automation and customer data in a single Customer Engagement Platform to personalize your customer communications and drive more engagement. Start engaging your customers like never...
Visit customer.ioWe analyzed Customer.io page load time and found that the first response time was 11 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
customer.io performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value3.9 s
53/100
25%
Value3.9 s
82/100
10%
Value630 ms
47/100
30%
Value0.045
99/100
15%
Value8.4 s
38/100
10%
11 ms
29 ms
19 ms
206 ms
277 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 23% of them (10 requests) were addressed to the original Customer.io, 20% (9 requests) were made to Use.typekit.net and 7% (3 requests) were made to Pixel.prfct.co. The less responsive or slowest element that took the longest time to load (463 ms) relates to the external source Use.typekit.net.
Page size can be reduced by 233.2 kB (50%)
470.8 kB
237.6 kB
In fact, the total size of Customer.io main page is 470.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. 50% of websites need less resources to load. Javascripts take 266.8 kB which makes up the majority of the site volume.
Potential reduce by 13.6 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 13.6 kB or 72% of the original size.
Potential reduce by 19.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. Obviously, Customer needs image optimization as it can save up to 19.5 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 157.1 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 157.1 kB or 59% of the original size.
Potential reduce by 43.0 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. Customer.io needs all CSS files to be minified and compressed as it can save up to 43.0 kB or 84% of the original size.
Number of requests can be reduced by 23 (72%)
32
9
The browser has sent 32 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Customer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
customer.io
11 ms
customer.io
29 ms
project-27ed602b.css
19 ms
bgn0vji.js
206 ms
60166117.js
277 ms
project-72e40992.js
40 ms
blog-d9918121.js
12 ms
ionicons.min.css
36 ms
6b
142 ms
logo-mono-white-680fd562.svg
53 ms
hipster-ami-avatar-ac25a050.jpg
5 ms
pratik-avatar-701d5383.jpg
6 ms
selected-customer-io-customers-2015-08-8e5cbc52.png
9 ms
p.gif
290 ms
customerio-icons-0a7c490f.woff
42 ms
hld56pMAXgiN8Txmasv2eJjuDHRNsjNwnasgMFaGmyMffw7EggMFeMI6MK6f5Mb.eot
72 ms
n56uGOocrVvTZEH_FcZ8GKWdypYJa7WbuDRyyLTaTljffwhEggMFeMI6MK6f5MS.eot
74 ms
NHBrJ-CupsgmpWsU7oq5MVCBgek1X1LybVNRjHOi9xMffw0EggMFeMI6MK6f5Mt.eot
187 ms
S8nEaOlSpCPOD4s0PqWh6m0swsS7_2GraByOCqavZIjffwEEggMFeMI6MK6f5gI.eot
195 ms
qzjfqUIFzXgRzUw-XTSC65CyCTlZBt3hTa9y59qBi5XffVeuggMFeMI6MK6f5Mw.eot
215 ms
z1xeocwQ97LhxmaQdgvXF4FZsCHbk4k3fs5GukLaUaXffwkEggMFeMI6MK6f5Mj.eot
220 ms
k9bGdG1WU1w9tdDc-JKnOvfkbvOgB5GOCagRhTVElgGffFEMggMFeMI6MK6f5Mb.eot
463 ms
ionicons.ttf
69 ms
analytics.min.js
235 ms
track.js
49 ms
analytics.js
83 ms
w.js
142 ms
track.js
50 ms
521617fc1077880ed1000090.js
73 ms
track.gif
14 ms
linkid.js
48 ms
tagjs
8 ms
collect
13 ms
222 ms
adsct
166 ms
Pug
133 ms
cb
102 ms
ga-audiences
95 ms
pixel
34 ms
cb
9 ms
tap.php
41 ms
sd
30 ms
ncm
5 ms
cb
3 ms
customer.io accessibility score
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
Links do not have a discernible name
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
customer.io best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
customer.io SEO score
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Customer.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 Customer.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.
customer.io
Open Graph data is detected on the main page of Customer. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: