What Bloggers Need to Know About Core Web Vitals & Page Experience | The Food Blogger Pro Podcast

Hello, everybody. Andrew, welcome to the live Q and A. Hello.

Happy to be alive.

Yeah, it's going to be a great conversation here. We already have some good questions coming in. We are talking today about page experience, core web vitals. And what happened was in this conversation came up in Slack for our team, the food blogger pro team. Like, we got to do Q and A on this. And I was like, how about we also do Andrew as a guest? Because you know a lot about this. So my guess is most people will be familiar with you and what you do from past podcasts, live Q&As. We might even have some nerd press folks here. Nerd. Do you have like a. An internal name for them? Nerd. Nerd pressers like nps. What you got to come. If you don't have one, you should come up with one.

One thing we figured out is, is, you know how, like if you have, you know, you have a flock of seagulls, right? Or, well, if you have a group of nerds, it's called an awkward.

Okay. So awkwards. Yes. Yes. Which is kidding even in saying it. So would love to hear a little bit about your background real quick as we jump into it, Andrew. And then as Andrew sharing his background, would love to hear anybody who's tuning in live, where you're tuning in from. Maybe your site's name or if you're just on social, where that is. And drink of choice. That's kind of what we go with before we pressed record. We both have an ember mug, which is awesome. I'm not using it because I have a cold press right now. So what yours is a coffee? A tea. Is that what you're kicking?

I got some black coffee in here. Yeah.

Nice. And then your background, Andrew.

Hi. So I've always been interested in websites since I was a kid or computers, I guess. We didn't have websites going back that far. So for years, I dabbled with websites on the side. And then in the late 2000s, through a career change, I started a food blog in 2010, actually, and got into the food blogging space. And then when other food bloggers found out, I knew what I was talking about with tech stuff. They're like, can I hire you? And things kind of grew from there. And oh my gosh, we're 11 years later and my food box still exists. It's sadly neglected, but it's still around. And we are now basically focused on website support and maintenance just for WordPress websites. And because of this community, most of our clients happen to be food bloggers. So we do have some other e commerce clients and other lifestyle bloggers and some nonprofits and foundations. But like 95% of our clients, I think are in the food space and.

Wellness space, which is awesome because your background is that you understand food. You had a food site, and so it's an area that you know and like. And then also one of the things that I love about your story is one of the things that we find is sometimes a pursuit, in this case of food, blogging can be a gateway to another successful career. And we've seen that multiple times where somebody will get into it and they'll be like, oh my gosh, I love video. And I didn't realize that before. And then they build a successful career in video. And for you, building a successful company, multiple employees with supporting other food creators, which is great. And today we're going to be talking about something that I'm guessing you've been talking about with a lot of nerdpressions. Okay. And that is page experience and core web vitals. So this is an important consideration, kind of something that Google has pushed out and said. We think this is a priority. And in the food space where search is so important, anytime Google says something, everybody pays attention to that and wants to make sure that they are making Google happy. And our goal in this conversation is to make sure we understand what it is and understand how we can improve it. But before we get into the specifics, we have to understand, like, what is this thing that you hear people talking about? So can you kind of lay some foundational knowledge for us to build on as we get into these questions?

Sure. So Google, in May of last year, I think it was said, hey, we're going to release this new algorithm change. We don't know when it's going to be exactly, but it'll be like, we'll give you six months notice and it'll be sometime in 2021. So we got basically a year's heads up and we're all like, okay, what.

Do we do with that?

But at least we knew it was coming at some point. And then in November they said, hey, okay, we're going to launch this in May of 2021. About a month ago, they decided to postpone it till mid June.

So.

So because they realized people weren't ready even with the warning. And that's. We'll talk about some of the nitty gritty. But it's because it's hard. This is really hard to do. So they already had the page Experience algorithm actually. So this is really just an expansion of it. So Google, they use these algorithms that are like hundreds of ranking factors. Some of them we know, very few of them we know. But then the rest we have to deduce what, what is a ranking factor? What is Google looking for? Right.

What are the ones that we know.

