2 resources from Chrome for Developers we point founders to, and the questions each answers.
🛠️ Tool
✓ Link checkedFreeBeginner
Why we picked it
You cannot fix what you never feel, and most of us build on fast laptops and office wifi. This is the official doc for simulating Slow 3G and a low-tier mobile CPU right inside the browser you already have, so you can load your own site under the conditions your users actually face. Use it as a first cheap check before you ever get your hands on a real budget phone.
From
Chrome for Developersby Chrome DevTools team, GoogleReference doc, ~10 min to try
Set the Network panel to Slow 3G to feel your real load time and spot pages that stall or ship too much on a patchy connection.
Add CPU throttling (the calibrated low-tier mobile preset in recent Chrome) to catch janky scrolling and slow interactions a cheap Android chip would hit.
This is a fast approximation, not the real thing: it is a starting point, and testing on an actual low-end device on a real network is still worth doing before you ship.
Why we picked it
This is the free, built-in way to see exactly where your landing page breaks: open DevTools, toggle the device toolbar, and drag the viewport from a narrow phone width up to desktop. It is the fastest feedback loop because it is already in the browser you use every day, no signup or install. Treat it as a starting point for spotting the break, then confirm on a real phone since the simulator cannot reproduce everything.