{"id":520,"date":"2018-01-18T15:19:20","date_gmt":"2018-01-18T15:19:20","guid":{"rendered":"https:\/\/www.searchenginewatch.com\/2018\/01\/18\/what-does-googles-speed-update-mean-for-mobile\/"},"modified":"2019-12-01T15:16:58","modified_gmt":"2019-12-01T15:16:58","slug":"what-does-googles-speed-update-mean-for-mobile","status":"publish","type":"post","link":"https:\/\/searchenginewatch.com\/2018\/01\/18\/what-does-googles-speed-update-mean-for-mobile\/","title":{"rendered":"What does Google&#8217;s &#8220;Speed Update&#8221; mean for mobile?"},"content":{"rendered":"<p><strong>Yesterday, <\/strong><a href=\"https:\/\/webmasters.googleblog.com\/2018\/01\/using-page-speed-in-mobile-search.html\"><strong>Google announced<\/strong><\/a><strong> a major upcoming change to its mobile ranking algorithm.<\/strong><\/p>\n<p>In a short blog post entitled \u2018Using <a href=\"https:\/\/searchenginewatch.com\/2019\/01\/11\/voice-search-optimization-guide-2019\/\">page speed<\/a> in mobile search ranking\u2019, it explained that starting in July 2018, <a href=\"https:\/\/searchenginewatch.com\/2019\/10\/08\/how-to-fix-the-top-most-painful-ux-mistakes-examples\/\">page speed<\/a> will officially be a ranking factor for mobile searches.<\/p>\n<p>The catchily-named \u201cSpeed Update\u201d (a feat of inventive naming on a par with \u201cAssistant\u201d) is set to only affect \u201cpages that deliver the slowest experience to <a href=\"https:\/\/searchenginewatch.com\/2018\/12\/21\/guide-google-analytics-confusing-terms\/\">users<\/a>\u201d and, in <a href=\"https:\/\/searchenginewatch.com\/2019\/05\/31\/image-optimization-for-seo\/\">Google\u2019s<\/a> words, will only impact a \u201csmall percentage of queries\u201d.<\/p>\n<p>However, given that <a href=\"https:\/\/searchenginewatch.com\/2018\/05\/21\/no-need-for-google-12-alternative-search-engines-in-2018\/\">Google<\/a> processes around 3.5 billion search queries per day (per <a href=\"http:\/\/www.internetlivestats.com\/google-search-statistics\/\">Internet Live Stats<\/a>), a \u201csmall percentage\u201d can still amount to a lot of websites.<\/p>\n<p>So for any website owners and SEOs who might be concerned about how this affects them, let\u2019s examine what we know about the update so far, and what it means for <a href=\"https:\/\/searchenginewatch.com\/category\/mobile\/\">mobile SEO.<\/a><\/p>\n<h2><strong>Speed as a ranking factor: coming to a mobile update near you<\/strong><\/h2>\n<p><a href=\"https:\/\/searchenginewatch.com\/2019\/04\/25\/whats-it-like-using-duckduckgo-in-2019\/\">Google<\/a> has used page speed as a ranking factor on desktop <a href=\"https:\/\/webmasters.googleblog.com\/2010\/04\/using-site-speed-in-web-search-ranking.html\">since April 2010<\/a>, but although having a fast mobile site has always stood companies in good stead for ranking well in search, it hasn\u2019t been an official ranking factor in <a href=\"https:\/\/searchenginewatch.com\/2019\/06\/17\/local-seo-guide\/\">Google\u2019s<\/a> algorithm until now.<\/p>\n<p>However, this announcement is far from coming out of left field. As far back as June 2016, <a href=\"https:\/\/searchenginewatch.com\/2019\/07\/11\/seo-lead-site-migration\/\">Google<\/a> webmaster trends analyst Gary Illyes confirmed that the next mobile algorithm update from <a href=\"https:\/\/searchenginewatch.com\/2019\/05\/30\/implement-googles-how-to-schema\/\">Google<\/a> would <a href=\"https:\/\/searchenginewatch.com\/2016\/06\/01\/will-googles-next-mobile-friendly-update-look-at-page-speed\/\">use page speed as a ranking factor<\/a>.<\/p>\n<p>Google has also frequently emphasized the importance of speed in mobile user experience in its advice to webmasters, and <a href=\"https:\/\/searchenginewatch.com\/2019\/05\/20\/seven-reasons-why-your-rankings-dropped-and-how-to-fix-them\/\">Google<\/a> initiatives like <a href=\"https:\/\/searchenginewatch.com\/2018\/04\/09\/an-seos-survival-guide-to-single-page-applications-spas\/\">Accelerated Mobile Pages<\/a> and Progressive Web Apps have aimed to furnish site owners with the <a href=\"https:\/\/sewprod.wpenginepowered.com\/2019\/07\/15\/keyword-research-tools-free\/\">tools<\/a> to make their websites fast and streamlined on mobile.<\/p>\n<p>The \u201cSpeed Update\u201d announcement doesn\u2019t give all that much new information about how website owners should improve their sites in order to rank well on <a href=\"https:\/\/searchenginewatch.com\/2019\/06\/10\/online-reviews-powerful-seo-weapons\/\">Google<\/a>, but here\u2019s what we do know:<\/p>\n<ul>\n<li>Speed Update will mainly impact the websites which deliver the \u201cslowest experience\u201d to users, although Google hasn\u2019t given a benchmark by which webmasters can judge whether or not their site falls into this category.<\/li>\n<li>It applies regardless of the technology used to build the page \u2013 so it would still apply to, say, AMP websites. If an AMP website for some reason delivers a slow experience, this would impact on its ranking.<\/li>\n<li>Content relevance still trumps speed. In Google\u2019s words, \u201cThe intent of the search query is still a very strong signal, so a slow page may still rank highly if it has great, relevant content.\u201d<\/li>\n<li>Google wants developers to \u201cthink broadly about how\u00a0performance\u00a0affects a user\u2019s experience of their page and to consider a variety of\u00a0user experience metrics.\u201d This means user experience matters as well as speed \u2013 we\u2019ll come back to that in a bit.<\/li>\n<li>There is no tool or notification that will tell webmasters whether their site is being affected by the update, but Google recommends using <a href=\"https:\/\/developers.google.com\/web\/tools\/chrome-user-experience-report\/\">Chrome User Experience Report<\/a>, <a href=\"https:\/\/developers.google.com\/web\/tools\/lighthouse\/\">Lighthouse<\/a> or <a href=\"https:\/\/developers.google.com\/speed\/pagespeed\/insights\/\">PageSpeed Insights<\/a> to evaluate a page\u2019s performance.<\/li>\n<\/ul>\n<h2><strong>Spotlight on mobile user experience<\/strong><\/h2>\n<p>As highlighted earlier, the language used by Google in its blog post indicates that the <a href=\"https:\/\/searchenginewatch.com\/2018\/05\/21\/no-need-for-google-12-alternative-search-engines-in-2018\/\">search engine <\/a>is looking at not just speed, but overall mobile user experience with this update.<\/p>\n<p>Google went so far as to spell this out in a <a href=\"https:\/\/searchengineland.com\/faqs-new-google-speed-update-amp-pages-search-console-notifications-desktop-pages-289929\">Q&amp;A<\/a> with Search Engine Land, saying that, \u201cThe intent of the signal is to improve the user experience on search.\u201d<\/p>\n<p>In other words, site owners who want to score highly here need to pay attention to more than just page load time. This is underscored by Google\u2019s recommendation of the Chrome User Experience Report as a tool to evaluate webpage performance in light of the update.<\/p>\n<p>A lot of improvements to mobile page speed also improve the wider user experience on mobile \u2013 for example, videos and audio set to autoplay are annoying and inaccessible to users, and also slow the page down by loading unnecessary content \u2013 meaning that site owners can kill two birds with one stone.<\/p>\n<p>Other steps that site owners can take to improve mobile UX include disabling annoying full-page pop-ups and interstitials (which Google is liable to penalize anyway) and implementing a slimmed-down, task-based design\u00a0that\u00a0allows users to quickly navigate to the functionality they need.<\/p>\n<p>Above all, a mobile website should enable users to efficiently accomplish what they came there to do, without being bogged down by unnecessary bells and whistles. If you achieve this, you should be able to stay on the right side of the Speed Update algorithm both in terms of page performance and in terms of mobile experience.<\/p>\n<p>Here are some more guides we\u2019ve published that will help you get to grips with <a href=\"https:\/\/searchenginewatch.com\/2018\/01\/23\/how-to-get-started-with-local-seo\/\">mobile SEO<\/a>, site speed and UX ahead of the July update:<\/p>\n<h3><strong>Mobile SEO<\/strong><\/h3>\n<ul>\n<li><a href=\"https:\/\/searchenginewatch.com\/2017\/12\/18\/how-to-carry-out-a-mobile-seo-audit-on-your-site\/\">How to carry out a mobile SEO audit on your site<\/a><\/li>\n<li><a href=\"https:\/\/searchenginewatch.com\/2017\/10\/03\/the-5-best-tools-to-develop-a-mobile-first-seo-strategy\/\">The 5 best tools to develop a mobile-first SEO strategy<\/a><\/li>\n<li><a href=\"https:\/\/searchenginewatch.com\/2017\/08\/04\/mobile-seo-the-3-areas-that-really-matter-for-seo-performance\/\">Mobile SEO: The 3 areas that really matter for SEO performance<\/a><\/li>\n<li><a href=\"https:\/\/searchenginewatch.com\/2016\/05\/17\/how-do-i-make-sure-my-site-is-mobile-friendly\/\">How do I make sure my site is mobile friendly? A checklist<\/a><\/li>\n<\/ul>\n<h3><strong>Mobile site speed<\/strong><\/h3>\n<ul>\n<li><a href=\"https:\/\/searchenginewatch.com\/2017\/06\/02\/how-to-optimize-your-mobile-site-speed-testing-for-issues\/\">How to optimize your mobile site speed: Testing for issues<\/a><\/li>\n<li><a href=\"https:\/\/searchenginewatch.com\/2017\/06\/09\/how-to-reduce-the-impact-of-images-on-your-mobile-site-speed\/\">How to reduce the impact of images on your mobile site speed<\/a><\/li>\n<li><a href=\"https:\/\/searchenginewatch.com\/2017\/06\/16\/how-to-optimize-images-for-mobile-implementing-light-responsive-correctly-formatted-images\/\">How to optimize images for mobile: Implementing light, responsive, correctly formatted images<\/a><\/li>\n<li><a href=\"https:\/\/searchenginewatch.com\/2017\/06\/23\/how-javascript-impacts-page-loading-speed-on-mobile\/\">How JavaScript impacts page loading speed on mobile<\/a><\/li>\n<\/ul>\n<h3><strong>Mobile UX<\/strong><\/h3>\n<ul>\n<li><a href=\"https:\/\/searchenginewatch.com\/2017\/05\/11\/how-video-impacts-mobile-web-performance-and-ux\/\">How video impacts mobile web performance and UX, part 1: data and download speed<\/a><\/li>\n<li><a href=\"https:\/\/searchenginewatch.com\/2017\/05\/19\/how-video-impacts-mobile-web-performance-and-ux-part-2-autoplay-and-audio\/\">How video impacts mobile web performance and UX, part 2: autoplay and audio<\/a><\/li>\n<li><a href=\"https:\/\/searchenginewatch.com\/2017\/05\/26\/how-video-impacts-mobile-web-performance-and-ux-part-3-detecting-and-remedying-issues\/\">How video impacts mobile web performance and UX, part 3: detecting and remedying issues<\/a><\/li>\n<li><a href=\"https:\/\/searchenginewatch.com\/2016\/08\/25\/why-mobile-commerce-sites-should-be-designed-for-context\/\">Why mobile commerce sites should be designed for context<\/a><\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Yesterday, Google announced a major upcoming change to its mobile ranking algorithm. What do we know so far about Google&#8217;s &#8220;Speed Update&#8221;, and what does it mean for mobile SEO?<\/p>\n","protected":false},"author":77,"featured_media":521,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[12,11],"tags":[37,507,92,272,508,509,108,510,511],"content_type":[27095],"class_list":["post-520","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-mobile","category-more-news","tag-google","tag-mobile-algorithm","tag-mobile-page-speed","tag-mobile-seo","tag-mobile-update","tag-mobile-ux","tag-mobile-first-index","tag-page-speed","tag-speed-update","content_type-news"],"acf":{"tad_independentcommercial":false,"tad_content_format":false},"post_info":{"name":"Rebecca Sentance","title":"","thumbnail_url":"https:\/\/searchenginewatch.com\/wp-content\/uploads\/2018\/10\/mobile-speed-120x90.jpg","category":"Mobile","timeago":"8y"},"_links":{"self":[{"href":"https:\/\/searchenginewatch.com\/wp-json\/wp\/v2\/posts\/520","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/searchenginewatch.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/searchenginewatch.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/searchenginewatch.com\/wp-json\/wp\/v2\/users\/77"}],"replies":[{"embeddable":true,"href":"https:\/\/searchenginewatch.com\/wp-json\/wp\/v2\/comments?post=520"}],"version-history":[{"count":0,"href":"https:\/\/searchenginewatch.com\/wp-json\/wp\/v2\/posts\/520\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/searchenginewatch.com\/wp-json\/wp\/v2\/media\/521"}],"wp:attachment":[{"href":"https:\/\/searchenginewatch.com\/wp-json\/wp\/v2\/media?parent=520"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/searchenginewatch.com\/wp-json\/wp\/v2\/categories?post=520"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/searchenginewatch.com\/wp-json\/wp\/v2\/tags?post=520"},{"taxonomy":"content_type","embeddable":true,"href":"https:\/\/searchenginewatch.com\/wp-json\/wp\/v2\/content_type?post=520"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}