91–100 of 130 posts
I've seen this blog, jacquesmattheij.com several times on HN and every time I try to access it I get 403 Forbidden. What gives? It's not very fast either...
> I’m sure I can do better still, for instance the CSS block is still quite large (too many rules, not minified yet) CSS doesn't minify particularly well since the class names, tag names, and attributes all have to stay in their full form. Basically it just ends up being removing extraneous whitespace. However, ever since reading James Hague's post on "Extreme Formatting"[0], I've rather liked CSS without all the ext…
But if everything that could possibly reference a class or tag or attribute is inlined into the same file then you know exactly what the scope of your CSS is for that particular request. So it should be possible to minify even the names.
@jacquesm are you sending compressed files ? I can't check that myself with my iPad 1. I'm in a camping with a bad WiFi. I can confirm that I saw and felt the difference ! Congratulations.
@jacquesm are you sending compressed files ? I can't check that myself with my iPad 1. I'm in a camping with a bad WiFi. I can confirm that I saw and felt the difference ! Congratulations.
Yes, the gzip module is on in the web server.
Earlier quoted context omitted.
But if everything that could possibly reference a class or tag or attribute is inlined into the same file then you know exactly what the scope of your CSS is for that particular request. So it should be possible to minify even the names.
Hm. A minimizing post-processor for a webpage and all the resources that it loads. That's an interesting idea which means it has probably already been done.
Earlier quoted context omitted.
Yes, the gzip module is on in the web server.
Are you using a front end web server for handling caches, TLS, etc. in front of the Hugo server or is the hugo server in the front line ?
This is absolutely brilliant if the only metric your audience cares about is page load time . For most sites that's only part of the story. Take the first paragraph, about how Google's homepage of just a textbox should really be a few hundred bytes instead of a megabyte. Google's homepage does a lot more than just enabling you to enter a search - there's the autosuggest feature, there's analytics, the apps tray, G+ i…
The google homepage doing a lot more was pointed out earlier, I've updated the page to reflect that. > If Jacques blog gets a significant amount more traffic by loading super fast then that's a definite, measurable success. If the only change is that it loads faster, and he doesn't grow his audience, then he hasn't really achieved anything. If audience growth were the target, then yes that's true. But what matters to…
I'm reasonably sure that this theory is backed up by data. I don't have the time to look up the studies just now, but as someone with a professional interest in this, I'm pretty sure I've seen them in the past.
Certainly, page speed has a surprisingly large impact on overall user experience - backed up by studies like Amazon's and Google's, both of which showed a correlation between faster page load and increased user activity.
Earlier quoted context omitted.
But if everything that could possibly reference a class or tag or attribute is inlined into the same file then you know exactly what the scope of your CSS is for that particular request. So it should be possible to minify even the names.
Hm. A minimizing post-processor for a webpage and all the resources that it loads. That's an interesting idea which means it has probably already been done.