Search Results for 'ssl'

Once you have ssl cert installed, you would likely add a rewrite rule to your htaccess file to gracefully direct old http links to https version. Talk to your hosting provider about activating mod spdy once you have https … And remember to test and update sitemap to ensure links point to https in sitemap, etc.

Great information. Thanks a lot Christopher. I am going to take SSL certificate. Actually, i want to know this because of your first post on this thread about mod_spdy. Thanks anyways.

Regards,

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 🙂

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

Also, anecdotal, smushit doesn’t work with SSL/https, so the ewwoptimizer is better choice if you can compile the correct binaries on server. I have not yet tested this, but was told this the other day as part of our overall testing for moving everything to SSL/https starting October 1 (coming up quick).

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.

• This reply was modified 11 years by simchris.

Hi Christopher, that’s really a nice thing to look at. I recently moved to Synthesis due to some bad experience with dreampress. They are saying they are the first one to implement mod_spdy.

I want to know from where can i start to implement SSL on this theme. Please provide some guidance.

Thanks

Nice work! @mehedi
I had planned to do something like that for WP (for our WP sites, for same reason you did it) based on the work I did building that exact thing for our classic non-WP site … but ran out of time. Will try your plug when I circle back 🙂

(example of my version running on our business site; not available as WP plugin, but same idea: http://www.send2press.com/services/press-release-distribution.shtml)

Thanks for the shout out, too. I won’t be helping out any more this month beyond bug report/fixes which I’m concentrating on now.

I’m now dealing with implementation of mod_spdy with mod_pagespeed to allow site to run under SSL for Google’s new push for that (super annoying). I’ll have some info on that once we suffer all the inevitable calamities of doing something only 10 people seem to know how to do (sigh … ask your hosting co about mod_spdy and watch their head explode). 🙂

GREAT JOB!!!!

Great dude, all the best for your website!
I don’t combine images using css sprites, they are as they were by default. Cloudflare is great, for now I’m using it anyway but I’ve planned to buy cdn and ssl cert, once I start earning. 😀

And I and you have kinda same type of website. My 21 days old and yours?

Lets compete in that (if you can help me in seo) 😛

Hello,

Apologies, I forgot to provide a link to the web site, here it is.

http://www.rosslandmuseum.ca/

If you right click on the images in the Big Slider and select “view image”, you’ll see that the original full image is called, not a resized thumbnail.

Thanks,
Peter

You might have a wait. Not everybody who is on the forum has time to fix your server for you. Your first chore would be to read through all the posts in the PageSpeed topic where many folks, including myself, have provided a wealth of FREE advice on how to optimize your server, pagespeed, caching, htaccess and set your server settings properly for gzip/deflate, time to live headers, etc.

The “tagdiv speed booster” plugin is only designed to help with issues of loading js and css files in the most efficient manner for the theme; it doesn’t do anything for your server side caching, account speed on the net (response time), gzip/deflate, expiration headers, or image compression. Put another way it’s not a “config file” for your server, it’s preset to speed up the theme, rather seamlessly in most cases. While you can add to it, if you need to have an additional plugin or something “optimized” for loading when theme pages load, it will NOT fix issues on your server or the content you upload.

Advice would be to first optimize your site content such as using GTMetrix to check your site for server side elements which need to be addressed FIRST, then move on to elements which can be addressed via htaccess, optimize images, and the like. Do all your checks with mod_pagespeed off as this caches elements while you’re working on things. Set the tagdiv speed booster last (only edit it if you understand what you’re doing); then when you have a decent setup, then switch on mod_pagespeed.

However, as noted in the PageSpeed topic, gzip/deflate, expires headers, and the like are good for 20 points all alone. Most common issue if your score is below 80 desktop.

Also, remember this forum provides theme support from the developer, not server management support. You need to learn to manage your server and hosting setup, and this is necessary regardless of what theme you run. So, unless you address those issues first, then the elements to fix in WordPress will not be very effective.

I’m sure Marius will be happy to help with questions on the td_speedbooster plugin included with the theme, but you really should read through the PageSpeed topic since I’ve provided a wealth of advice, and how-to elements there which are critical to optimizing your site — including my own mod_pagespeed settings!

• This reply was modified 11 years by simchris.

I don’t think the theme expressly is advertised as having any special/advanced support for BuddyPress … however, is believed to work with BuddyPress as you know from your prior posts on this topic. Remember that updates/upgrades are being done based on those most requested items, and this is a “newspaper” theme, and not expressly a theme designed for forums and social communities, which might be found in a theme specifically tailored for BuddyPress. Compatibility is more often the responsibility of BuddyPress devs and not the theme devs as noted on the BuddyPress site here:

(snip)

Themes

The concept of what makes a “BuddyPress Theme” can be a bit confusing. Since BuddyPress 1.7, your WordPress site is no longer required to have a theme that explicitly supports BuddyPress. Instead, BuddyPress comes with support for just about any modern and standard WordPress theme (especially the default ones.)

Back in 2010, bbPress popularized the concept of “Theme Compatibility.” This is a way of saying that even if your theme doesn’t directly support a specific feature, that feature will still function, look, and feel as it was originally intended to.

It’s a way to shift responsibility of code interoperability off of individual themes and onto feature developers to consider a wider audience.

Fun fact: WordPress has come with theme compatibility for comments for years — if your theme doesn’t directly support comments, WordPress fills in that gap and your visitors would never notice the difference. Neat, eh?

Savvy theme authors can still build beautiful and amazing WordPress themes that exclusively target BuddyPress and bbPress; theme compatibility just simplifies the process for them by giving them a set of conventions to work within.

We’ll be adding some screenshots of popular themes with BuddyPress integration soon. In the meantime check out some WordPress themes that include BuddyPress support in the WordPress theme repository.

(/snip)

That likely didn’t help, but thought I’d share based on my own experience with BuddyPress and various WP themes the past couple of years.

No prob. As I think I said, I spent an entire month (January 2014) messing with this stuff, and a mix of Amazon’s CDN, our new server, mod_pagespeed, etc.

I think I mentioned someplace the flaw in Google’s speed algorithm, where one of my test pages got a 91/100 with 47% of page rendering due to blocking elements; combined some files, now only have one blocking element, but less than 1% is considered able to render before loading the main CSS file, and the score went up to 97/100 for desktop and 91/100 mobile with user UX score of 85/100, and the items for the UX score are stupid.

(Test this page, which doesn’t use CDN, doesn’t use WordPress:
http://www.send2press.com/services/ez_price_list.shtml

You can drive yourself to drink with this stuff.

And the super annoying thing is the new expectation by Google for all pages to load via https, which requires SSL cert, and to possibly enably mod_SPDY on server since https is inherently slower than http. But … that’s another story, and the one I’m suffering with now. (Sigh.)

Ok FYI if interested, I reinstalled again yesterday because of the things Steven told me.

Well Chris- I still use the W3 Cache (page only) and wrote the rest of .htaccess by myself, like u posted in another thread. (little bit proud on myself that it did not crash 😀 )
Is everything ok with that or have any other suggestion?

See my current htaccess here:

# BEGIN W3TC Page Cache core
<IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{HTTPS} =on
    RewriteRule .* - [E=W3TC_SSL:_ssl]
    RewriteCond %{SERVER_PORT} =443
    RewriteRule .* - [E=W3TC_SSL:_ssl]
    RewriteCond %{HTTP:Accept-Encoding} gzip
    RewriteRule .* - [E=W3TC_ENC:_gzip]
    RewriteCond %{HTTP_COOKIE} w3tc_preview [NC]
    RewriteRule .* - [E=W3TC_PREVIEW:_preview]
    RewriteCond %{REQUEST_METHOD} !=POST
    RewriteCond %{QUERY_STRING} =""
    RewriteCond %{HTTP_COOKIE} !(comment_author|wp\-postpass|w3tc_logged_out|wptouch_switch_toggle) [NC]
    RewriteCond "%{DOCUMENT_ROOT}/wp-content/cache/page_enhanced/%{HTTP_HOST}/%{REQUEST_URI}/_index%{ENV:W3TC_SSL}%{ENV:W3TC_PREVIEW}.html%{ENV:W3TC_ENC}" -f
    RewriteRule .* "/wp-content/cache/page_enhanced/%{HTTP_HOST}/%{REQUEST_URI}/_index%{ENV:W3TC_SSL}%{ENV:W3TC_PREVIEW}.html%{ENV:W3TC_ENC}" [L]
</IfModule>
# END W3TC Page Cache core
# 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>
# END WordPress
AddType text/javascript .js

# BEGIN Expire headers
<IfModule mod_expires.c>
ExpiresActive On
ExpiresDefault "access plus 5 seconds"
ExpiresByType image/x-icon "access plus 2500000 seconds"
ExpiresByType image/jpeg "access plus 2500000 seconds"
ExpiresByType image/png "access plus 2500000 seconds"
ExpiresByType image/gif "access plus 2500000 seconds"
ExpiresByType application/x-shockwave-flash "access plus 2500000 seconds"
ExpiresByType text/css "access plus 700000 seconds"
ExpiresByType text/javascript "access plus 700000 seconds"
ExpiresByType application/javascript "access plus 700000 seconds"
ExpiresByType application/x-javascript "access plus 700000 seconds"
ExpiresByType text/html "access plus 600 seconds"
ExpiresByType application/xhtml+xml "access plus 600 seconds"
</IfModule>
# END Expire headers

# BEGIN Cache-Control Headers
<IfModule mod_headers.c>
<filesMatch "\.(ico|jpe?g|png|gif|swf)$">
Header set Cache-Control "public"
</filesMatch>
<filesMatch "\.(css)$">
Header set Cache-Control "public"
</filesMatch>
<filesMatch "\.(js)$">
Header set Cache-Control "private"
</filesMatch>
<filesMatch "\.(x?html?|php)$">
Header set Cache-Control "private, must-revalidate"
</filesMatch>
</IfModule>
# END Cache-Control Headers

<IfModule mod_headers.c>
    Header unset ETag
</IfModule>
<IfModule mod_alias.c>
RedirectMatch 403 /xmlrpc.php
</IfModule>

# pass the default character set
AddDefaultCharset utf-8
# BEGIN Keep-Alive
<ifModule mod_headers.c>
Header set Connection keep-alive
</ifModule>
# END Keep-Alive

#BEGIN GZIP 
<IfModule mod_deflate.c>
<filesMatch "\.(js|css|html|php)$">
SetOutputFilter DEFLATE
</filesMatch>
</IfModule>
#END GZIP

#BEGIN CF ALLOW
Allow from 2400:cb00::/32
Allow from 2606:4700::/32
Allow from 2803:f800::/32
Allow from 2405:b500::/32
Allow from 2405:8100::/32
#END CF ALLOW

As you can see I had to add the keep-alive code and other stuff like gzip- because otherwise GTMetrix would complain about that.

http://gtmetrix.com/reports/cherrykoks.de/4DKTK3Af I guess I can not influence the the both points about cloudflare?

The only thing I’m little bit confused about, is the fact that the mentioned code

 foreach ($this->styles_for_footer as $style_id => $style_src) {
            echo "<link rel='stylesheet' id='" . $style_id . "-css'  href='" . $style_src . "?ver=" . $current_theme_version . "' type='text/css' media='all' />\n";

in the booster plugin causes my strings. Can I change that?

And:

in the Pagespeed guide from tagdiv I read this:

The plugin will move the theme and recommended plugins js and css at the page bottom. If you have other plugins installed you have to modify the Speed Booster plugin file so it will also move those files at end of the page. In the next section you will learn how to accomplish this.
4.2 To get the list of registered css and js add the following code at the end of the functions.php file:
function td_inspect_scripts() {
global $wp_scripts, $wp_styles;
echo ‘registered scripts<br>’;
foreach ($wp_scripts->queue as $handle) {
echo $handle . ‘ | ‘ . $wp_scripts->registered[$handle]->src . ‘<br>’;
}
echo ‘registered styles<br>’;
foreach ($wp_styles->queue as $handle) {
echo $handle . ‘ | ‘ . $wp_styles->registered[$handle]->src . ‘<br>’;
}
}
add_action( ‘wp_print_scripts’, ‘td_inspect_scripts’ );

SpeedBooster plugin ist runnin as you know, do I have to change that as advised?

The sentence with “If you have other plugins installed you have to modify plugin so it will also move those files”

Other plugins means = every plugin I’m using? No problem to add this code to functions.php – just wanna make sure if this is right.

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