Optimizing your mobile site is more than just search engine optimization (SEO) or making sure your content looks acceptable on mobile devices. There are a number of specific areas in which a little attention to how your website’s mobile counterpart is created can go a long way towards improving performance as well as ranking. From the common sense to the not-so-obvious, these seven tips cover a cross-section of areas where you can make measurable gains.

1. Use Google’s “Mobile-Friendly Test” to check your site.

Google’s Mobile-Friendly Test is a fantastic tool and a good place to get started. After giving your site’s URL, the tool will tell you if your site is mobile-friendly as well as show you how Google sees your page through the eyes of a mobile browser. It will even alert you to page elements that cannot be loaded, allowing you to quickly ensure your mobile display is as complete as possible.

2. Optimize for search engines.

True of non-mobile sites as well, but especially important for mobile, always ensure that search engines can crawl your content. Many webmasters will block images, CSS and JavaScript from search engines in their robots.txt files. This prevents crawlers from seeing them, however, and rendering your mobile site as intended. Google provides a tool called “Fetch As Google” that can help.

Advanced tip: Don’t presume that search engines will be able to identify your mobile site. Include viewport data in your HTML to remove any doubt.

3. Test all of your media on mobile.

Some video files are blocked from mobile playback or may use a format not supported by many devices. Don’t presume that because it scales it will also play. These days, it’s also advisable to use HTML5 for media playback.

4. Check your redirects!

If your desktop site redirects users to the mobile site when it detects that they’re on a mobile device, ensure that the redirects — including paths and query string arguments — are correct. Simply redirecting every desktop page to the mobile home page results in search engines having just a single point of entry to your mobile site; this can sometimes confuse their crawlers.

5. Serve mobile content before ads.

This tip can be argued, but adding a mobile ad page before serving mobile content is generally a bad idea. This includes both advertisements and pleas to download a mobile app before proceeding to the actual mobile site. Many users will abandon a mobile site when presented with such a “speed bump.” Resist the temptation. Instead, use a banner rather than an interstitial or popup page.

6. Optimize your mobile pages.

Remember that a large number of your users on mobile devices are also on slower and sometimes unreliable connections like cellular. While desktop web pages should be well optimized, mobile pages demand it. Images should be as small as possible. Be mindful that the resolution of a mobile device may be significantly smaller than a desktop site. Take advantage of this fact and serve smaller images.

Advanced tip: If you have dynamic content generation for desktop and mobile, add a “Vary” header to your output to signal to search engines that they should re-crawl with mobile settings.

6. Optimize your mobile pages.

Yes, this is the same tip as the previous one, but it’s so important that we felt it necessary to say it twice.

7. Think about URLs.

Google and all major search engines do not give any extra benefits for using separate URLs for mobile. That is, if your site is on www.example.com but your mobile site is m.example.com, Google neither penalizes nor rewards your search engine ranking. Use separate URLs if that is your architecture, but don’t feel that you must to get better ranking.

That said, remember, if your mobile and desktop sites are on separate URLs, search engines are going to index them separately. That also includes your reputation scores on these pages, which will be calculated separately. Higher-traffic websites might not care about this, but smaller ones might. You might want to avoid separate URLs for this reason.

My friends over at Media Temple have promoted a fantastic guide to DPI, and so much more. This article really covers it all and in an outstanding way. I can't recommend it enough. Thanks to Media Temple for pointing it out, and thanks to Sebastien for writing this. Bravo!

Today I revisited some code I'd written about a month ago and reduced the time it takes to run a data loading job from 52 minutes down to sub-10 minutes by replacing a relatively slow API call with a direct call to local code. This is something that was "good enough" until now, but was on my radar as being eligible for improvement. Since I had a new data loading job that would take over 10 hours using the API call, I had to write the new job a better way. Copying this better code back where it could make a difference meant that all of my data loading jobs were now refactored and much faster.

The takeaway here for developers is to periodically revisit your code and refactor it. Find new efficiencies. Examine how your code has been working and consider what you might have learned since the last time you worked on it. You may notice something now that you didn't notice the last time you were in the code.

I'd like to see a contest to see who can design the best web site using only HTML 1.0 and no more than 40k in graphics, GIF and JPG only. That's right, what's the best 1994-era web site that someone with today's skills could design, if they were sent back in time.