{"id":4506,"date":"2026-02-05T15:52:08","date_gmt":"2026-02-05T12:52:08","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/woocommerce-icin-cdn-ve-onbellek-ayarlari-sepet-ve-odeme-sayfalarini-bozmadan-hizlanmak\/"},"modified":"2026-02-05T15:52:08","modified_gmt":"2026-02-05T12:52:08","slug":"woocommerce-icin-cdn-ve-onbellek-ayarlari-sepet-ve-odeme-sayfalarini-bozmadan-hizlanmak","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/woocommerce-icin-cdn-ve-onbellek-ayarlari-sepet-ve-odeme-sayfalarini-bozmadan-hizlanmak\/","title":{"rendered":"WooCommerce \u0130\u00e7in CDN ve \u00d6nbellek Ayarlar\u0131: Sepet ve \u00d6deme Sayfalar\u0131n\u0131 Bozmadan H\u0131zlanmak"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><p>WooCommerce ma\u011fazalar\u0131nda performans konu\u015fuldu\u011funda, konu \u00e7ok h\u0131zl\u0131 bir \u015fekilde <strong>CDN<\/strong> ve <strong>\u00f6nbellek<\/strong> ayarlar\u0131na geliyor. Ancak e-ticaret taraf\u0131nda klasik WordPress blog\u2019lar\u0131ndan farkl\u0131 bir ger\u00e7eklik var: Sepet, \u00f6deme ve hesap sayfalar\u0131 tamamen dinamik \u00e7al\u0131\u015f\u0131yor ve en ufak yanl\u0131\u015f cache kural\u0131; bo\u015f sepetler, kaybolan kuponlar, hatal\u0131 kargo \u00fccretleri ve tamamlanmayan sipari\u015fler olarak size geri d\u00f6n\u00fcyor. Bu yaz\u0131da DCHost ekibi olarak sahada defalarca test etti\u011fimiz, canl\u0131 WooCommerce ma\u011fazalar\u0131nda uygulad\u0131\u011f\u0131m\u0131z stratejileri sade bir dille toparlayaca\u011f\u0131z.<\/p>\n<p>Amac\u0131m\u0131z; \u201cCDN kapal\u0131 kals\u0131n, sorun \u00e7\u0131kmas\u0131n\u201d de\u011fil, tam tersi: <strong>CDN ve \u00f6nbelle\u011fi agresif ama kontroll\u00fc kullanarak<\/strong> ma\u011fazan\u0131z\u0131 h\u0131zland\u0131rmak, bunu yaparken de <strong>sepet ve \u00f6deme ad\u0131mlar\u0131n\u0131 bozmadan<\/strong> ilerlemek. URL bazl\u0131 hari\u00e7 tutma, cookie tabanl\u0131 cache bypass, HTTP ba\u015fl\u0131klar\u0131 ve farkl\u0131 web sunucular\u0131nda (Nginx, Apache, LiteSpeed) pratik kurallara kadar ad\u0131m ad\u0131m gidece\u011fiz. Son b\u00f6l\u00fcmde ise elinizin alt\u0131nda tutabilece\u011finiz uygulanabilir bir kontrol listesi bulacaks\u0131n\u0131z.<\/p>\n<div id=\"toc_container\" class=\"toc_transparent no_bullets\"><p class=\"toc_title\">\u0130&ccedil;indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#WooCommercede_Hiz_ve_CDN_Neden_Bu_Kadar_Kritik\"><span class=\"toc_number toc_depth_1\">1<\/span> WooCommerce\u2019de H\u0131z ve CDN Neden Bu Kadar Kritik?<\/a><\/li><li><a href=\"#CDN_Nedir_WooCommercede_Ne_Ise_Yarar\"><span class=\"toc_number toc_depth_1\">2<\/span> CDN Nedir, WooCommerce\u2019de Ne \u0130\u015fe Yarar?<\/a><\/li><li><a href=\"#WooCommercede_Asla_Onbellege_Alinmamasi_Gereken_Sayfalar\"><span class=\"toc_number toc_depth_1\">3<\/span> WooCommerce\u2019de Asla \u00d6nbelle\u011fe Al\u0131nmamas\u0131 Gereken Sayfalar<\/a><\/li><li><a href=\"#WooCommerce_Icin_Guvenli_CDN_ve_Onbellek_Stratejisi\"><span class=\"toc_number toc_depth_1\">4<\/span> WooCommerce \u0130\u00e7in G\u00fcvenli CDN ve \u00d6nbellek Stratejisi<\/a><ul><li><a href=\"#1_Statik_Dosyalari_CDNe_Tasi_HTMLi_Dikkatli_Cachele\"><span class=\"toc_number toc_depth_2\">4.1<\/span> 1) Statik Dosyalar\u0131 CDN\u2019e Ta\u015f\u0131, HTML\u2019i Dikkatli Cache\u2019le<\/a><\/li><li><a href=\"#2_Tam_Sayfa_Onbellegi_Full_Page_Cache_Dikkatli_Kullan\"><span class=\"toc_number toc_depth_2\">4.2<\/span> 2) Tam Sayfa \u00d6nbelle\u011fi (Full Page Cache) Dikkatli Kullan<\/a><\/li><li><a href=\"#3_URL_Bazli_Cache_Bypass_Kurallari\"><span class=\"toc_number toc_depth_2\">4.3<\/span> 3) URL Bazl\u0131 Cache Bypass Kurallar\u0131<\/a><\/li><li><a href=\"#4_Cookie_Bazli_Cache_Bypass_Sepette_Urun_Varsa_Cache_Yok\"><span class=\"toc_number toc_depth_2\">4.4<\/span> 4) Cookie Bazl\u0131 Cache Bypass: Sepette \u00dcr\u00fcn Varsa Cache Yok<\/a><\/li><li><a href=\"#5_Kullanici_Rolune_Gore_Onbellek\"><span class=\"toc_number toc_depth_2\">4.5<\/span> 5) Kullan\u0131c\u0131 Rol\u00fcne G\u00f6re \u00d6nbellek<\/a><\/li><\/ul><\/li><li><a href=\"#Farkli_Web_Sunucularinda_WooCommerce_Cache_Kurallari\"><span class=\"toc_number toc_depth_1\">5<\/span> Farkl\u0131 Web Sunucular\u0131nda WooCommerce Cache Kurallar\u0131<\/a><ul><li><a href=\"#Nginx_FastCGI_Cache_Icin_Ornek_Konfigurasyon\"><span class=\"toc_number toc_depth_2\">5.1<\/span> Nginx FastCGI Cache \u0130\u00e7in \u00d6rnek Konfig\u00fcrasyon<\/a><\/li><li><a href=\"#LiteSpeed_Web_Sunucusu_ve_LiteSpeed_Cache_Eklentisi\"><span class=\"toc_number toc_depth_2\">5.2<\/span> LiteSpeed Web Sunucusu ve LiteSpeed Cache Eklentisi<\/a><\/li><li><a href=\"#Apache_Varnish_veya_Reverse_Proxy_Onbellegi\"><span class=\"toc_number toc_depth_2\">5.3<\/span> Apache + Varnish veya Reverse Proxy \u00d6nbelle\u011fi<\/a><\/li><\/ul><\/li><li><a href=\"#CDN_Tarafinda_WooCommerce_Icin_Ozel_Kurallar\"><span class=\"toc_number toc_depth_1\">6<\/span> CDN Taraf\u0131nda WooCommerce \u0130\u00e7in \u00d6zel Kurallar<\/a><ul><li><a href=\"#1_HTML_Icin_Temel_Cache_Politikasi\"><span class=\"toc_number toc_depth_2\">6.1<\/span> 1) HTML \u0130\u00e7in Temel Cache Politikas\u0131<\/a><\/li><li><a href=\"#2_Sepet_ve_Odeme_Icin_URL_Bazli_Haric_Tutma\"><span class=\"toc_number toc_depth_2\">6.2<\/span> 2) Sepet ve \u00d6deme \u0130\u00e7in URL Bazl\u0131 Hari\u00e7 Tutma<\/a><\/li><li><a href=\"#3_Cache-Key_ve_Cookie_Farkindaligi\"><span class=\"toc_number toc_depth_2\">6.3<\/span> 3) Cache-Key ve Cookie Fark\u0131ndal\u0131\u011f\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#Sepet_ve_Odeme_Sayfalari_Icin_HTTP_Basliklari_ve_Cookie_Stratejisi\"><span class=\"toc_number toc_depth_1\">7<\/span> Sepet ve \u00d6deme Sayfalar\u0131 \u0130\u00e7in HTTP Ba\u015fl\u0131klar\u0131 ve Cookie Stratejisi<\/a><ul><li><a href=\"#1_Cache-Control_Basliklari\"><span class=\"toc_number toc_depth_2\">7.1<\/span> 1) Cache-Control Ba\u015fl\u0131klar\u0131<\/a><\/li><li><a href=\"#2_Cookie_Guvenligi_ve_SameSite\"><span class=\"toc_number toc_depth_2\">7.2<\/span> 2) Cookie G\u00fcvenli\u011fi ve SameSite<\/a><\/li><\/ul><\/li><li><a href=\"#WooCommerce_Performansini_Destekleyen_Diger_Onbellek_Katmanlari\"><span class=\"toc_number toc_depth_1\">8<\/span> WooCommerce Performans\u0131n\u0131 Destekleyen Di\u011fer \u00d6nbellek Katmanlar\u0131<\/a><ul><li><a href=\"#1_PHP_OPcache\"><span class=\"toc_number toc_depth_2\">8.1<\/span> 1) PHP OPcache<\/a><\/li><li><a href=\"#2_Nesne_Onbellegi_Redis_Memcached\"><span class=\"toc_number toc_depth_2\">8.2<\/span> 2) Nesne \u00d6nbelle\u011fi (Redis \/ Memcached)<\/a><\/li><li><a href=\"#3_Veritabani_Optimizasyonu\"><span class=\"toc_number toc_depth_2\">8.3<\/span> 3) Veritaban\u0131 Optimizasyonu<\/a><\/li><li><a href=\"#4_Dogru_Sunucu_Kaynaklari_ve_DCHost_Altyapisi\"><span class=\"toc_number toc_depth_2\">8.4<\/span> 4) Do\u011fru Sunucu Kaynaklar\u0131 ve DCHost Altyap\u0131s\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#Adim_Adim_WooCommerce_Icin_Guvenli_CDN_ve_Cache_Kontrol_Listesi\"><span class=\"toc_number toc_depth_1\">9<\/span> Ad\u0131m Ad\u0131m: WooCommerce \u0130\u00e7in G\u00fcvenli CDN ve Cache Kontrol Listesi<\/a><\/li><li><a href=\"#Sonuc_Sepeti_Bozmadan_Hizlanan_WooCommerce_Magazasi\"><span class=\"toc_number toc_depth_1\">10<\/span> Sonu\u00e7: Sepeti Bozmadan H\u0131zlanan WooCommerce Ma\u011fazas\u0131<\/a><\/li><\/ul><\/div>\n<h2><span id=\"WooCommercede_Hiz_ve_CDN_Neden_Bu_Kadar_Kritik\">WooCommerce\u2019de H\u0131z ve CDN Neden Bu Kadar Kritik?<\/span><\/h2>\n<p>WooCommerce, WordPress \u00fczerinde \u00e7al\u0131\u015fan olduk\u00e7a esnek ama ayn\u0131 zamanda veritaban\u0131 ve PHP taraf\u0131nda a\u011f\u0131rla\u015fmaya meyilli bir e-ticaret eklentisi. \u00dcr\u00fcn sayfalar\u0131, filtreler, kampanya etiketleri, stok kontrolleri, kuponlar, kargo hesaplamalar\u0131\u2026 Hepsi her istekle birlikte arka planda \u00e7al\u0131\u015f\u0131yor.<\/p>\n<p>\u00d6zellikle \u015fu senaryolarda performans kritik hale geliyor:<\/p>\n<ul>\n<li>Yo\u011fun kampanya d\u00f6nemleri (indirim g\u00fcnleri, \u00f6zel g\u00fcnler, TV reklam\u0131 sonras\u0131 trafik art\u0131\u015f\u0131)<\/li>\n<li>Geni\u015f \u00fcr\u00fcn katalo\u011funa sahip ma\u011fazalar (binlerce \u00fcr\u00fcn, onlarca kategori)<\/li>\n<li>Mobil trafi\u011fin y\u00fcksek oldu\u011fu, zay\u0131f ba\u011flant\u0131lardan eri\u015filen siteler<\/li>\n<\/ul>\n<p>Bu noktada devreye iki temel ara\u00e7 giriyor:<\/p>\n<ul>\n<li><strong>CDN (Content Delivery Network)<\/strong>: Statik dosyalar\u0131n\u0131z\u0131 (CSS, JS, g\u00f6rseller, fontlar) ziyaret\u00e7iye en yak\u0131n noktadan sunarak ilk y\u00fckleme s\u00fcresini d\u00fc\u015f\u00fcr\u00fcr.<\/li>\n<li><strong>\u00d6nbellek (cache)<\/strong>: Sunucunun her istekte ayn\u0131 PHP kodlar\u0131n\u0131 ve veritaban\u0131 sorgular\u0131n\u0131 <em>yeniden<\/em> \u00e7al\u0131\u015ft\u0131rmas\u0131n\u0131 engelleyen, haz\u0131rlanan \u00e7\u0131kt\u0131y\u0131 belirli bir s\u00fcre saklayan katman.<\/li>\n<\/ul>\n<p>Sorun, bu iki katman\u0131n yanl\u0131\u015f yap\u0131land\u0131r\u0131ld\u0131\u011f\u0131nda <strong>dinamik e-ticaret s\u00fcre\u00e7leriyle \u00e7ak\u0131\u015fmas\u0131<\/strong>. Bu yaz\u0131n\u0131n oda\u011f\u0131 tam da buras\u0131: Hangi sayfalar\u0131, ne kadar s\u00fcre, hangi seviyede cache\u2019lemeniz gerekti\u011fini netle\u015ftirmek.<\/p>\n<h2><span id=\"CDN_Nedir_WooCommercede_Ne_Ise_Yarar\">CDN Nedir, WooCommerce\u2019de Ne \u0130\u015fe Yarar?<\/span><\/h2>\n<p>CDN, sitenizin bar\u0131nd\u0131\u011f\u0131 sunucudan ba\u011f\u0131ms\u0131z \u00e7al\u0131\u015fan, d\u00fcnya geneline da\u011f\u0131lm\u0131\u015f noktalardan (POP) i\u00e7erik da\u011f\u0131tan bir a\u011fd\u0131r. Temel \u00e7al\u0131\u015fma mant\u0131\u011f\u0131:<\/p>\n<ul>\n<li>\u0130lk istekte dosyay\u0131 origin sunucudan (\u00f6rne\u011fin DCHost \u00fczerindeki <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a>\u2019inizden) al\u0131r.<\/li>\n<li>Belirli bir s\u00fcre kendi noktas\u0131nda \u00f6nbelle\u011fe al\u0131r.<\/li>\n<li>Ayn\u0131 dosya tekrar talep edildi\u011finde, kullan\u0131c\u0131ya do\u011frudan CDN\u2019den sunar.<\/li>\n<\/ul>\n<p>WooCommerce taraf\u0131nda CDN\u2019in ideal kullan\u0131m senaryosu:<\/p>\n<ul>\n<li><strong>G\u00f6rseller<\/strong> (\u00fcr\u00fcn g\u00f6rselleri, banner\u2019lar, ikonlar)<\/li>\n<li><strong>CSS ve JS<\/strong> dosyalar\u0131<\/li>\n<li>Font dosyalar\u0131<\/li>\n<li>Baz\u0131 durumlarda sepet\/\u00f6deme <em>d\u0131\u015f\u0131ndaki<\/em> HTML sayfalar\u0131<\/li>\n<\/ul>\n<p>CDN ile neleri cache\u2019leyece\u011finiz ve hangi ba\u015fl\u0131klarla (Cache-Control, Expires vb.) y\u00f6netece\u011finiz konusu, daha \u00f6nce detayl\u0131 anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/cdn-onbellekleme-cache-control-ve-edge-kurallari-wordpress-ve-woocommercede-tam-isabet-ayarlar\/\">CDN \u00f6nbellekleme ve Cache-Control ba\u015fl\u0131klar\u0131n\u0131 do\u011fru kullanma rehberimizle<\/a> de do\u011frudan ba\u011flant\u0131l\u0131. Burada WooCommerce\u2019e \u00f6zg\u00fc k\u0131s\u0131mlar\u0131 derinle\u015ftirece\u011fiz.<\/p>\n<h2><span id=\"WooCommercede_Asla_Onbellege_Alinmamasi_Gereken_Sayfalar\">WooCommerce\u2019de Asla \u00d6nbelle\u011fe Al\u0131nmamas\u0131 Gereken Sayfalar<\/span><\/h2>\n<p>\u0130lk kural\u0131 netle\u015ftirelim: <strong>Her \u015feyi cache\u2019lemek performans\u0131 art\u0131rmaz, baz\u0131 \u015feyleri cache\u2019lemek sadece ma\u011fazan\u0131z\u0131 bozar.<\/strong> WooCommerce\u2019de \u00f6zellikle bu URL ve i\u015flemler <strong>HTML d\u00fczeyinde \u00f6nbelle\u011fe al\u0131nmamal\u0131d\u0131r<\/strong>:<\/p>\n<ul>\n<li><strong>Sepet sayfas\u0131<\/strong>: Genellikle <code>\/cart\/<\/code><\/li>\n<li><strong>\u00d6deme sayfas\u0131<\/strong>: Genellikle <code>\/checkout\/<\/code><\/li>\n<li><strong>Hesab\u0131m sayfas\u0131<\/strong>: <code>\/my-account\/<\/code> ve alt URL\u2019leri<\/li>\n<li><strong>Giri\u015f\/kay\u0131t sayfalar\u0131<\/strong><\/li>\n<li><strong>Sepete ekleme i\u015flemleri<\/strong>: <code>?add-to-cart=<\/code> parametresi i\u00e7eren URL\u2019ler<\/li>\n<li><strong>AJAX endpoint\u2019leri<\/strong>: <code>\/wp-admin\/admin-ajax.php<\/code>, <code>?wc-ajax=<\/code> i\u00e7eren istekler<\/li>\n<li><strong>REST API<\/strong>: <code>\/wp-json\/<\/code> alt\u0131ndaki istekler<\/li>\n<\/ul>\n<p>Nedeni basit: Bu sayfalar <strong>kullan\u0131c\u0131ya \u00f6zeldir<\/strong>. Ayn\u0131 URL, farkl\u0131 ziyaret\u00e7iler i\u00e7in farkl\u0131 i\u00e7erik \u00fcretir. Bir m\u00fc\u015fterinin sepetini cache\u2019leyip ba\u015fka bir m\u00fc\u015fteriye vermek; hem g\u00fcvenlik, hem de kullan\u0131c\u0131 deneyimi a\u00e7\u0131s\u0131ndan kabul edilemez.<\/p>\n<p>Dolay\u0131s\u0131yla \u201cWooCommerce i\u00e7in CDN ve \u00f6nbellek ayarlar\u0131\u201d dendi\u011finde ilk yap\u0131lacak i\u015f, bu kritik URL\u2019ler i\u00e7in hem sunucu taraf\u0131nda hem de CDN taraf\u0131nda <strong>bypass\/hari\u00e7 tutma kurallar\u0131<\/strong> tan\u0131mlamakt\u0131r.<\/p>\n<h2><span id=\"WooCommerce_Icin_Guvenli_CDN_ve_Onbellek_Stratejisi\">WooCommerce \u0130\u00e7in G\u00fcvenli CDN ve \u00d6nbellek Stratejisi<\/span><\/h2>\n<h3><span id=\"1_Statik_Dosyalari_CDNe_Tasi_HTMLi_Dikkatli_Cachele\">1) Statik Dosyalar\u0131 CDN\u2019e Ta\u015f\u0131, HTML\u2019i Dikkatli Cache\u2019le<\/span><\/h3>\n<p>\u00c7o\u011fu ma\u011faza i\u00e7in ba\u015flang\u0131\u00e7taki en g\u00fcvenli senaryo \u015fu:<\/p>\n<ul>\n<li>G\u00f6rseller, CSS, JS ve font dosyalar\u0131n\u0131 CDN \u00fczerinden sunmak<\/li>\n<li>HTML sayfalar\u0131n\u0131 ilk etapta <strong>CDN taraf\u0131nda cache\u2019lememek<\/strong><\/li>\n<\/ul>\n<p>B\u00f6ylece:<\/p>\n<ul>\n<li>En a\u011f\u0131r dosyalar (\u00f6zellikle \u00fcr\u00fcn g\u00f6rselleri) co\u011frafi olarak kullan\u0131c\u0131ya yak\u0131n noktadan gelir.<\/li>\n<li>Sepet\/\u00f6deme gibi dinamik ak\u0131\u015flara m\u00fcdahale etmemi\u015f olursunuz.<\/li>\n<\/ul>\n<p>Daha ileri bir seviyeye ge\u00e7mek isterseniz, sepet ve \u00f6deme hari\u00e7 di\u011fer baz\u0131 sayfalar i\u00e7in (\u00f6r. blog, statik i\u00e7erik sayfalar\u0131) CDN taraf\u0131nda da HTML cache\u2019i a\u00e7abilirsiniz. Bunun i\u00e7in <strong>URL bazl\u0131 kurallar<\/strong> tan\u0131mlaman\u0131z \u015fart; buna a\u015fa\u011f\u0131da de\u011finece\u011fiz.<\/p>\n<h3><span id=\"2_Tam_Sayfa_Onbellegi_Full_Page_Cache_Dikkatli_Kullan\">2) Tam Sayfa \u00d6nbelle\u011fi (Full Page Cache) Dikkatli Kullan<\/span><\/h3>\n<p>Sunucu taraf\u0131nda Nginx FastCGI cache, LiteSpeed Cache, Varnish gibi tam sayfa \u00f6nbellek \u00e7\u00f6z\u00fcmleri WooCommerce\u2019i ciddi anlamda h\u0131zland\u0131rabilir. Ancak yanl\u0131\u015f bir kural, sepet\/\u00f6deme ad\u0131mlar\u0131n\u0131 an\u0131nda bozabilir.<\/p>\n<p>WordPress genelinde tam sayfa cache kullan\u0131m\u0131n\u0131, pratik \u00f6rneklerle birlikte <a href=\"https:\/\/www.dchost.com\/blog\/wordpresste-tam-sayfa-onbellekleme-nasil-kurulur-nginx-fastcgi-cache-varnish-ve-litespeed-cache-ile-woocommercee-nazikce-dokunmak\/\">WordPress\u2019te tam sayfa \u00f6nbellekleme rehberimizde<\/a> ayr\u0131nt\u0131l\u0131 anlatt\u0131k. WooCommerce \u00f6zelinde ise \u015fu ekstra kurallar kritik:<\/p>\n<ul>\n<li>Sepet, \u00f6deme, hesab\u0131m, giri\u015f\/kay\u0131t sayfalar\u0131n\u0131 URl\u2019e g\u00f6re <strong>her zaman cache d\u0131\u015f\u0131 b\u0131rak\u0131n<\/strong>.<\/li>\n<li><strong>Oturum a\u00e7m\u0131\u015f kullan\u0131c\u0131lar<\/strong> i\u00e7in HTML cache\u2019i devre d\u0131\u015f\u0131 b\u0131rak\u0131n.<\/li>\n<li><strong>woocommerce_cart_hash<\/strong> ve <strong>woocommerce_items_in_cart<\/strong> cookie\u2019leri varsa cache\u2019i bypass edin.<\/li>\n<\/ul>\n<h3><span id=\"3_URL_Bazli_Cache_Bypass_Kurallari\">3) URL Bazl\u0131 Cache Bypass Kurallar\u0131<\/span><\/h3>\n<p>Hem sunucu hem de CDN taraf\u0131nda yapman\u0131z gereken ilk \u015feylerden biri, belirli URL desenlerini asla cache\u2019e sokmamakt\u0131r. \u00d6rne\u011fin:<\/p>\n<ul>\n<li><code>\/cart\/<\/code><\/li>\n<li><code>\/checkout\/<\/code><\/li>\n<li><code>\/my-account\/<\/code><\/li>\n<li><code>\/wp-admin\/<\/code>, <code>\/wp-login.php<\/code><\/li>\n<li><code>*wc-ajax=*<\/code> i\u00e7eren URL\u2019ler<\/li>\n<li><code>*add-to-cart=*<\/code> i\u00e7eren URL\u2019ler<\/li>\n<\/ul>\n<p>CDN panelinizde genellikle \u201cPage Rules \/ Rules \/ Cache Bypass\u201d benzeri bir b\u00f6l\u00fcmde; bu URL kal\u0131plar\u0131na <strong>cache kapal\u0131<\/strong> ya da <strong>cache bypass<\/strong> davran\u0131\u015f\u0131 ataman\u0131z gerekir. Sunucu taraf\u0131nda da benzer mant\u0131\u011f\u0131 Nginx location bloklar\u0131, Apache Rewrite\/Cache ayarlar\u0131 veya LiteSpeed Cache eklentisinin \u201cDo Not Cache URIs\u201d alan\u0131 ile uygulayabilirsiniz.<\/p>\n<h3><span id=\"4_Cookie_Bazli_Cache_Bypass_Sepette_Urun_Varsa_Cache_Yok\">4) Cookie Bazl\u0131 Cache Bypass: Sepette \u00dcr\u00fcn Varsa Cache Yok<\/span><\/h3>\n<p>WooCommerce, \u00f6zellikle sepet durumu ve giri\u015f yapm\u0131\u015f kullan\u0131c\u0131lar i\u00e7in \u00e7e\u015fitli cookie\u2019ler kullan\u0131r. En kritik olanlar:<\/p>\n<ul>\n<li><code>woocommerce_items_in_cart<\/code><\/li>\n<li><code>woocommerce_cart_hash<\/code><\/li>\n<li><code>wordpress_logged_in_*<\/code><\/li>\n<\/ul>\n<p>G\u00fcvenli strateji:<\/p>\n<ul>\n<li>Bu cookie\u2019lerden herhangi biri mevcutsa, HTML cache <strong>bypass<\/strong> edilsin.<\/li>\n<li>Cookie yoksa ve URL sepet\/\u00f6deme de\u011filse, cache devreye girebilsin.<\/li>\n<\/ul>\n<p>B\u00f6ylece:<\/p>\n<ul>\n<li>Sepete \u00fcr\u00fcn eklememi\u015f, oturum a\u00e7mam\u0131\u015f ziyaret\u00e7iler i\u00e7in agresif cache ile y\u00fcksek h\u0131z sa\u011flars\u0131n\u0131z.<\/li>\n<li>Sepete \u00fcr\u00fcn ekleyen veya giri\u015f yapan kullan\u0131c\u0131lar i\u00e7in her zaman taze, ki\u015fiye \u00f6zel i\u00e7erik sunars\u0131n\u0131z.<\/li>\n<\/ul>\n<h3><span id=\"5_Kullanici_Rolune_Gore_Onbellek\">5) Kullan\u0131c\u0131 Rol\u00fcne G\u00f6re \u00d6nbellek<\/span><\/h3>\n<p>Bir\u00e7ok ma\u011fazada y\u00f6netici veya edit\u00f6r rol\u00fcndeki kullan\u0131c\u0131lar i\u00e7in site, \u00f6nbellek y\u00fcz\u00fcnden \u201cyanl\u0131\u015f\u201d g\u00f6r\u00fcnebiliyor. \u0130yi bir pratik:<\/p>\n<ul>\n<li><strong>Y\u00f6netici, edit\u00f6r, ma\u011faza y\u00f6neticisi<\/strong> gibi rollerde oturum a\u00e7an kullan\u0131c\u0131lar i\u00e7in daima cache bypass uygulay\u0131n.<\/li>\n<li>S\u0131radan m\u00fc\u015fteriler ve anonim ziyaret\u00e7iler i\u00e7in cache kurallar\u0131 ge\u00e7erli olsun.<\/li>\n<\/ul>\n<p>Bunu genellikle:<\/p>\n<ul>\n<li>WordPress taraf\u0131nda bir cache eklentisi (kullan\u0131yorsan\u0131z) ile rol bazl\u0131 kural yazarak<\/li>\n<li>CDN taraf\u0131nda ise <em>logged-in cookie<\/em> varl\u0131\u011f\u0131na g\u00f6re varyantlar olu\u015fturarak<\/li>\n<\/ul>\n<p>ba\u015farabilirsiniz.<\/p>\n<h2><span id=\"Farkli_Web_Sunucularinda_WooCommerce_Cache_Kurallari\">Farkl\u0131 Web Sunucular\u0131nda WooCommerce Cache Kurallar\u0131<\/span><\/h2>\n<h3><span id=\"Nginx_FastCGI_Cache_Icin_Ornek_Konfigurasyon\">Nginx FastCGI Cache \u0130\u00e7in \u00d6rnek Konfig\u00fcrasyon<\/span><\/h3>\n<p>Nginx FastCGI cache, do\u011fru kuruldu\u011funda WooCommerce i\u00e7in olduk\u00e7a verimli bir tam sayfa \u00f6nbellek \u00e7\u00f6z\u00fcm\u00fc. A\u015fa\u011f\u0131daki sadele\u015ftirilmi\u015f \u00f6rnek, mant\u0131\u011f\u0131 anlaman\u0131z i\u00e7in yeterli olacakt\u0131r:<\/p>\n<pre class=\"language-nginx line-numbers\"><code class=\"language-nginx\">set $skip_cache 0;\n\n# Sepet, \u00f6deme, hesab\u0131m, admin, login, ajax vb. i\u00e7in cache kapal\u0131\nif ($request_uri ~* \n    &quot;(wp-admin|wp-login.php|cart|my-account|checkout|wc-ajax|get_refreshed_fragments|feed|sitemap)&quot; \n) {\n    set $skip_cache 1;\n}\n\n# Giri\u015f yapm\u0131\u015f kullan\u0131c\u0131lar ve sepette \u00fcr\u00fcn olanlar i\u00e7in cache kapal\u0131\nif ($http_cookie ~* &quot;(wordpress_logged_in_|woocommerce_items_in_cart|woocommerce_cart_hash)&quot;) {\n    set $skip_cache 1;\n}\n\nlocation ~ .php$ {\n    include fastcgi_params;\n    fastcgi_pass unix:\/run\/php-fpm.sock;\n\n    fastcgi_cache_bypass $skip_cache;\n    fastcgi_no_cache    $skip_cache;\n    fastcgi_cache       WORDPRESS;\n    fastcgi_cache_valid  200 301 302 60m;\n}\n<\/code><\/pre>\n<p>Burada \u00f6nemli olan, <strong>$skip_cache<\/strong> de\u011fi\u015fkenini hem <code>fastcgi_cache_bypass<\/code> hem de <code>fastcgi_no_cache<\/code> i\u00e7in kullanmak. B\u00f6ylece:<\/p>\n<ul>\n<li>\u0130lgili istekler hi\u00e7bir zaman cache\u2019e yaz\u0131lmaz.<\/li>\n<li>\u00d6nceden yaz\u0131lm\u0131\u015f bir kay\u0131t varsa dahi, geri okunmaz.<\/li>\n<\/ul>\n<p>Nginx taraf\u0131ndaki mikro \u00f6nbellekleme ve daha geli\u015fmi\u015f ayarlar i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/nginx-mikro-onbellekleme-ile-php-uygulamalarini-ucurmak-1-5-sn-cache-bypass-ve-purge-ne-zaman-nasil\/\">Nginx mikro \u00f6nbellekleme rehberimiz<\/a> de i\u015finize yarayacakt\u0131r.<\/p>\n<h3><span id=\"LiteSpeed_Web_Sunucusu_ve_LiteSpeed_Cache_Eklentisi\">LiteSpeed Web Sunucusu ve LiteSpeed Cache Eklentisi<\/span><\/h3>\n<p>LiteSpeed sunucu kullan\u0131yorsan\u0131z (\u00f6rne\u011fin DCHost \u00fczerindeki LiteSpeed destekli hosting\/VPS senaryolar\u0131nda), WooCommerce ile olduk\u00e7a uyumlu \u00e7al\u0131\u015fan LiteSpeed Cache eklentisi \u00f6ne \u00e7\u0131k\u0131yor. Dikkat etmeniz gereken ba\u015fl\u0131ca ayarlar:<\/p>\n<ul>\n<li><strong>Cache &gt; WooCommerce<\/strong> b\u00f6l\u00fcm\u00fcnde WooCommerce entegrasyonunu aktif etmek.<\/li>\n<li><strong>Cache &gt; Excludes &gt; Do Not Cache URIs<\/strong> k\u0131sm\u0131na <code>\/cart\/<\/code>, <code>\/checkout\/<\/code>, <code>\/my-account\/<\/code> gibi URL\u2019leri eklemek.<\/li>\n<li>Gerekirse <strong>Do Not Cache Cookies<\/strong> alan\u0131na <code>woocommerce_items_in_cart<\/code> ve <code>woocommerce_cart_hash<\/code> eklemek.<\/li>\n<\/ul>\n<p>LiteSpeed Cache eklentisinin genel ayarlar\u0131n\u0131 ad\u0131m ad\u0131m anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/litespeed-cache-eklentisi-ile-wordpress-hizlandirma-paylasimli-hosting-icin-detayli-ayar-rehberi\/\">LiteSpeed Cache ile WordPress h\u0131zland\u0131rma rehberimiz<\/a>, WooCommerce kurulumlar\u0131n\u0131z i\u00e7in de iyi bir temel sunar.<\/p>\n<h3><span id=\"Apache_Varnish_veya_Reverse_Proxy_Onbellegi\">Apache + Varnish veya Reverse Proxy \u00d6nbelle\u011fi<\/span><\/h3>\n<p>Apache arkas\u0131nda Varnish veya Nginx reverse proxy kullanan yap\u0131larda mant\u0131k ayn\u0131d\u0131r:<\/p>\n<ul>\n<li>Varnish VCL i\u00e7inde <code>\/cart\/<\/code>, <code>\/checkout\/<\/code>, <code>\/my-account\/<\/code>, <code>\/wp-admin<\/code>, <code>\/wp-login.php<\/code> gibi yollar\u0131 <strong>pass<\/strong> edin.<\/li>\n<li>Cookie i\u00e7inde <code>wordpress_logged_in_<\/code>, <code>woocommerce_cart_hash<\/code> vb. varsa yine <strong>pass<\/strong> edin.<\/li>\n<li>Geri kalan istekler i\u00e7in cache <strong>hit<\/strong> olmas\u0131na izin verin.<\/li>\n<\/ul>\n<p>\u00d6zetle, hangi web sunucusunu kullan\u0131rsan\u0131z kullan\u0131n; sepet\/\u00f6deme URL\u2019lerini ve belirli cookie\u2019leri cache d\u0131\u015f\u0131nda tutmak ortak prensip.<\/p>\n<h2><span id=\"CDN_Tarafinda_WooCommerce_Icin_Ozel_Kurallar\">CDN Taraf\u0131nda WooCommerce \u0130\u00e7in \u00d6zel Kurallar<\/span><\/h2>\n<p>CDN sa\u011flay\u0131c\u0131lar\u0131n\u0131n \u00e7o\u011funda mant\u0131k ayn\u0131d\u0131r: Belirli URL desenleri, HTTP ba\u015fl\u0131klar\u0131 ve cookie\u2019lere g\u00f6re cache politikas\u0131 tan\u0131mlars\u0131n\u0131z. WooCommerce i\u00e7in tipik bir kurallar seti \u015fu \u015fekilde olabilir:<\/p>\n<h3><span id=\"1_HTML_Icin_Temel_Cache_Politikasi\">1) HTML \u0130\u00e7in Temel Cache Politikas\u0131<\/span><\/h3>\n<ul>\n<li><strong>Varsay\u0131lan<\/strong>: HTML i\u00e7in cache <strong>kapal\u0131<\/strong> (sadece statik dosyalar cache\u2019lenir).<\/li>\n<li><strong>\u0130ste\u011fe ba\u011fl\u0131<\/strong>: Blog, kampanya, statik sayfalar i\u00e7in belirli yol desenlerinde HTML cache\u2019i <strong>a\u00e7\u0131k<\/strong>.<\/li>\n<\/ul>\n<p>\u00d6rne\u011fin:<\/p>\n<ul>\n<li><code>example.com\/blog\/*<\/code> \u2192 HTML 15 dk cache<\/li>\n<li><code>example.com\/kampanya\/*<\/code> \u2192 HTML 5 dk cache<\/li>\n<li>Di\u011fer t\u00fcm HTML istekleri \u2192 cache kapal\u0131<\/li>\n<\/ul>\n<h3><span id=\"2_Sepet_ve_Odeme_Icin_URL_Bazli_Haric_Tutma\">2) Sepet ve \u00d6deme \u0130\u00e7in URL Bazl\u0131 Hari\u00e7 Tutma<\/span><\/h3>\n<p>CDN panelinizde \u201crules\u201d veya \u201cpage rules\u201d b\u00f6l\u00fcm\u00fcnde \u015fu t\u00fcr kal\u0131plar i\u00e7in cache\u2019i mutlaka kapat\u0131n:<\/p>\n<ul>\n<li><code>*\/cart*<\/code><\/li>\n<li><code>*\/checkout*<\/code><\/li>\n<li><code>*\/my-account*<\/code><\/li>\n<li><code>*wc-ajax=*<\/code><\/li>\n<li><code>*add-to-cart=*<\/code><\/li>\n<\/ul>\n<p>Bunlar\u0131 genellikle \u201cCache level: Bypass\u201d veya benzeri bir ayarla y\u00f6netirsiniz. B\u00f6ylece CDN, bu iste\u011fi her zaman origin\u2019e iletir ve kendi \u00fczerinde saklamaz.<\/p>\n<h3><span id=\"3_Cache-Key_ve_Cookie_Farkindaligi\">3) Cache-Key ve Cookie Fark\u0131ndal\u0131\u011f\u0131<\/span><\/h3>\n<p>Daha geli\u015fmi\u015f senaryolarda, CDN\u2019in <strong>cache key<\/strong> mant\u0131\u011f\u0131n\u0131 da \u00f6zelle\u015ftirebilirsiniz. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>Farkl\u0131 para birimleri i\u00e7in farkl\u0131 cache key (\u00f6r. <code>?currency=<\/code>)<\/li>\n<li>Farkl\u0131 diller i\u00e7in (\u00f6r. <code>\/tr\/<\/code>, <code>\/en\/<\/code>) ayr\u0131 varyantlar<\/li>\n<li>Cihaz t\u00fcr\u00fcne g\u00f6re (mobil\/desktop) ayr\u0131 cache key<\/li>\n<\/ul>\n<p>Ayr\u0131ca baz\u0131 CDN\u2019ler, belirli cookie\u2019ler geldi\u011finde cache\u2019i otomatik bypass edecek \u201ccookie rules\u201d deste\u011fi sunar. Bu durumda <code>woocommerce_items_in_cart<\/code>, <code>woocommerce_cart_hash<\/code> ve <code>wordpress_logged_in_*<\/code> cookie\u2019lerini listeleyerek WooCommerce ak\u0131\u015f\u0131n\u0131 g\u00fcvence alt\u0131na alabilirsiniz.<\/p>\n<p>CDN ve taray\u0131c\u0131 \u00f6nbelle\u011fini birlikte d\u00fc\u015f\u00fcnmek i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/tarayici-ve-cdn-onbelleginde-cache-busting-stratejileri\/\">taray\u0131c\u0131 ve CDN \u00f6nbelle\u011finde cache busting stratejileri<\/a> yaz\u0131m\u0131z\u0131 da mutlaka okuman\u0131z\u0131 \u00f6neririz. \u00d6zellikle CSS\/JS g\u00fcncellemelerinde, eski s\u00fcr\u00fcmlerin tak\u0131l\u0131 kalmas\u0131n\u0131 engellemek i\u00e7in bu bilgiler \u00e7ok i\u015fe yar\u0131yor.<\/p>\n<h2><span id=\"Sepet_ve_Odeme_Sayfalari_Icin_HTTP_Basliklari_ve_Cookie_Stratejisi\">Sepet ve \u00d6deme Sayfalar\u0131 \u0130\u00e7in HTTP Ba\u015fl\u0131klar\u0131 ve Cookie Stratejisi<\/span><\/h2>\n<p>CDN ve cache katmanlar\u0131 kadar, <strong>HTTP ba\u015fl\u0131klar\u0131<\/strong> da sepet ve \u00f6deme sayfalar\u0131n\u0131n davran\u0131\u015f\u0131n\u0131 belirliyor. \u00d6nerdi\u011fimiz yap\u0131:<\/p>\n<h3><span id=\"1_Cache-Control_Basliklari\">1) Cache-Control Ba\u015fl\u0131klar\u0131<\/span><\/h3>\n<p>Sepet ve \u00f6deme sayfalar\u0131nda \u015fu ba\u015fl\u0131k yap\u0131s\u0131 g\u00fcvenlidir:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">Cache-Control: no-store, no-cache, must-revalidate, max-age=0\nPragma: no-cache\nExpires: 0\n<\/code><\/pre>\n<p><strong>no-store<\/strong>, taray\u0131c\u0131ya bu sayfan\u0131n hi\u00e7bir kopyas\u0131n\u0131 saklamamas\u0131n\u0131 s\u00f6yler. \u00d6zellikle \u00f6deme ad\u0131mlar\u0131nda, geri tu\u015funa bas\u0131ld\u0131\u011f\u0131nda taray\u0131c\u0131n\u0131n eski bir kopyay\u0131 g\u00f6stermesini engellemek i\u00e7in \u00f6nemlidir.<\/p>\n<h3><span id=\"2_Cookie_Guvenligi_ve_SameSite\">2) Cookie G\u00fcvenli\u011fi ve SameSite<\/span><\/h3>\n<p>WooCommerce cookie\u2019leri i\u00e7in <strong>Secure<\/strong>, <strong>HttpOnly<\/strong> ve uygun <strong>SameSite<\/strong> ayarlar\u0131 hem g\u00fcvenlik hem de \u00f6deme sa\u011flay\u0131c\u0131 entegrasyonlar\u0131 a\u00e7\u0131s\u0131ndan kritiktir. Bu konuyu derinlemesine ele ald\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/samesitelax-mi-strict-mi-secure-ve-httponly-ile-nginx-apachede-cerezleri-tertemiz-nasil-kurarsin\/\">SameSite ve Secure cookie\u2019ler rehberimiz<\/a>, sepet ve \u00f6deme \u00e7erezlerini do\u011fru yap\u0131land\u0131rman\u0131zda yard\u0131mc\u0131 olacakt\u0131r.<\/p>\n<h2><span id=\"WooCommerce_Performansini_Destekleyen_Diger_Onbellek_Katmanlari\">WooCommerce Performans\u0131n\u0131 Destekleyen Di\u011fer \u00d6nbellek Katmanlar\u0131<\/span><\/h2>\n<p>CDN ve tam sayfa cache, i\u015fin sadece bir k\u0131sm\u0131. WooCommerce\u2019i ger\u00e7ekten ak\u0131c\u0131 hale getirmek i\u00e7in a\u015fa\u011f\u0131daki katmanlar da kritik \u00f6neme sahip:<\/p>\n<h3><span id=\"1_PHP_OPcache\">1) PHP OPcache<\/span><\/h3>\n<p>OPcache, PHP kodlar\u0131n\u0131z\u0131n derlenmi\u015f halini bellekte tutarak her istekte yeniden derlenmesini engeller. Do\u011fru ayarlanm\u0131\u015f bir OPcache:<\/p>\n<ul>\n<li>CPU kullan\u0131m\u0131n\u0131 d\u00fc\u015f\u00fcr\u00fcr.<\/li>\n<li>TTFB (Time To First Byte) s\u00fcresini k\u0131salt\u0131r.<\/li>\n<li>Yo\u011fun trafik anlar\u0131nda daha stabil yan\u0131t s\u00fcreleri sa\u011flar.<\/li>\n<\/ul>\n<p>OPcache taraf\u0131nda \u00f6nerdi\u011fimiz ayarlar\u0131, <a href=\"https:\/\/www.dchost.com\/blog\/php-opcache-ayarlari-wordpress-laravel-ve-woocommerce-icin-en-iyi-konfigurasyon-rehberi\/\">PHP OPcache ayarlar\u0131 rehberimizde<\/a> WordPress ve WooCommerce \u00f6zelinde detayland\u0131rd\u0131k.<\/p>\n<h3><span id=\"2_Nesne_Onbellegi_Redis_Memcached\">2) Nesne \u00d6nbelle\u011fi (Redis \/ Memcached)<\/span><\/h3>\n<p>WooCommerce, \u00f6zellikle \u00fcr\u00fcnler, sepet hesaplamalar\u0131 ve sorgu sonu\u00e7lar\u0131 i\u00e7in yo\u011fun \u015fekilde veritaban\u0131na ba\u015fvurur. Bu sorgular\u0131n sonu\u00e7lar\u0131n\u0131 bellekte saklamak i\u00e7in <strong>Redis<\/strong> veya <strong>Memcached<\/strong> ile nesne \u00f6nbelle\u011fi kullanmak b\u00fcy\u00fck fark yarat\u0131r.<\/p>\n<p>Bu konuda iki \u00f6nemli ad\u0131m var:<\/p>\n<ul>\n<li>Sunucu taraf\u0131nda Redis veya Memcached servisinin kurulup yap\u0131land\u0131r\u0131lmas\u0131 (DCHost \u00fczerindeki VPS\u2019lerinizde bu kurulumu kolayca yapabilirsiniz).<\/li>\n<li>WordPress taraf\u0131nda uygun eklentiyle nesne cache\u2019in etkinle\u015ftirilmesi.<\/li>\n<\/ul>\n<p>Kurulum ve hangi senaryoda hangi \u00e7\u00f6z\u00fcm\u00fcn daha mant\u0131kl\u0131 oldu\u011fu konusunu <a href=\"https:\/\/www.dchost.com\/blog\/wordpress-ve-woocommerce-icin-redis-mi-memcached-mi-kalici-nesne-onbellegi-ttl-ve-eviction-ayarlarini-ne-zaman-nasil-yaparsin\/\">WordPress ve WooCommerce i\u00e7in Redis mi Memcached mi?<\/a> yaz\u0131m\u0131zda ayr\u0131nt\u0131l\u0131 anlatt\u0131k.<\/p>\n<h3><span id=\"3_Veritabani_Optimizasyonu\">3) Veritaban\u0131 Optimizasyonu<\/span><\/h3>\n<p>Cache ne kadar iyi olursa olsun, en yo\u011fun anlarda baz\u0131 istekler veritaban\u0131na mutlaka ula\u015f\u0131r. \u00d6zellikle:<\/p>\n<ul>\n<li>B\u00fcy\u00fck \u00fcr\u00fcn kataloglar\u0131<\/li>\n<li>Yo\u011fun sipari\u015f ge\u00e7mi\u015fi<\/li>\n<li>Raporlama ve istatistik eklentileri<\/li>\n<\/ul>\n<p>MySQL\/MariaDB taraf\u0131nda ek y\u00fck olu\u015fturabilir. \u0130ndeksleme, sorgu optimizasyonu ve InnoDB tuning konular\u0131n\u0131, WooCommerce odakl\u0131 olarak <a href=\"https:\/\/www.dchost.com\/blog\/woocommerce-icin-mysql-innodb-tuning-kontrol-listesi-buffer-pool-indeksleme-ve-slow-query-analizi-nasil-akillica-yapilir\/\">WooCommerce i\u00e7in MySQL\/InnoDB tuning kontrol listesi<\/a> yaz\u0131m\u0131zda pratik \u00f6rneklerle aktard\u0131k.<\/p>\n<h3><span id=\"4_Dogru_Sunucu_Kaynaklari_ve_DCHost_Altyapisi\">4) Do\u011fru Sunucu Kaynaklar\u0131 ve DCHost Altyap\u0131s\u0131<\/span><\/h3>\n<p>\u00d6nbellek ayarlar\u0131n\u0131 m\u00fckemmel yapsan\u0131z bile, CPU ve RAM yetersizse veya disk IOPS de\u011feri d\u00fc\u015f\u00fckse, performans bir noktadan sonra t\u0131kan\u0131r. WooCommerce i\u00e7in:<\/p>\n<ul>\n<li>H\u0131zl\u0131 NVMe diskler<\/li>\n<li>Yeterli vCPU ve RAM<\/li>\n<li>PHP-FPM, HTTP\/2 ve HTTP\/3 deste\u011fi<\/li>\n<\/ul>\n<p>gibi bile\u015fenler kritik. <a href=\"https:\/\/www.dchost.com\/blog\/woocommerce-kapasite-planlama-rehberi-vcpu-ram-iops-nasil-hesaplanir\/\">WooCommerce kapasite planlama rehberimizde<\/a>, vCPU, RAM ve IOPS ihtiyac\u0131n\u0131 ad\u0131m ad\u0131m nas\u0131l hesaplayabilece\u011finizi anlatt\u0131k. DCHost olarak sa\u011flad\u0131\u011f\u0131m\u0131z NVMe tabanl\u0131 VPS ve <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a> altyap\u0131lar\u0131, tam da bu senaryolar i\u00e7in tasarlanm\u0131\u015f durumda.<\/p>\n<h2><span id=\"Adim_Adim_WooCommerce_Icin_Guvenli_CDN_ve_Cache_Kontrol_Listesi\">Ad\u0131m Ad\u0131m: WooCommerce \u0130\u00e7in G\u00fcvenli CDN ve Cache Kontrol Listesi<\/span><\/h2>\n<p>T\u00fcm anlatt\u0131klar\u0131m\u0131z\u0131, uygulamas\u0131 kolay bir kontrol listesine d\u00f6n\u00fc\u015ft\u00fcrelim. Mevcut ma\u011fazan\u0131za uyarlarken bu ad\u0131mlar\u0131 tek tek i\u015faretleyebilirsiniz.<\/p>\n<ol>\n<li><strong>Statik i\u00e7eriklerinizi CDN\u2019e ta\u015f\u0131y\u0131n.<\/strong>\n<ul>\n<li>G\u00f6rsel, CSS, JS ve font dosyalar\u0131n\u0131n CDN \u00fczerinden servis edildi\u011fini do\u011frulay\u0131n.<\/li>\n<li>Taray\u0131c\u0131 geli\u015ftirici ara\u00e7lar\u0131nda <em>Response Headers<\/em> alt\u0131nda CDN ba\u015fl\u0131klar\u0131n\u0131 kontrol edin.<\/li>\n<\/ul>\n<\/li>\n<li><strong>HTML i\u00e7in varsay\u0131lan politikay\u0131 belirleyin.<\/strong>\n<ul>\n<li>\u0130lk etapta CDN taraf\u0131nda HTML cache\u2019ini <strong>kapal\u0131<\/strong> tutun.<\/li>\n<li>Gerekirse blog ve statik sayfalar i\u00e7in kademeli olarak a\u00e7\u0131n.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Sepet, \u00f6deme ve hesab\u0131m URL\u2019lerini hari\u00e7 tutun.<\/strong>\n<ul>\n<li>CDN kurallar\u0131n\u0131zda <code>*\/cart*<\/code>, <code>*\/checkout*<\/code>, <code>*\/my-account*<\/code>, <code>*wc-ajax=*<\/code>, <code>*add-to-cart=*<\/code> i\u00e7in cache bypass ekleyin.<\/li>\n<li>Sunucu taraf\u0131nda (Nginx, Apache, LiteSpeed) ayn\u0131 URL\u2019ler i\u00e7in cache devre d\u0131\u015f\u0131 olsun.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Cookie bazl\u0131 cache bypass kurun.<\/strong>\n<ul>\n<li><code>wordpress_logged_in_*<\/code>, <code>woocommerce_items_in_cart<\/code>, <code>woocommerce_cart_hash<\/code> cookie\u2019leri varsa cache\u2019i bypass edin.<\/li>\n<li>Bu kurallar\u0131 hem web sunucusu hem de CDN taraf\u0131nda tan\u0131mlay\u0131n (m\u00fcmk\u00fcnse).<\/li>\n<\/ul>\n<\/li>\n<li><strong>HTTP ba\u015fl\u0131klar\u0131n\u0131 kontrol edin.<\/strong>\n<ul>\n<li>Sepet ve \u00f6deme sayfalar\u0131nda <code>Cache-Control: no-store, no-cache<\/code> gibi ba\u015fl\u0131klar\u0131n d\u00f6nd\u00fc\u011f\u00fcn\u00fc do\u011frulay\u0131n.<\/li>\n<li>Statik dosyalarda ise uzun s\u00fcreli <code>max-age<\/code> ve <code>immutable<\/code> gibi politikalar kullan\u0131n.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Nesne \u00f6nbelle\u011fi ve OPcache\u2019i etkinle\u015ftirin.<\/strong>\n<ul>\n<li>DCHost \u00fczerindeki sunucunuzda Redis veya Memcached kurun ve WordPress ile entegre edin.<\/li>\n<li>OPcache ayarlar\u0131n\u0131 WooCommerce y\u00fck\u00fcne uygun \u015fekilde optimize edin.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Canl\u0131ya almadan \u00f6nce test edin.<\/strong>\n<ul>\n<li>Farkl\u0131 taray\u0131c\u0131 ve cihazlardan test sepeti olu\u015fturun.<\/li>\n<li>Giri\u015f yapm\u0131\u015f\/giri\u015f yapmam\u0131\u015f kullan\u0131c\u0131 senaryolar\u0131n\u0131 ayr\u0131 ayr\u0131 deneyin.<\/li>\n<li>Kupon, kargo hesaplama, stok g\u00fcncelleme gibi hassas ak\u0131\u015flar\u0131 \u00f6zellikle kontrol edin.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n<h2><span id=\"Sonuc_Sepeti_Bozmadan_Hizlanan_WooCommerce_Magazasi\">Sonu\u00e7: Sepeti Bozmadan H\u0131zlanan WooCommerce Ma\u011fazas\u0131<\/span><\/h2>\n<p>WooCommerce i\u00e7in CDN ve \u00f6nbellek ayarlar\u0131, d\u0131\u015far\u0131dan bak\u0131ld\u0131\u011f\u0131nda karma\u015f\u0131k g\u00f6r\u00fcnebilir; ama asl\u0131nda temel prensipler net: <strong>Sepet, \u00f6deme, hesab\u0131m ve giri\u015f s\u00fcre\u00e7leri her zaman taze, di\u011fer her \u015fey m\u00fcmk\u00fcn oldu\u011funca cache\u2019lenmi\u015f olmal\u0131.<\/strong> Bunu sa\u011flamak i\u00e7in URL bazl\u0131 hari\u00e7 tutma, cookie bazl\u0131 cache bypass, do\u011fru HTTP ba\u015fl\u0131klar\u0131 ve iyi yap\u0131land\u0131r\u0131lm\u0131\u015f bir nesne\/OPcache katman\u0131 yeterli.<\/p>\n<p>DCHost olarak sahada g\u00f6rd\u00fc\u011f\u00fcm\u00fcz en b\u00fcy\u00fck sorun, ya her \u015feyin a\u015f\u0131r\u0131 temkinle tamamen cache d\u0131\u015f\u0131 b\u0131rak\u0131lmas\u0131 (gereksiz kaynak israf\u0131), ya da tam tersi panikle t\u00fcm CDN\/\u00f6nbellek katmanlar\u0131n\u0131n kapat\u0131lmas\u0131. Oysa do\u011fru mimariyle; NVMe diskli bir VPS veya g\u00fc\u00e7l\u00fc bir dedicated sunucu \u00fczerinde, iyi yap\u0131land\u0131r\u0131lm\u0131\u015f Nginx\/Apache\/LiteSpeed ve ak\u0131ll\u0131 CDN kurallar\u0131yla, hem <strong>Core Web Vitals<\/strong> metriklerini iyile\u015ftirmek hem de sepet\/\u00f6deme ak\u0131\u015f\u0131n\u0131 sorunsuz tutmak m\u00fcmk\u00fcn.<\/p>\n<p>Mevcut WooCommerce ma\u011fazan\u0131zda bu yaz\u0131daki ad\u0131mlar\u0131 uygularken deste\u011fe ihtiya\u00e7 duyarsan\u0131z, DCHost ekibi olarak altyap\u0131 se\u00e7imi (VPS, dedicated, colocation), cache mimarisi ve CDN entegrasyonu konusunda yan\u0131n\u0131zday\u0131z. Log analizi, y\u00fck testleri ve canl\u0131 ge\u00e7i\u015f planlar\u0131yla, sepetinizi bozmadan ma\u011fazan\u0131z\u0131 birlikte h\u0131zland\u0131rabiliriz.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>WooCommerce ma\u011fazalar\u0131nda performans konu\u015fuldu\u011funda, konu \u00e7ok h\u0131zl\u0131 bir \u015fekilde CDN ve \u00f6nbellek ayarlar\u0131na geliyor. Ancak e-ticaret taraf\u0131nda klasik WordPress blog\u2019lar\u0131ndan farkl\u0131 bir ger\u00e7eklik var: Sepet, \u00f6deme ve hesap sayfalar\u0131 tamamen dinamik \u00e7al\u0131\u015f\u0131yor ve en ufak yanl\u0131\u015f cache kural\u0131; bo\u015f sepetler, kaybolan kuponlar, hatal\u0131 kargo \u00fccretleri ve tamamlanmayan sipari\u015fler olarak size geri d\u00f6n\u00fcyor. Bu yaz\u0131da DCHost [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":4507,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-4506","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-teknoloji"],"_links":{"self":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/4506","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/comments?post=4506"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/4506\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/4507"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=4506"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=4506"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=4506"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}