Tools & Wizards About Us
blog.intercom.io screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    31% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 85% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    82% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

blog.intercom.io

The Intercom Blog - Articles on Customer Support, Product & more

Page Load Speed

4.7 sec in total

First Response

236 ms

Resources Loaded

3.1 sec

Page Rendered

1.3 sec

blog.intercom.io screenshot

About Website

Welcome to blog.intercom.io homepage info - get ready to check Blog Intercom best content for United States right away, or after learning these important things about blog.intercom.io

The Intercom Blog is where our team shares insights and lessons about customer support and customer service, building product, and more.

Visit blog.intercom.io

Key Findings

We analyzed Blog.intercom.io page load time and found that the first response time was 236 ms and then it took 4.5 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

blog.intercom.io performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value11.3 s

5/100

10%

TBT (Total Blocking Time)

Value22,680 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.156

74/100

15%

TTI (Time to Interactive)

Value32.9 s

0/100

10%

Network Requests Diagram

blog.intercom.io

236 ms

blog.intercom.io

825 ms

main-20-08-2015.css

607 ms

modernizr.js

296 ms

jquery.js

603 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 22% of them (18 requests) were addressed to the original Blog.intercom.io, 20% (16 requests) were made to and 12% (10 requests) were made to Blog.intercomassets.com. The less responsive or slowest element that took the longest time to load (825 ms) belongs to the original domain Blog.intercom.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 990.2 kB (12%)

Content Size

8.0 MB

After Optimization

7.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blog.intercom.io main page is 8.0 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Images take 7.2 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 87.2 kB

  • Original 103.4 kB
  • After minification 98.1 kB
  • After compression 16.2 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 87.2 kB or 84% of the original size.

Image Optimization

-8%

Potential reduce by 542.4 kB

  • Original 7.2 MB
  • After minification 6.7 MB

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. Blog Intercom images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 229.3 kB

  • Original 398.1 kB
  • After minification 391.4 kB
  • After compression 168.8 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 229.3 kB or 58% of the original size.

CSS Optimization

-42%

Potential reduce by 131.4 kB

  • Original 312.3 kB
  • After minification 312.1 kB
  • After compression 180.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. Blog.intercom.io needs all CSS files to be minified and compressed as it can save up to 131.4 kB or 42% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (46%)

Requests Now

59

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

blog.intercom.io

blog.intercom.io

236 ms

blog.intercom.io

blog.intercom.io

825 ms

main-20-08-2015.css

main-20-08-2015.css

607 ms

modernizr.js

modernizr.js

296 ms

jquery.js

jquery.js

603 ms

jquery-migrate.min.js

jquery-migrate.min.js

300 ms

pippity.js

pippity.js

300 ms

187824445.js

187824445.js

215 ms

1536404.js

1536404.js

74 ms

wp-embed.min.js

wp-embed.min.js

298 ms

site.js

site.js

488 ms

widgets.js

widgets.js

47 ms

oct.js

oct.js

48 ms

gtm-e6e782794c8a4e47ac40ebae1ad3ce952d4269c62e68eca2f6a8c31410ee1d1e.js

gtm-e6e782794c8a4e47ac40ebae1ad3ce952d4269c62e68eca2f6a8c31410ee1d1e.js

3 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

293 ms

fbevents.js

fbevents.js

145 ms

hero_RileyNewman.png

hero_RileyNewman.png

595 ms

adamrisman

adamrisman

482 ms

logo.svg

logo.svg

235 ms

sprite-10-10-2015a.png

sprite-10-10-2015a.png

429 ms

book3-banner.png

book3-banner.png

471 ms

hire-banner-1a.jpg

hire-banner-1a.jpg

527 ms

hire-banner-2.png

hire-banner-2.png

470 ms

podcast-banner-1a.jpg

podcast-banner-1a.jpg

750 ms

podcast-banner-2a.jpg

podcast-banner-2a.jpg

708 ms

smcbride

smcbride

469 ms

destraynor

destraynor

470 ms

geoffreykeating

geoffreykeating

471 ms

emcguane

emcguane

472 ms

bgbary

bgbary

498 ms

thoughtwax

thoughtwax

498 ms

zmiro

zmiro

499 ms

RICE_hero_1968.png

RICE_hero_1968.png

580 ms

Blind-Men-Elephant-hero.png

Blind-Men-Elephant-hero.png

580 ms

rolls_royce_1248_2.png

rolls_royce_1248_2.png

651 ms

ship_hero_1968.png

ship_hero_1968.png

523 ms

Used-Car-Sales.png

Used-Car-Sales.png

658 ms

zuckerberg_1968.png

zuckerberg_1968.png

695 ms

hero.png

hero.png

625 ms

hero_19682.png

hero_19682.png

604 ms

hero_19681.png

hero_19681.png

603 ms

mixpanel-2.2.min.js

mixpanel-2.2.min.js

465 ms

count.js

count.js

504 ms

marketing.gif

marketing.gif

456 ms

gtm.js

gtm.js

540 ms

adsct

adsct

516 ms

adsct

adsct

506 ms

admin-ajax.php

admin-ajax.php

796 ms

pageviews

pageviews

523 ms

guThPHptPhzaevwHohE+mm6f4CRh3SvA=

guThPHptPhzaevwHohE+mm6f4CRh3SvA=

52 ms

wCOeNK+A==

wCOeNK+A==

52 ms

RlxcQvg8iTp8K5t6xEyeyP4oumXUjYcuJXbcnkh00y+BPxqkJD6GpB6xkWsUeweKDlkJcuAQWcBM7ofd9a4UrBB3guzpOn5tOhjedvADrhk+nmKX4BbC1LBA==

