yükleniyor

Cpanel / WHM Mod_Pagespeed Kurulumu Ve Ayarları

Cpanel / WHM Mod_Pagespeed Kurulumu Ve Ayarları

Mod_Pagespeed ; Google tarafından yapılmış, amacı siteleriniz’de bulunan css, js, ve resim dosyalarınızın sıkıştırılarak daha hızlı açılmasını sağlayan bir eklentidir. SEO açısından önem arzetmektedir, bu eklentiyi kullanan siteleri google yakından izlemektedir yeni sürüm çıktığında Google Web Master Tools’da otomatik mesaj gelerek yeni sürüm çıktığına dair uyarı gelmektedir. Lafı fazla uzatmadan kuruluma geçelim arkadaşlar.


Cpanel Mod_pagespeed Kurulum :

Ssh giriş yaptıktan sonra altaki kodu çalıştırın;


/usr/local/cpanel/3rdparty/bin/git clone https://github.com/pagespeed/cpanel.git /tmp/pagespeed/

Üsteki kodu uyguladıktan sonra alta ki kodları sırayla uygulayın.


cd /tmp/pagespeed/Easy

tar -zcvf Speed.pm.tar.gz pagespeed

mkdir -p /var/cpanel/easy/apache/custom_opt_mods/Cpanel/Easy

mv Speed.pm Speed.pm.tar.gz -t /var/cpanel/easy/apache/custom_opt_mods/Cpanel/Easy/

cd && rm -rf /tmp/pagespeed

Kurulumu yaptıktan sonra whm giriyoruz. Apache derleme ekranında resimdeki işlemi yapıyoruz.


Mod_Pagespeed Apache Derleme

Mod_Pagespeed Apache Derleme


Cpanel Mod_pagespeed Ayarları :

Derleme işlemi bittikten sonra WinSCP Programı ile server baglanıyoruz. Alta ki dosya konumuna giriyoruz.


/usr/local/apache/conf

pagespeed.conf dosyasını seçip yukardan düzenle ‘ye tıklıyoruz ve alt kısımda bulunana kodların hepsini kopyalıyıp pagespeed.conf dosyasına yapıştırıyoruz.


<IfModule !mod_version.c>

LoadModule version_module modules/mod_version.so

</IfModule>

<IfVersion < 2.4>

LoadModule pagespeed_module modules/mod_pagespeed.so

</IfVersion>

<IfVersion >= 2.4.2>

LoadModule pagespeed_module modules/mod_pagespeed_ap24.so

</IfVersion>

<IfModule pagespeed_module>

# Turn on mod_pagespeed. To completely disable mod_pagespeed, you

# can set this to "off".

ModPagespeed on

ModPagespeedFetchWithGzip on

SetOutputFilter DEFLATE

# 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/"

# 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, TestingCoreFilters and AllFilters.

#

ModPagespeedRewriteLevel PassThrough

# Explicitly disables specific filters. This is useful in

# conjunction 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

# conjunction 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

ModPagespeedImgInlineMaxBytes 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.

#

# ModPagespeedImgMaxRewritesAtOnce 8

# 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

# Whether or not to log timing information for rewriting filters.

# Off by default to keep logs uncluttered.

#

# ModPagespeedLogRewriteTiming on

# 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 extend_cache,combine_css,move_css_to_head,rewrite_javascript,rewrite_images,add_head,rewrite_css,collapse_whitespace,remove_comments,remove_quotes,sprite_images,convert_meta_tags

# 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.

<Location /mod_pagespeed_beacon>

SetHandler mod_pagespeed_beacon

</Location>

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

#

# ModPagespeedStatistics off

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

<Location /mod_pagespeed_statistics>

Order allow,deny

Allow from localhost

Allow from 127.0.0.1

SetHandler mod_pagespeed_statistics

</Location>

</IfModule>

Sitenizin kaynağını görüntelediğinizde değişikliği farkedeceksiniz. Ayrıca benim vps de nginx de kurulu ama hiç sorun olmadı. Umarım güzelce anlata bilmişimdir.

Ürün ve hizmetlerimiz hakkında daha detaylı bilgi almak için, Hemen Arayın! 0850 303 96 38

X

Müşteri Paneli

Şifremi Unuttum!

Henüz Hesabınız Yok mu?

Hemen Hesap Oluştur!