I Evicted Framer Motion From a Client Site and Cut the Bundle by 27%

I run a small web agency in South Florida. We build Next.js sites for local businesses — construction companies, engineering firms, med spas. The kind of companies where every second of load time costs real money. Last month I was doing a performance audit on a client site we'd built and noticed something ugly: the mobile Lighthouse score was stuck in the low 70s. Desktop was fine — 95+. But mobile was getting murdered by Total Blocking Time. I opened the bundle analyzer and there it was. Framer Motion was the single largest dependency in the entire project. We were using it for maybe six animations — a few fade-ins on scroll, a mobile nav slide, some hover effects. Six animations. 40KB+ of JavaScript shipped to every visitor. That's when I decided to evict it entirely. The Problem With Animation Libraries in 2026 Here's what nobody tells you about Framer Motion (or Motion, as it's now called): it's an incredible library. The API is beautiful. The spring physics are best-in-class. For