Yes, I skimmed a bit on the "registration" flow. it is a simple "mailto" link with 3 advantages: a) provides the required name and email, b) verifies you're a legitimate person and c) white-list our team email so we are never marked as spam.
If someone hasn't stayed long enough to trigger GA, is it really a user? :)
Another option: only delay the scripts the first time user has landed on your page
I think the single script embed is a good path (much better than asking people to change DNS, remove scripts or such). Maybe you can optimize other areas using JS (like images).
How is this different/more scalable than running google tag manager as async, with the rest of the scripts as defer/async as well.
Not so long ago I side-project fassttt.com and thought the biggest issues are server-side, with bad images and improper caching. Ended up creating a complete minifier/compressor/cdn-enabler.
I since realized the problems are mostly client-side. Cumbersome styling framework and JS rendering engines that are dynamic and VERY hard to optimize.
BTW, if people only care about site-speed score, see https://nitropack.io/ which almost always give you a 100 score.
is there a reason why you can't have a deployment/set of pods per client? the article keeps mentioning every solution failed when the whole dataset hit a certain limit.
classic cloud announcement. a new service that sorta does something sorta different based on sorta mature sorta open source that is sorta configurable and has no pricing of yet. but sure, let's go ahead and announce it.
S3 is $0.023/GB (still x4 higher), plus $0.004 per 10K requests
CloudFront is $0.085/GB, plus $0.0075-$0.01 per 10K requests)
GCP is $0.08-0.12/GB (same for all services), plus $5 per 1M requests)
And who says most of the bandwidth goes towards static assets? 99% of our requests are dynamic (thus the NodeJS frontends)