Since around August 11, 2026, Google Search Console reports INP issues (longer than 200 ms, mobile) on our Intercom-hosted Help Center (help.libon.com).
Before that date, we had no INP issues at all. Today, 261 URLs are affected, with a group INP of 223–227 ms, and the number keeps growing.
Nothing changed on our side around that date: help.libon.com is a simple CNAME to eu.intercomhelpcenter.com, and we have no control over the Help Center's code, scripts or hosting. The sudden jump points to a change on Intercom's side (a Help Center release or infrastructure change around August 11).
What we measured:
- Real-user data (PageSpeed / Chrome UX Report): Core Web Vitals fail on INP (213 ms). Real-user TTFB is 1.4 s.
- HAR capture (Slow 4G): 21 JavaScript chunks from static.intercomassets.eu (~400 KB) must download before the page finishes loading at ~4.5 s, delaying fonts until 3.4 s. The Messenger then adds ~285 KB.
- Lighthouse: Total Blocking Time 440 ms, render-blocking requests (est. 1.3 s savings), more than half of the Intercom JavaScript unused on page load.
Since Google uses Core Web Vitals as a ranking signal, this directly affects the SEO of every customer using the Help Center, and customers have no way to fix it themselves.
Request:
- Investigate what changed in the Help Center around August 11, 2026 and its impact on INP.
- Reduce and defer the JavaScript loaded on Help Center pages.
- Provide a native option to defer the Messenger on Help Center pages.
Other customers: if you host your Help Center on Intercom, check Search Console → Core Web Vitals → Mobile. If you see the same jump in mid-August, please upvote and share your data here.
