Menu

1 / 6

The progress bar that made typing lag: debugging a 331 ms INP in a React game

DEV Community: css·Alex Xiao·2 days ago
#ihUYVVaY
#devtocss#devto#dev#full#transition
Reading 0:00
15s threshold

TL;DR: A friend told me that typing felt laggy in Museek , my free multiplayer music quiz. I was sure the culprit was my autocomplete filtering. The profiler disagreed. The real problem was a progress bar animating its width once per second, plus a full-screen backdrop-filter: blur() . Switching the bar to transform cut background Rendering time by roughly 7x and took keystrokes out of the slow interactions list.

The bug report

Museek is a browser-based "blind test": up to 12 players each bring a Spotify, Deezer or Apple Music playlist, a song snippet plays, and everyone types the artist and title as fast as they can. It's built with Next.js 16, React 19 and Tailwind 4, with a Node/Socket.io backend.

A friend playing a game sent me this: "There's a delay between what I type and what shows up in the answer field."

In a game where you're racing a 30-second timer, that's not a cosmetic issue.

My first guess (and why it was wrong)

Each answer field has an autocomplete.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.