So. Well, the page experience ones are some that they tell us actually. Right, sure. So existing page experience algorithm factors or ranking factors that existed before or that exist now and have been for a few years. Is your site mobile friendly for example? Right. And they switched to a mobile first indexing. So like that's actually like if your site's not mobile friendly, you will not rank as well. Yeah, it's literally that simple. Right. Because they're really pushing for mobile web because that's what people are doing. Is your site safe? Has it been hacked? Right. Is there any malware on it? So that's actually a ranking factor. Right.

So HTTPs versus that's the other one.

Yeah, yep. So that, because I think it was 2014 or maybe earlier where they said, hey, this is going to be a ranking factor, you know, so Google makes these decrees, they say we want to make the web a better place. We could argue whether or not Google should be the ones doing that. But they do it, I think in terms of HTTPs, I totally agree. It's great that we're all SSL now. It's actually faster too. So they're pushing technology forward this way. Another one of them that many people have probably heard is no intrusive interstitials. So if you click through from a search result to a site and then you get this big pop up right away that gets in the way of your content that can actually penalize you in the rankings because it's interfering with your experience of going from Google and getting your answer.

Yep.

So all the ones we just mentioned already exist. They're part of the page experience. So what's happening now is they've created this metric called or group of metrics, I guess called Core web Vitals. And right now they're starting with three specific metrics and they've said this will probably evolve. So once a year they're going to revisit this and say, hey, there's a new metric or we're changing this metric. It's going to, it's, this is going to be a moving target. So it's not a set it and you're good for 10 years kind of thing. But basically they're looking at improving user experience. As part of this, and part of that is site speed. So you want to make sure the site loads fast. Part of that is that the site is interactive, so when you swipe or slide through, it doesn't lag or you tap a button and it actually responds. And then part of that is visual effects, visual stability. So, you know, if you like, how many times have you gone to click on a button and an ad pops up and it pushes down and then you click on the ad by accident? Super annoying. So that's the third one. So they're basically, they've set measurements and criteria for those three metrics or for three metrics, which we should talk about in a sec, and said, hey, you have to hit this score or better, and either you pass or you don't pass by passing that specific score. It's the same score for every website. Doesn't matter if you're a food blog or facebook or google.com and then either you pass all three metrics or you don't.

Yeah, it's like a pass fail. Yep, yep.

They say pass does not pass.

Okay, yeah, sure. So we know how much that actually impacts.

That's your result question. Big, big question right now. Google has said this will not cause massive ranking changes when they roll this out. Okay. I want to stress that your site will not change rankings because of this in mid June. Like, the danger will probably be imperceptible. There might be a couple of sites that move up or down, you know, a couple of spots, but you probably won't notice it. So Google has said, first of all, they're rolling it out slowly, so they're going to start rolling it out mid June, and then it'll fully roll out by the end of August. And then they've said over time, it will become more important.

Sure.

And part of that is as more sites get on top of this and improve their metrics, it becomes more of a ranking factor. But right now, like, 10 or 15% of sites even match this. Sure. So the trick is, because we know it's a ranking factor, everybody's glommed onto that and said, oh, we should fix this.

It's super important because we don't have that many things that we do know are ranking factors. So when there is something, everybody kind of, there's a big to do about it. It's like, oh, my gosh, we got to make sure that we do this, because now we actually know this. Google's going to rank this or this is going to be a ranking factor. So if we know we got to improve it.

Right. And so I say that because like, you shouldn't ignore it. But don't panic. We're getting emails from people freaking out because they're afraid June 1st their rankings are going to drop. And I can tell you right now, if your rankings drop, it's not because of this. There may be other reasons. And Google posted a frequently Asked questions on this and they even underscored repeatedly, content is the most important thing. Answer the user's query intent. When somebody searches for the best gluten free chocolate chip cookies.

Yeah.

Give them the best gluten free chocolate chip cookies. And if your site takes a little bit longer, if your recipe's better, it's still going to rank well.

