Widget performance

How heavy is the Drift chat widget?

DebugBear measured it at 464KB. Here is what that means for your page, how it compares, and how to check your own installation.

Last checked 1 September 2026

Widget size/Drift

The short answer

How big is the Drift chat widget?

DebugBear measured the Drift chat widget at 464KB of download. That places it 3 of 7 among the mainstream widgets they tested, which ranged from 79KB to 749KB. For scale, that is roughly 12 times the 39KB TGLiveChat widget.

What Drift is

Conversational marketing chat aimed at B2B sales teams.

This product is being wound down

Salesloft took the Drift application offline on 5 September 2025 after an OAuth breach affecting more than 700 organisations, and Clari and Salesloft announced the sunset on 6 March 2026. drift.com now redirects to Salesloft Chat Agents.

How it compares

Measured download size, heaviest first
WidgetDownloadJS execution
Tawk.to749 KBNot published
Zendesk Chat533 KB991 ms
Drift464 KBNot published
LiveChat385 KBNot published
Intercom301 KBNot published
Crisp155 KBNot published
LiveAgent79 KBNot published
TGLiveChat~39 KBnot in the test

Competitor figures are DebugBear's, updated 10 November 2025. The TGLiveChat figure is our own measurement, with the method on the widget size page.

Where Drift is the better choice

Nothing any more. It is being wound down, which is the reason people are reading this at all.

Where we are different

It still exists.

Worth being plain about the trade: TGLiveChat is not a helpdesk. There is no ticketing, no SLA engine, no assignment rules and no reporting suite. If you were using those, a lighter widget is not a saving, it is a downgrade. If you were not, you were carrying the weight of a product you never opened.

Measuring your own installation

Every published figure, including ours, is somebody else's configuration. Open DevTools, go to the Network tab, filter by the vendor domain and hard reload. Read the transfer column, not the resource size column. Then look at the Performance tab for scripting time. Two minutes, and it is the only number that describes your site.

The bottom line

Drift downloads 464KB. Whether that is a problem depends entirely on what you get for it. A heavy widget attached to a helpdesk your team lives in is a fair trade. A heavy widget attached to a chat bubble nobody answers is not.

Defer it before you replace it. That is the cheaper fix and it usually works.

Frequently asked questions

How big is the Drift chat widget?
DebugBear measured it at 464KB of download. That is number 3 of 7 in their test of mainstream chat widgets.
Does the Drift widget hurt Core Web Vitals?
Indirectly. Widget weight is not itself a ranking factor, but the download and the JavaScript execution both push Largest Contentful Paint and Total Blocking Time in the wrong direction, and those are. The effect is far larger on a mid range phone over mobile data than on a desktop. Load it deferred rather than on page load and most of the cost goes away.
How do I make Drift load faster?
Defer it. Load the widget on first scroll, or behind a placeholder button that swaps for the real thing on click, rather than firing it on page load. That works whatever the vendor does and it is the single biggest improvement available. Removing the widget entirely is rarely the right answer if the team is actually using it.
How do I measure this myself?
Open DevTools, go to the Network tab, filter by the Drift domain, and hard reload the page. Read the transfer column rather than resource size, because transfer is what actually crossed the wire after compression. Then check the Performance tab for scripting time. Your number will differ from any published figure, because your configuration does.
Is there a lighter alternative to Drift?
The lightest widget in DebugBear's test was LiveAgent at 79KB. The TGLiveChat widget is about 39KB gzipped across 3 requests, though it is a deliberately narrower product: chat that routes to Telegram, with no ticketing and no helpdesk. Whether lighter is better depends entirely on whether you were using the rest.
What does Drift do well?
Nothing any more. It is being wound down, which is the reason people are reading this at all.

Sources and references

Measurements of Drift belong to DebugBear and are cited for comparison. We measure our own widget and nobody else's.

Related guides