Stop Building Heavy React Apps for Cheap Indonesian Phones

I was sitting in a warung in Tanah Abang last month, watching a merchant try to load a local e-commerce site on a three-year-old Redmi phone. The screen stayed blank for eight seconds while the JavaScript parsed, heating up his battery, before he finally closed the tab to open WhatsApp instead. That lost sale happens thousands of times a day in Indonesia because developers test their sites on M2 Macbooks in South Jakarta co-working spaces. ## Your M2 Macbook is lying to you Most local developers build websites using high-end machines connected to fast office Wi-Fi. They run local development servers and think the site is fast because it loads instantly on their localhost. The reality is that your average user in Central Java is on an entry-level Oppo or Vivo with a throttled 4G connection. React sends megabytes of JavaScript that these low-end CPUs struggle to parse, causing frustrating interface lag. When we built the dashboard for Redakta, we initially used a heavy React setup. The site ran fine for us, but our users on older phones in Bandung saw the interface freeze every time they tried to analyze a new trend. ## Single Page Apps are not default answers Bootcamps teach junior devs that every website needs to be a Single Page Application (SPA) built with React or Next.js. They think client-side rendering is modern, while traditional multi-page apps are outdated. This is backwards. For a simple landing page or a basic e-commerce shop, sending a massive JS bundle is architectural malpractice. For Flowcast, our AI gateway, we stripped out the unnecessary JS and went back to simple server-rendered HTML for the landing pages. Conversion rates went up by twenty percent because the site became usable on spotty Telkomsel connections. ## Choose boring tech that loads instantly If you want to reach users outside Jakarta, you need to optimize for CPU performance, not just image sizes. This means using Astro, HTMX, or even just clean PHP and CSS instead of bloated framework stacks. During my time at Kilau Berlian, we migrated a client's customer portal from a heavy React app to a lightweight server-side setup. The load time dropped from nine seconds to under two on cheap Android devices. Users don't care about your state management library. They care about ordering their goods before their bus arrives. Open Chrome DevTools right now, go to the Performance tab, and set your CPU throttling to "6x slowdown" and network to "Fast 3G". Load your website and watch how it actually behaves for a user on a Rp 2 million phone. If it takes longer than three seconds to become interactive, start stripping out the non-essential NPM packages.