Installing mod_pagespeed on Cpanel Server

Download rpm from google developer website.

cd /usr/local/src; mkdir modpagespeed; cd modpagespeed
wget https://dl-ssl.google.com/dl/linux/direct/mod-pagespeed-stable_current_i386.rpm
rpm2cpio mod-pagespeed-stable_current_i386.rpm | cpio -idmv 
cp /usr/local/src/modpagespeed/usr/lib/httpd/modules/mod_pagespeed.so /usr/local/apache/modules/ 
chmod 755 /usr/local/apache/modules/mod_pagespeed.so
mkdir -p /var/mod_pagespeed/{cache,files} 
chown nobody:nobody /var/mod_pagespeed/*

cd /usr/local/src; mkdir modpagespeed; cd modpagespeed

wget https://dl-ssl.google.com/dl/linux/direct/mod-pagespeed-stable_current_i386.rpm

rpm2cpio mod-pagespeed-stable_current_i386.rpm | cpio -idmv

cp /usr/local/src/modpagespeed/usr/lib/httpd/modules/mod_pagespeed.so /usr/local/apache/modules/

chmod 755 /usr/local/apache/modules/mod_pagespeed.so

mkdir -p /var/mod_pagespeed/{cache,files}

chown nobody:nobody /var/mod_pagespeed/*

Next command need to be with some care

/usr/local/apache/bin/apxs -c -i /home/cpeasyapache/src/httpd-[hit tab key]/modules/filters/mod_deflate.c

1	/usr/local/apache/bin/apxs -c -i /home/cpeasyapache/src/httpd-[hit tab key]/modules/filters/mod_deflate.c

First write

/usr/local/apache/bin/apxs -c -i /home/cpeasyapache/src/httpd-

1	/usr/local/apache/bin/apxs -c -i /home/cpeasyapache/src/httpd-

Then press tab, it will automatically write your apache version installed, like

/usr/local/apache/bin/apxs -c -i /home/cpeasyapache/src/httpd-2.2.24/

1	/usr/local/apache/bin/apxs -c -i /home/cpeasyapache/src/httpd-2.2.24/

Then write remaining to complete command

/usr/local/apache/bin/apxs -c -i /home/cpeasyapache/src/httpd-2.2.24/modules/filters/mod_deflate.c

1	/usr/local/apache/bin/apxs -c -i /home/cpeasyapache/src/httpd-2.2.24/modules/filters/mod_deflate.c

Create a file named modpagespeed.conf

cat &gt; /usr/local/apache/conf/pagespeed.conf  &lt;
 LoadModule deflate_module modules/mod_deflate.so

 # Turn on mod_pagespeed. To completely disable mod_pagespeed, you
 # can set this to "off".
 ModPagespeed on
# Direct Apache to send all HTML output to the mod_pagespeed
 # output handler.
 AddOutputFilterByType MOD_PAGESPEED_OUTPUT_FILTER text/html
# The ModPagespeedFileCachePath and
 # ModPagespeedGeneratedFilePrefix directories must exist and be
 # writable by the apache user (as specified by the User
 # directive).
 ModPagespeedFileCachePath "/var/mod_pagespeed/cache/"
 #ModPagespeedGeneratedFilePrefix "/var/mod_pagespeed/files/" depreciated
# Override the mod_pagespeed 'rewrite level'. The default level
 # "CoreFilters" uses a set of rewrite filters that are generally
 # safe for most web pages. Most sites should not need to change
 # this value and can instead fine-tune the configuration using the
 # ModPagespeedDisableFilters and ModPagespeedEnableFilters
 # directives, below. Valid values for ModPagespeedRewriteLevel are
 # PassThrough, CoreFilters and TestingCoreFilters.
 #
 # ModPagespeedRewriteLevel PassThrough
# Explicitly disables specific filters. This is useful in
 # conjuction with ModPagespeedRewriteLevel. For instance, if one
 # of the filters in the CoreFilters needs to be disabled for a
 # site, that filter can be added to
 # ModPagespeedDisableFilters. This directive contains a
 # comma-separated list of filter names, and can be repeated.
 #
 # ModPagespeedDisableFilters rewrite_images
# Explicitly enables specific filters. This is useful in
 # conjuction with ModPagespeedRewriteLevel. For instance, filters
 # not included in the CoreFilters may be enabled using this
 # directive. This directive contains a comma-separated list of
 # filter names, and can be repeated.
 #
 # ModPagespeedEnableFilters rewrite_javascript,rewrite_css
 # ModPagespeedEnableFilters collapse_whitespace,elide_attributes
# ModPagespeedDomain
 # authorizes rewriting of JS, CSS, and Image files found in this
 # domain. By default only resources with the same origin as the
 # HTML file are rewritten. For example:
 #
 # ModPagespeedDomain cdn.myhost.com
 #
 # This will allow resources found on http://cdn.myhost.com to be
 # rewritten in addition to those in the same domain as the HTML.
 #
 # Wildcards (* and ?) are allowed in the domain specification. Be
 # careful when using them as if you rewrite domains that do not
 # send you traffic, then the site receiving the traffic will not
 # know how to serve the rewritten content.
# Other defaults (cache sizes and thresholds):
 #
 # ModPagespeedFileCacheSizeKb 102400
 # ModPagespeedFileCacheCleanIntervalMs 3600000
 # ModPagespeedLRUCacheKbPerProcess 1024
 # ModPagespeedLRUCacheByteLimit 16384
 # ModPagespeedCssInlineMaxBytes 2048
 # ModPagespeedImageInlineMaxBytes 2048
 # ModPagespeedCssImageInlineMaxBytes 2048
 # ModPagespeedJsInlineMaxBytes 2048
 # ModPagespeedCssOutlineMinBytes 3000
 # ModPagespeedJsOutlineMinBytes 3000
# Bound the number of images that can be rewritten at any one time; this
 # avoids overloading the CPU. Set this to 0 to remove the bound.
 #
 # ModPagespeedImageMaxRewritesAtOnce 8
# Settings for image optimization:
 #
 # Jpeg recompression quality (0 to 100, -1 strips metadata):
 # ModPagespeedJpegRecompressionQuality -1
 #
 # Percent of original image size below which optimized images are retained:
 # ModPagespeedImageLimitOptimizedPercent 100
 #
 # Percent of original image area below which image resizing will be
 # attempted:
 # ModPagespeedImageLimitResizeAreaPercent 100
# When Apache is set up as a browser proxy, mod_pagespeed can record
 # web-sites as they are requested, so that an image of the web is built up
 # in the directory of the proxy administrator's choosing. When ReadOnly is
 # on, only files already present in the SlurpDirectory are served by the
 # proxy.
 #
 # ModPagespeedSlurpDirectory ...
 # ModPagespeedSlurpReadOnly on
# The maximum URL size is generally limited to about 2k characters
 # due to IE: See http://support.microsoft.com/kb/208427/EN-US.
 # Apache servers by default impose a further limitation of about
 # 250 characters per URL segment (text between slashes).
 # mod_pagespeed circumvents this limitation, but if you employ
 # proxy servers in your path you may need to re-impose it by
 # overriding the setting here. The default setting is 1024
 # characters.
 #
 # ModPagespeedMaxSegmentLength 250
# Uncomment this if you want to prevent mod_pagespeed from combining files
 # (e.g. CSS files) across paths
 #
 # ModPagespeedCombineAcrossPaths off
# Explicitly tell mod_pagespeed to load some resources from disk.
 # This will speed up load time and update frequency.
 #
 # This should only be used for static resources which do not need
 # specific headers set or other processing by Apache.
 #
 # Both URL and filesystem path should specify directories and
 # filesystem path must be absolute (for now).
 #
 # ModPagespeedLoadFromFile "http://example.com/static/" "/var/www/static/"
# Enables server-side instrumentation and statistics. If this rewriter is
 # enabled, then each rewritten HTML page will have instrumentation javacript
 # added that sends latency beacons to /mod_pagespeed_beacon. These
 # statistics can be accessed at /mod_pagespeed_statistics. You must also
 # enable the mod_pagespeed_statistics and mod_pagespeed_beacon handlers
 # below.
 #
 # ModPagespeedEnableFilters add_instrumentation
# Uncomment the following line so that ModPagespeed will not cache or
 # rewrite resources with Vary: in the header, e.g. Vary: User-Agent.
 # ModPagespeedRespectVary on
# This handles the client-side instrumentation callbacks which are injected
 # by the add_instrumentation filter.
 # You can use a different location by adding the ModPagespeedBeaconUrl
 # directive; see the documentation on add_instrumentation.

 SetHandler mod_pagespeed_beacon

# Uncomment the following line if you want to disable statistics entirely.
 #
 # ModPagespeedStatistics off
# This page lets you view statistics about the mod_pagespeed module.

 Order allow,deny
 # You may insert other "Allow from" lines to add hosts you want to
 # allow to look at generated statistics. Another possibility is
 # to comment out the "Order" and "Allow" options from the config
 # file, to allow any client that can reach your server to examine
 # statistics. This might be appropriate in an experimental setup or
 # if the Apache server is protected by a reverse proxy that will
 # filter URLs in some fashion.
 Allow from localhost
 Allow from 127.0.0.1
 SetHandler mod_pagespeed_statistics

# Page /mod_pagespeed_message lets you view the latest messages from
 # mod_pagespeed, regardless of log-level in your httpd.conf
 # ModPagespeedMessageBufferSize is the maximum number of bytes you would
 # like to dump to your /mod_pagespeed_message page at one time,
 # its default value is 100k bytes.
 # Set it to 0 if you want to disable this feature.
ModPagespeedMessageBufferSize 100000
# mod_pagespeed has the ability to collect statistics about page visits as
 # well as page, resource, and div location (see div_structure_filter)
 # referrals. These will eventually be used to speed up pages with at least
 # resource pre-fetch, if not Chrome's new pre-render, technology. See
 # googlewebmastercentral.blogspot.com/2011/06/announcing-instant-pages.html
 # We recommend enabling the div_structure filter if turning on statistics
 # collection below. Enabling the div_structure filter will increase the
 # effectiveness of pre-rendering prediction, because it will take into
 # account both URLs and page locations when aggregating user click through
 # behavior. To enable the div_structure filter, uncomment the appropriate
 # line below or add div_structure to the enabled filters at the top of this
 # configuration file.
 # Page /mod_pagespeed_referer_statistics lets you view the accumulated
 # referral statistics.
 # ModPagespeedCollectRefererStatistics on enables collection (default off)
 # ModPagespeedHashRefererStatistics obscures collected info (default off)
 # ModPagespeedRefererStatisticsOutputLevel can be changed if the page
 # /mod_pagespeed_referer_statistics is slow to load:
 # - Organized (default) is the most readable and ordered logically, but
 # involves computation
 # - Simple is readable but unordered
 # - Fast is the fastest and contains all necessary information, but is
 # fairly unreadable
# ModPagespeedCollectRefererStatistics on
 # ModPagespeedHashRefererStatistics on
 # ModPagespeedRefererStatisticsOutputLevel Simple
 # ModPagespeedEnableFilters div_structure

Allow from localhost 
Allow from 127.0.0.1 
SetHandler mod_pagespeed_message 

Allow from localhost 
Allow from 127.0.0.1 
SetHandler mod_pagespeed_referer_statistics 

END

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

150

151

152

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

192

cat > /usr/local/apache/conf/pagespeed.conf <

LoadModule deflate_module modules/mod_deflate.so

# Turn on mod_pagespeed. To completely disable mod_pagespeed, you

# can set this to "off".

ModPagespeed on

# Direct Apache to send all HTML output to the mod_pagespeed

# output handler.

AddOutputFilterByType MOD_PAGESPEED_OUTPUT_FILTER text/html

# The ModPagespeedFileCachePath and

# ModPagespeedGeneratedFilePrefix directories must exist and be

# writable by the apache user (as specified by the User

# directive).

ModPagespeedFileCachePath "/var/mod_pagespeed/cache/"

#ModPagespeedGeneratedFilePrefix "/var/mod_pagespeed/files/" depreciated

# Override the mod_pagespeed 'rewrite level'. The default level

# "CoreFilters" uses a set of rewrite filters that are generally

# safe for most web pages. Most sites should not need to change

# this value and can instead fine-tune the configuration using the

# ModPagespeedDisableFilters and ModPagespeedEnableFilters

# directives, below. Valid values for ModPagespeedRewriteLevel are

# PassThrough, CoreFilters and TestingCoreFilters.

# ModPagespeedRewriteLevel PassThrough

# Explicitly disables specific filters. This is useful in

# conjuction with ModPagespeedRewriteLevel. For instance, if one

# of the filters in the CoreFilters needs to be disabled for a

# site, that filter can be added to

# ModPagespeedDisableFilters. This directive contains a

# comma-separated list of filter names, and can be repeated.

# ModPagespeedDisableFilters rewrite_images

# Explicitly enables specific filters. This is useful in

# conjuction with ModPagespeedRewriteLevel. For instance, filters

# not included in the CoreFilters may be enabled using this

# directive. This directive contains a comma-separated list of

# filter names, and can be repeated.

# ModPagespeedEnableFilters rewrite_javascript,rewrite_css

# ModPagespeedEnableFilters collapse_whitespace,elide_attributes

# ModPagespeedDomain

# authorizes rewriting of JS, CSS, and Image files found in this

# domain. By default only resources with the same origin as the

# HTML file are rewritten. For example:

# ModPagespeedDomain cdn.myhost.com

# This will allow resources found on http://cdn.myhost.com to be

# rewritten in addition to those in the same domain as the HTML.

# Wildcards (* and ?) are allowed in the domain specification. Be

# careful when using them as if you rewrite domains that do not

# send you traffic, then the site receiving the traffic will not

# know how to serve the rewritten content.

# Other defaults (cache sizes and thresholds):

# ModPagespeedFileCacheSizeKb 102400

# ModPagespeedFileCacheCleanIntervalMs 3600000

# ModPagespeedLRUCacheKbPerProcess 1024

# ModPagespeedLRUCacheByteLimit 16384

# ModPagespeedCssInlineMaxBytes 2048

# ModPagespeedImageInlineMaxBytes 2048

# ModPagespeedCssImageInlineMaxBytes 2048

# ModPagespeedJsInlineMaxBytes 2048

# ModPagespeedCssOutlineMinBytes 3000

# ModPagespeedJsOutlineMinBytes 3000

# Bound the number of images that can be rewritten at any one time; this

# avoids overloading the CPU. Set this to 0 to remove the bound.

# ModPagespeedImageMaxRewritesAtOnce 8

# Settings for image optimization:

# Jpeg recompression quality (0 to 100, -1 strips metadata):

# ModPagespeedJpegRecompressionQuality -1

# Percent of original image size below which optimized images are retained:

# ModPagespeedImageLimitOptimizedPercent 100

# Percent of original image area below which image resizing will be

# attempted:

# ModPagespeedImageLimitResizeAreaPercent 100

# When Apache is set up as a browser proxy, mod_pagespeed can record

# web-sites as they are requested, so that an image of the web is built up

# in the directory of the proxy administrator's choosing. When ReadOnly is

# on, only files already present in the SlurpDirectory are served by the

# proxy.

# ModPagespeedSlurpDirectory ...

# ModPagespeedSlurpReadOnly on

# The maximum URL size is generally limited to about 2k characters

# due to IE: See http://support.microsoft.com/kb/208427/EN-US.

# Apache servers by default impose a further limitation of about

# 250 characters per URL segment (text between slashes).

# mod_pagespeed circumvents this limitation, but if you employ

# proxy servers in your path you may need to re-impose it by

# overriding the setting here. The default setting is 1024

# characters.

# ModPagespeedMaxSegmentLength 250

# Uncomment this if you want to prevent mod_pagespeed from combining files

# (e.g. CSS files) across paths

# ModPagespeedCombineAcrossPaths off

# Explicitly tell mod_pagespeed to load some resources from disk.

# This will speed up load time and update frequency.

# This should only be used for static resources which do not need

# specific headers set or other processing by Apache.

# Both URL and filesystem path should specify directories and

# filesystem path must be absolute (for now).

# ModPagespeedLoadFromFile "http://example.com/static/" "/var/www/static/"

# Enables server-side instrumentation and statistics. If this rewriter is

# enabled, then each rewritten HTML page will have instrumentation javacript

# added that sends latency beacons to /mod_pagespeed_beacon. These

# statistics can be accessed at /mod_pagespeed_statistics. You must also

# enable the mod_pagespeed_statistics and mod_pagespeed_beacon handlers

# below.

# ModPagespeedEnableFilters add_instrumentation

# Uncomment the following line so that ModPagespeed will not cache or

# rewrite resources with Vary: in the header, e.g. Vary: User-Agent.

# ModPagespeedRespectVary on

# This handles the client-side instrumentation callbacks which are injected

# by the add_instrumentation filter.

# You can use a different location by adding the ModPagespeedBeaconUrl

# directive; see the documentation on add_instrumentation.

SetHandler mod_pagespeed_beacon

# Uncomment the following line if you want to disable statistics entirely.

# ModPagespeedStatistics off

# This page lets you view statistics about the mod_pagespeed module.

Order allow,deny

# You may insert other "Allow from" lines to add hosts you want to

# allow to look at generated statistics. Another possibility is

# to comment out the "Order" and "Allow" options from the config

# file, to allow any client that can reach your server to examine

# statistics. This might be appropriate in an experimental setup or

# if the Apache server is protected by a reverse proxy that will

# filter URLs in some fashion.

Allow from localhost

Allow from 127.0.0.1

SetHandler mod_pagespeed_statistics

# Page /mod_pagespeed_message lets you view the latest messages from

# mod_pagespeed, regardless of log-level in your httpd.conf

# ModPagespeedMessageBufferSize is the maximum number of bytes you would

# like to dump to your /mod_pagespeed_message page at one time,

# its default value is 100k bytes.

# Set it to 0 if you want to disable this feature.

ModPagespeedMessageBufferSize 100000

# mod_pagespeed has the ability to collect statistics about page visits as

# well as page, resource, and div location (see div_structure_filter)

# referrals. These will eventually be used to speed up pages with at least

# resource pre-fetch, if not Chrome's new pre-render, technology. See

# googlewebmastercentral.blogspot.com/2011/06/announcing-instant-pages.html

# We recommend enabling the div_structure filter if turning on statistics

# collection below. Enabling the div_structure filter will increase the

# effectiveness of pre-rendering prediction, because it will take into

# account both URLs and page locations when aggregating user click through

# behavior. To enable the div_structure filter, uncomment the appropriate

# line below or add div_structure to the enabled filters at the top of this

# configuration file.

# Page /mod_pagespeed_referer_statistics lets you view the accumulated

# referral statistics.

# ModPagespeedCollectRefererStatistics on enables collection (default off)

# ModPagespeedHashRefererStatistics obscures collected info (default off)

# ModPagespeedRefererStatisticsOutputLevel can be changed if the page

# /mod_pagespeed_referer_statistics is slow to load:

# - Organized (default) is the most readable and ordered logically, but

# involves computation

# - Simple is readable but unordered

# - Fast is the fastest and contains all necessary information, but is

# fairly unreadable

# ModPagespeedCollectRefererStatistics on

# ModPagespeedHashRefererStatistics on

# ModPagespeedRefererStatisticsOutputLevel Simple

# ModPagespeedEnableFilters div_structure

Allow from localhost

Allow from 127.0.0.1

SetHandler mod_pagespeed_message

Allow from localhost

Allow from 127.0.0.1

SetHandler mod_pagespeed_referer_statistics

END

Include pagespeed.conf in /usr/local/apache/conf/includes/pre_main_global.conf

vi /usr/local/apache/conf/includes/pre_main_global.conf

1	vi /usr/local/apache/conf/includes/pre_main_global.conf

Include conf/pagespeed.conf

1	Include conf/pagespeed.conf

Now rebuild apache configuration and restart apache

/scripts/buildhttpdconf 
/etc/rc.d/init.d/httpd restart

1 2	/scripts/buildhttpdconf /etc/rc.d/init.d/httpd restart

To test that mod_pagespeed is enabled, run following in your local server

curl -D- http://domainame.com | less

1	curl -D- http://domainame.com \| less

It should return

HTTP/1.1 200 OK
Date: Mon, 24 Jun 2013 13:34:26 GMT
Server: Apache/2.2.24 (Unix) mod_ssl/2.2.24 OpenSSL/1.0.0-fips mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635
Accept-Ranges: bytes
X-Mod-Pagespeed: 1.4.26.3-3101
Vary: Accept-Encoding

HTTP/1.1 200 OK

Date: Mon, 24 Jun 2013 13:34:26 GMT

Server: Apache/2.2.24 (Unix) mod_ssl/2.2.24 OpenSSL/1.0.0-fips mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635

Accept-Ranges: bytes

X-Mod-Pagespeed: 1.4.26.3-3101

Vary: Accept-Encoding

You can also go to Google speed test page to confirm pagespeed is enabled

https://developers.google.com/speed/pagespeed/insights

1	https://developers.google.com/speed/pagespeed/insights

Congrats ! you have now enabled mod_pagespeed on your cpanel server.

Please follow and like us:

Installing mod_pagespeed on Cpanel Server

Comment Policy:

Tell us what you're thinking... Cancel reply

Please follow & like us :)

Recent Posts

Installing mod_pagespeed on Cpanel Server

Related posts:

Comment Policy:

Tell us what you're thinking... Cancel reply

Please follow & like us :)

Recent Posts