3 ms·
I make my personal pages fast this way since last century. Probably a huge amount of people did the same. It's pretty obvious. When you need fancy graphics (a
by nine_k 10y ago
I make my personal pages fast this way since last century. Probably a huge amount of people did the same. It's pretty obvious.
When you need fancy graphics (a static photo album), things become less easy: you e.g. may want to preload prev / next images in your album to make navigation feel fast.
Things become really tricky when you want interactivity, and in many cases users just expect interactivity from a certain page. But client-side JS is a whole another kettle of fish.
When things become ugly is when you want to extract some money from page's popularity. You need to add trackers for statistics, ad networks' code to display the ads, and complicate the layout to make room for the ads, placing them somehow inobtrusively but prominently. This is going to be slow at worst, resource-hungry at best.
(Corollary from the above: subscription is more battery-friendly than an ad-infested freebie.)