Solving the "Chat Plugin Bloat" problem on WordPress

A huge constraint we set was that Furie could not touch the host WordPress database. Too many chat plugins destroy PageSpeed scores by writing logs to wp_options or loading heavy assets.

We architected the plugin as a lightweight async wrapper. All the socket connections (Pusher) and state management happens on our external API layer. Even the chat history is stored remotely.

If you are a WP dev who avoids plugins for performance reasons, I'd love for you to audit our implementation and let me know if we hit the mark on performance.