Mobile-First

As soon as Google announced "Mobile-First" indexing, we hit the drawing board to understand and answer what would become every website owner's biggest questions.

"How do I keep up with, and stay competitive with Google's Mobile-First changes?

(If you're not already asking yourself this question, you should start. The future of your business depends on it)

We first looked at how the vast majority of mobile sites were being built, and immediately found a major flaw in the design architecture.

Most all of them are constructed for desktop first, then the elements of the website are manipulated to fit smaller screens LAST.

This is what we all know as mobile-responsive or mobile-friendly site design.

We've Found That Mobile Responsive and

Mobile Friendly Sites Just Aren't Fast Enough...

This approach to building a site that's mobile friendly or responsive causes all sorts of problems.

Things that are in one place on your computer screen are in totally different places on your cell phone.

Then you find youself going back and forth, reshaping your main site to make sure it works on mobile.

It's completely frustrating and a huge waste of time. We've been through it!

What's worse and has a larger effect, is you're compromising the performance of your website!

How can a website load quickly when there's so much to figure out in the background?

So, the question remained.

How could we get the absolute best performance across all devices?

Then the answer hit...

What if we took the complete opposite approach?

What if we build for the smallest mobile device first?

It makes perfect sense...

Let's completely reverse the idea behind old ways of building websites.

Let's instead start building pages on the smallest screen first, because it forces you to add the most important elements you want on your site, then add additional elements as you increase the screen size.

This ensures everything fits together as it should, because you've essentially built your site for each size screen, instead of trying to shrink a larger site into a smaller screen.

Like most ideas, it all sounded great in theory, but would it actually work?