Regading discussions of Web2.0 speed - I think it’s quite a bit faster than web 1.0 in general operation, and can handle much higher load. My old web 1.0 app would fall to pieces with 30+ users, whereas web 2 can handle 80+ with ease on the same hardware.
However, the initial page load time is pretty poor in Web 2.0.
Doing some debugging in Safari, I quickly see a major problem. It appears as if the initial page load pulls in a lot of inidividual files, and even if these files are cached, the 304 “unchanged” server response is stalling for up to 1 second.
Here’s an example - note that even though these items are all fully cached, it’s taking the Xojo web engine up to 1.0 seconds to respond with a simple 24-byte “304 Unchanged” response.
Here’s a detail showing the stall:
What’s causing the stall?
I notice one script is not like the others - CustomColumnTypes.js is always returning a 200 response, never a 304, and this is also the slowest item to load, and the final script that loads.
Could there be a framework bug with CustomColumnTypes.js which is hanging up the entire initial page load?
This is testing a Web 2.0 app built with Xojo 2021 R 2.1 on local ethernet. Server = macOS 10.13, client = macOS 11.6 / Safari 15.0. I see the same behavior in Chrome, so I don’t think it’s browser-specific.