Skip to content

Comment on How Google Pagespeed works

Comments

Too bad Google's own page describing Pagespeed and Lighthouse fares abysmally on their own tests. (https://imgur.com/a/56FVOwK)

I'm sick and tired of Google playing the role of the global regulator of what's acceptable and what's not. Not everyone can afford own data centers and CDNs to serve content. Not every single page can benefit from SSL.

And web's not the only area they are regulating through monopoly - the number of hoops one has to jump through these days to run an e-mail server, just to have its e-mail acceptable by the holy Google e-mail servers is silly.

Not every single page can benefit from SSL.

huh?

You don't need "SSL" (TLS, https, etc.) to serve static, uncontroversial content

That only covers the "encryption" part of SSL/TLS.

If there is any incentive to fake your content (e.g. for phishing or other attacks, or even simply spreading false information), you'll also want the "authenticity" part of TLS for preventing middlemen from arbitrarily changing content.

That's absolutely untrue. For example a man in the middle could intercept and modify the page.

https://www.troyhunt.com/heres-why-your-static-website-needs...

This was a good article, I concede the point.

With Let's Encrypt you really have no reason not too though. And what's not controversial in one country may be in another.

http://objective.st gets a 100% score. No SSL, no CDN. Hosted on a single Digital Ocean droplet.

Mind you, also virtually no traffic and very little and lightweight content, but still...

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.