111–120 of 292 posts
Not that wickedly fast unless you're really near Dallas where the server is: https://performance.sucuri.net/domain/varvy.com Hosting on a single VPS is never gonna be very fast globally no matter what you pay your hosting. In fact our free plan on netlify would make this a whole lot faster...
Off topic, but is that service showing crazy slow numbers for "USA, Atlanta" for anyone else?
Ehh, I just got 10.91s load time in Chrome 53 from Colorado, USA. Image of Chrome Dev Tools: https://reportcards.scdn3.secure.raxcdn.com/assets/uploads/f... As an aside, does HTTP/2 provide any benefit for a single HTML file with no external assets?
HTTP/2 header compression is one benefit that helps even it you have just 1 request.
The HPACK spec is a pretty easy read [1]. There is a static, hardcoded table that contains most of the HTTP header names, and even some common predefined KV pairs. You save some bytes on the wire if your header's name or value is one of these entries; the header name will essentially always will be in the static table.
But for names and values that aren't in the static table, you have to put them into the dynamic table and encode them using either the integer packing or the huffman code. The client has to decompress these, of course.
On future requests, you have some leftover state in your dynamic table so future 'duplicate' headers are packed, and take up very little space. But for the first (ever) HTTP request-response pair, you have to trade ALL the headers in "full". So the true benefits of the dynamic table don't kick in.
[1] https://http2.github.io/http2-spec/compression.html#header.e...
Earlier quoted context omitted.
There is a free tier. It looks like it's free up to 1GB per day [1]. On my home account I've only used it for demo projects that are scarcely used, but it's fine for that. [1] https://cloud.google.com/appengine/docs/quotas
Does it 'stop' if you reach the quota or do you get a bill?
His affiliate link for VPS service has its cheapest option priced at $25 a month. You can get a nice little VPS for static hosting on SSD from digital ocean for $5 a month. $6 a month with backup.
Time4VPS offers you 2 cores (compared to one on DO), 80 GB SSD (compared to 20 on DO), 2 TB bandwidth (compared to one on DO), and 2 GB of RAM (compared to 512 MB on DO) for 3 euros (3.36 dollars). 1 additional euro for daily and weekly backups.
Started renting one just two days ago, so I can't really guarantee that it's reliable, but it was recommended to me by a friend who's renting it for over 100 days now without any downtime.
[1] https://www.time4vps.eu/pricing/ (or, if it sounds good and you want to use my referral link: https://billing.time4vps.eu/?affid=992)
Not that wickedly fast unless you're really near Dallas where the server is: https://performance.sucuri.net/domain/varvy.com Hosting on a single VPS is never gonna be very fast globally no matter what you pay your hosting. In fact our free plan on netlify would make this a whole lot faster...
Off topic, but is that service showing crazy slow numbers for "USA, Atlanta" for anyone else?
stop the presses for the entire company to have a meeting on how to shave off 300 milliseconds for the poor residents of Japan!
Not that wickedly fast unless you're really near Dallas where the server is: https://performance.sucuri.net/domain/varvy.com Hosting on a single VPS is never gonna be very fast globally no matter what you pay your hosting. In fact our free plan on netlify would make this a whole lot faster...
I hate to be negative, but what really is the point of this? That a simple webpage without any content can be fast? Of course it can. Is it desirable to inline your CSS, "like a boss?" Maybe if you have one single web page. What if you have dynamic content and your users intend to browse more than one page? With externalized CSS, that is all cached. Same with images. If I'm building a web application, I certainly do…
It also seems somewhat antiquated. As service-worker comes online we can... do a lot more with a more naive method.
This does not work in most cases when you use big images. From StackOverflow answer [1]: "It's only useful for very tiny images. Base64 encoded files are larger than the original. The advantage lies in not having to open another connection and make a HTTP request to the server for the image. This benefit is lost very quickly so there's only an advantage for large numbers of very tiny individual images. "
[1] - http://stackoverflow.com/questions/11736159/advantages-and-d...