A 14kb page can load much faster than a 15kb page

Post by youngtaff » Thu, Aug 25, 2022, 1:53 PM UTC

hackernewds wrote: post #152

iainmerrick wrote: post #108

Earlier quoted context omitted.

I don’t have a citation handy, but this is something that Google has famously studied. They claimed years ago that a tiny increase in the loading time of the Google home page led to a measurable decrease in the number of searches (like, a few percent). Not everyone is operating “at Google scale”, of course, but in aggregate the effect is real and faster-loading pages have better metrics. So, most satellite internet u…

Amazon has publicly stated that every 100ms in additional loading time leads to 1% loss in revenue. For the scale of Amazon, that is massive

Post by shepherdjerred » Thu, Aug 25, 2022, 1:55 PM UTC

soheil wrote: post #264

tracker1 wrote: post #207

Earlier 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.

> easy to configure, relatively flexible, sane defaults Compared to what? You think nginx is not easy to configure or has insane defaults somehow? Really baffled why people come out of the wood work to pile on beautifully architectured designs in favor of some random project they happen to like or just because it's written in a language they have a special affinity for like Go or something.

Post by subhashchy » Thu, Aug 25, 2022, 1:57 PM UTC

mminer237 wrote: post #273

subhashchy wrote: post #266

This is very cool. In the age if bloated JS frameworks and Bulky Desktop sites loaded on Mobile devices, its refreshing to see someone putting efforts to make the pages fit in a single MTU. However, just page size is half the story. Look at the screenshots below - #1 - Here you can see this page (9KB) - 110ms - https://i.imgur.com/qeT2Az0.jpg #2 - Another page, 29 KB in size - 42ms. https://i.imgur.com/tWsLGr1.jpg Bo…

Yeah, it's just waiting on the server for most of that time in the first screenshot. Static (or cached) sites are going to be a lot faster than sites that have to re-render things every time.

Post by soheil » Thu, Aug 25, 2022, 2:21 PM UTC

kdmccormick wrote: post #271

soheil wrote: post #264

Earlier quoted context omitted.

> easy to configure, relatively flexible, sane defaults Compared to what? You think nginx is not easy to configure or has insane defaults somehow? Really baffled why people come out of the wood work to pile on beautifully architectured designs in favor of some random project they happen to like or just because it's written in a language they have a special affinity for like Go or something.

In terms of saner defaults: The charset="utf-8" default described above is one example. TLS enabled by default is another. Also, you could asked all your questions without being incendiary and making assumptions about why people like Caddy. Nobody mentioned Go except you.

Post by rstupek » Thu, Aug 25, 2022, 2:34 PM UTC

soheil wrote: post #277

shepherdjerred wrote: post #274

Earlier quoted context omitted.

Have you used Caddy for reverse proxying compared to nginx? It's infinitely easier. Two lines per site, https built in, dynamic upstreams are handled by default, HTTP 2 enabled (maybe nginx does HTTP 2 by default,; not sure).

Easier in what sense? If you find the most esoteric feature and then claim it's easier for that purpose, that doesn't count! If you're going to claim it's easier to configure than nginx you have to make a fair comparison by comparing not the features that you care about, but instead the features that define the system as a whole.