Hosting & performance
Yadda muke sa WordPress ya zama da sauri: LiteSpeed Enterprise, LSCache da kuma Redis ga kowane shafi
Bukatar WordPress mafi sauri ita ce wacce ba ta taba gudana ba - ga yadda tsarinmu ke amsa yawancin ziyarce-ziyare daga cache kafin a kira PHP ko MySQL, kuma abin da hakan ke nufi ga Core Web Vitals.
Buƙatar da ta fi sauri ita ce wadda ba ta taba gudana ba
Buƙatar WordPress ta al'ada tana da tsada. Mai uwar garken yanar gizo yana mika shi ga PHP, PHP tana kunna WordPress, tana sarrafa plugins, tana tambayar MySQL sau da yawa, tana haɗa HTML, sannan ne kawai take tura bayanan baya. A kan shafin da yake da aiki sosai, wannan tsari yana faruwa ga kowane baƙo, kuma a nan ne kusan duk lokacin ku na zuwa ga farkon bayani (time-to-first-byte) yake zuwa.
Amsarmu ita ce mu tabbatar da cewa, a yawancin ziyarce-ziyarce, babu wani abu daga ciki da ke faruwa sam. A duk fadin shafukan da muke daukar bakunta — sama da shafukan PBN 100,000 da kuma manyan shafukan WordPress da ake sarrafawa — yawancin ra'ayoyin shafin gaba ana ba da su azaman cikakken shafin da aka riga aka yi daga cache, ba tare da kiran PHP ko tabawa ba. bayanan bayanai. Sauran wannan sakon shine game da yadda yadudduka da ke sanya hakan gaskiya suka dace tare, da kuma inda kowannensu ya sami matsayinsa.
Mahimmin bayani anan shine wadannan ba sauran ma'ajiyar bayanai ba ne da za ku zaba a tsakaninsu. Ma'ajiyar shafi guda, ma'ajiyar abu, da kuma bakin CDN kowannensu yana kama wani nau'in roko ne daban, kuma amfanin yana cikin yadda suke mika wa junansu ayyuka.
LiteSpeed Enterprise + LSCache: layin shafi-gaba-ɗaya
Kowace shafi tana aiki ne a kan LiteSpeed Enterprise tare da LSCache a matakin sabar. Lokacin da amsar gaban shafi ta zama mai sauƙin adana a cikin ma'ajiyar wucin gadi, sabar yanar gizon tana sanya mata jagororin sarrafa ma'ajiyar wucin gadi da alamomi na LiteSpeed, kuma LiteSpeed tana ba da cikakken shafin kai tsaye a karo na gaba da aka ziyarce shi - babu tsarin PHP da aka ƙaddamar, babu tambayar MySQL da aka bayar. Wannan shi ne babban makami mafi karfi a kan WordPress TTFB, domin yana cire dukkan farawar aikace-aikacen daga hanyar da ake matsanancin amfani da ita.
Saboda LSCache yana zaune ne a cikin sabar yanar gizo maimakon a cikin PHP plugin, yana fara aiki a wuri da wuri a cikin tsarin neman shafi, kuma yana adana shafuka ta hanyar da sabar za ta iya gogewa nan take. Wani cache crawler yana kiyaye shafukan da aka fi ziyarta a buɗe, domin mai ziyara na farko bayan an yi purge ba shi ne ke shan wahalar sake samar da shafin ba. Sakamakon shi ne samun TTFB mai ƙasa sosai kuma mai ƙarfi fiye da cache ɗin da yake na plugin kawai wanda aka haɗa shi da tsarin da ba na musamman ba, inda cache ɗin yake har yanzu a bayan PHP.
Ana jigilar manhajar mu ta ajiyar bayanai ta matakin repo tare da sanya ta a shirye kuma ta atomatik akan kowane shafi, inda ta haɗa WordPress da LSCache daidai ba tare da wani ƙarin shiri ba. Akan asalin da ba LiteSpeed ba kawai ta kan yi shiru ne ta fuskar cikakkun shafuka kuma ta matsa gefe, yayin da ajiyar abubuwa da dokokin warewa ke ci gaba da gudanar da aikinsu - ta yadda ba a bar shafin da aka ƙaura cikin wani yanayi na karyewa ko rabi da rabi ba.
Kasancewa da sauri ba tare da bayar da tsofaffin bayanai ba: ESI da sharewa ta atomatik mai wayo
Kachen shafi baki ɗaya mai tsauri yana da manyan hanyoyin gazawa guda biyu: ba wa mai amfani da ya shiga shafin wani shafi na daban, da kuma ba wa kowa shafin da ya kamata ya canza. Ana magance duka biyun a matakin kache maimakon ta hanyar yin kache kaɗan.
ESI (Edge Side Includes) yana ba mu damar adana shafin a cikin cache yayin da muke buɗe wurare don sassan da dole ne su kasance a rayse. A kan shagon WooCommerce, ana ba da shafukan kasida, samfur da rukuni azaman cikakken cache na shafi don samun mafi saurin TTFB, yayin da ESI ke nuna ɓangaren keken kaya, jimillar mini-keken kaya da kuma matsayin asusu a kowane buƙata. Ana keɓance keken kaya, wurin biya, my-account da kowane shafi na nonce ko zaman tattaunawa ta tsohuwa. Masu siyayya koyaushe suna ganin kwandon su da wurin biya mai aiki; kowa har yanzu yana samun shagon daga cache.
Ana sarrafa sabuntawa ta hanyar sharewa ta atomatik mai wayo. Kayan sharewa suna aiki ta atomatik lokacin da abun ciki, samfurori, farashi ko umarni suka canza, don haka shafukan da aka adana masu dacewa suna sabuntawa nan take maimakon kan lokaci, kuma zaku iya sharewa a buƙata daga dashboard ko daga ciki WordPress. Sharewa ta hanyar tag yana nufin gyara post ɗaya yana share wannan post da abubuwan da aka adana — ba dukkan cache ba — don haka gyara guda ɗaya ba ya fara dukkan shafin daga farko.
Abin adana abu na Redis na kowane shafi: don abin da ba zai iya zama cikakken shafi ba
Ba kowace bukatar ce za ta zamo static full page ba. Zaman shiga wanda aka yi login, admin din WordPress, kwandunan WooCommerce, bincike, da dynamic fragments da ESI ke barwa a raye, duka dole ne su gudanar da PHP. Domin wadannan, makasudin yakan koma ne daga 'tsallake application din' zuwa 'tsallake database din'.
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.
Kayan ajiye bayanan abu (object cache) na kowace shafin yanar gizo ne daban, ba a raba shi da wasu ba, wanda hakan yana da muhimmanci ga ingancin aiki da kuma ware su daban. Idan aka haɗa shi da takaita amfani da bayanan bayanai (database throttling) na kowace shafi, tambayoyi masu nauyi ko marasa kyau na wata shafin ba za su iya hana wasu shafukan da ke makwabtaka da ita samun damar shiga bayanan ba. Za ku iya karanta ƙarin bayani game da yadda dukkan tsarin mai yadudduka da yawa ke haɗuwa tare a shafin fasalin ajiya na mu, da kuma game da iyakokin da ke tsakanin masu amfani a ƙarƙashin tsarin warewa.
Bakin da kuma sufuri a ƙarƙashinsa
Cache da ke zaune a origin har yanzu dole ne ya wuce ta cibiyar sadarwa. A gaban uwar garken akwai bakin CDN edge, don haka abubuwan da ba sa motsawa da shafukan da za a iya adana su a cache ana ba da su daga wani wuri kusa da mai ziyara, kuma origin yana kasancewa a nutse ko da a ƙarƙashin nauyi. Don layin hosting ɗinmu na Footprint-Free, guda ɗiyan bakin edge ɗin tarin multi-CDN ne da aka bazu a fadin masu ba da sabis da yawa, wanda ke bauta wa wata manufa ta footprint da kuma ta aiki; akan WordPress na yau da kullum kawai wani Layer ne mai sauri, mai kyau wanda ke sanye da origins a banza.
A ƙarƙashin hakan, ba a sakaci da ginshiƙan gindima ba. Shafuka suna aiki ne akan ajiya na NVMe tare da HTTP/3, don haka bayanan da cache ke aikawa suna isa ne ta hanyar zamani, wanda aka raba tare da saurin ajiya a bayan kowace gazawar cache. Babu wannan daga cikin sassan da aka ƙara daga baya: LiteSpeed, LSCache, Redis na kowane shafi, NVMe da HTTP/3 su ne ginshiƙi a kowane tsari, ba matakin ƙarin kuɗi ba.
Abin da ke motsa Core Web Vitals da gaske
Yana da kyau a yi daidai, domin ana yawan tallata hosting fiye da yadda ya kamata dangane da Core Web Vitals. TTFB shi ne sashen aikin da uwar garken ke da iko da shi, kuma tsarar adana bayanai ta caching da ke sama ita ce ke rage shi — shafi gaba ɗaya wanda aka adana a wuri kuma aka kawo shi ta hanyar HTTP/3 daga gefen cibiyar sadarwa shine mafi ƙarancin abin da TTFB zai iya zama. Tun da TTFB shi ne mafarin Largest Contentful Paint, saurin tushen yana ba duk wani ma'auni na gaba damar samun nasarar da ba zai iya samu ba ta wata hanya.
Amma ana yanke shawara kan LCP, CLS da INP galibi a cikin bauza, ta shafin kanta: hoton gida mai girma da ba a inganta shi ba, CSS da JavaScript da ke hana fassarawa, shimfidar wuri da ke canjawa yayin da fonti da tallace-tallace ke lodawa, da aiki mai nauyi a babban zaren daga matosai. Babu wani adadin adana bayanan uwar garken (caching) da zai gyara hoton gida na MB 2 ko jigo da ke jigilar megabytes na JavaScript. Uwar garken da ta dace tana sa gudummawar uwar garken ta zama ta kyauta kuma mai dorewa, sannan kuma yana kan shafin don a rike gaban ginin cikin sauki.
Wannan rabe-rabe na aiki shi ne ingantacciyar manhajar tunani mai amfani. Muna tabbatar da cewa buƙatar ta isa ga burauz ɗin cikin sauri kuma ta kasance cikin sauri a ƙarƙashin cunkoso; kai kuma ka kiyaye ɗaukar bayaninka ya zama kaɗan kuma a tsaye. Inda waɗannan biyun suka haɗu — ɗumamar cache, isar da baki, da kiyaye bayanan bayanai don amsawa ta yadda shafuka masu sauyawa ba za su tsaya ba — shine ainihin inda aka gyara gininmu, kuma shi ne ke sa managed WordPress a kan wannan dandali yafi sauri fiye da irin wannan rukunin yanar gizon a kan mai masaukin baki na yau da kullum.
Tambayoyin da aka fi yawa
Shin har yanzu ina buƙatar fasahar adana bayanai ta caching kamar WP Rocket?
A'a. Ana sarrafa adana shafin gaba ɗaya a uwar garken yanar gizo ta hanyar LiteSpeed's LSCache, kuma plugin ɗin cache namu — wanda aka riga aka shigar kuma aka sabunta shi ta atomatik — yana haɗa WordPress da shi yadda ya kamata, tare da cache ɗin abubuwa na Redis na kowane rukunin yanar gizo a bayansa. Sanya wani plugin na biyu na adana shafin gaba ɗaya a sama galibi yana fafatawa da cache ɗin matakin uwar garken maimakon taimakawa, don haka ba a buƙata kuma ba a ba da shawarar ba.
Shin ajiyar wucin gadi (caching) zata lalata karusar WooCommerce dina ko shafukan da aka shiga (logged-in)?
A'a. A turance, shafukan kwandon siyarwa, biyan kuɗi, asawarmu da duk wani shafi na nonce ko zaman tattaunawa ba sa shiga cikin ajiyar wucin gadi bisa ga tsari, kuma ESI tana sa sassan kwando da jimla su kasance a raye a kan shafukan da aka adana. Masu siyayya koyaushe suna ganin kwandonsu da wurin biyan kuɗi mai aiki yayin da shagon ke ci gaba da lodawa daga ajiyar wucin gadi.
Ta yaya cache ke kasancewa sabuwa a duk lokacin da na wallafa ko gyara?
Smart auto-purge na aiki a kan abubuwan da suka shafi WordPress hooks, don haka wallafa, gyara abun ciki, ko canza samfur, farashi ko oda yana share shafukan da abin ya shafa kawai da ajiyar su — ba dukan cache ba — kuma wani mai rarrafe yana sake dumama su. Haka kuma zaka iya sharewa a kan buƙata daga dashboard ko daga cikin WordPress.
Shin hosting kadai zai iya ba ni ingantattun 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.
Mai alaƙa
Gwada shi kyauta na tsawon kwanaki 14
Kaddamar da shafukanka na farko kyauta na kwanaki 14 — ba tare da katin ba. Kana motsa wata cibiyar da ke akwai? Hijira ta farko tana kanmu.
Fara kyauta