Once i have everything optimized for ssl i will pass along my adventures…
In meantime for those curious this has some good info…
http://serverfault.com/questions/570288/is-it-bad-to-redirect-http-to-https
Check the entire site for internal links and ensure they are all using HTTPS if you specific your own domain name in links, so you are not causing your own redirects.
Update your <meta property=”og:url” to using the https version of your domain.
If you use <base href= again update to use HTTPS.
Install SPDY protocol if possible
Make sure to use CSS Image sprites where possible, to reduce numbers of request.
Update your sitemaps to indicate https status, so spiders over time learn this change.
Change Search Engine preferences like Google Webmaster Tools to prefer HTTPS
Where possible off-load any stactic media to HTTPS CDN servers.
Hi, mod_spdy is setup on the server; https is setup on your domain (Google “get SSL cert for my website”) or visit the SSL certificates section in your GoDaddy account if you use them for anything. You need to get SSL cert which is installed for your domain, this then allows your site pages to load via https (secure) vs http just like any ecom site or Amazon, GoDaddy, eBay, etc. The “signed” certificate provides some level of security in that a “signing authority” has verified you are who you say you are before issuing the certificate (your hosting provider may even sell SSL certs at discount; check their site).
Mod_spdy doesn’t do SEO or speed up normal http pages, only those loaded via https (secure). Hence “spdy” (short for “speedy”).
So:
1) get SSL cert for your site; this allows pages and content to load https vs http
2) check with your hosting provider on mod_spdy support which speeds up https so it’s not 10x slower than http
SSL and mod_spdy have nothing to so with the theme. SSL authenticates the website domain, not the content itself per se, although you would get a “warning” if some content is not loaded securely, like an external file not being loaded via SSL.
Hope that helps 🙂
FYI, Google News requirements have nothing to do with this “theme” but your site contents, editorial focus, original vs “cloned” content, actual editorial staff, number of updates per week, not violating Google policies (e.g., linking to a software product which allows people to download YouTube videos – for example – is a violation of Google policy), paid text links, spammy anchor links to commercial sites which are not “nofollowed,” etc.
Our various sites have been in GN since it was in beta almost a decade ago, and one of our sites running this theme is in GN now.
ref: (RTFM) – GOOGLE OFFICIAL REQUIREMENTS FOR GOOGLE NEWS:
https://support.google.com/news/publisher/answer/40787?hl=en
After playing with sub domains, Amazon CDN, etc., I found it was just simpler to load all the images locally so that things like compression, mod_pagespeed, etc. all actually work. I’d rather have the compression, progressive convert, for faster load than the tiny fraction faster load via subdomain or sub->CDN.
Frankly, a lot of that works if you are CNN or TIME magazine, but for most “small” sites and blogs, not so much.
But, this is the point of testing all the options then evaluating benefits vs drawbacks. I spent the entire month of January this year doing nothing but this kind of thing. Now I’ve gotten a tad cynical about it.
I look forward to all this shite being in the past, as it’s brain numbing. 🙂
You likely need to remove the auto generated echo home_url() to the static URL you want in all the header-styleX.php files to be safe.
in the /parts/ folder, try the
header-style-1.php
logo-mobile.php
edit this line
<a itemprop="url" href="<?php echo home_url(); ?>">
<img width="300" class="td-retina-data" data-retina="<?php echo htmlentities($td_customLogoR) ?>" src="<?php echo $td_customLogo?>" alt="<?php echo $td_logo_alt ?>"<?php echo $td_logo_title ?>/>
</a>need to replace these
href="<?php echo home_url(); ?>"
with
href="http://yoursite.com/directory"
You likely have a conflict between the methods being used.
For example when I upload a 745×483 30kb file (size on server; actual size is 24kb); the resize plugin I’m using (to make “larger” images only) along with functions quality setting of “50”, the resulting 700×357 thumb is 23.57kb on server, 1074×483 is 38.25kb; 326×235 is 10.74kb. “Actual” sizes are lower (I’m looking via my ftp tool.)
For example, the orig. 745×483 image is 24.1kb, but 28kb on disk. 30kb on unix server.
I found smushit didn’t help me.
mod_pagespeed does make my images progressive once they are cached (meaning the images seen in the page source have the pagespeed modified file names).
Ssl is implemented at you hosting co., you need ssl cert for your domain, then you load pages via https vs http. Were lucky we have our own server with it installed… Right now testing hookup with mod pagspeed weve been running since dec. typing on ipad, pardon punctuation.
FYI, if you’re using a plugin with timthumb, it usually has a cache folder for creating the thumbs, and the folder “read/write permissions” must be 777; this will generally be reset when moving to new host to 755 or even 750. You can usually set this via ftp, by going to
> wp-content > plugins > yourplug > cache*
(*or “images” or whatever – see docs for plugin you’re using, or find the folder full of images)
Change cache (CHMOD; change command) to “777” so it’s fully writable. Then go back to page using the plug, and the images should be written properly.
The theme doesn’t use timthumb.
