Upload via FTP is the best way.

Looks like the CSS is being blocked by your robots.txt file or similar; See the specific “why” info on the page you’re linking to from Google. 🙂

Like it says right on that page “may not appear mobile friendly if blocking some of the page resources…”

Check your server time.

ref

http://stackoverflow.com/questions/24572077/google-service-account-example-returns-error-refreshing-the-oauth2-token-err

So, check you have enough resources from the system tab for the theme.

Generally you do need to allocate more memory to WP, make sure your timeout is not too short for php, etc. This is true of ANY theme running Visual Composer, which is almost an entire new application running inside of WordPress.

We’re using a plugin for this over here, with Newsmag.

There are several to try out in the WordPress.org plugin repository, depending on your needs and mail setup. You may need to setup SMTP mail plugin to send emails properly, also, just like when using WooCommerce.

Make sure you have enough resources allocated to php;
try disabling pingback (remove item from header.php);
disable XMLRPC in your functions.php

Check with hosting account to see what error log says, and if under attack.

But it works when you preview it from the page editor ?

Perhaps try resaving permalinks; and also try clearing transients with wp-optimize plugin.

That’s what I do with oddball server caching stuff.

Also for those who use Google, easy find:
http://osxdaily.com/2010/12/13/open-7z-files-on-a-mac/

How to Open a .7z File in Mac OS X

Follow these steps to open and decompress .7z files:

First you need to download Unarchiver (it’s free, you can also get it from the Mac App Store)

https://itunes.apple.com/app/the-unarchiver/id425424353?mt=12&ls=1

Launch Unarchiver and you’ll see a file association list, tell Unarchiver to associate with .7z files (you can select others if you wish)

Once Unarchiver is associated with the .7z you can then double-click any .7z file on your Mac and it will open and uncompress like any other archive format, or you can launch Unarchiver and drag and drop 7z files into the utility

I’m saying that small amount of text doesn’t slow down the mobile load — not all the ads are loading just the TEXT for the code. Once compressed and gzipped by server/browser and cached, not an issue.

If you’re showing (3) ads on mobile then only those 3 ads are loaded, not six.

Same way one menu is hidden for mobile in responsive design but different menu would load on mobile; part of the code works on one but not the other, but both are there so page doesn’t have to ‘reload’ when changing from landscape to portrait.

Again, however, simplest way is to load only a responsive ad unit and load that in the actual templates where you want, like a sidebar widget, and Google would then resize on the fly to the viewport.

Just food for thought. I don’t work here 🙂

One sentence of code doesn’t really slow down site. It doesn’t actually LOAD the graphic and hide it; it only hides the “code” not being used for that viewport; very common thing in responsive design.

Likely time out connecting to FB. Not much else you can do about that.

Some people take different approach and make “static” widgets, and then once a week manually update the numbers. Kind of more elegant way to do it if time permits. (Pages load faster too!)

Been there 😉

Did you try doing it in custom ad box ?
https://forum.tagdiv.com/newsmag-using-other-ads/

Note some php code needs to run either inside or outside of WP loop, or might conflict with WP, or whatever.

In those cases, better to actually put the code directly in the template where you want it.

But TagDiv might have better answer. And probably would like to see example of “what” type of PHP code you’re trying to use exactly. [shortcode] won’t work, I believe.

Yep. Been using all our sites with WP 4.6.1 since it came out 🙂

Make sure you update Visual Composer plugin also!

ALSO note that many hosting panels can do basic http > https redirect at the hosting panel after the SSL/https cert is setup.

In practice however, what I have found on CentOS/Plesk/Apache with “Let’s Encrypt” that Chrome still continues to allow, and the server, continues to allow loading via http, and so it throws up errors in Chrome for mixed content.

As always, after doing all these shenanigans, test your site in a web browser to ensure you do have ‘lock’ on all pages/posts; keeping in mind the errant AdSense ad might throw an error you can’t do anything about unless you opt for text-only ads.

I updated the older SSL/https thread also with code examples ! 🙂

See
https://forum.tagdiv.com/topic/moving-to-ssl/#post-140870

As an update to this older thread; most hosting providers worth their salt are now moving to support “https everywhere” initiative with free SSL certs for https via “Let’s Encrypt,” even on shared IPs. Note using this type of cert will mean OOOOOLD web broswers might not be able to access website at all since they can’t support modern secure standards — and, really, should NOT even be used on the web. SO, some kind of ‘sniffer’ to say “hey, dummy, update your browser to Chrome…” is worthwhile.

