Live data from Hacker News

How Google Pagespeed works

calibreapp.com

41–48 of 48 posts

Re: How Google Pagespeed works

#41
post #22

Earlier quoted context omitted.

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

Re: How Google Pagespeed works

#43

It’s astounding to me that web development is in such a state that it takes google dinging placement for people to start thinking that speed is important. Speed is a feature. Speed is your most important feature. It’s a gazillion times more important than all the other cool features that developers and product managers think are important.

But react is all I know how to write...!

React doesn't make your site slow.

Re: How Google Pagespeed works

#44
Reading the definition for TTI is also helpful in narrowing down your page speed problems: https://github.com/WICG/time-to-interactive#definition

Also this seems like the right time for me to brag about the impact we were able to have on our site's responsiveness. I know a lot of people will think a lot of this is BS being pushed by Google, and I agree in some cases, but overall our site is incredibly fast now (perceptively, significantly faster), and that's thanks to Lighthouse and its suggestions.

This is without HTML caching, so still some room for improvement :) https://i.imgur.com/d7KCTmj.png

This is a full Vue SPA with chunking enabled.

Edit: oops, I was behind a VPN when I ran the test which impacted my ping. All metrics are down to 0.3s max :)

Re: How Google Pagespeed works

#45
post #22

Earlier quoted context omitted.

> Not every single page can benefit from SSL. huh?

You don't need "SSL" (TLS, https, etc.) to serve static, uncontroversial 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...

Re: How Google Pagespeed works

#46
post #27

Earlier quoted context omitted.

> we do not serve any mobile visitors at all > > How is that possible > These are adwords landing pages. We're in super MVP-mode In your specific case, google pagespeed ranking is probably irrelevant. If you truly have 0 mobile visitors, and these are just adwords landing pages, then people are probably not "Googling" your company, so search ranking is probably totally irrelevant at this point too.

As far as I understood from the article, it also impacts the adwords quality score. Or did I misunderstand this?

That's what I took from it yep.

Re: How Google Pagespeed works

#47

Earlier quoted context omitted.

Hi! Author of the post here. Lighthouse definitely has some improvements to make for the audit suggestions that offer advice to improve the score. I think people get a little bit frustrated/blinded by the advice when there's nothing that can be done about third parties (I know I do!). Our product Calibre (mentioned in the bottom of the post) has a n adblocking/third party blocking feature that allows you to compare y…

So, I'm curious. How does https://calibreapp.com/ compare to https://www.webpagetest.org/ and https://www.sitespeed.io/ and https://gtmetrix.com/ ? Why would someone want to pay you for your service, as opposed to using any of the above? Do you support browsers other than Chrome? Do you support a wide variety of simulated hardware? Do you support a wide variety of testing locations? Do you support any page speed test…

Depends on your use case - I recommend Calibre to some clients, SpeedCurve to others and self hosted WebPageTest or Sitespeed.io to others.

One of the key deciding factors is do you want to run the service yourself e.g. VMs, containers, in multiple regions or do you want to make that someone else's problem and get on with running your business - most of my clients are in the later camp

Both Calibre and SpeedCurve have clean UI's that allow performance to be tracked over time, from multiple locations and integration with other services via web hooks, APIs etc.

GTMetrix is old and outdated IMV, - it still heavily relies on YSlow rules which are well past their sell-by-date

WebPageTest is my favourite (SpeedCurve uses it under the hood) but it's got no ability to track over time, SiteSpee.io is really nice too but is self-hosted.

With the exception of some real devices in Dulles, all of the products rely on emulation for mobile, and Safari is a real gap for them all too

Re: How Google Pagespeed works

#48
post #45

Earlier quoted context omitted.

You don't need "SSL" (TLS, https, etc.) to serve static, uncontroversial 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.
Post reply on HN