Original research

Chat Widget Performance 2026: Which Live Chat Slows Your Site Most

A chat widget is code from another company that runs on every page of your site. We measured how much it costs: how many kilobytes and network requests each popular chat tool adds to a page view.

For each tool we took up to 5 websites from our market-share scan that use it, opened their homepage in Chrome and counted only the requests that belong to the chat tool.

Facts checked November 16, 2026 Last changed November 16, 2026

Key findings

  1. 1

    The lightest chat widget we measured was Thulium, at a median of 5 KB over the network, because on most sites it loaded only a small starter script until the chat was needed. The heaviest was Genesys, at 1155.9 KB.

  2. 2

    Across the 21 widgets we measured, the median widget adds 393 KB and 15 network requests to a page before a visitor opens the chat.

  3. 3

    Genesys loads about 2.9 times as much data as the median chat widget on every page view.

  4. 4

    15 of the 21 widgets load more than 500 KB of JavaScript (unpacked) on every page view.

How much each chat widget downloads

Median bytes transferred by the widget's own requests on real websites that load it. Lighter is better.

Chat toolTransferredRequestsJavaScriptSites measured
Thulium5 KB64 KB5
Shopify Inbox78 KB9274 KB5
LiveAgent82 KB1582 KB5
Zoho SalesIQ89 KB6202 KB5
Crisp110 KB7307 KB5
Smartsupp118 KB7309 KB5
Re:amaze216 KB5793 KB5
tawk.to244 KB16587 KB5
Intercom250 KB6940 KB5
LiveChat359 KB221,140 KB5
Sprinklr393 KB151,319 KB5
Trengo414 KB41,538 KB5
Zendesk422 KB151,303 KB5
Chatwoot494 KB351,016 KB5
Tidio522 KB81,044 KB5
Gorgias529 KB261,155 KB5
Ada533 KB181,809 KB5
Freshchat764 KB162,709 KB5
Userlike772 KB112,387 KB5
Salesforce780 KB192,557 KB5
Genesys1,156 KB344,801 KB5
Questions

Frequently asked

Which live chat widget is the lightest?

In our test, Thulium: a median of 5 KB and 6 requests per page view.

Which live chat widget is the heaviest?

Genesys, with a median of 1155.9 KB over the network and 4801.4 KB of JavaScript once unpacked.

Does a chat widget slow down my website?

It adds downloads and JavaScript to every page. How much it matters depends on the widget and on whether it loads after the rest of the page. Most widgets load asynchronously, so they cost data and processor time more than they delay the first view of the page.

How was this measured?

In headless Chrome, on real websites that use each tool, counting only the requests to the chat vendor's own hosts. The figures are medians over 3 to 5 sites per tool.

Still have a question?

How we measured

  • Sites: for each chat tool with at least 25 sites in our October 2026 market-share scan, the best-ranked sites that load it as their only chat tool (no adult or gambling sites, no login pages).
  • Browser: headless Chrome with a desktop window (1366 × 900), an empty profile and the cache turned off, so every file is downloaded.
  • We loaded each homepage, waited until the network was quiet (at most 45 seconds) and then 8 more seconds, and recorded every request through the Chrome DevTools Protocol.
  • A request counts for the widget when its address belongs to the chat vendor: its script, API, file and CDN hosts. The rest of the page is not counted.
  • Transfer is the compressed size over the network. Script size is the JavaScript after decompression, which is what the browser has to parse and run.
  • Each figure is the median over the sites measured for that tool (3 to 5 sites).

What this does not show

  • A lab measurement, not real-user data: one headless Chrome on a Raspberry Pi in Hungary, on a home internet connection.
  • Each figure is the median of 3 to 5 sites that use the tool, so a site's own widget settings (AI bot, greeting, branding) move it.
  • Only what loads with the page is counted, before anyone opens the chat. Opening the chat window loads more.
  • Widgets that wait for cookie consent were skipped, because they load nothing until a visitor accepts.
  • Some widgets load their full chat window only while the team is online. We measured on a weekday in the evening, Central European time, so for those tools the figures are closer to the after-hours cost.
  • Network conditions and the vendor's CDN on the day change the numbers from run to run.

Sources

  1. yaplet.com · The market-share scan the sample sites come from
  2. chromedevtools.github.io · Chrome DevTools Protocol: network events used to count requests and bytes

All sources re-checked on November 16, 2026. We check them every week and update this page when something changes.

Let Yaplet answer your customers

Live chat, an AI agent that answers from your own website, and one inbox for every channel. Free plan, no card.

  • Free forever
  • No card needed

Not ready to sign up? Test the AI on your own website first →