Earlier quoted context omitted.
Source ?
https://www.emergeinteractive.com/insights/detail/does-irres... In the US as of 2020, it was 3KG CO2 per GB Data.
A 14kb page can load much faster than a 15kb page
311–320 of 356 posts
Re: A 14kb page can load much faster than a 15kb page
#312Earlier quoted context omitted.
Have to say, I absolutely love Caddy as a general webserver and reverse-proxy. Lightweight, easy to configure, relatively flexible, sane defaults.
The Caddy website has it written "Caddy is a powerful, extensible platform to serve your sites, services, and apps, written in Go" That could confuse developers thinking they can only develop apps in Go with caddy?
Re: A 14kb page can load much faster than a 15kb page
#313Earlier quoted context omitted.
Great, now go to Developer Tools and enable throttling.
Sure, I’ll also go ahead and find the oldest possible version of Firefox compatible with my operating system, open several hundred tabs, and probably just unplug my router too while I’m at it
Re: A 14kb page can load much faster than a 15kb page
#314This made me check my own site[1], the page itself is tiny(3kb). It's the images that get me, and they're svgs. Gotta be something wrong there too, an svg shouldn't be 75kb. edit: nevermind, svg is 13kb, don't know what I was mistaking there. [0] - www.reciped.io
75% of your download time is jQuery and webfonts. You'll need to review your own code to see if jQuery can be eliminated, but the fonts are probably an easier fix. You're serving them locally which is good, but changing to woff2 would help. Looks like you make a lot of use of the Gibsoni-Italic, so it's probably worth keeping. If it were only here or there, I'd say nix it and rely on font synthesis instead. If you're…
This is really interesting, and would be pretty easy I think. I'll look into this.
Re: A 14kb page can load much faster than a 15kb page
#315Earlier quoted context omitted.
I didn’t know there was a commercial version. What are the advantages of using that over open source version?
The paid version (nginx plus) has a few additional features that you often end up needing/wanting (the dashboard for example, for ops users) in enterprise environments. For what its worth, I switched from nginx to Caddy years ago and haven't looked back - Caddy's built in support for LetsEncrypt and zero configuration for the most common reverse proxy scenarios is just too compelling to ignore now - the speed and eas…
Re: A 14kb page can load much faster than a 15kb page
#316Love how this person's blog itself consist of single HTTP requests per page load. No extra css, images, scripts, or anything! This blogger cares about web perf!
Maybe I should just remove it? But I still have a lot of blog posts that include multiple images, and I don't want to reduce them to tiny thumbnails -- they're nice photos!
Re: A 14kb page can load much faster than a 15kb page
#317Re: A 14kb page can load much faster than a 15kb page
#318That's only doable with a text-centric website. I'm currently finishing a photography section for my personal website, and the gallery pages are several hundred kBs in size, while single photo page is almost 1MB in size (provided you load it on a 28" screen; browser will load smaller variants on smaller screens). Most of that weight is the thumbnails (and almost-full-size photo in the latter case). The only JS I have…
Re: A 14kb page can load much faster than a 15kb page
#319Earlier quoted context omitted.
It needs to get faster. Soon!
What are you planning?
Re: A 14kb page can load much faster than a 15kb page
#320Earlier quoted context omitted.
Favivon isn't blocking the initial request so it really shouldn't matter. > HN could put the CSS and JS into the generated HTML file and still stay under 14kB At the expense of caching those resources that stay static. With http/2 the benefit of merging into one resource should be negligible anyways.
> With http/2 the benefit of merging into one resource should be negligible anyways. That's not true, by including them in the HTML you save an extra round trip for requesting them. That's what HTTP2 Push was supposed to solve, but it's being deprecated & removed.