Help me with my new website!

[bennyboy]

Sorry for not responding for so long, I have had some real-life issues.
Look, guys, I think I understand you. You've put an insane amount of effort into making web-pages with some 1000 or more lines of Javascript, CSS, SVG and other things and you are convinced that people value those things. But unless someone is an ICT expert, he doesn't see how much effort you put into making a website to value it.
In fact, it can easily have the exact opposite effect. If you make a lot of effort learning how to use some professional editor for PNGs rather than using a simple SVG image, a user who's not a web-design expert doesn't think "Oh, look, the programmer has put a lot of effort making this image.", he thinks "Damn, why does this web page load so slow?".
I've worked on the design a little bit, but making a "professional" website is probably a fruitless waste of my time. Do you honestly think I will attract more visitors by improving the design than by making another webpage about the topics that interest people, like this one?
http://flatassembler.000webhostapp.com/toponyms.html
And why is it so hard to follow the PacMan link on your smartphone and tell me if the game works or not? Not that that information would be particularly useful to me, I am just curious about whether a simple game made using Javascript and SVG would work on an iPhone (or some other smartphone) or not, and I don't have an access to iPhone (or any smartphone other than Samsung Galaxy S3 Mini).

I never thought I'd say, "Oh my god, my eyes are ringing."  But that's how loud that page is.

There are, right here, probably half a dozen experienced web designers / programmers. Not to put too fine a point on it, but if you were willing to listen, I could teach you a great deal about web design indeed. You seem to think that you have to choose between a pleasant appearance and quality content. Obviously, that's the wrong way to look at it: the pleasant appearance is meant to make it easier and more attractive for people to engage with the content.

A general rule, though, is to work from general to specific. You want to get your masterpage set up, your navigation system, and so on, before you start crafting the specific content.

---

Trust me, no one here is trying to engage in a "Oh, yeah?  Well, my sites are written in this many lines of code, minimum" dick measuring contest with you.  No one who actually makes sites semi-seriously does that.  Most of the time we're looking for a way to avoid writing a lot of code, because that means more shit that can go wrong, and more shit to maintain/edit/change/test/etc.

Absolutely.  Code points go to elegance in minimalism, not for grunt work.  And that's what css is great for. The only time I'll add more lines is if it makes the code easier to document and to follow if someone comes back to it.