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. 😁

 Have responce for that too.

 I have no doubt your more than capable of sorting it all independent, but figure if gpt can cut the search time down for you as to where the issue may be ots worth the time saving. I use to hate going through txt looking for mistakes

 So ill put this up and leave it at that.

 Yep. Those screenshots show more than the width problem, and the login history is useful.

The third screenshot from the OPPO is particularly diagnostic. That's not a browser rendering failure. Web Wiz is explicitly reporting:

err_mySQL_db_connection

database_connection.asp

[MySQL][ODBC 5.3(w) Driver] Can't connect to MySQL server on '203.170.82.33'

So at that moment the forum application itself could not reach its MySQL database. Your phone successfully reached the web server; the web server then failed talking to the database.

The Firefox screenshots show another separate problem. The first is an ordinary HTTP 500 Internal Server Error while requesting what appears to be upload_avatars.... The second shows the image-management/upload popup actually working, so that feature is at least intermittent rather than simply unsupported by Firefox.

The login behaviour is interesting too. You said:

original-site login let you into beta once, then wouldn't; creating a new login got you in.

That makes me suspicious that the beta was cloned from the original site including some user/session/database configuration, but isn't completely isolated or correctly configured yet. Old cookies could contribute to login weirdness, but they cannot explain the MySQL connection error shown in screenshot three. That's server-side.

So you've actually found at least three different beta faults already:

Responsive/mobile layout: content wrapper shrinks to ~⅓ width on your OPPO; another Firefox user gets ~¾ width.

Server/application failure: HTTP 500 on the avatar/upload area.

Database connectivity: Web Wiz intermittently can't connect to the MySQL server.

And possibly a fourth: old-site versus beta authentication/session crossover, which needs deliberately testing before calling it a bug.

One thing I'd not do yet is clear all your cookies. Your existing browser state that produces the problem is useful for beta testing. If you wipe it, you potentially destroy the conditions needed to reproduce the login fault.

Instead, test the beta in an incognito/private tab alongside your existing session. If the old credentials behave differently there, you've immediately separated cookie/session contamination from a server/account problem.

And this also explains something from earlier: the 502 I got externally isn't necessarily an isolated oddity anymore. You've independently captured 500 and database failures from inside the beta. There are definitely server-side issues occurring, alongside the visual/browser problem.