It looks like its not a dependencies problem, or maybe but I am not sure, found this guide and followed step one
cpanelkb. net /how-to-install-mod-pagespeed-on-cpanel-server/
everything went more or less ok but at the end I get this error:
[Fri Mar 11 23:55:25.479635 2016] [pagespeed:warn] [pid 5774] ModPagespeedGeneratedFilePrefix is deprecated. Please remove it from your configuration.
root@server [/usr/local/src/mod_pagespeed]#
ok so I took the like out from the file and stop getting thias alert.
now Iam tring with httpg -M and i get a list witjh pagespeed_module (shared)
but when i try curl -I http://yourwebsite.com I just get this info:
HTTP/1.1 302 Found
Date: Sat, 12 Mar 2016 06:19:06 GMT
Server: Apache/2.4.18 (Unix) OpenSSL/1.0.1e-fips mod_bwlimited/1.4
Location: myserver/
Content-Type: text/html; charset=iso-8859-1
according to the article mod page speed shopuld appear here.
I made a test to see if any of my resorces are being compressed or unified but nothing, looks like its not working.
Plus
I made a change to the article because I am on apache 2.4 so google developers recommends this:
PageSpeed Configuration
Enabling the Module
PageSpeed contains an “output filter” plus several content handlers.
Note: The location of the configuration file is dependent both on the Linux distribution on which PageSpeed is installed and on whether you’re using PageSpeed with Apache or Nginx.
In Apache the configuration file is pagespeed.conf and will be in either:
Debian/Ubuntu: /etc/apache2/mods-available/
CentOS/Fedora: /etc/httpd/conf.d/
In Nginx the configuration typically should go in your nginx.conf which for source installs defaults to being in:
/usr/local/nginx/conf/
In Apache PageSpeed is enabled automatically when you install the module while in Nginx you need to add several lines to your nginx.conf. In every server block where PageSpeed is enabled add:
pagespeed on;
Needs to exist and be writable by nginx. Use tmpfs for best performance.
pagespeed FileCachePath /var/ngx_pagespeed_cache;
Ensure requests for pagespeed optimized resources go to the pagespeed handler
and no extraneous headers get set.
location ~ “.pagespeed.([a-z].)?[a-z]{2}.[^.]{10}.[^.]+” {
add_header “” “”;
}
location ~ “^/pagespeed_static/” { }
location ~ “^/ngx_pagespeed_beacon$” { }
See the Admin Page documentation for instructions on how to configure handlers to provide visibility and control into PageSpeed’s operation.
Apache-Specific Configuration
Setting up the Output Filter
The output filter is used to parse, optimize, and re-serialize HTML content that is generated elsewhere in the Apache server.
Direct Apache to send all HTML output to the mod_pagespeed output handler.
AddOutputFilterByType MOD_PAGESPEED_OUTPUT_FILTER text/html
Note: mod_pagespeed automatically enables mod_deflate for compression.
Turning the module on and off
To turn mod_pagespeed ON, insert as the top line of pagespeed.conf:
ModPagespeed on
There are two ways to disable mod_pagespeed. To disable HTML rewriting but continue to serve .pagespeed. resources and parse query options (for instance for ?ModPagespeed=on) put this line in your configuration:
ModPagespeed off
To completely disable mod_pagespeed (.pagespeed. resources will result in 404s) use the following line:
Note: New feature as of 1.3.25.1
ModPagespeed unplugged
The on and off values can be used in .htaccess files, scopes, query parameters, and headers. The unplugged value can only be used in the top-level Apache configuration and in virtual hosts. Note that ModPagespeed on in a virtual host can override a top-level unplugged directive.
Support for Apache 2.4.x
mod_pagespeed is compatible with Apache 2.2.x and Apache 2.4.x series, versions 2.4.2 and newer. Please note that Apache 2.4.1 has a bug that may cause stability problems in combination with mod_pagespeed, so use with 2.4.1 is strongly discouraged.
As Apache 2.4 is not API compatible with 2.2, support for it is provided via a separate module binary, mod_pagespeed_ap24.so instead of the usual mod_pagespeed.so. The configuration provided in our binary packages will normally load the right module version automatically. However, if you upgrade the CentOS packages from an earlier version, the needed configuration change may not get applied on top of a user-customized pagespeed.conf, so you may need to adjust the LoadModule line manually.
Source builds with mod_pagespeed-provided Apache headers will build both 2.2.x and 2.4.x binaries as well, and you will need to add a LoadModule line matching the server version in use, or use a pattern similar to:
<IfModule !mod_version.c>
LoadModule version_module /usr/lib/apache2/modules/mod_version.so
<IfVersion < 2.4>
LoadModule pagespeed_module /usr/lib/apache2/modules/mod_pagespeed.so
= 2.4.2>
LoadModule pagespeed_module /usr/lib/apache2/modules/mod_pagespeed_ap24.so
soo changed the code and the file name to mod_pagespeed_ap24.so
still NOTHING!
Please help me 