[uallo]

    <meta name="viewport" content="width=800, initial-scale=0">

This sets the width to a mininum of 800px, no matter what phone model or browser you use. I'm a little confused how you can can claim this "Works well on any device" when apparently it was not tested on a phone. I, too, closed the tab before I even had a chance to learn about your product.

Update: Not OP, but I'm on a Pixel 8a with Firefox.

[reconnecting]

This is a software website, and we don't expect many visitors from mobile devices. However, I'll check if this issue can be resolved without using CSS.

Thanks for letting me know.

[Etheryte]

I think this is a classic case of familiarity blind spot. It's easy to think of your users as people similar to you, but that's not necessarily the case. Statistically mobile phone users outnumber non-mobile users online nearly two to one, some statistics put the estimate even higher.

[reconnecting]

This is a misleading reference to statistics without context. It's not a B2C website, and in fact, most of our audience accesses it from Linux devices rather than mobile Firefox.

Anyway, even if someone does visit using mobile Firefox, it only takes one zoom-in/ zoom-out to adjust. So it's not really a webpage code issue, it's more about how Firefox renders pages on mobile devices.

[Etheryte]

This whole interaction is weird to me. Multiple commentators here have confirmed that your site is broken due to a, let say, somewhat unorthodox technical choice you've made. Rather than fix it, which would've probably taken less time than the thread here, you're trying to convince everyone else that they're holding it wrong. As an aside, it's not surprising that nearly none of your users access your webpage from mobile when it's broken on mobile.

[lcnPylGDnU4H9OF]

> As an aside, it's not surprising that nearly none of your users access your webpage from mobile when it's broken on mobile.

I doubt their lower mobile visitor numbers are due to the UX on mobile. They may have a lower conversion rate from mobile visitors but it sounds like people don’t visit much on their phones. A given user won’t know it’s broken on mobile before loading the page on mobile.

Additionally, it is a marketing page for a B2B SaaS for web application security. With that context, only if they said anything other than “most of our audience accesses it from Linux devices” I would have reason to think they’re lying. I get the feeling that their business isn’t hurting for mobile users. (When I visited on my phone I figured it’s pointless unless I’m on something with a real keyboard once I saw what’s on offer.)

[reconnecting]

It is not broken on mobile. There is simply nothing to be broken.

What commenters above are probably suggesting is that there is no adaptive version for mobile, but no one had promised one.

One small, but important correction, it's a B2B on-prem web application, and this is exactly the reason why any devices except those that can run the web server itself are not the target audience.

[reconnecting]

Likewise. It works great on all [1] my mobile devices.

[1] https://www.tirreno.com/news-phone.jpg

[uallo]

> Anyway, even if someone does visit using mobile Firefox, it only takes one zoom-in/ zoom-out to adjust. So it's not really a webpage code issue, it's more about how Firefox renders pages on mobile devices.

No, it requires constant zooming and panning to be able read anything. And this has nothing to do with Firefox, Chrome and other browsers behave exactly the same. It is absolutely an issue with your website.

[reconnecting]

It works great [1] on my mobile device.

[1] https://www.tirreno.com/news-screenshot.jpg

[reconnecting]

It has been tested and works well on various devices, including phones, which is why I’m kindly asking for your exact device model.