RlxcQvg8iTp8K5t6xEyeyP4oumXUjYcuJXbcnkh00y+BPxqkJD6GpB6xkWsUeweKDlkJcuAQWcBM7ofd9a4UrBB3guzpOn5tOhjedvADrhk+nmKX4BbC1LBA==

51 ms

RlxcQvg8iTp8K5t6xEyeyP4oumXUjYcuJXbcnkh00y+BPxqkJD6GpB6xkWsUeweKDlkJcuAQWcBM7ofd9a4UrBB3guzpOn5tOhjedvADrhk+nmKX4BKS1K9A==

RlxcQvg8iTp8K5t6xEyeyP4oumXUjYcuJXbcnkh00y+BPxqkJD6GpB6xkWsUeweKDlkJcuAQWcBM7ofd9a4UrBB3guzpOn5tOhjedvADrhk+nmKX4BKS1K9A==

51 ms

RlxcQvg8iTp8K5t6xEyeyP4oumXUjYcuJXbcnkh00y+BPxqkJD6GpB6xkWsUeweKDlkJcuAQWcBM7ofd9a4UrBB3guzpOn5tOhjedvADrhk+nmKX4BKS1K9A==

RlxcQvg8iTp8K5t6xEyeyP4oumXUjYcuJXbcnkh00y+BPxqkJD6GpB6xkWsUeweKDlkJcuAQWcBM7ofd9a4UrBB3guzpOn5tOhjedvADrhk+nmKX4BKS1K9A==

51 ms

wCOeNK+A==

wCOeNK+A==

51 ms

gbl2f4989A8Yd2ilGwBu0R6JZWAHiyhRUUTNPOADDe5gj75DVNATQKZKmDDH8KUitFSV1yepv7LCMXzi4+k0FYEZ5jetNdphDBsySD3MqcgnR1AhmAYZ5R6FI9CvX+rIFScLI7TTvECQnubCeU3lyW8NFnmJjlthhuHedPOmm3O6OZVLPix35Lm4mb7g4uYSZmmahfTM0ucVEz8PIk8eC+feshIls9+Lz5p2IWHLiV+1JZMfNsngT8SLCg2hqwWtZ1jEHsHigZZDXroEFHASOKP3fWuFKwUf4Lk4Tx6bT4c2nr8B6IRPppun+AkYd0rw

gbl2f4989A8Yd2ilGwBu0R6JZWAHiyhRUUTNPOADDe5gj75DVNATQKZKmDDH8KUitFSV1yepv7LCMXzi4+k0FYEZ5jetNdphDBsySD3MqcgnR1AhmAYZ5R6FI9CvX+rIFScLI7TTvECQnubCeU3lyW8NFnmJjlthhuHedPOmm3O6OZVLPix35Lm4mb7g4uYSZmmahfTM0ucVEz8PIk8eC+feshIls9+Lz5p2IWHLiV+1JZMfNsngT8SLCg2hqwWtZ1jEHsHigZZDXroEFHASOKP3fWuFKwUf4Lk4Tx6bT4c2nr8B6IRPppun+AkYd0rw

51 ms

h4Pk1FYIb5TWuNdhjDhgxSD3Mq8skRVAimQUa5R+EI9NuXOnLFycII7TQvEKTnuXBeU3nyW4NFXqLjVphhuHfdvOvmnG5O5ZIPyx15Lm6mL7i4uYRZmmYhPbP0ZcXEL4PIk6fCubesRMnsj+KLpl1I2HLiV23J5IdNMvgT8apCQ+hqQesZFrFHsHig5ZCXLgEFnATO6H3fWuFKwQd4Ls6Tp+bToY3nbwA64ZPp5il+AWwtSwQ=

h4Pk1FYIb5TWuNdhjDhgxSD3Mq8skRVAimQUa5R+EI9NuXOnLFycII7TQvEKTnuXBeU3nyW4NFXqLjVphhuHfdvOvmnG5O5ZIPyx15Lm6mL7i4uYRZmmYhPbP0ZcXEL4PIk6fCubesRMnsj+KLpl1I2HLiV23J5IdNMvgT8apCQ+hqQesZFrFHsHig5ZCXLgEFnATO6H3fWuFKwQd4Ls6Tp+bToY3nbwA64ZPp5il+AWwtSwQ=

51 ms

Sxg=

Sxg=

51 ms

AJKsUr8

AJKsUr8

51 ms

k6VPz8dDG8zcAnfDpePMUvwBsMUsE

k6VPz8dDG8zcAnfDpePMUvwBsMUsE

51 ms

wCOftK+A==

wCOftK+A==

51 ms

v0sY

v0sY

50 ms

AJKsUr8

AJKsUr8

51 ms

HQxvM3AJ3w6XjzFL8AbDFLBA==

HQxvM3AJ3w6XjzFL8AbDFLBA==

50 ms

AI5+0r4

AI5+0r4

50 ms

__ptq.gif

__ptq.gif

467 ms

369 ms

59 ms

60 ms

analytics.js

analytics.js

37 ms

roundtrip.js

roundtrip.js

336 ms

insight.min.js

insight.min.js

79 ms

track.js

track.js

33 ms

track.gif

track.gif

22 ms

collect

collect

22 ms

collect

collect

54 ms

ga-audiences

ga-audiences

38 ms

inside-intercom-subscribers

inside-intercom-subscribers

42 ms

get_f_asset.php

get_f_asset.php

119 ms

get_f_asset.php

get_f_asset.php

114 ms

GMGXL2NANZHMTOS5B445BF.js

GMGXL2NANZHMTOS5B445BF.js

390 ms

Accessibility Review

blog.intercom.io accessibility score

94

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-hidden="true"] elements contain focusable descendents

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.

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

Links do not have a discernible name

Best Practices

blog.intercom.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

blog.intercom.io SEO score

91

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

blog.intercom.io

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