Search Results for 'mobile friendly'

Also, not a good idea as the site would not then pass Google’s new mobile ready label program for phone users.

REF:

Wondering if your site will qualify for Google’s new mobile-friendly labels or be ready for a potential mobile-friendly ranking boost? Google has a new tool to help.

The new tool is at https://www.google.com/webmasters/tools/mobile-friendly and it basically gives you a pass or fail grade. Either it tells you that you are mobile friendly or you are not mobile friendly.

Yeah. They removed the fixed layout a few versions back. And technically that “made sense” only because Google WANTS all sites to be mobile-ready, and sites work better when mobile friendly vs running separate sub domain, or a plugin which re-writes the entire site for mobile, etc. It also was difficult to manage a non-responsive layout while having al the fancy stuff people kept asking for, like megamenus, etc. — basically bloating the CSS with both responsive and non-responsive code and all the if/then stuff, made it less healthy for the majority of folk who do want a “responsive” theme.

Also, there are more and more underpinnings from Bootstrap inspired code, which is “responsive”…

You don’t need to use WP Touch with the theme since it is responsive by design, meaning mobile users already see a mobile-friendly version. You should check with the WP Touch plugin developer for compatibility.

There is no real reason to add both the Jetpack mobile feature, a mobile plugin, when the theme already serves a mobile version. That plugin is primarily for “old” sites which don’t have responsible mobile ready designs.

This is a responsive theme; there is no “non responsive” option as far as I know. It’s designed so that it will better viewed by Google which now “dings” non-responsive/mon-mobile friendly sites, and for compatibility on iphones, tablets, as well as desktop.

You can create a “boxed” layout, simply by putting in a background color or image for the theme. You might try that first and see if it suits your needs?

You would likely need to remove the CSS from the theme for the responsive @media viewports.

Responsive design is better for SEO, and Google actually dings you for not having mobile friendly site now, and with more and more people doing their web surfing on mobile devices, it isn’t advisable to “turn it all off….”

But you can hack the style.css sheet to remove the @media points for other sizes, and see if that works for you.

Since the theme is sold as designed for responsive design, you could also look for a fixed layout theme, perhaps; but I’d try hacking the style.css sheet first 🙂

Hi Emil,

Thanks for the reply.
I only used the emulator to be able to show you the problem.

I did test on a few mobile phones and had the problem.

On the newspaper demo site there appears to be no issue on my mobile phone. Has some custom css been applied to this site?

I find it strange that out of the box the theme has this issue, as other themes I have not had to mess around with custom css.

I will attempt to apply this custom css, it will be a shame if this does not work as i purchased the theme for a clients site. If it does not work properly it will be a shame as I love the theme . One important part is the client wanted site to be mobile friendly.

I will advise.

Hi,
you may want to read through the entire pagespeed topic (big sticky top of the forum), as all of this has been well covered there.

Generally you can’t do anything about things like addthis (although I did post a hack to load that in async mode), or jetpack – as those load on other servers and will show up as errors when you run pagespeed analytics. If it’s not loading off your site, it will likely show up as an error of some kind – this includes recaptcha, adsense ads, etc.

Not sure what you mean about looking at source code of theme vs source code of the page — the theme code is not rendered while the code on your site is rendered with all the stuff coming from dbase and external and queries, etc. If you’re trying to compare the “demo” to your pages, that may not work either. You should follow the instructions to setup the cache (remember you need to CLEAR cache every time you change things like htaccess, new plugin, etc.), the speed booster, the page expires time.

For realistic speed – test without addthis, adsense, or jetpack. Then put that stuff back and decide how much impact you want to have on your site. I use addthis for social buttons on one site, and then the theme stuff on another. I don’t use jetpack as it’s slow and I hate loading stuff from a mothership that isn’t my own. I limit number of ads on page (4 ads will be slow if images!) – try loading text only ads, to speed up page!

But a *lot* of this, if not all, has been covered in the pagespeed topic. So, best to start there, and remember it’s virtually impossible to get above 91-93 in desktop with a busy site, lots of pix, wordpress theme, external stuff. Mobile will be slower, no matter what you do. 76+ isn’t too awful right now. 80+ is goal. 65 would be awful. To really optimize for mobile requires making a version of page which most newspaper sites won’t do, and that is mostly text, one picture, minimal navigation, etc.

Google sadly doesn’t differentiate from “tablet friendly” and “iphone friendly.” SO, I’ve stopped crying over trying for a perfect score on phones — it’s not my primary audience. Tablets are, then desktop.

Anyway… that might not help. But
1) set cache to page cache ONLY
2) don’t use any minification stuff until you have speed booster plugin working right
3) make sure your htaccess has expires headers
4) make sure your web server is doing gzip/deflate
5) optimize your images prior to upload; if possible use my hack to increase compression level for thumbnails (or use smush.it or similar; I prefer to edit my functions.php file to change compression to “50”)
6) run your speed tests
7) turn off anything you don’t absolutely NEED if you’re seeking highest score
8) test and retest

THEME UPDATES:
I find it’s best to fully over-write the old theme with NEW theme folder each time, via FTP. I’ve had mixed results with “patching” over the past 10 years with WP sites, and more often than not they break somewhere due to permissions.

Frankly, it’s good habit, since you can also download a full snapshot via FTP before you do an update, to ensure you have a full snapshot. I date and RAR mine here for archival purposes.

• This reply was modified 12 years by simchris.
• This reply was modified 12 years by simchris.