 Hey guys, thanks for tuning in to our new hackathon on air Today, we're gonna speak about the SEO speed update. You've probably heard about it. It's Quite a big update. That's coming in July 2018 So we thought it would be good to bring someone on the hackathon on air that's working in the SEO field at Google So that's Vincent who's joining us today In case you want to follow us on Twitter, we're all like quite active there So if you have any questions following this live stream Any questions related to it just you know, she does a message follow us and we're more than happy to support you as much as we can So as you most of you know, I'm Dominic I work in mobile ex in at Google in London and with us today is Dennis and Vincent So I'll give it over to Dublin to so they have a chance to introduce themselves Yeah, hi everybody, thanks for tuning in again. Hello from snowy Dublin. I brought Vincent with me He's our expert for today. So he will He will be able to answer hopefully all the questions you have around mobile speed and the mobile speed update So Vincent, maybe you want to introduce yourself? Yeah, so I'm Vincent Corson. I've been working at Google for almost six years I work in a team called the search quality team and my job is basically to Speak and listen to the ecosystems of people that are interested in the organic search engine that Google provides To improve our products and to make sure that the messages that our engineering teams want to make clear to the public are actually communicated I usually focus on the French markets emerging French But basically I was invited by Dom and Dennis here to talk to all you today about the speed update So I'm delighted to do this. It's great to have you on the stream Well, I'd say without further ado, just jump into the content and see What there is we can talk about So I guess most of you have heard already about our speed update I think we announced it like almost two months ago. No, I think was announced in January So starting in July 2018 page speed will be a ranking factor for mobile searches That's like the bottom line, I guess but there is a little bit more to it So and if you want to read more about it, you just can follow this handy short link And they will have the whole blog post but And that's why we also brought Vincent to give you a little bit more of context tears of Vincent Maybe you can tell us a little bit more about the speed up way. Yeah, definitely So whenever there is an update to Google's algorithms in search engine The first question is what's changing? Am I impacted? What's happening? Is it a big one? It's actually much more than one question. So there are quite a few questions So I'm gonna try to highlight just a few points here to give the scope and impact of this updates and Then and then we'll take questions later on during the during the event. So the first thing of note is that This is a change that is in continuity with the direction that we have been going to for the past decade basically page speed How fast a URL the contents of a URL actually load on a user's device has already been a ranking factor or Desktop searches or about seven to eight years. So it's nothing new in the desktop world What is happening is that soon in July 2018? It's going to be also the case for mobile queries Whatever the mobile device. So this is in this was announced in the first half of January and it's planned for July 2018 the reason that we give that much of a heads up is that we have heard from the community of SEOs SEO professionals website owners small and big companies, etc Is that for some of the updates they would have like more of a head of heads up? So we've done this now for a few of our updates and this one doesn't change. We try to give a heads up Then the next question is What sort of impact does it have so here? We basically don't expect a majority of the queries entered by users to be impacted by this subject It should be a small percentage of the queries. We are not really in a position to communicate specifics of which queries etc But know that it's it's it should not be an Change an update that will have a major impact on all of your queries. It's it's quite targeted in terms of what Pages what content will actually be impacted by this change This is an update that is more about making sure that the very slow pages Don't necessarily show up as much as up as currently rather than making sure the very fast pages Show up. So I'm not saying that you shouldn't really optimize for speed What I'm saying is that the only pages that should be Impacted are the ones that really really have a very long loading time and have a very poor experience for users So we're gonna go over some of what that means in terms of metrics to follow etc in the next few slides So this is the general scope of these updates and now I'll hand over to Dom for For a bit more information on the tools that exist Yeah, well Tom so what can we do to actually not get surprised by the speed of that in terms of How can we mainly measure speed? How can we optimize for that? Could you give us a few ideas here? Yeah, sure. I think first of all What when Vincent already said it's really important that we have given everyone a heads up So it really shouldn't be a surprise to anyone However, we do know that some people like to lie, you know, leave things at the last minute and You know, then obviously it can become quite tricky to to be ready for it So I think the most important thing is to really Understand where are you at with your site? so There are a whole bunch of performance tools out there and they all do have, you know, different ways of measuring page speed So we just picked four here That are not all Google-owned For example, web page test web page test is a kind of like a third-party tool however that we do frequently use and It's really important to use a variety of tools to get a better understanding of the current performance of your site So there is Lighthouse, which we've been talking about quite a lot recently It's a really nice optimization tool that sits within Chrome DevTools And it allows you to run certain audits on your sites to get Results about how do I perform in terms of speed? How do I perform in terms of accessibility? How do I perform in terms of SEO, which is a which is a new audit that was included into Lighthouse? This is a really great tool and it's not just for developers because it is sitting in DevTools And if you are familiar with DevTools, definitely make use of it. However, it also exists as a Chrome extension So basically whatever URL you're on you can just hit a little icon and it will auto-generate a report giving you a lot of information From which basically you can Create a little roadmap and decide what you actually want to focus on Another great performance tool is Chrome DevTools itself There are different tabs and you can really dig like dig deep into performance to see what is going on in a browser's Browser's main thread what is blocking the rendering the parsing and how can you action up on that to make sure that You improve the critical rendering path because what really matters is that you bring content to the screen as quickly as possible Then there is PageSpeed Insights, which probably most of you know, it's Quite quite an old tool However, we recently launched a version 2 of it which now includes data from the Chrome user experience report Which is really nice because for the first time we're you know, we're not testing speed based on some Testing environment that we came up with but we're actually taking the real user data that accesses your site And and show you how long did it take for the user to load the most critical content So so we believe that that's a really really great tool So definitely check it out and see what is the score for the first contentful paint? What is the score for the on-load event? And then you will also get in like a little graph that will show you Where do you where are you at in terms of like your competition like we're we're showing you? Are you in the fast section of your vertical or in the medium section or the slow section? And that will also give you an idea whether you should focus on performance optimization or not Last but not least web page test, which is a tool that powers currently test my site the the Google tool and web page test really is a very sophisticated tool that allows you to Test your site under various circumstances So you can set up different testing environments and then you can see how do you perform? You will get back a waterfall So you know exactly you which resource is being loaded where and how does it impact this the speed of your Speed of your website. So really that's the The first thing you should do is like familiarize yourself with the performance tools and get an idea Where are you currently at and then you can make the decision whether you should make an effort to improve speed? To be ready for July 2018 or if you're already Getting good results, then maybe you want to focus on something else like user experience improvement So there's you know, there's obviously a lot of stuff you can do That will give you a good idea what you should focus on and prioritize If we jump to the next slide For those of you that want to learn a bit more on the performance tools we have done like we have covered all of this content in Previous hackathon on air. So I put those two short links on the slide There is one hackathon on air that Covers pretty much all performance tools and then there is one hackathon on air That really digs deep onto Chrome developer tools and shows you what's possible with with this performance tool so I really really Suggest that you check it out, you know Have a look if there are certain tools that you're familiar with just you know Jump that part of the content and see if there's anything you can extract from it We also have a ton of other videos on Optimization where you can get like really valuable information that will help you to to get ready for July 2018 So we'll just leave the slide on maybe for a couple more seconds so everyone can take the short links And then we'll move on to I can interrupt you down a very The one of these formats the YouTube hackathon on air is that you when you watch them you can ask questions and People try to answer them live and it's the same for this Specific YouTube library and currently there's already two questions that came in in the chat But don't hesitate to add yours so that we'll try to answer them as we go Perfect. Yeah, let's jump to the next slide here I hope everybody got the chance to have a look at the short links Otherwise, you also will find our event page in the description Shortly so you can also just head there there you find the whole repository of all the videos we've done so far Might it might be worth having a look and see if there's something you might be interested in I think another really really cool feature. We just announced a few days ago is our new speeds for a card Actually fitting sitting in our thing with Google and mobile hub now I think it's really nice because it lets you basically compare your site to other sites or maybe could be competitors But also be subsides of your of your own sites, of course And it also uses the crux the Chrome user experience reports as Tom said before You actually get a feeling of how does my site out in the wild? You don't have to rely on synthetic laboratory data. This is real actual user data So I think that's kind of cool. You can also choose here I think as of now we have 12 Geos added and there will be more but all the major markets should be covered already You can choose your connection speed. So maybe check out if there's a difference between 3g or 4g Are you particularly good or maybe not so good in one of the speeds itself You can compare up to 10 different URLs, which is kind of cool So if you're in a highly competitive market, this might be very handy as well to see like How am I sticking up against my competition? Especially if it's like a very competitive market usually it's It can be really handy to be just faster like just being having a faster site Can make a huge difference in these markets then Well, just a side note the speed scorecard shows the 90th percentile of first contentful paint So this is how the speed is actually measured and the ranking is a combination of first contentful paint thumb content loaded and unload Again, if you might want to learn more about these metrics Just have a look at the videos we posted before and especially in the web performance tools Hackathon and air we're explaining a bit more like which content or which metric to look at to Pick certain problems or get certain information I think another cool thing that is yeah, it's on the same side. We also released it with our speed scorecard It's our new impact calculator Potentially a bit more interesting for for the marketeers and SEO specialists out there. Maybe But this is more of a like how does speed impact the business side of things so you add a few metrics there And then you can basically see if I'll be like one or two seconds faster What would that do with my potential revenues? So what would be the incremental revenue by let's say increasing my sites My sites loading time by two seconds So this is kind of cool, especially if you need maybe buy in to get more Development resources and you need to convince someone this could be a good way to actually start this conversation saying look Performance might not be the shiniest of all things But there is an actual return on investment So it is really worth investing in performance because it will increase And this might give you the option Actually work on your side Cool. So I would like to give it back to Dom Dom Maybe you can maybe you can tell us a little bit about the top speed offenders We usually call them and what to look out for from a technical point of view if I want to improve my side Yeah, sure Definitely, that's actually a great picture and I believe Dennis you took that really like right. Well, I was from Hong Kong Yeah, I really like Containers shot That's amazing Yeah, so what's what's slowing down your side? You know, it's it's kind of like I think we already talked about it so many times yet It's you know, kind of like the top speed offenders. They don't change So that's why we want to talk about a few things that are typically the the reasons why your side is slow And that is prioritizing content CSS JavaScript and images So starting off it is incredibly important to prioritize your content correctly Purely because if you are loading a lot of stuff that's actually not Let's say visible on the mobile device And it is still being downloaded. It will it is still being prioritized by the browser and then maybe it's It's you know, that the browser will hide it Hence like you're kind of like waiting for resources to be loaded and and then the resources are not actually shown on the screen And the resources that are actually important you have to wait even longer for so it's really really important To focus on what is the most critical content and making sure that This critical content is loaded is loaded first There are some ways to to give a browser a hint that a certain resource is important or maybe not that important So definitely check out preload and prefetch preload is A value for the rel attribute that basically allows it to give the browser a hint and say hey this resource is is really important Please try to load it as quickly as possible Whereas prefetch is doing the opposite. It's usually used for resources that might be used You know in the future in future navigation. So you're telling the browser You know, I still want to load this resource But can you please you know load it at the lowest priority possible because I don't really need it right now We also have a hackathon on air on that specific topic. So Definitely check it out as well If you want to learn more about preload prefetch pre render Etc and definitely make sure that you prioritize the content correctly because it can make a huge difference if you do The the second thing to focus on would be css Most of you probably know that css blocks the rendering of the page because obviously the css Can you know like layouts the page so the browser has to wait until it's fully loaded and And understood so definitely make sure that you have a strategy behind the css Ideally you want to load the critical css first and if if you can load it in line That's even better because you're not You don't need to make the the server request to get your css file If you can't load it in line fine, but definitely try to load the critical css first Any additional css it can you know you can still load it and you can still cache it just to make you know Kind of like to make sure that you don't sort of delay the The slow user experience to the second or third page But additional css should be loaded asynchronously or via prefetch So this is super critical and The next thing you should focus on is javascript the problem is somewhat similar javascript is parser blocking so When the browser downloads a document and parses through the document and hits a javascript file it stops pausing to download the javascript and execute it And obviously during that time You you have delays Usually the the blank screen and nothing is being rendered So that's why we say if possible of avoid large javascript libraries or files purely because of the effect that it's parser blocking Make sure that You use javascript only if it's really necessary. So like no over engineering If you don't really use it need it And if you need to load javascript libraries try to load load them async or defer That will guarantee that you're downloading the libraries and you can execute them However, you do all that without blocking the parser So definitely look into that in case you're not familiar with it But it's it's crucial to paint the content as quickly to the screen as possible And last but not least and that's probably one of the most well known speed offenders. It's images Obviously images are super important and there are certain verticals where it's more important than others On average images account for about 63 of a pages weight And and that's quite a lot and there are certain Certain verticals where that even goes up into the 80s so It's really really important to optimize images because especially if you're on a slow connection It can delay the rendering process a lot because If you're an HTTP one and if you're on a 3g connection You have six concurrent connections if you're then downloading large images You have like a bandwidth exhaustion and it takes quite a while until a large image is being downloaded So definitely follow the steps of reducing the quality or possible If you have an e-commerce shop and say I really need high quality images because what I'm selling is a high quality product That there are still the ability to load a lower resolution for a lower resolution image first And once you sort of like structured your side and you show some show some content You can swap it out for a high quality image Always make sure to compress images Because you can save up to 70 80 percent of the of the file size by just compressing the images damage properly And then it's really important to lazy load content. That's below the fold We keep suggesting that because it makes such a big difference If you have a lot of images that show below the fold There's no need to download all of this for your users If some of them might not even scroll all the way down So it's a really good way to reduce the server requests and free up some bandwidth for more important stuff And the implementation of the lazy loading is pretty straightforward. There are some very tiny javascript javascripts that lets you basically Yeah, lazy load by adding a simple class to into an image tag So those are the four stop top speed offenders. Obviously, there's much more there like redirects You know, you could be looking at restructuring your content So there's a much there's a lot more going on where you know where you can improve But we would say those four focus areas if you have sorted them out, you're probably in a really good shape Maybe one point to add to the lazy loading because I just recently had a question that um Is there a certain threshold where you would start lazy loading done? Is it like just below the fold or is it one and a half above the fold? Do you know what I mean? And when should I start lazy loading because there might be users who actually scroll a little bit right away So would it make sense to yeah, maybe yeah have one and a half above the fold content's not lazy loaded and done start Yeah, I think it's a good idea definitely Because you do sometimes have the sensation that when you scroll down and you're lazy loading that for a short period of time You see either a gray background or a spinner because you were pulling in the image at that point Um, so yeah, definitely. Um, that's a that's a great idea to say. Okay one and a half From from the top. I don't lazy load the images and everything below that I actually do Lazy load the images. So yeah, thanks Dennis for for that and I just look at the chat and um I want to pick up a question because it fits in nicely here And the question is coming from Muhammad and he's asking will amp resolve this well You know, it's it's like how should we answer it like amp basically follows Certain best practices. So if you think about it that amp reduces or or limits the file size of the css resource to 50 kilobytes A amp requires the css to be in line amp requires images to Always have a height and a width Defined so that the browser can lay out the page without actually having the the image ready yet So if you take if you keep that in mind then that is one of the reasons amp is so fast So if you follow the same best practices, um, you can also speed up a non amp page You know probably to up to the same standard, but sure amp is You know, it's great if you want to quickly speed up your site and follow the best practices that um that amp requires And just quickly before I give it back to Dublin Um, in case you wonder back, you know in the previous hackathon on errors we always had a lot of slides and We decided that this time we want to make it more interactive So that's what we have less content from our side and we have some questions prepared and we're also looking at the chat So that's why we want to make it interactive now and Give it up to Vincent who will be able to answer all the great questions that are coming in. So Vincent, please. Thank you dom For all the updates. So once again use the chat To let us know your live questions and we'll try to answer them The on mobile at the very bottom of the the page In the youtube app you have a little banner that's Foldable that says top chat and you can chat in there and that's that's your questions. So To come back as well to the to muhammad's question about How amp fits into this this whole speed update story? Going away from just the performance aspect, but to the To the speed update really the seo algorithm updates A question that we've that that i've had to answer several times and that we get often in our support forums and in other communities is Well, does that mean that if I use amp my pages will basically not be impacted by the speed update Doesn't mean that google is forcing its technology accelerated mobile pages By using the speed update. So to answer that question I would say no because the speed update is technology agnostic if you will That means that basically What's the speed update focuses on is mostly what happens on the user's device Notwithstanding the technology. So maybe someone is using full html css usual frameworks and Their page is super fast and then maybe someone is using amp, but they implemented it in a weird way And then the page is actually really not loading that fast on users On users devices and then that might be negative for them in terms of the the seo world, right? So this is not as simple as amp equal. I'm safe everything else. Everything else. I'm not safe I think another point here, which is good to mention. I'll just Getting this from the blog post now. So you might Please keep me honest here is that like It's still it is a ranking factor, of course, but still we would like rank content and Still higher so there might even be rather slow pages and I'm not saying Just go ahead and a slow page, but still content is king. I guess right. So yeah, that's that's a very fair point between a super fast page that loads in 0.5 seconds on 3g And a page that loads in 10 seconds on 3g as well Then we're not just going to show the first one because it's super fast if that page has almost no content Compared to the other page, which is super relevant has been existing for a while Is referenced elsewhere on the web has user interaction maybe some comments of form whatever it is Um is really adding a lot of value for users that second page even if it's quite slow We'll probably still continue to be showed because ultimately what we want to do is show Urals that have answers to people's questions. So you're very right to call this out still It might be worth Exploring a bit more because oftentimes it depends a bit on in which vertical you are And it can be the easier option to speed up your side and then this would also be a question from me to you now I guess it depends on the vertical But what is your experience with implementing AMP pages on like development effort and the time it might take? Yeah, I mean it varies greatly so We've seen we've seen companies that implemented a AMP page within a day There are others that obviously need a bit more time because the Infrastructure is a bit more complex But typically amp is quite quick in a couple of weeks. You can you can implement amp So yeah, we I wouldn't want to give like a definite answer to that But considering amp is standalone You can definitely play around with it and get some results very quickly and then you can see if that's a technology that works for you Yeah, I think important to reemphasize. We're not trying to push that technology on you So like if you say well, I can actually live without amp. That's completely fine You know, we're trying to to kind of like set a framework of best practices That will speed up your side and if you follow that on your own page Then you will also see the the positive speed impact So but definitely I recommend to play around with it because there are a lot of cool features And we're developing more and we're listening to the community So yeah, again, like, you know, have have a look at it Check it out. And and if you think it's right for you, then it shouldn't take too much of your time to To get the first release up there Thank you, Adam switching gears a bit. We have a second question from Muhammad that was asking Why does the speed score scorecard? Sorry Does not support cctld so country code tlds. I'm not sure exactly what that Question entails if there are an example if there's an example that you could share with us Muhammad I don't know if you either of you has heard about what this could be related to I mean, you know, we we already said that We're basically We're taking the data from the chromies experience report And it basically means that the data set is currently not large enough to include all the tlds I think in july we Sorry in january, we just added three million and we're obviously aiming to add much much more domains But again, right now there's it's quite a large data set if you Use the speed scorecard and you cannot find your Your your domain. Unfortunately. It's probably not included in the chromies experience report yet We're working hard on it And definitely let us know and we'll we want to try and look into you know, adding as much content as we can All right, thank you Another question we can look at is Jeremiah's question which says What's w3c timing data points does page speed look at specifically? Is it page interactive? Is it first byte? Is it downloaded? um, so Page speed obviously it's it's complex and we're looking at multiple factors The best answer we can give you here is if you use the speed is the speed scorecard To rank domains it's it uses a combination of unload of dumb content loaded and on first content First content full paint. There's there's not one single metric That that you should focus on because each metric has sort of like its own importance So definitely keep an eye on as many metrics as you can I think it's also worth pointing out at this point All of the tools will not tell you how you will rank in SEO in the end. Um, they all therefore Typically different audiences or depending on if you want to have real user metrics or more of a laboratory Experience for debugging and they all have like Their costs definitely But none of them will really tell you if i'm good in let's say web page test. I'll be good in SEO, right? Yeah, pretty much the the SEO side of things if there's one general thing that we can say It's that it focuses on user experience So it's a little bit vague, but some of the metrics that we've been talking about are doing just that right? So how fast does it load for the user? What is really happening on the device as opposed to on the developer's computer on a 24 inch screen with a Really good landline to like connection etc. So be sure to look into these when you when you think about performance I think in another point we're pointing out is in our Last or the one before that hackathon on air. We pointed out how can I actually check? What is my user experience? So we're tying web analytics data to potential Yeah, stuff you can do with your mobile site. So let's say well if you see your bounce rate is very high for your landing pages It's an easy one that is probably very closely tied to speed whereas um, let's say People exit at weird points. And this might be more of a p other pwa thing so Maybe check that out as well see what you can check on google analytics And then just in general as since we just have tried to improve user experience This should definitely Improve your SEO ranking at some point as well because I think that's what it basically comes up to if I have a nice user experience and provide Answers to the questions people ask this should be Yeah, it's it's never one-to-one causality, but it's there's certainly a logic there Um, you you mentioned, uh, pwa's progressive web apps. There's a question there that sort of segues into it and that I can cover which is Why would you use amp right now when a modern amp is slower than an optimized responsive website and that comes from Antonio Um, so why use amp? Well, you tell me Amp is a framework. There are many frameworks you can use and it's not a one-size-fits-all And it's not a magical solution that will solve all of your problems Um, so basically you might have a reason to use amp on Only a certain part of your website, right? You want to be you might want to be very specific You might think it's really not useful. So you don't use it Uh, it's really up to you. You have to do that analysis and choose which technology fits best your needs One use case that we're starting to see more of and and that is, uh, getting people talking these days is the whole amp to pwa sort of experience, which is Um, that you you can find some articles, uh, about this. We'll try to link to it as well in description Maybe after the or in the comments after the this hangouts Basically, this is a way of providing some Amp pages that would load pretty fast. Maybe I don't know. Maybe not as fast as a super fast responsive for simple content, etc Um, but that then that that technology is very well Uh, designed to fit very nicely into progressive web apps, which is another framework which enables Uh, offline content which enables notifications with so re-engagement with users Many different things of the modern web and amp is a very nice segue into this So you might think this is a good use case even though it might be a little bit, uh, slower than Your responsive pages for you. I think it's also worth pointing out that Um, you can hand tune your sites and they might be almost as fast But it might be tricky to get the same instant loading experience since amp is not just It is a well a bunch of web best practices, but it also uses the google cache So if you're fine with that and you're like pre render stuff and get it out of the google cache, um It's very likely that the loading will be faster than Even the very best hand tuned html vanilla html css Maybe that's done. Do you have an opinion on that? That's usually the answer I give to my customers as well because the google cache is actually the second thing that makes it As lightning fast as it is Um, yeah, yeah, no, I mean that that's right and but I think vincent Put it nicely. Um, if you feel that amp is not right for you. Um, just don't use it. Um, we're not forcing anyone to use it but It is a good it is a good framework. Um, but yeah, definitely you need to make the call whether it's right for you or not um, I just read a question from egoshi asking does changing hosting affect rankings? um, and then in parentheses shifting from one dedicated hosting to another well, um It depends So when we're talking about speed and you change from a really slow hosting to a really fast hosting it might Change your rankings If it's vice versa, it might also change your rankings. Um, the question is at that at that point too broad to answer um, so if anything if everything stays the same um, the rankings will probably stay the same too. So, um, yeah, we that you know, it's the best answer I can give to that. Um to Expand a little bit of that and to talk more generally about SEO Very quickly as a parenthesis. So that's in terms of speed, right? And the sort of speed that uh, the hosting provider is able to provide to your to the visitors to your website What you would have as an SEO manager or a website owner to pay attention to when you switch hosting providers Is uh, everything related to the crawling of your website. So your website your URLs needs to be crawled Properly by the google bot, which is the automated spider software that basically crawls all the way and tries to find all of the pages that exist online So when you change hosting providers, you need to make sure that you have sufficient bandwidth for the crawling You need to make sure that you're not blocking specific ip addresses that are used by the google bot crawler You need to make sure that in terms of configuration and accessibility of your pages nothing changes there So that's in addition to the speed update, but keep that in mind All right, uh, do we have another question here? Did you find one dom? um, I think I just want to answer to one of the questions that um, heather submitted um, basically Heather is asking if we have any examples of uh sites that implemented um our recommendations so I Basically, I think what I would do in your case is Why don't you check out the uh, uh, the speed uh, the speed scorecard and just you know Find some domains that are ranked that are like ranking well as in terms of speed like that get a really good speed score um And then you go to this page and then you have a look at what have they they done to achieve this very quick speed score um Because if a site gets a really good result, they definitely follow certain best practices And I think that's where you can extract a lot of valuable information. You will see that Some of them might have async all their javascript others will have split up their css files prioritized the content Improved their images So that would probably be the first step I would take to just find the quickest sites and just have a look at What are they doing and maybe certain parts you can then um Sort of copy and and and do on your own side as well To add to this maybe um, if I'm not mistaken We also for most countries who released a benchmark study now as well out on though winning on mobile hub as well and think with google just as the speed scorecard Where you actually can see domains that did really well in terms of speed and user experience there's also a ranking and We'll fit more of an explanation what went into that rankings. It's not just speed. It's also a lot of user experience But this might be worth checking it out In the easiest way is we can either link it in the comments or just google winning on mobile and it should end up On the finger people side This might be worth having a look as well and and my personal advice as well is it's kind of kind of Generic advice, but just talk to people talk to other developers Ask them what they've tried go to conferences listen to what they say. There's meetups everywhere. There's javascript meetups There's web development front end mobile development meetups everywhere So just try to go to these and talk to people and listen what they have to say Uh, Heather is following up with did you say benchmark study? Yeah, then it's uh, I hope that's the official name It is a benchmark study and again winning on mobile on think with google should Need you to the right Examines it depends a bit which country you're in. So I think we haven't released all of them. I'm not Incorrect But yeah, you should find at least Worst case just studies from other markets But still if you're looking for url examples and from a technical side of you this will help you Yeah um We have another question by uh Heather says thank you You're welcome Christian asks us, uh, how will google deal uh in terms of sco with non-server side render pages Basically full browser side rendering. So uh for this I will answer with one generic answer again This depends on how the google bot can actually render the page when the google bot visits your page It accesses it it loads it and it renders The code right so it tries to interpret exactly how the page will look like for the user um It does this to try to understand your css Your javascript all of these resources and it will actually in some tools tell you if there are resources that are blocking this if there are problems with the rendering of Exploring uh of crawling a url Uh, the nitty thing is that google makes available a tool for you to check that So it's within the google search console Which is the general set of tools used by seos to look at their websites in terms of seo and uh within that suite of tools, uh, the specific report is called fetches google So you can go in there. Uh, fetches google in the search console Indicates a url and then ask for fetch and render and when you ask for fetched and render it will do exactly this Automatically at this moment. So it will crawl the page instantly and go see what it looks like And it will show you how the page has been rendered and then you will be able to see if there are rendering problems or not That being said It doesn't see the the google bot does not see everything. Um, it is running of A certain version of chrome, which is now starting to be a little bit old Older let's say so some of the very newer frameworks and technologies might still Be tough to interpret and to render fully by the by the google bot There is a discussion group that is out there, uh, where some googlers From the rendering side of things, uh within our engineering teams Survey the discussion and answer answer When people have questions about a certain specific new framework, etc So, uh, again, we will we will share this in the in the documents or in the Description, uh, later on after this all has this, uh, hang out on me Any more questions We have a follow-up from christian, which is how about google ads bots and others Are they able to understand the content? I'm not sure to be honest. I don't work with the ads side of things I don't know if you would have an idea about this either of you I No, we um all on work with the ads team. Um More than happy to um to read up on it and share it in one of the future Hackathon on air if we have any anything good to say here. Um, but Yeah, we don't want to give away information that might not be accurate. Um Sandeep asks how to add a site into google news. That's a bit unrelated to to the speed update write good content um and build a strong website and Then you might be picked up. I also think there is actually a way to apply to be included but Yeah, there is no magic trick on how to be How to we get your articles into google news? um Cool, let's um, yeah back to you vincent. I think you have a couple more questions I think we covered most of the the questions And the points that we had prepared in case we didn't have questions. So that's uh, really good The questions were actually quite on the point. There's one thing that Wasn't addressed Which is something that I hear actually quite often Which is This doesn't Really affect me right because my users are not on smartphones at all I don't see visits coming from smartphones on my website So I don't I shouldn't really care about the speed update, right? um To which my answer is usually say well Why are they not coming to your website for mobile? Is it because They're not searching at all on mobile or is it because your website is not ready at all for mobile? And Basically is not catering to them at all. They try to load it. It doesn't work. They just bounce away Um, because they don't want to wait 20 seconds for the page to load, etc so I would say don't dismiss straight away Uh, working on your mobile websites and on the speed of your mobile website Just because currently you're not seeing any traffic It might be that there is no traffic Because you're not focusing on it at all Good point. Uh, although I have to say like it's hard to find like for me it feels Must be hard to find actually sites with no mobile traffic Maybe I'm a bit biased here because I'm usually just consulting on mobile user experience But um, yeah, you have a certain set of There's probably a professional bias in there as well, but still My feeling would be that most sites will have um mobile traffic at some point Yeah, just generally what we're seeing of our queries and what most of my customers tell me In terms of their traffic for a lot of them actually mobile traffic now is overtaken Traffic coming from desktop, especially if you also count tablet traffic into mobile traffic Usually it's the case that's over Okay, um We have one last question from Jeremiah who is apologizing About the fact that it's the last question or about the fact that he's asking too many questions. I'm not sure he's asking Any good libraries or strategies for detecting content that is below the fold Or is it just pick a pixel height and run with it? Um, I'll take that. Um, I think the best answer here is Just do a quick google search. Um, we try to avoid recommending one library over the other Um, there is a lot of stuff out there, especially on github. So, um Just just have a have a browse and you will find tons of scripts and libraries that will do exactly what you need Um, and a lot of them work quite well. We test a few of them. So yeah, I think just google search will will do the job here All right. Thank you. Um The questions they keep coming. That's great. Um, so hi, uh from nico I'd like to know if you have any advice for the running, uh for sites, uh running on new javascript frameworks Like react.js or angular.js, right? So this would be covered in This sort of discussion would be covered in the discussion group Uh that I mentioned a few minutes ago That we will share in the description of this video. So come back to it in uh in an hour or so and uh, you you will have a link Uh where this sort of discussion is happening. How do very modern frameworks actually Work with rendering from the google blog site Yeah, and just to jump in there, um because there's There's a lot you can do when you're running a site on react or angular. There are a lot of ways you can optimize it Um, and just recently, uh, one of our fellow googlers, um adi osmani posted a really cool post on um Tinder and how they optimized um their pwa And that was built with react and there are tons of tips in there of how you can um use code splitting And um, you know, optimize react for speed. So I highly recommend this So if you just um do a quick google search for that post, um, I can just yeah again highly recommend it. It's uh Full of great content I think we're we're nearing probably the end right it's it's been almost an hour but there's one question that is actually pretty good for this which is, uh From ravie, uh, so greetings. I joined this session But i'm not able to understand the topic fully. Is there any updates coming from google for ico's or for websites or So my my answer would be this, uh Video is going to be available A couple minutes after we finish the live version of it on youtube at the same address So just make sure to start looking start watching from the beginning A short answer is yes, there is an update coming in july We won't spoil it now Cool, uh, yeah, I think with that it's time to wrap up. Um, maybe one more comment Also in the comments, um, again, you will find our event page. Um, so if you find that helpful Please go to our event page consider signing up there If you sign up, you will just receive two emails a month But we just remind you that we will screen again. Usually it's the third week of every month Um, and if you're new to that, usually they'll you mostly cover mobile topics ranging from technical topics to ux topics to now SEO topics Usually try if we're not specialists in this we're trying to get other googlers who are specialists to get on the show That work quite well so far So, yeah, please go there Check the content out. There's also a repository of other videos to see if there's something helpful for you Um, and sign up if you feel like it, um and join us for our future streams Cool. Yeah, thank you again for inviting me. That was uh, very welcome. Really really great experience. Thank you for joining in. Um, Tom, um, thanks again. Um, I hope you're Still good in london and not like covered in snow already Um, i'm sitting in a room with no windows. Um, I might be covered in snow. Um, but um, yeah, it was As always a pleasure. It was great to have you guys all watching and uh, definitely check back and most importantly Follow us on twitter because we're quite active there and if you have any questions Send us a tweet and we give our best to answer. Um, your questions, um in the future. So, um, definitely try try and stay connected to us and um, yeah, just you know follow us and um Have a good rest of the day. I would say Thank you. Bye. Bye guys. Thanks for tuning in. Bye guys