you should also add a block like so in your htaccess file above the #wordpress stuff…

e.g., (note; this example is using pretty permalinks with post name; so don’t use my wordpress code unless you want to; this is just example of how to put in the EXTRA stuff ABOVE the #wordpress stuff!)

**this presumes APACHE server.

<IfModule mod_rewrite.c>
RewriteEngine On
    RewriteCond %{SERVER_PORT} !^443$
    RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]
</IfModule>

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

ALSO: in your wp-config.php file, this is useful:

define('WP_HOME', 'https://SITEHERE.com');
define('WP_SITEURL', 'https://SITEHERE.com');
define('WP_CONTENT_URL', 'https://SITEHERE.com/wp-content' );
define('WP_PLUGIN_URL', 'https://SITEHERE.com/wp-content/plugins' );
define('FORCE_SSL_ADMIN', true);

Finally, in some setups you might find this more useful to put at top of htaccess than my first example — basically a slightly different way of doing it:

<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{HTTPS} !=on
RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,QSA]
</IfModule>

*updated : Oct. 27, 2016 / 12:19pm PDT.

• This reply was modified 9 years by simchris.

Note you do need to setup global redirect to https for your site in htaccess file; also useful to add explicit link to site home/URL as https in your wp-config.php file including force SSL line (See WP ‘codex’ on editing wp-config.php for more info.)

You may also need to do a search/replace in your dbase via mysql/phpmyadmin in your hosting account to make sure all links previously noted as http are setup as https.

Also remember you need to change logo links, any anything like link to RSS feed, in the theme panel to https vs http manually.

After doing all that, be sure to resave permalinks, force reset sitemap XML by turning that off/on in your plugin for that, and if using any secure form, make sure you go to that “page” in your web browser, and do F12 in chrome to see if any http vs https mis-match which cause (!) in browser vs [lock].

I’ve actually just been doing this for our news sites with Newsmag theme.

AND: remember you need to submit https version of site in your Google search console as new site, reconfirm, then resubmit site maps for https version to Google.

And, if using “Let’s Encrypt” SSL cert vs paid version; I found it’s useful to check the box to allow both www and non www access, for some odd reason.

Hope that might help in some small way.

Thanks. Was going to do this myself, also 🙂

See the docs > tutorials > DIY & best of forums for theme recommendations, and also my long long winded thread from past couple of years.

Testing your post with GTmetrix.com also useful to test where you might need to tune up image compression, time to live, caching, etc.

Make sure you have working open graph (OG) tags; often done with plugin like Yoast SEO.

Whoever told you WordPress could only support 500 pages does not know what they are talking about.

TIME Magazine runs on WordPress.

Our main news system has 15,000 pages, and several of our 10 year old sites running on WP since 2005 have over 10,000 pages of content.

Remember WP serves dynamic pages; so the limitations are
1) hosting
2) memory/RAM
3) php and MySQL capabilities (see 1 and 2)
4) optimizations of your post/page structure (obviously doing 15 queries per page better than 50)

Many budget hosting platforms can’t support more than XX number of pages due to 5,000 sites being on a small web server and each site might have a low memory and resource restriction. But obviously you shouldn’t be running a 10,000 page website on $10/month hosting 😉

For those who might want to experiment,
we actually use a nifty plugin for quite awhile now called ”
Contextual Related Posts” — which has a sidebar widget, and is nice because it does a cached copy of related items per post in the post meta so actually very efficient.

Can use thumbs, or only text, can be based on cats, content, or tags, I believe.

see
https://wordpress.org/plugins/contextual-related-posts/

Your needs may vary, but we actually use this with TagDiv themes in place of the normal footer related posts, like so

(note the ‘more to read’ bottom of page)
http://californianewswire.com/2016-neurotech-leaders-forum-welcomes-key-startups-and-industry-figures-in-san-francisco/

(( note: site not fully optimized as we had web server crash Aug 5, move to new system, migrating all sites to https, and testing http/2, mod_pagespeed if off, etc. ))

• This reply was modified 9 years by simchris.

Also note, “Safari for Windows” was deprecated several years ago, but some folks still using it. So, anybody reporting that not working – it never will 🙂