Having Fun with Mobile Responsiveness
of your website can give it a distinct edge over the competition, the thing that users really care about is functionality. If you have an amazing, scrolling parallax website with cool animations and custom graphics, none of that is going to matter if it takes longer than a few seconds to load on a mobile device.
Have Fun, Keep it Simple For mobile design, you can keep it very simple and still have fun and show people you know how to use mobile responsiveness without getting carried away and impacting site speed.
Big, Blocky and Bold Again, this goes against what many designers like to “see” in a website, but the fact is most mobile users want big, bright, blocky, in-your-face buttons so that they can navigate a website easily. This doesn’t mean it has to be ugly. Navigation should be a primary concern, and everything else is just gravy on the top. Most current web users are drawn to buttons, compared to in the past when people knew instinctively to navigate via top menus only.
Reduce Page Load Time It might seem like a few seconds doesn’t make much of a difference, but realistically every second it takes your page to load makes it exponentially less likely that someone will wait to see what your page is all about. It’s sad but true; we’ve grown impatient to the point that getting a full minute page view is considered well above average. So if your page takes longer than a few seconds to load, you can plan on people getting frustrated and exiting the site early. One of the easiest ways to counter this is by reducing the amount of video and images that have to load in order for a page to load. Keep images small, utilize Lazy Load when needed, and don’t make your website ping YouTube before loading (i.e. don’t use a video background above the fold).
Test, Test and Test Although in our opinion, Edge isn’t a great browser for most things, it does have one great feature, and that’s the device emulator. With it, you can see what your website will look like across a multitude of devices on pretty much every kind of browser. This is very helpful in debugging and working out the kinks that inherently exist when trying to make a website that is compatible on as many devices as possible. The other way to go about this is to actually just test the device on every device you have available, and on every screen size possible. People set their screen resolutions differently, have different screen sizes and use their mobile devices differently. Even still, a responsive site “should” be responsive and behave properly on all devices if it’s been coded properly and breakpoints have been set. Have more questions? Get in touch with us and we’ll be happy to help.