Gpt testing resaults

At present, external testing is being blocked by the beta itself rather than by the testing services. Both:

and

end up at HTTPS from my external connection and return 502 Bad Gateway. �

 +1

So I wouldn't bother doing detailed browser performance testing yet. The first useful thing to tell whoever is building it is:

External access to beta.kiwiairgunners.co.nz is producing a 502 on HTTPS. Check the HTTP→HTTPS redirect, reverse proxy/web server and beta virtual-host configuration.

Once that's sorted, these are the ones I'd actually put Kiwi Airgunners through:

WebPageTest — first choice. It can test Core Web Vitals, Lighthouse and visual loading behaviour and has configurable browser/location testing. �

license.webpagetest.org

GTmetrix — useful second opinion. The current free account includes a small number of tests and gives Web Vitals, page size, request information and throttled-connection testing. �

gtmetrix.com

PageSpeed Insights — quick mobile/desktop baseline. Good for finding the obvious performance problems before spending time manually checking browsers. �

PageSpeed Insights

BrowserStack — save this until last. Its free trial currently gives 30 minutes of interactive cross-browser testing and 100 responsive screenshots. That's enough to deliberately hit iPhone Safari, Mac Safari, Firefox and Edge rather than wasting the allowance on Chrome/Android that you can test yourself. �

BrowserStack

One interesting point: the old/main Kiwi Airgunners site has historically had DNS/SSL problems reported by external monitors as well, so I'd keep the beta's DNS/SSL setup high on the checklist rather than assuming this 502 is just my connection. �

Webrate

Once that 502 disappears, give me a yell and I'll hit the beta again. At that point we can start looking at the actual site, not just whether the bloody door opens. 😁

Yep. That screenshot makes it much clearer.

The page itself is using the full phone viewport — we know that because the Kiwi Airgunners banner correctly fills virtually the entire width.

But everything immediately below it is constrained to roughly 265 px / 38–40% of your screen. Then some footer text is centred relative to that same narrow region rather than the whole screen.

So I wouldn't blame font rendering or Firefox. The content wrapper below the header has a fixed or constrained width.

The particularly useful clue is that several completely different components all terminate at almost exactly the same x-position:

Forum Home/New Posts navigation

Welcome to Beta box

Latest Forum Posts box

That means we're probably looking at one shared parent/container, rather than three individual CSS faults.

The developer should inspect the first container immediately after the banner and look for something like:

width: 260px;

max-width: ...;

width: 40%;

or an old table/grid structure with a fixed-width column.

There's another clue in your screenshot: "View in: Mobile | Classic". This is Web Wiz Forums 12.07, so there may be a legacy mobile stylesheet/template involved. Your phone appears to be getting the mobile version, and that mobile template may be inheriting a desktop column width that isn't being expanded to the viewport.

I'd report the bug roughly like this:

Mobile layout: Header/banner correctly scales to full viewport width, but main content container is only ~40% of viewport width. All content boxes share the same right boundary, suggesting a parent wrapper/table/column width issue rather than individual elements. Check mobile stylesheet/breakpoint and parent container immediately below header. Firefox desktop reportedly shows a similar issue at ~75% width.

That Firefox observation now becomes very useful, because the amount changes with viewport/browser while the basic fault remains. That's exactly the sort of thing I'd expect from a responsive width calculation/breakpoint problem.

And your OPPO is actually doing a pretty good job as a beta-testing torture device. 😁