Hi, do you have any figures for this subject?
>If your pages load slowly, it will reduce your ad quality score, and ads will cost more.
Thanks.
How Google Pagespeed works
11–20 of 48 posts
Re: How Google Pagespeed works
#12Earlier quoted context omitted.
… but to answer your question better. It sucks that Google's own services don't live up to the performance expectations of tools made in other parts of Google.
I imagine the various teams at Google see each other as competition more than we might realize. How many chat-like applications are there? How about the Java/Kotlin Android teams versus the Flutter team? All of the GPL die-hards looking at the non-GPL (MIT, BSD, and Apache2) Fuchsia project wondering just how committed Google is to the Linux kernel.
Yes, different teams have different priorities, but there isn't direct competition between a performance-measuring tool and ad-serving.
In this case it's probably more the performance team wanting to do unbiased measurement. As they should.
Re: How Google Pagespeed works
#13Nice 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?
Re: How Google Pagespeed works
#14> 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 - "…
Find a real business model instead of serving cancer & malware to your visitors?
Re: How Google Pagespeed works
#15> 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 - "…
[deleted]
Re: How Google Pagespeed works
#16Nice 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?
It’s just one of many factors so probably not.
Re: How Google Pagespeed works
#17> 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 - "…
Well I think the good news is that all of your competitors have to suffer the same problems, so you'll all be punished equally.
Re: How Google Pagespeed works
#18> 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 - "…
I get an excellent PageSpeed score by hosting my own stuff on Azure. CDNs make sense only for sites with huge traffic. And at that point, maybe you could afford to pay for extra bandwidth and still not use a CDN. And I've mostly stopped using PageSpeed at all, because the metrics are obvious: total download size matters.
All the arguments for "but your user might already have such-and-such-version-of-jQuery cached" just have not had a good enough impact on total experience. There are so many versions of whatever you might be importing, and HTTP keep-alive works really, really well.
Of course, I also don't have any tracking setup, say nothing of the 50 dozen systems most sites use. I've never gotten anything out of them that I couldn't have figured out on my own. They always come back to "users bounce when shit is slow". Thanks, tracking scripts, for contributing to my bounce-rate.
So there you go, do you want to create a good user experience, or do you want to sell your users out for a pittance?
Have your first user experience in your site be super optimized. Static HTML. Host all assets on your own. Size images correctly. Minimize, then inline the CSS and JS. There are plenty of design-time scripts to automate it. And if you're making SPAs, you can implement all the dynamic loading you want past the initial page because users clicking to open your app are already engaged. But get that first page on-screen in less than a second on a 2G network.
Re: How Google Pagespeed works
#19> 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 Apple when the iTunes team were invalidating ProRes files created from Final Cut Pro.
Re: How Google Pagespeed works
#20> The speed of your site on mobile will affect your overall SEO ranking.
> If your pages load slowly, it will reduce your ad quality score, and ads will cost more.
We've deliberately excluded mobile devices from our ad campaigns. Do I understand correctly that even though we do not serve any mobile visitors at all, we're still judged by the page speed of the mobile page, not just the desktop one?