<![CDATA[The Soundify Lab]]>https://audio-dev.hashnode.devhttps://cdn.hashnode.com/res/hashnode/image/upload/v1593680282896/kNC7E8IR4.pngThe Soundify Labhttps://audio-dev.hashnode.devRSS for NodeMon, 21 Sep 2026 04:08:09 GMT60<![CDATA[Why I stopped obsessing over PageSpeed scores (and started focusing on actual Latency)]]>https://audio-dev.hashnode.dev/why-i-stopped-obsessing-over-pagespeed-scores-and-started-focusing-on-actual-latencyhttps://audio-dev.hashnode.dev/why-i-stopped-obsessing-over-pagespeed-scores-and-started-focusing-on-actual-latencySun, 10 May 2026 16:02:23 GMTLately, I’ve been spiraling down the rabbit hole of Web Vitals. We all want that perfect 100/100 score, right? But here’s the thing I realized while working on some audio-heavy projects: a high Lighthouse score doesn't always mean a "smooth" user experience.

I was testing some data-fetching methods for Soundify Premium and noticed something interesting. You can have a green score, but if your API takes 2 seconds to respond with metadata, the user still feels like the site is "slow."

I’ve shifted my focus to:

  1. Edge Caching: Getting data closer to the user.

  2. Payload Size: Why fetch the whole discography when the user only needs the top 5 tracks?

  3. Perceived Performance: Using skeleton loaders that actually make sense.

It’s easy to get lost in the metrics, but at the end of the day, if the music doesn’t play instantly, the score is just a number.

Curious to know—how many of you are actually hitting that 100/100 mark without compromising on heavy features? Let’s talk in the comments!

#WebPerformance #DevLife #Optimization #Frontend

]]>