March 2026 Update: Performance Improvements and WebSocket Stability Fixes

March 2026 brings a focused round of performance improvements and stability fixes across ChatNoRegister. There are no major new features in this update -- this is a deliberate maintenance and optimization release designed to make everything that already exists work better, faster, and more reliably. The goal was to address specific issues that had emerged since the WebSocket launch and to reduce page load times across the site ahead of the next feature cycle.

WebSocket Connection Stability Improvements

Since launching the real-time WebSocket system in an earlier update, we had been monitoring connection behavior across different user segments. The system worked well for most users on stable connections, but a small but meaningful percentage of users -- particularly those on mobile networks, users behind certain corporate firewalls, and users with ISPs that have aggressive connection timeout policies -- were experiencing reconnection delays that were longer than acceptable.

The root cause was a combination of factors: the initial reconnect logic was not aggressive enough in its early attempts, and the AJAX fallback was resuming from the beginning of the message log rather than from the last known position, causing unnecessary re-rendering of old messages on every reconnection event.

This update addresses both issues:

• Faster reconnect logic -- the client now attempts reconnection with an exponential back-off pattern starting at 1 second, doubling on each attempt (1s, 2s, 4s, 8s) and capping at 15 seconds. In practice this means most reconnections after a brief network blip complete within 1-4 seconds rather than the previous 5-10 seconds.
• Improved silent fallback -- when the AJAX fallback activates, it now resumes from the last known message position rather than reloading the full message log. This eliminates the flash of old messages that some users were seeing during reconnection events.
• PM2 health monitoring upgrade -- the WebSocket server process is now configured to restart automatically within 3 seconds of a crash, rather than waiting for the next PM2 health check cycle (which could take up to 30 seconds). This reduces the window during which users might experience degraded service after an unexpected server process exit.

Page Load Time Improvements

The headline numbers are a 47% reduction in homepage load time (1.7s to 0.9s) and a 47% reduction in article page load time (1.5s to 0.8s). These are approximate figures measured under controlled conditions, and real-world performance will vary based on your connection speed, device, and whether assets are already cached. The improvements are most pronounced on first visit when nothing is cached.

The main changes driving these improvements were: converting several hero images from PNG to WebP format with appropriate srcset attributes for different screen sizes, adding explicit width and height attributes to all images to prevent layout shift, deferring the loading of the chat widget script on informational pages where it is not immediately needed, and reducing the number of blocking CSS rules by consolidating redundant style declarations.

Bug Fixes in This Update

• Sitemap fix -- the dynamic sitemap was not correctly including all published articles due to a pagination bug in the query. All articles are now correctly indexed. The robots.txt file has been updated to point to the PHP sitemap endpoint rather than the static XML file, ensuring Google always gets the most current version.
• CSS on category pages -- users browsing category pages like /cat/tips and /cat/blog were seeing broken styles due to relative CSS path resolution failing from nested URL structures. All stylesheets on category pages are now referenced with absolute paths.
• Powers Store help links -- the help badge that opens a detailed explanation of each power was only working correctly for the Prism power. All 22 powers now have functioning help links that open the correct guide page.
• Article page table overflow -- tables in article content were overflowing their containers on screens narrower than 600px, causing horizontal page scroll. Tables are now wrapped in a responsive container that enables horizontal scroll within the table element without affecting the rest of the page layout.
• Private message notification count -- in some scenarios, the unread message count badge on the private message icon was not resetting to zero after opening the conversation. This has been corrected.
• AI personality timing edge case -- a race condition in the AI personality activity detection logic was occasionally causing AI messages to fire immediately after a real user message rather than waiting the appropriate cooldown period. The timing logic has been tightened.

Infrastructure Updates

In addition to the user-facing fixes, several infrastructure improvements were made in this update. The database query for loading chat history on room entry has been optimized with an additional index that reduces the query time by approximately 40% on rooms with large message histories. The Node.js WebSocket server memory allocation has been increased to handle higher concurrent connection counts without degradation. Server-side caching headers have been updated for static assets to improve CDN hit rates, reducing origin server requests for repeat visitors.

What Is Coming Next

With the stability work from this update completed, the development focus shifts back to new features. The next major update will include:

• Additional Powers -- new name effects, avatar animations, and an initial seasonal category planned for late spring 2026
• User profile pages -- a basic public profile showing earned powers, join date, and activity highlights
• Room themes -- the ability for room owners to set a custom color scheme and background for their room
• Improved new user onboarding -- clearer first-time prompts inside the chat room for users who have just arrived for the first time

All updates in this release are live now. If you are seeing anything that does not look right, clearing your browser cache should resolve any stale asset issues from the previous version. Thank you for your patience and continued use of ChatNoRegister.