What might speed up the page eventually...

MXXIV·2/25/2014, 2:18:53 AM·2 votes·414 views

Hello.

Correct me if I'm wrong:

###For all: First, you all guys might wonder why page sometimes takes long to load and the content takes a while to appear. Sometimes, rarely, it does not appear at all.
There is some explaining to be done about that. Generally, the big part of what you see is, most likely, created on your computer, not just received from server - and the generating script must wait for everything to load before it starts rendering.
On the contrary, normal site simply appears as it loads.

###For the forum webmasters

I've noticed very strange way to make web site. You're using HTML templates parsed via javascript. I could surely elaborate on why is that a bad idea, but well, I guess you're just making the project a little fun. So be it.
Now once this must be done, I'm wondering, why the hell are static templates being sent every time with the page... Don't you use them to save bandwidth?

Just put them in JSON file or JS file that gets cached. And please, if possible, run the parser when DOM is ready, not onload. Because waiting for posts to appear just because of loading goodle statistics or whatever is driving me nuts.

Eventually, the parser might run when the JSON/JS containing templates loads and then append content when DOM is ready. That would be even pro.

I think fast speed is most important here, really. And I'd dare to say that there are still possible improvements. Honestly, I don't know page that has such problems with loading. Applies on old board too.

2 Comments

QuesoLoco2/26/2014, 1:29:09 AM1 votes

A note on why they're not served as a JSON file.

The initial page is sent with GZIP encoding on there (never saw GZIP on any of the other response headers, I think they should check that out, especially when 75% of their initial payload is in PNGS), so the actual weight of the templating isn't that heavy, also given that they're not of script type=text/javascript (or application/[(java)|(ecma)]script), it means that the actual DOM parser skips over those blocks as they're not related to the rendering of the page, so they don't actually slow down the other assets.

That being said, there are a couple of things else they could work with. The CDN subdomain sends cookies with it, when the CDN itself should not request / send cookies on the actual requests, due to them being static assets.

Also, can we not get unencrypted session ID's on all resources?