You Ask, I Answer: How To Check Mobile Friendly Website?

Warning: this content is older than 365 days. It may be out of date and no longer relevant.

You Ask, I Answer: How To Check Mobile Friendly Website?

Sasha asks, “How do you check if your website is mobile-friendly?”

There are four different, easy ways to check:

The Mobile Friendly Test for a single URL
Search Console for site-wide checks using the mobile usability tests
Search Console for site-wide mobile Core Web Vitals
Google Chrome Developer Tools to check the UX

Watch the video for a walkthrough of each.

You Ask, I Answer: How To Check Mobile Friendly Website?

Watch this video on YouTube.

Can’t see anything? Watch it on YouTube here.

Listen to the audio here:

Download the MP3 audio here.

Machine-Generated Transcript

What follows is an AI-generated transcript. The transcript may contain errors and is not a substitute for watching the video.

In today’s episode, Sasha asks, How do you check if your website is mobile friendly? Really good question.

super important to be doing these days, because pretty much every website should be mobile friendly.

And there’s four different ways to check.

They’re all free, all easy to use, you just have to interpret the results.

So the first way, let’s go ahead and move things over here.

The first one is Google’s mobile friendly test.

This is part of search console, but it’s a standalone tool, and you put in a website URL here.

So let’s go ahead and do that.

And what the tool will do is it will go and get the page, the single URL that you’ve put in as gonna check it for all the basics.

This is a good tool, if you need to check a specific page, it’s not as good if you have to check an entire website, because let’s face it, who wants to sit there and type in a whole bunch of URLs.

However, for specific pages, especially if you’re going to roll out something like a landing page for a campaign really important tool, you want to make sure that the landing page is is friendly on on mobile devices, especially if you were expecting that landing page to rank in search.

Here we see my homepage is considered mobile friendly, right gives you a green if it’s mobile friendly.

And then if it’s not, it will give you a bunch of warnings and tell you what’s wrong.

So that’s way number one.

Way number two is in Google Search Console, which if you don’t already use, that would be the time to start using it.

There’s two different things in Search Console that will help us understand mobile friendliness.

The first is the mobile usability test down here.

And this looks at your site.

And then it will highlight pages where it thinks you just haven’t passed the test.

And you can also see the pages that are valid the pages that are working well.

And if something is wrong, it will tell you down here what these things aren’t like clickable elements too close together, content wider than the screen those things that you’d want to fix.

And then if you click on it, you can dig into if there were errors here, you could be able to dig in and find out okay, what are the pages that are having this problem.

So super useful.

This is good for site wide.

When you’ve got a big website.

Like if you have one page and a website, the other test is fine.

This is for if you’ve got a lot of pages like a blog, you’ve got landing pages.

This is critical if you are to be using the domain version of search console, especially if you have subdomains.

So a lot of folks have things like marketing automation software and stuff that sets up its own landing pages and subscription pages and all that stuff.

And that’s fine.

But you want to run mobile friendliness on those if they are part of your domain.

So if you had like marketing, Christopher penn.com, you’d want to use search console at the domain level, so that it could also check your marketing automation software and say, Okay, this, these pages here are not mobile friendly, because it does count against you if it’s part of your if it’s a sub domain on your main domain.

So that’s test number two.

test number three is the core web vitals.

So core web vitals, we’ve talked a lot about these recently, are these measurements for assessing? How well does your website work for things that will eventually be ranking factors? So let’s go ahead in this report here, and there are no there’s nothing I highlighted either way for my website for my domain.

If there had been, let’s go back here, you would see indicators like your what other what URLs are working or not working on? Setting up an example here.

So for some of the pages on my site, large contentful paint, as long as the four seconds.

So there’s an element on some of the pages of my website.

That takes too long before the largest element renders.

So I might want to look at doing optimization of page load time or shrinking files and stuff like that.

So the first few tests that we talked about here for testing mobile friendliness, rely on Google, and its software to crawl your website.

And to let you know, either at the page level at the domain level that your site is mobile friendly.

And that’s important.

Like those, those are things that for SEO purposes, especially, you need to do you need to get Google stamp of approval saying yes, things are working, and things are optimized.

But there’s one more thing that you should do.

And that is let’s go to the website here.

In Google Chrome, if you go up to the View menu, and you choose developer, and you choose developer tools, the developer tools will load and what you’ll notice is, this is Little tiny icon here called the device toolbar.

Let’s go ahead and click that and turn that on.

And now I can choose different devices to look at my website on.

So for example, let’s do an iPad.

Right.

And so it has a, let’s make it 75%.

And now I’m simulating actually touching the screen.

So this is what my site looks like on an iPad.

Okay, let’s switch over to a Samsung Galaxy.

This is what my website now looks like on a Samsung Galaxy.

This check is looking at the user experience from your own perspective, right? Is this a good experience? Is this something that you would be happy to see when you plug in your own website? Or is this kind of like a not great experience? And based on the devices that you have available here? Just do a few checks to just check things out and see like, how does this look on a series of devices? Is it good? Is it bad? If it’s not a pleasant experience, or if things are not showing up, the way you expect them to? This is going to tell you that Google’s tests will not tell you this, they will just check to make sure it’s functionally working.

But for example, if I am trying to promote something on my website, is there stuff here that shouldn’t be? Is there stuff that’s getting in the way like, this is my newsletter here? And it’s what about a third of the way down the page? Do I want that form moved up? If so, I know I need to reorder the blocks in my design.

And so this is the fourth check is using Google’s chrome and the device manager to do those user experience tests really, really, with an expert i a human eye towards are things working the way they’re supposed to be.

mobile usability is all about making sure that people can do what you want them to do on a smart device.

And if you have not already go into Google Analytics, and check to see what percentage of your site’s web traffic is, from a mobile device, if it’s more than, like 3%, or 5%, you want to run these mobile usability checks.

for SEO purposes, it doesn’t matter what percentage of your site’s traffic is, is mobile.

If you want to rank well, in Google’s mobile first index in the mobile first world, you got to do what Google says.

So those are the four checks, you should run these.

The individual page one, your running time, got a new important page on your website, Search Console, you should be checking Search Console at least once a month, at least, ideally, maybe every couple of weeks.

And when you’re in Search Console, you know, you’re not going to do everything.

But at least it’s going to make sure there’s no obvious warnings like things just on fire.

And then for the developer tools, version, doing the UX check, do that.

Anytime you got a big design change, and maybe once a quarter, just again, going in there making sure somebody hasn’t messed up with the website, put something on there that you didn’t expect.

A new maybe tags if you add a new tags or new trackers to the site, hopefully via Tag Manager that hasn’t broken those as well.

Anytime you make any infrastructure change, so if you, for example, rollout CloudFlare, and you use their rocket loader, which optimizes JavaScript, if you do that, immediately go test, go test, go test go test because sometimes things like that will just totally break your site.

Anytime we add a new plugin and like WordPress, rerun the developer tools test and make sure that things are not broken unexpectedly.

So really good question.

Lots of different ways to do this.

Do these like I said any to the circumstances mentioned? Got follow up questions, leave them in the comments box below.

Subscribe to the YouTube channel on the newsletter.

I’ll talk to you soon take care want help solving your company’s data analytics and digital marketing problems.

This is Trust insights.ai today and let us know how we can help you

Machine-Generated Transcript

Comments

Leave a Reply Cancel reply

Pin It on Pinterest