Yes, both of those sites benefit from zoomability. The first one, I just tested (by visiting "water.com" in your tool). When I tested #5 (500 x 477), the viewport disappears off the end of the right edge of my screen. I can't see the whole thing at once, no matter what I do. I have to scroll, and that's confusing because my scroll swipe will move the content inside the viewport before moving the site itself, and thus the viewport itself. If I could pinch out on it, I'd see the whole thing at once.
As an aside, the Android I used to test this allowed me to turn on Force Zoom, and that allowed me to use the site better.
The second site (grid.html) can appear very small. I think you intended to say it should be zoomable, as I was able to zoom in and out on that one.
My point is, even when you yourself cannot conceive of a reason a user would like to zoom the site, trust me, there probably is one. In another reply, you mentioned the 300ms delay that turning on zoom control introduces. I hadn't thought of that before, and that is a good point for disabling zoom control. Maybe Apple can follow Google's lead, and give their users the option to override it. That would allow the majority of your users the faster touch-responsiveness that you're trying to give them, while still letting the rest of us have the control we'd like over our browsers.
As an aside, the Android I used to test this allowed me to turn on Force Zoom, and that allowed me to use the site better.
The second site (grid.html) can appear very small. I think you intended to say it should be zoomable, as I was able to zoom in and out on that one.
My point is, even when you yourself cannot conceive of a reason a user would like to zoom the site, trust me, there probably is one. In another reply, you mentioned the 300ms delay that turning on zoom control introduces. I hadn't thought of that before, and that is a good point for disabling zoom control. Maybe Apple can follow Google's lead, and give their users the option to override it. That would allow the majority of your users the faster touch-responsiveness that you're trying to give them, while still letting the rest of us have the control we'd like over our browsers.