I Accidentally Built the Fastest Chat Widget on the Internet

Most products start with a plan.

Mine started with an obsession.

I was exploring the architecture of decentralized messaging—systems where privacy, security, and speed aren't just "features," they are the base layer.

When I looked back at the traditional web, the contrast was shocking. I realized how bloated our tools have become.

And I asked myself: Why can't website chat be as lean and private as a decentralized protocol?

So I decided to build one.

And somewhere along the way, I accidentally built the fastest chat widget on the internet.

Not because I set out to "beat" anybody.

Not because I wanted performance trophies.

But because I was frustrated with one simple thing:

Why are modern chat widgets so bloated?

• 100 KB
• 200 KB
• 300 KB
• multiple frameworks
• tracking scripts
• analytics
• third-party dependencies
• long blocking times
• slow initialization

Chat widgets are notorious for tanking Lighthouse scores.

So I started removing things.

And removing more things.

And then more.

And suddenly… the entire widget was 3 KB gzipped.

Just 3 KB gzipped.

Smaller than most logos.

The moment I realized something weird happened

When I first tested the performance, I assumed I had made a mistake:

• 0–5 ms total blocking time
• 3 KB network download
• instant load on mobile
• 3G-friendly
• edge-native latency: 10–30 ms

I re-ran the test.

Same result.

I ran a comparison.

Then things got interesting.

I didn't expect that.

I originally wanted "fast."

This was… something else.

Why it ended up faster than everything else

It wasn't magic.

Just constraints.

1. No frameworks

No React.

No Vue.

No jQuery.

No tracking scripts.

No UI libraries.

Just pure JS, optimized manually.

2. Edge-native by default

Instead of centralized servers, everything runs on Cloudflare's edge with 300+ global data centers.

Visitors always hit the closest location.

Distance = latency.

Shorter = faster.

3. Zero dependencies = zero bloat

Everything is self-contained.

Nothing is imported.

Nothing is lazy-loaded later.

There's nothing to break.

I even went as far as removing GA4 from my own site. If I'm fighting bloat in the widget, I have to fight it in the analytics, too.

4. Minimal UI logic

I asked myself a question:

"What's the least amount of code needed to send and receive a message instantly?"

Turned out to be way less than expected.

5. Optimized for old devices

If it works on a 7-year-old Android on a congested 3G network…

it works anywhere.

The inspiration came from an unlikely place

I was exploring new, decentralized messaging protocols—systems built to be instant, private, and incredibly lean. It was a revelation.

Then, I looked back at the "modern" web.

I realized we’ve accepted a massive "Performance Tax." Why does a standard website chat widget need 200 KB of code when modern protocols can handle global messaging with a fraction of that?

I decided to apply that "Protocol-First" mindset to a standard web tool. I stripped away everything that wasn't essential. No frameworks. No legacy bloat. Just pure, optimized JS running on 300+ global edge locations.

That's when it hit me: This wasn't just a side project. This was a new category. Most live chat is bloated by design. This is lightweight live chat by choice.

Live chat is bloated. This is lightweight live chat.

The old way:

• heavy
• slow
• dashboard-driven
• tracking-heavy
• complicated

The new way:

• instant
• 3 KB
• edge-native
• privacy-first
• WhatsApp-like replies
• no dashboards needed

This wasn't intentional.

But sometimes the best ideas happen by accident.

So yes… I accidentally built the fastest chat widget on the internet.

And now it's live.

Under 3 KB.

Tens-of-milliseconds delivery in many regions.

Zero tracking.

Zero cookies.

Unlimited messages.

Try it yourself.