Karɓar baƙuncin gidan yanar gizo da aiki
Yadda muke sa WordPress yin sauri: LiteSpeed Enterprise, LSCache da kuma Redis na kowane shafi
Bukatar WordPress mafi sauri ita ce wadda ba a taba aiwatarwa ba — ga yadda tsarinmu yake ba da amsar mafi yawan ziyarori daga cache kafin a taba kiran PHP ko MySQL, da kuma abin da hakan ke nufi ga Core Web Vitals.
Bukata mafi sauri ita ce wadda ba a taɓa aiwatarwa ba
Bukatar WordPress ta yau da kullum tana cin albarkatu da yawa. Sabar gidan yanar gizon tana mika aiki ga PHP, PHP tana kunna WordPress, tana gudanar da plugins, tana tambayar MySQL sau da dama, tana hada HTML, sannan ne kawai take mayar da bytes. A shafin da ke da yawan zirga-zirga, wannan dukkan tsarin yana faruwa ne ga kowane mai ziyara, kuma a nan ne kusan dukkan lokacinku na zuwa byte na farko (time-to-first-byte) yake tafiya.
Amsar mu ita ce tabbatar da cewa, a yawancin ziyarce-ziyarce, babu ɗaya daga cikin waɗannan da zai faru ko kaɗan. A fadin shafukan da muke karɓar baƙuncinsu — sama da shafukan PBN guda 100,000 tare da babban WordPress da ake sarrafawa — babban ɓangare na duba shafukan gaba ana bayar da su a matsayin cikakken shafi da aka riga aka shirya kai tsaye daga ma'ajiya, ba tare da kiran PHP ba ko taɓa ma'ajiyar bayanai. Sauran wannan rubutu yana bayani ne kan yadda matakan da suka tabbatar da hakan suke haɗuwa, da kuma inda kowannensu ya cancanci matsayinsa.
Muhimmin abin lura shi ne waɗannan ba ma'ajiyar cache ba ne masu gasa da juna waɗanda za ku zaɓa a tsakaninsu. Cache na cikakken shafi, cache na abu, da gefen CDN kowannensu yana karɓar nau'in buƙata daban-daban, kuma ƙimar tana cikin yadda suke miƙa aiki ga juna.
LiteSpeed Enterprise + LSCache: shimfidar cikakken shafi
Kowane shafi yana aiki a kan LiteSpeed Enterprise tare da LSCache a matakin sabar. Lokacin da amsar fuskar shafi (front-end) ta kasance mai yiwuwa a adana a cache, sabar yanar gizon tana buga mata tambarin kanun labarai na LiteSpeed cache-control da na tag, kuma LiteSpeed tana ba da cikakken shafin kai tsaye a ziyara ta gaba — ba a ƙirƙirar wani aikin PHP ba, ba a aika wata tambayar MySQL ba. Wannan shi ne babban mataki mafi tasiri a kan WordPress TTFB, saboda yana cire duk wani tada manhaja daga hanyar gudanarwa mai muhimmanci.
Saboda LSCache yana aiki a cikin sabar gidan yanar gizo maimakon a cikin plugin na PHP, yana fara aiki da wuri a cikin tsarin buƙata kuma yana adana shafuka ta hanyar da sabar za ta iya sharewa nan take. Mai rarrafe na cache yana sanya shahararrun shafuka a shirye, ta yadda mai ziyara na farko bayan an share cache ba zai fuskanci jinkirin sake samar da shafin ba. Sakamakon shi ne samun TTFB wanda ya yi ƙasa sosai kuma ya fi daidaito idan aka kwatanta da cache na plugin kawai da aka haɗa a kan tsarin gama-gari, inda cache yake a bayan PHP.
Kayan aikin cache na matakin ma'ajiya namu na kashin kai yana zuwa da riga an girka shi kuma ana sabunta shi ta atomatik a kowane shafi, yana hada WordPress da LSCache daidai tun daga farko. A kan asalin da ba na LiteSpeed ba, kawai ba ya fitar da bayanan kan cikakken shafi kuma yana matsawa gefe, yayin da cache na abu da ka'idojin kebewa ke ci gaba da gudanar da aikinsu — don haka ba a taba barin shafin da aka yi hijira a lalace a yanayin da ba a kammala saita shi ba.
Kasancewa cikin sauri ba tare da bada tsohon bayani ba: ESI da sharewa ta atomatik mai basira
Cire zunzurutun shafi na rumbun ajiya mai tsanani yana da hanyoyi guda biyu na gazawa na gargajiya: nuna wa mai amfani da ya shiga shafin wani, da kuma nuna wa kowa shafin da ya kamata ya canza. Duka ana magance su a matakin rumbun ajiya maimakon rage ajiya a rumbun ajiya.
ESI (Edge Side Includes) yana ba mu damar ajiye shafin a cache yayin da muke barin wurare don sassan da dole ne su ci gaba da kasancewa a raye. A cikin shagon WooCommerce, ana bayar da shafukan kundin kayayyaki, samfura da rukunoni a matsayin cikakken shafin cache don mafi saurin TTFB mai yiwuwa, yayin da ESI ke nuna ɓangaren kwando, jimillar ƙaramin kwando da kuma halin asusu a kowace buƙata. An cire kwando, biyan kuɗi, asusuna da duk wani shafin nonce ko zama ta asali. Masu sayayya a koyaushe suna ganin kwandon kayansu da kuma wurin biyan kuɗi mai aiki; kowa har yanzu yana samun shagon daga cache.
Ana sarrafa sabuntawa ta hanyar kwashe bayanan da ba a buƙata ta atomatik mai basira. Hanyoyin kwashe bayanan suna aiki kai tsaye a duk lokacin da abun ciki, kayayyaki, farashi ko oda suka canza, don haka shafukan da aka adana a ma'ajiyar wucin gadi suna sabuntawa nan take maimakon jiran lokaci, kuma kuna iya kwashe bayanan a duk lokacin da kuke buƙata daga allon sarrafawa ko daga cikin WordPress. Kwashe bayanai ta hanyar alamomi na nufin gyara rubutu guda ɗaya zai goge wannan rubutun da taskokinsa ne kawai — ba dukkan ma'ajiyar wucin gadi ba — don haka gyara guda ɗaya ba zai sa a sake kunna dukkan shafin daga farko ba.
Wurin ajiya na musamman na Redis ga kowane shafi: don abin da ba zai iya zama cikakken shafi ba
Ba kowace buƙata ce za ta iya zama cikakken shafi mara canzawa ba. Zama na shiga asusu, shugaban WordPress, kwandunan WooCommerce, bincike, da ɓangarori masu canzawa waɗanda ESI ta bari a raye duk dole ne su tafiyar da PHP. Ga waɗannan, burin yana sauyawa daga 'tsallake manhaja' zuwa 'tsallake rumbun bayanai'.
Kowane shafi yana samun keɓaɓɓen Redis object cache ɗinsa. WordPress yana adana sakamakon karanta madaidaitan bayanai da aka maimaita — zaɓuɓɓuka, transients, binciken post da term, samfurin WooCommerce da bayanai na session — a cikin memory, domin kar a riƙa gudanar da tambaya iri ɗaya akan MySQL a kowane ziyara. Sakamakon yana ƙara fitowa fili sosai a inda full-page cache ba zai iya taimakawa ba: dashboard mai sauri, keken sayayya mai sauri, da kuma raguwar nauyin database sosai lokacin da ake da yawan zirga-zirga.
Wurin ajiye bayanan abu (object cache) na kowane shafi ne daban ba na tarayya ba, wanda ke da muhimmanci ga aiki da kuma warewa. Idan aka haɗa da tsarin kayyade bayanan rumbun ajiya ga kowane shafi, manyan bincike ko marasa kyau da wani shafi ya yi ba za su iya hana maƙwabtansa samun damar yin amfani da rumbun adana bayanan ba. Za ku iya ƙarin karantawa game da yadda dukkan tsarin mai hawa da yawa yake aiki a shafinmu na fasalin caching, da kuma kan iyakokin tsakanin masu amfani a ƙarƙashin ɓangaren warewa.
Gefen da sufurin da ke ƙarƙashinsa
Kashin da ke kan asalin uwar garken har yanzu dole ne ya tsallaka hanyar sadarwa. A gaban uwar garken akwai gefen CDN, ta yadda ake bayar da kayayyaki marasa sauyawa da shafukan da za a iya adana kashinsu daga wurin da ke kusa da mai ziyara, kuma asalin uwar garken yana kasancewa cikin kwanciyar hankali ko da ana cikin matsin aiki. Ga layin karbar bakuncinmu marar bibiya (footprint-free), wannan gefen tafki ne na multi-CDN da aka rarraba a tsakanin masu ba da sabis da dama, wanda ke biyan manufar kauce wa bibiyar SEO tare da ta ingancin aiki; a kan WordPress na yau da kullun kuwa, kawai wani mataki ne mai sauri kuma mai inganci wanda ke barin asalin uwar garken ya huta.
A karkashin kasa, ba a yi rowa a kan muhimman abubuwa ba. Shafuka suna aiki a kan ma'ajiyar NVMe tare da HTTP/3, saboda haka bayanan da ma'ajiyar cache ke aikawa suna isowa ta hanyar sufuri ta zamani mai aiki tare da sauri wajen adanawa idan ba a sami bayani a cache ba. Babu ɗaya daga cikin waɗannan matakan da yake na ƙarin kuɗi: LiteSpeed, LSCache, Redis ga kowane shafi, NVMe da HTTP/3 su ne asali a kowane tsari, ba matakin tallata ƙarin kaya ba ne.
Abin da ke kawo canji na gaske ga Core Web Vitals
Yana da kyau a fito da gaskiya, domin sau da yawa ana wuce gona da iri wajen tallata hosting a kan Core Web Vitals. TTFB ita ce ɓangaren lissafin da uwar garken ke da iko a kansa, kuma tsarin caching da aka ambata a sama shi ne ke rage shi — cikakken shafin da aka adana a cache wanda aka bayar ta hanyar HTTP/3 daga gefen hanyar sadarwa yana kusa da mafi ƙarancin matakin da TTFB ke iya samu. Domin TTFB ita ce gaba-gaba a cikin Largest Contentful Paint, asali mai sauri yana ba kowane ma'auni na ƙasa damar samun ci gaba da ba zai iya samu ba ta wata hanya.
Amma LCP, CLS da INP galibi ana yanke hukuncinsu ne a cikin binciken yanar gizo, ta shafin kansa: babban hoton farko da ba a inganta ba, CSS da JavaScript masu toshe nuna shafi, tsarin shafi da ke sauyawa yayin da rubutu da tallace-tallace ke lodawa, da kuma aiki mai nauyi a babban zaren aiki daga kayan aikin plugins. Babu adadin ajiyar uwar garke da zai gyara babban hoto na 2 MB ko jigon shafi da ke tura megabytes na JavaScript. Karbar bakuncin shafi na gaskiya yana sanya gudummawar uwar garke ta zama mai sauki da daidaito, sannan ya rage ga shafin ya kiyaye bangaren gaba ya kasance marar nauyi.
Wannan rabon aiki shi ne kyakkyawan tsarin fahimta. Muna ba da tabbacin cewa buƙata tana isa ga manhajar bincike cikin sauri kuma tana ci gaba da kasancewa da sauri a lokacin cunkoson zirga-zirga; ku kuma kuna tabbatar da cewa nauyin bayanan ya kasance ƙanƙane kuma tabbatacce. Inda abubuwan biyu suka haɗu — ɗumama ma'ajiyar cache, isarwa ta bakin gaba (edge delivery), da kuma sa rumbun adana bayanai ya ci gaba da ba da amsa da sauri domin shafuka masu canzawa kada su tsaya cak — a nan ne daidai aka tsara tsarin fasaharmu, kuma shi ne abin da ke sa tsarin WordPress da ake gudanarwa a wannan dandalin ya fi shafin iri ɗaya sauri idan yana kan kowace irin masaukin yanar gizo na gama-gari.
Tambayoyin da aka fi yi
Har yanzu ina buƙatar plugin ɗin caching kamar WP Rocket?
A'a. LiteSpeed LSCache ne ke kula da ɓoye cikakken shafi (full-page caching) a uwar garken gidan yanar gizo, kuma manhajar mu ta ɓoye bayanai — wacce aka riga aka shigar kuma take sabunta kanta da kanta — tana haɗa WordPress da shi yadda ya kamata, tare da ma'ajiyar ɓoye ta Redis a bayan kowane shafi. Ɗora wata manhajar ɓoye cikakken shafi ta biyu a kanta yawanci yana kawo cikas ga ma'ajiyar matakin uwar garke maimakon taimako, don haka ba a buƙata kuma ba a ba da shawarar hakan ba.
Shin yin cache zai lalata kwandon WooCommerce nawa ko shafukan da aka shiga?
A'a. An keɓance keken sayayya, wurin biya, my-account da duk wasu shafukan nonce ko na zama daga ma'ajiya ta asali, kuma ESI yana sanya gutsuren keken da jimillar kuɗi a raye a kan shafukan da ke cikin ma'ajiya. Masu sayayya a koyaushe suna ganin kwandon su da wurin biya mai aiki yayin da shagon ke ci gaba da lodawa daga ma'ajiya.
Ta yaya cache ke kasancewa sabo lokacin da na buga ko na gyara?
Tsabtace kai-tsaye mai hankali yana aiki a kan hanyoyin WordPress masu dacewa, don haka bugawa, gyara abun ciki, ko canza samfuri, farashi ko oda yana share shafukan da abin ya shafa da rumbun adana bayanan su kawai — ba duka ma'ajiyar ba — kuma mai rarrafe yana sake dumi su. Hakanan zaku iya sharewa bisa buƙata daga allon sarrafawa ko daga cikin WordPress.
Shin karɓar baƙuncin (hosting) shi kaɗai zai iya ba ni cikakkun Core Web Vitals?
Yana ba ku mafi kyawancin TTFB da zai yiwu, wanda shi ne gudummawar sabar kuma yana ba da damar farko don Largest Contentful Paint. Amma LCP, CLS, da INP galibi shafin da kansa ne ke yanke musu hukunci — girman hotuna, abubuwan da ke hana fassarar shafi, kwanciyar hankali na shimfidawa, da JavaScript na babban zaren sarrafawa. Tsarinmu yana sa gudummawar sabar ta zama mai sauri kuma mai dorewa; kiyaye nauyin ɓangaren gaba yana da sauƙi shi ne abin da ke rufe ragowar gibin.
Masu dangantaka
Gwada shi kyauta na kwanaki 14
Kaddamar da shafukanku na farko kyauta na kwanaki 14 — babu bukatar katin kuɗi. Kuna ƙaura da hanyar sadarwar da ke akwai? Hijira kyauta ce, ba tare da iyaka ba.
Fara kyauta