Yeah. So I think that's a really important reminder because sometimes I think to your point, it can seem like, wait a minute, if I don't do this, then I'm going to get cut off and I'm not going to get any more search traffic. And it's more of like the culmination of 200 different things that you're doing well, of which the most important is content. All those other variables, core web vitals, a fast site, no interstitials. Those all become multipliers on really good content. So if you have really good content and you check all the boxes off for the other recommendations or best practices, awesome. If you have super crummy content and you check all the boxes of the recommendations, it's like a multiplier on zero. Right. 0 times 100 times 100 times 100 times 100 is zero. And you got to start with that core foundation of technology, which I think is such a great takeaway. Should we jump into some of these specific questions that are coming in or anything else that you want to say to lay the foundation?

Let me explain what the three scores are actually, because I think that will be helpful. There's three specific metrics that they're now tracking as part of the core web vitals. The first measures how fast your site loads and. And it's called Largest Contentful Paint or lcp. And what that's doing is saying how long does it take when you hit go on the URL for the biggest thing above the fold to show up? So before you scroll in, your first view on mobile is your title, the thing, your header, whatever the biggest thing is in terms of dimensions, how long does that take to load and display? They basically picked biggest as a proxy for most important.

Sure.

There's another metric called first contentful Paint where it's like, how long does it take for anything to show up? That metric is still part of the site speed overall. But they say, well, okay, largest is more important. Depending on what that is and when it loads in the sequence that's going to change your score. The target to hit with that is 2.5 seconds or faster. If your largest thing, whatever it is, takes less than two and a half seconds, then you're good. I should also mention the way this stuff is measured. It's actually they're looking at real world measurements. Many of you are familiar with Google PageSpeed Insights where you can run a test and in the lab data it'll show you the simulated 3G test where we're like, hey, we're pretending this is a slow phone and here's the score. But what Google's actually using for the rankings is what's called the Chrome User Experience Report or Crux C R U X. And what that is is basically they're looking at people using the Chrome web browser. That browser is sending back those timing data to Google. So it's real world. It's real world user data. So if your users are on lots of slow devices, like if you happen to be on a blog where that's, you know, like, like maybe you're, you know, focused on budget stuff and your users are likely to have slower phones.

Or slower tools for rural communities with slow Internet access.com. yeah, yeah.co.uk.

Yeah.

So that's.

Since it's a real world metric, we're talking about actual, like I've got an Android phone with a Chrome browser. If it takes 2.4 seconds for that largest element to load, we're good. If it takes 2.6, we're not. And so all of that data is being sent back and it takes time to collect that data. So chrome looks at 28 days of data. So when you make a change, it actually needs 28 more days to collect more data to show you this Chrome.

So even if you improve it the next day, you check it, that one day is going to be one day of improved content and 27 days of non improved content.

Yes. And that's, I think, one of the reasons why they've had to delay this rollout because it takes so much time to really like, tweak and make sure it's working and see results. So let me, let me get back to the three metrics. So we've got largest contentful paint. Then the second one is a measurement of interactivity. And so that's first input delay. That's basically like when you try to do something. How long does it take? In our experience, most food blogs don't have a problem with this. The metric to hit is 100 milliseconds or less, so a tenth of a second. So basically it has to feel responsive. Unless there's something really wrong with your site, you're probably fine on this one. Unless you've loaded up with tons of JavaScript. That's really bogging down.

Sure.

And then the third one, and this is really the hardest one. It's a measurement of visual stability and it's called cumulative layout shift cls. And that's basically a measurement of how much do things move around on the page and get in your way. The crazy thing with this is basically all layout shifts are treated equally. And so if it's like the page is loading and stuff is moving, that counts as layout shifts versus you're reading through. And an ad loads and pushes your content down, which is really. That's when it's really annoying. Right. That is counted as well. So this is where we're spending most of our site speed optimization time on CLS is really hard and I think we'll get into like some more details on that. But the metric on that is 0.1 or lower is what you want to hit to pass.

What does that metric represent?

It's some crazy calculation that they keep changing.

Super helpful.

Yeah, super helpful. Basically they've come up with this scoring system for cls.

Yeah, it's like a CLS score, which is.

And it basically looks at how big the thing is that moves and how much it moves. Sure. But then it's a cumulative shift. So if you're scrolling down and something shifts again, it shifts again. You can install a Chrome browser extension that'll show it to you in real time. It'll calculate it and say, oh, as an ad pops in, suddenly you see the score go up.

