> In July, the SEO ranking algorithm was updated to include page speed as a ranking factor for both mobile pages and ads.
July 2018, according to both linked sources.
How Google Pagespeed works
31–40 of 48 posts
Re: How Google Pagespeed works
#32Nice article, but is it just me that thinks it is weird that Google ranks better the pages that are speedier in their browser? Antitrust here?
This is curious, I'd like to see some study on this point but do you think that the ranking would vary a lot depending on which browser was used to provide the small speed related element? Any anecdotal data about sites that are super slow on Chrome but blazing on other browsers?
Just that the rank criteria is how fast it is in Chrome. Some of the micro benchmarks, like Time To Interactive, looks really browse dependent.
Re: How Google Pagespeed works
#33> In July, the SEO ranking algorithm was updated to include page speed as a ranking factor for both mobile pages and ads . What's one supposed to do when PageSpeed only points to Google's own asset delivery services as being "the" big problems which cause a lower score? - "serve images in next gen formats" - complains about images served from tpc.googlesyndication.com - "efficiently encode images" - same as above - "…
The left hand does not always know what the right hand is doing in large corps. I'm assuming the SEO team is not in daily contact with the ad delivery team(s). The SEO team is just reporting on what they how they are seeing the page load without concern for where the slowdowns occur. It is quite funny/sad/ironic that it is within the same letters of the Alphabet that are the problem. I had the same experience with Ap…
I wish people would remember this phenomenon when they are engaging in wild theories of intricate (and often malevolent) corporate strategy.
Such as: buying GitHub is unlikely to be Microsoft's attempt to trap OSS; Apple's early adoption of new ports probably isn't motivated by selling an extra $12 dongle for every $2000 Macbook; a journalist criticising Facebook is rather unlikely to be acting on corporate orders to sully the competition, etc.
Re: How Google Pagespeed works
#34It’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.
Re: How Google Pagespeed works
#35Too 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…
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...
Re: How Google Pagespeed works
#36> In July, the SEO ranking algorithm was updated to include page speed as a ranking factor for both mobile pages and ads . What's one supposed to do when PageSpeed only points to Google's own asset delivery services as being "the" big problems which cause a lower score? - "serve images in next gen formats" - complains about images served from tpc.googlesyndication.com - "efficiently encode images" - same as above - "…
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 profile other than Lighthouse and Google Page Speed? Do you support running your software in a Docker container of my own choice?
Because I can get all those things via one or more of the competitors in this space, and I'm not seeing any compelling reason to even look at Calibre.
Please feel free to convince me that I'm wrong.
Re: How Google Pagespeed works
#37It’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...!
Re: How Google Pagespeed works
#38Too 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…
> Not every single page can benefit from SSL. huh?
You don't need "SSL" (TLS, https, etc.) to serve static, uncontroversial content
Re: How Google Pagespeed works
#39> In July, the SEO ranking algorithm was updated to include page speed as a ranking factor for both mobile pages and ads . What's one supposed to do when PageSpeed only points to Google's own asset delivery services as being "the" big problems which cause a lower score? - "serve images in next gen formats" - complains about images served from tpc.googlesyndication.com - "efficiently encode images" - same as above - "…
"serve images in next gen formats" - complains about images served from tpc.googlesyndication.com
I knew PageSpeed was bunk when that recommendation came up on a web page I was working with. All of the "next gen" formats that PageSpeed recommended weren't supported by any mainline browsers — not even Chrome.
That may have changed by now, but my opinion of PageSpeed hasn't.
Re: How Google Pagespeed works
#40Earlier 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
With Let's Encrypt you really have no reason not too though. And what's not controversial in one country may be in another.