{"id":25135,"date":"2020-05-28T00:00:00","date_gmt":"2020-05-28T00:00:00","guid":{"rendered":"https:\/\/alienroad.com\/google-bilgi-bankasi\/evaluating-page-experience-for-a-better-web\/"},"modified":"2020-05-28T00:00:00","modified_gmt":"2020-05-28T00:00:00","slug":"evaluating-page-experience-for-a-better-web","status":"publish","type":"ar_kb","link":"https:\/\/alienroad.com\/google-bilgi-bankasi\/evaluating-page-experience-for-a-better-web\/","title":{"rendered":"Evaluating page experience for a better web"},"content":{"rendered":"<p class=\"gargardate\">Thursday, May 28, 2020<\/p>\n<aside class=\"key-point\">It&#8217;s been a while since we published this blog post. Some of the information may be outdated (for example, some images may be missing, and some links may not work anymore). Check out our updated documentation on <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/core-web-vitals\/\">page experience<\/a>.<\/aside>\n<p>\n    Through both <a href=\"https:\/\/ai.googleblog.com\/2009\/06\/speed-matters.html\" class=\"external-link\">internal studies<\/a> and<br \/>\n  <a href=\"https:\/\/blog.chromium.org\/2020\/05\/introducing-web-vitals-essential-metrics.html\" class=\"external-link\">industry research<\/a>,<br \/>\n    users show they prefer sites with a great page experience. In recent years, Search has added a<br \/>\n    variety of user experience criteria, such as<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/using-page-speed-in-mobile-search-ranking\/\">how quickly pages load<\/a> and<br \/>\n    <a href=\"https:\/\/developers.google.com\/search\/mobile-sites\">mobile-friendliness<\/a>, as factors for ranking results. Earlier<br \/>\n    this month, the Chrome team announced<br \/>\n    <a href=\"https:\/\/blog.chromium.org\/2020\/05\/introducing-web-vitals-essential-metrics.html\" class=\"external-link\">Core Web<br \/>\n      Vitals<\/a>, a set of metrics related to speed, responsiveness and visual stability, to help<br \/>\n    site owners measure user experience on the web.\n   <\/p>\n<p>\n     Today, we&#8217;re building on this work and providing an early look at an upcoming Search ranking<br \/>\n     change that incorporates these page experience metrics. We will introduce a new signal that<br \/>\n     combines Core Web Vitals with our existing signals for page experience to provide a holistic<br \/>\n     picture of the quality of a user&#8217;s experience on a web page.\n   <\/p>\n<p>\n    As part of this update, we&#8217;ll also incorporate the page experience metrics into our ranking<br \/>\n     criteria for the Top Stories feature in Search on mobile, and remove the AMP requirement from<br \/>\n     Top Stories eligibility. Google continues to support AMP, and will continue to link to AMP<br \/>\n     pages when available. We&#8217;ve also updated our developer tools to help site owners optimize their<br \/>\n     page experience.\n   <\/p>\n<p>\n    <b>A note on timing<\/b>: We recognize many site owners are rightfully placing their focus on<br \/>\n     responding to the effects of COVID-19. The ranking changes described in this post will not<br \/>\n     happen before next year, and we will provide at least six months notice before they&#8217;re rolled<br \/>\n     out. We&#8217;re providing the tools now to get you started (and because site owners have<br \/>\n     consistently requested to know about ranking changes as early as possible), <b>but there is no<br \/>\n     immediate need to take action<\/b>.\n   <\/p>\n<h2 id=\"about-page-experience\" tabindex=\"-1\">\n     About page experience<br \/>\n   <\/h2>\n<p>\n    The <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/core-web-vitals\/\">page experience<\/a> signal measures aspects of<br \/>\n     how users perceive the experience of interacting with a web page. Optimizing for these factors<br \/>\n     makes the web more delightful for users across all web browsers and surfaces, and helps sites<br \/>\n     evolve towards user expectations on mobile. We believe this will contribute to business success<br \/>\n     on the web as users grow more engaged and can transact with less friction.\n   <\/p>\n<p>\n     <a href=\"https:\/\/web.dev\/articles\/vitals#core-web-vitals\" class=\"external-link\">Core Web Vitals<\/a> are a set of real-world,<br \/>\n     user-centered metrics that quantify key aspects of the user experience. They measure dimensions<br \/>\n     of web usability such as load time, interactivity, and the stability of content as it loads (so<br \/>\n     you don&#8217;t accidentally tap that button when it shifts under your finger &#8211; how annoying!).\n   <\/p>\n<p>   <video alt=\"A screencast illustrating how layout instability can negatively affect users.\" \nautoplay=\"\" class=\"w-screenshot\" controls=\"\" height=\"510\" loop=\"\" muted=\"\" width=\"100%\"\n          poster=\"\/search\/blog\/images\/Accidental_Submit_Still.webp\"><source src=\"https:\/\/developers.google.com\/static\/search\/blog\/images\/AccidentalSubmit.webm\" type=\"video\/webm; codecs=vp8\" \/><source src=\"https:\/\/developers.google.com\/static\/search\/blog\/images\/AccidentalSubmit.mp4\" type=\"video\/mp4; codecs=h264\" \/><\/video><\/p>\n<p>\n     We&#8217;re combining the signals derived from Core Web Vitals with our existing Search signals for<br \/>\n     page experience, including<br \/>\n     <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/finding-more-mobile-friendly-search-results\/\">mobile-friendliness<\/a>,<br \/>\n     <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/heres-to-more-https-on-the-web\/\">HTTPS-security<\/a>, and<br \/>\n     <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/helping-users-easily-access-content-on-mobile\/\">intrusive interstitial guidelines<\/a>,<br \/>\n     to provide a holistic picture of page experience. Because we continue to work on identifying<br \/>\n     and measuring aspects of page experience, we plan to incorporate more page experience signals<br \/>\n     on a yearly basis to both further align with evolving user expectations and increase the<br \/>\n     aspects of user experience that we can measure.\n   <\/p>\n<p>\n    <img decoding=\"async\" alt=\"A diagram illustrating the components of Search's signal for page experience.\"\n         src=\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-41a1ecb52ba9.png\" loading=\"lazy\" \/>\n   <\/p>\n<h2 id=\"page-experience-ranking\" tabindex=\"-1\">\n   Page experience ranking<br \/>\n  <\/h2>\n<p>\n    Great page experiences enable people to get more done and engage more deeply; in contrast, a<br \/>\n    bad page experience could stand in the way of a person being able to find the valuable<br \/>\n    information on a page. By adding page experience to the hundreds of signals that Google<br \/>\n    considers when ranking search results, we aim to help people more easily access the information<br \/>\n    and web pages they&#8217;re looking for, and support site owners in providing an experience users<br \/>\n    enjoy.\n  <\/p>\n<p>\n    For some developers, understanding how their sites measure on the Core Web Vitals\u2014and addressing<br \/>\n    noted issues\u2014will require some work. To help out, we&#8217;ve <a href=\"https:\/\/web.dev\/articles\/vitals-tools\" class=\"external-link\">updated<\/a><br \/>\n    popular developer tools such as Lighthouse and PageSpeed Insights to surface Core Web Vitals<br \/>\n    information and recommendations, and Google Search Console provides a dedicated<br \/>\n    <a href=\"https:\/\/support.google.com\/webmasters\/answer\/9205520\" class=\"external-link\">report<\/a> to help site owners<br \/>\n    quickly identify opportunities for improvement. We&#8217;re also working with external tool developers<br \/>\n    to bring Core Web Vitals into their offerings.\n  <\/p>\n<p>\n    While all of the components of page experience are important, we will prioritize pages with the<br \/>\n    best information overall, even if some aspects of page experience are subpar. A good page<br \/>\n    experience doesn&#8217;t override having great, relevant content. However, in cases where there are<br \/>\n    multiple pages that have similar content, page experience becomes much more important for<br \/>\n    visibility in Search.\n  <\/p>\n<h2 id=\"page-experience-and-the-mobile-top-stories-feature\" tabindex=\"-1\">\n    Page experience and the mobile Top Stories feature<br \/>\n   <\/h2>\n<p>\n      The mobile Top Stories feature is a premier fresh content experience in Search that currently<br \/>\n      emphasizes AMP results, which have been optimized to exhibit a good page experience. Over the<br \/>\n      past several years, Top Stories has<br \/>\n      <a href=\"https:\/\/blog.amp.dev\/2018\/03\/08\/standardizing-lessons-learned-from-amp\/\" class=\"external-link\">inspired<\/a><br \/>\n      new thinking about the ways we could promote better page experiences across the web.\n    <\/p>\n<p>\n     When we roll out the page experience ranking update, we will also update the eligibility<br \/>\n     criteria for the Top Stories experience. AMP will no longer be necessary for stories to be<br \/>\n     featured in Top Stories on mobile; it will be open to any page. Alongside this change, page<br \/>\n     experience will become a ranking factor in Top Stories, in addition to the many factors<br \/>\n     assessed. As before, pages must meet the<br \/>\n     <a href=\"https:\/\/support.google.com\/news\/publisher-center\/answer\/6204050\" class=\"external-link\">Google News content<br \/>\n       policies<\/a> to be eligible. Site owners who currently publish pages as AMP, or with an AMP<br \/>\n     version, will see no change in behavior \u2013 the AMP version will be what&#8217;s linked from Top<br \/>\n     Stories.\n    <\/p>\n<h2 id=\"summary\" tabindex=\"-1\">\n    Summary<br \/>\n   <\/h2>\n<p>\n      We believe user engagement will improve as experiences on the web get better&mdash;and that by<br \/>\n      incorporating these new signals into Search, we&#8217;ll help make the web better for everyone. We<br \/>\n      hope that sharing our roadmap for the page experience updates and launching supporting tools<br \/>\n      ahead of time will help the diverse ecosystem of web creators, developers, and businesses to<br \/>\n      improve and deliver more delightful user experiences.\n    <\/p>\n<p>\n     Please stay tuned for our future updates that will communicate more specific guidance on the<br \/>\n     timing for these changes to come into effect. As always, if you have any questions or feedback,<br \/>\n     visit our <a href=\"https:\/\/support.google.com\/webmasters\/community\/\" class=\"external-link\">webmaster<br \/>\n     forums<\/a>.\n    <\/p>\n<p>\n    <span class=\"byline-author\">Posted by<br \/>\n      <a href=\"https:\/\/twitter.com\/sosubram\" class=\"external-link\">Sowmya Subramanian<\/a>, Director of Engineering for Search Ecosystem<br \/>\n    <\/span>\n  <\/p>\n<hr>\n<h2 id=\"updates\" tabindex=\"-1\">\n  Updates<br \/>\n<\/h2>\n<ul>\n<li><b>Update on June 15, 2021<\/b>: The page experience update is rolling out to all users globally.<br \/>\n    It will be complete by the end of August 2021.<\/li>\n<li><b>Update on August 4, 2021<\/b>:<br \/>\n    <a href=\"https:\/\/alienroad.com\/google-bilgi-bankasi\/simplifying-the-page-experience-report\/\">Clarified that Safe Browsing isn&#8217;t used as a ranking signal<\/a>.<br \/>\n    Safe Browsing systems continue to play an important role to keep users of Google Search safe,<br \/>\n    and any flags will continue to be surfaced in Search Console outside of Page Experience<br \/>\n    report.<\/li>\n<li><b>Update on January 31, 2024<\/b>:<br \/>\n      <a href=\"https:\/\/web.dev\/blog\/inp-cwv-march-12\" class=\"external-link\">Interaction to Next Paint (INP) will replace FID<\/a><br \/>\n      as a part of Core Web Vitals on March 12, 2024.<\/li>\n<li><b>Update on March 12, 2024<\/b>:<br \/>\n    <a href=\"https:\/\/web.dev\/blog\/inp-cwv-launch\" class=\"external-link\">Interaction to Next Paint (INP) has replaced FID<\/a> as a part of Core Web Vitals.\n  <\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Thursday, May 28, 2020 It&#8217;s been a while since we published this blog post. Some of the information may be outdated (for example, some images may be missing, and some links may not work anymore). Check out our updated documentation on page experience. Through both internal studies and industry research, users show they prefer sites [&hellip;]<\/p>\n","protected":false},"menu_order":81590,"template":"","meta":{"footnotes":""},"ar_kb_kategori":[665],"ar_kb_etiket":[],"class_list":["post-25135","ar_kb","type-ar_kb","status-publish","has-post-thumbnail","hentry","ar_kb_kategori-blog"],"_links":{"self":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/25135","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb"}],"about":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/types\/ar_kb"}],"version-history":[{"count":0,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb\/25135\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media\/27258"}],"wp:attachment":[{"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/media?parent=25135"}],"wp:term":[{"taxonomy":"ar_kb_kategori","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_kategori?post=25135"},{"taxonomy":"ar_kb_etiket","embeddable":true,"href":"https:\/\/alienroad.com\/wp-json\/wp\/v2\/ar_kb_etiket?post=25135"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}