Pretty accurate, except for one major thing: all the pages load instantly. In 1999 you pretty much expected each web page to take at least 10 seconds to load, mostly for the images to gradually...fade...into.....view.
I remember a very specific rastering effect with loading images, probably around 1994-1996? The image would load every nth line and then iteratively nth line + i until i==n. Compared to what I would see later (just loading in every line from top to bottom), you could get a sense of the whole image sooner, just in an increasing fraction of the vertical resolution. I can't recall which image type this was or whether it was Mosaic or Navigator, but the effect was very distinct; at the time I assumed it was the way the image data was streamed in, but now I'm wondering whether it was just the way the image codec built the viewable bitmap.
Interlaced GIFs. Early browsers only rendered the single lines as they came in (leaving the unloaded parts blank), but eventually browsers started doubling the lines so the image seemed to increase in resolution as it loaded. I think MSIE started the latter behavior, and that's what modern browsers do.
Progressive JPEGs are somewhat similar, but IIRC didn't gain traction until 2000 or so.
That was interlaced GIF, see https://en.wikipedia.org/wiki/GIF#Interlacing (the demo image in the article is from Chrome which tries to approximate the image with rectangular regions, the 1990s browsers showed not yet received lines as blank which made interlacing effect)
For me, the “https” in the Netscape URL is sort of an anachronism. I mean, yes, technically it was available in Netscape in 1999, but very few sites used it (even among e-commerce sites).
It's what people who didn't understand the separation of concerns with HTTP, HTML, CSS, JavaScript and server side were did by deciding to jam it all into JavaScript and entangle it in code complete and gang of four constructs and then call it superior, easy, efficient, well designed, robust ... It's ... It's simply wild.
HTML content? In the javascript. Style information? In the javascript. A way to negotiate network loading and resources, document structure? You guessed it. Want the back button to work again? More JavaScript. URLs to be universal? Even more!
Eventually you'll get the page to be almost as functional as it would have been by default had you not used any of it.
Read the mdn and w3c documentation guys, I promise you 99.9% of what you want is in there without reinventing it from base principles. It's not 2010 anymore
It's like a bad cook who is trying to fix a poorly made meal by making more mistakes, covering it in salt and oil, smearing honey over it, and calling it delicious.
I'm thought the Netscape logo only animated when the page was loading? I found myself instinctively hitting the stop button to try and make the logo stop looping.
Overall, it's really great though. I love the stuff popping up on Neocities.
Quite a while ago, someone (jwz?) brought back the original Netscape home page circa 1994, complete with dialup-level speed throttling. It "feels" like 56K to me, but I believe 9600-14.4K would have been more common at the time.
