Why I Built TheFastestWeb

A few months ago, I migrated my website FixMyPDF from vanilla JavaScript to a modern JS framework. The site looked better, the code was cleaner, and everything seemed to work perfectly fine. I couldn't see any visible speed issues, so I moved on and didn't think twice about it.

Then, over the next week, my organic traffic started dropping. Quietly at first — from 100+ daily visits down to 80, then 60, then 40. Within a week, I was getting barely 20 visits a day. I had no idea what was happening. Nothing had changed on the content side. No algorithm update that I knew of. Just a slow, steady decline that felt impossible to explain.

Out of desperation, I finally checked my Core Web Vitals. That's when I saw it — my performance scores had dropped drastically after the migration. The site that “looked fast” was actually much slower under the hood. Larger bundles, render-blocking scripts, layout shifts I couldn't see with my eyes but Google could measure with precision.

I sat down and spent a full day fixing the performance issues. Optimized the bundle, lazy-loaded what I could, fixed the layout shifts. The scores went back up, and over the next couple of weeks, the traffic slowly recovered.

That experience is exactly why I built TheFastestWeb. I wanted a simple tool that tracks website speed over time and alerts you when something goes wrong — before you lose traffic over it. No complicated dashboards. No enterprise pricing. Just submit your site, and we'll keep an eye on your performance score every single day.

If your speed drops, you'll know about it immediately. If it stays fast, you get to show it off on the leaderboard and earn a backlink while you're at it.

That's it. That's the whole story. If you care about your website's performance, I built this for you.