>need to zoom and pan to read
over every time I forbidden to pan and zoom by the site author.
Especially when I'm behind 43" 4k monitor and the site decide
WHAT TEN LINES
PER SCREEN
IS EVERYTHING
I WISHED FOR
Developers assume everyone has the latest iPhone or Pixel. So they take like a minute to load, heat my phone up, drop the battery by 10%, and have a 20% chance of OOM-ing my browser.
The Guardian is the absolute worst at this. I don't know why, it brings mobile Firefox to its knees.
Basically, fancy "mobile friendly" JS is no good if it makes my phone stutter and go catatonic.
Whereas if people just wrote old school "CSS Zen Garden" sites, or even this old table stuff, any ancient phone could handle them easily.
But no, I need to go pay a kid to dig up more coltan.
I can scroll. It's ok. What I can't do is will my phone faster, without shelling out more stupid cash.
Once you decide to scale text to device size so that it's readable, you are stuck doing the rest of mobile web design (fluid layout).
The problem will fix itself.
Unfortunately, it tends to take more thought because we usually want widescreen components, like sidebars, that are easier to build when you can hard-code a device width, and hard-coding width is what breaks zooming and text size changes.