Yeah. And what is that? Do you know what that extension is called?

I can tell you in just a second. There's a few of them.

Is it by Google?

Hold on, let me open up my extensions and I'll find you the exact name of the one I'm using.

Real time feedback. This is great.

There are a few that out there. This happens to be the one I'm using in it. It has 80,000 users. So I think it's. It's a good one.

But yeah, it's called Web Vitals.

Yes.

And it will show you that the.

Web Vital score one Other thing I should mention is right now they're only using mobile scores as a ranking factor. In the future, they will add desktop as well.

Okay, awesome. And it looks like. Is it Carrie? Am I saying that right? Yes.

Thanks, Kerry.

Good to have you on the call, Kerry. So super helpful. And then, last piece that would be important to point out. Where do you find these? Where does this information live?

There's a few places to find it. The one that we found is the most reliable right now is through PageSpeed Insights. When you run a Page Speed Insights test, you can just run any URL from your site through that. Also, side note, if you look at the CLS score on that tool, it's pretty bad. I'm just saying there's a lot of Google saying, do as I say, not as I do. So we're internally getting a little cranky about that.

Anyway, Google is failing its own tests. Yeah, right.

All right. So anyway, sorry, too much coffee.

So you go to coffee because of the.

It's nice and warm. Go to Google PageSpeed Insights. Alexa just posted the link in there. Drop a URL from your site in and it's going to run a test. And actually let me walk through the different blocks of that. The topic is going to be an overall score for right now. Please ignore that. People give way too much weight to that score. Then you're going to see a section called field data. And below that will be Origin Summary. I'll talk about those two in a second. Then below that is the lab data. The lab data are six metrics that are from that simulated test that you literally just ran seconds ago. That's going to give you an LCP time, a first contentful paint time, a site index, total blocking time. There's a bunch of technical things in there. It'll also give you cumulative layout shift score. So those six scores are actually what's used to make the top score. The big score above that big score is literally just a calculation based on those six scores. So if one of those changes dramatically, that can cause your overall score to swing 10 or 20 points. So don't give too much credence to that overall. I would just get rid of the overall score because it just confuses people. So, so that lab data is what you just ran on a simulated test on whatever server Google happened to use. So going back above, we've got field data and Origin summary. So field data, both of those are pulling from the actual data from the Chrome user experience report. This is the information that's pulling from the Same database that Google's going to use for rankings. So field data is for that specific URL that you just tested. If there's enough data for that one URL, it'll show that there's. So if you have a really popular post that gets a lot of traffic, there might be data there. Then the Origin summary is the average scores for all URLs on your site. If there's no field data, it'll just show the Origin summary automatically. If there is field data, you can check a box and it'll show the Origin summary. The Origin Summary scores, those four that it gives you will be the same no matter what URL you test in there. That's showing the 28 days trailing information. And three of those four scores are the core web vitals. And it'll say right above, Based on the 28 days of data, this passes or doesn't pass. The other place where. And this is also causing a lot of confusion, is if in Google Search Console you can find this information, right?

Yeah.

And they've actually created a page Experience Dashboard that they released a couple weeks ago in Search Console that it's supposed to be pulling from the exact same data, but we found it's often delayed or buggy. We've seen sites that pass in Search Console but fail horribly when we look at the Origin summary data, or vice versa, and we're looking at the actual speed going. This doesn't make sense. So I do want to mention in the Search Console, they want you to validate fixes, right?

Sure.

And they're giving you all this information. The information presented in Search Console and whether or not you validate your fixes has no bearing on your actual search results. It's just a tool to help you track that stuff.

Yeah, yeah, Right. So if you want your data in Search Console to reflect more accurately, you validate the fix. Validating the fix doesn't make your page show up higher because the page is the page. And then there's these tools like Google Search Console that are looking at it and analyzing it. But it's not Google Search Console that then is reporting back to Google and saying like do or don't show this. Well, those are separate things.

There are some tools in there that can help. You can re index a page so you can trigger certain things in there. But in terms of this stuff, as a team, we've decided we're looking at the Origin Summary. That's our source of truth. As far as we can tell, that's the best way to go, right?

Now. Cool. That's great.

Sam.