Website Optimization Training
1 / 12
Website Speed &
Performance
Caching, CDN setup, file formats, and resource optimisation — from diagnosis to resolution.
12 Slides Interactive Real Case Study Bilingual EN / ID
Use ← → arrow keys or the buttons above to navigate
Kecepatan &
Performa Website
Caching, setup CDN, format file, dan optimasi resource — dari diagnosis sampai penyelesaian masalah.
12 Slide Interaktif Studi Kasus Nyata Dua Bahasa EN / ID
Pakai tombol ← → atau klik panah di atas untuk navigasi
OverviewGambaran Umum
The 4 Pillars of Website Speed4 Pilar Kecepatan Website
Each pillar addresses a different bottleneck. You need all four working together.Setiap pilar mengatasi hambatan yang berbeda. Keempat-empatnya harus jalan bareng.
Think of your website like a restaurant. Speed optimization is about getting food to the table faster — by having ingredients ready (caching), a nearby kitchen (CDN), serving food on smaller plates so it's easier to carry (optimized file formats), and removing unnecessary dishes from the menu (resource optimization). Bayangkan website kamu kayak restoran. Optimasi kecepatan itu soal nyampaikan makanan ke meja lebih cepat — dengan bahan yang sudah siap (caching), dapur yang dekat (CDN), menyajikan makanan di piring lebih kecil supaya mudah dibawa (format file yang optimal), dan hapus menu yang nggak perlu (optimasi resource).
🗄️ CachingCaching
Saves a ready-made copy of your page so the server doesn't rebuild it on every visit. Like keeping a printed menu instead of writing it fresh each time.Simpan salinan halaman yang sudah jadi biar server nggak perlu bangun ulang setiap ada pengunjung. Kayak nyimpen menu cetak daripada nulis ulang setiap saat.
🖼️ Optimized file formatsFormat file yang optimal
The format you use for images and files directly affects how fast they load. WebP images are typically 25–35% smaller than PNG or JPG at the same visual quality — so the same photo loads noticeably faster with zero compromise on how it looks. Format yang kamu pakai untuk gambar dan file langsung mempengaruhi seberapa cepat mereka load. Gambar WebP biasanya 25–35% lebih kecil dari PNG atau JPG dengan kualitas visual yang sama — jadi foto yang sama load lebih cepat tanpa mengorbankan tampilannya.
WebP ~28 KB
JPG ~55 KB
PNG ~120 KB
Example: same photo, same quality. Hostinger CDN auto-converts to WebP.Contoh: foto yang sama, kualitas sama. Hostinger CDN otomatis konversi ke WebP.
🌐 CDN (Content Delivery Network)CDN (Content Delivery Network)
Copies your site to servers worldwide. Visitors load from the nearest server — not one across the globe. Hostinger CDN is powered by Cloudflare's global network.Salin website kamu ke server di seluruh dunia. Pengunjung load dari server terdekat — bukan dari server yang jauh. Hostinger CDN didukung jaringan global Cloudflare.
⚙️ Resource optimizationOptimasi resource
Trim the fat: compress images, minify CSS/JS, remove unused plugins, lazy-load off-screen content. Fewer bytes = faster load.Buang yang nggak perlu: kompres gambar, minify CSS/JS, hapus plugin yang nggak dipakai, lazy-load konten yang belum kelihatan. Lebih sedikit byte = load lebih cepat.
Goal of this topic: Know what each tool does, when to use it, how to determine whose fault the slowness is, and how to guide customers step by step to a fix. Tujuan topik ini: Tahu fungsi setiap alat, kapan pakai masing-masing, cara tentukan siapa yang salah, dan cara panduan pelanggan langkah demi langkah sampai masalah selesai.
Customer signalsSinyal pelanggan
What Customers Say vs. What They MeanApa yang Pelanggan Bilang vs. Apa yang Dimaksud
Customers describe symptoms. Your job is to translate their words into the right diagnosis.Pelanggan cerita gejalanya. Tugasmu menerjemahkan kata-kata mereka ke diagnosis yang tepat.
Customers rarely say "my TTFB is high." They say "it's slow." Learn to read between the lines. Pelanggan jarang bilang "TTFB saya tinggi." Mereka bilang "lambat." Belajar baca yang tersirat.
Common slow-site phrasesKalimat umum soal situs lambat
💬
"My website takes forever to load""Website saya loadnya lama banget"
Classic general slowness. Start with a GTMetrix test + check caching and CDN status. Keluhan umum soal lambat. Mulai dari test GTMetrix + cek status caching dan CDN.
💬
"Google PageSpeed gives me a low score""Skor Google PageSpeed saya rendah"
Customer already ran a test. Ask them to share the score and the "Opportunities" list from the report. Pelanggan sudah test sendiri. Minta mereka share skor dan daftar "Opportunities" dari laporan.
💬
"Visitors from [country] say it's slow, but fine for me""Pengunjung dari [negara] bilang lambat, tapi buat saya fine"
Likely a CDN or geographic issue. Origin server is far from those visitors — CDN will help. Kemungkinan masalah CDN atau geografis. Server origin jauh dari pengunjung tersebut — CDN bisa bantu.
💬
"It was fast before, now it's suddenly slow""Sebelumnya cepat, sekarang tiba-tiba lambat"
Something changed. Check: new plugin? Traffic spike? Resource usage? Recent WordPress update? Ada yang berubah. Cek: ada plugin baru? Lonjakan traffic? Resource usage? Update WordPress terbaru?
💬
"I get 503 errors or the site crashes under traffic""Muncul error 503 atau situs crash waktu ramai"
Resource exhaustion — CPU/RAM maxed out. Check hosting resource usage in hPanel. Often caused by wp-cron, heavy plugin, or plan limit reached. Kelebihan resource — CPU/RAM mentok. Cek penggunaan resource hosting di hPanel. Sering disebabkan wp-cron, plugin berat, atau batas paket tercapai.
💬
"Images take ages to load""Gambar loadnya lama banget"
Uncompressed images, no lazy loading, or CDN not serving static assets. Ask them to check image file sizes. Gambar belum dikompres, tidak ada lazy loading, atau CDN tidak serving static assets. Minta mereka cek ukuran file gambar.
Signals that point to a security / attack issueSinyal yang mengarah ke masalah keamanan / serangan
🚨
"Sudden massive traffic spike / site went down out of nowhere""Traffic tiba-tiba melonjak / situs tiba-tiba down"
Possible DDoS attack. Enable CDN "Under Attack" mode immediately, then investigate. Kemungkinan serangan DDoS. Aktifkan mode "Under Attack" di CDN sekarang juga, lalu investigasi.
🚨
"Lots of 403 errors / unusual IPs in logs""Banyak error 403 / IP aneh di log"
Bot traffic or scraping. Use CDN traffic blocking — block by IP or country. Traffic bot atau scraping. Gunakan pemblokiran traffic CDN — blokir per IP atau negara.
DiagnosisDiagnosis
Our Side vs. Customer's SideMasalah dari Kita vs. dari Pelanggan
Before optimizing anything — figure out where the problem actually lives.Sebelum optimasi apapun — cari tahu dulu masalahnya ada di mana.
This is the most important question to answer first. Applying caching fixes to a server-side infrastructure problem wastes everyone's time. Ini pertanyaan paling penting yang harus dijawab duluan. Kalau masalahnya di infrastruktur server tapi kita malah perbaiki caching, buang-buang waktu semua orang.
🏢 Likely our side (Hostinger)Kemungkinan dari kita (Hostinger)
Server downtime or known incidentDowntime server atau insiden yang diketahui
High server-wide resource usage (check status page)Penggunaan resource server tinggi (cek status page)
DNS propagation in progress after migrationDNS masih propagasi setelah migrasi
👤 Likely customer's sideKemungkinan dari sisi pelanggan
Unoptimized images (multi-MB photos)Gambar belum dioptimasi (foto ukuran MB)
Too many or conflicting pluginsTerlalu banyak atau plugin yang konflik
No caching plugin enabledTidak ada plugin caching yang aktif
wp-cron running on every page visitwp-cron berjalan di setiap kunjungan halaman
Heavy theme / bloated page buildersTema berat / page builder yang boros resource
Key signal: If hPanel shows 20% resource usage but SSH shows 90% CPU — the dashboard average is misleading. Look at individual processes (wp-cron.php, index.php) to find the real culprit. That's a code problem, not a server problem. Sinyal penting: Kalau hPanel menunjukkan 20% resource tapi SSH menunjukkan 90% CPU — angka rata-rata di dashboard menyesatkan. Lihat proses individual (wp-cron.php, index.php) untuk menemukan penyebab sebenarnya. Itu masalah kode, bukan masalah server.
Diagnosis flowAlur diagnosis
Step-by-Step: How to Diagnose a Slow SiteLangkah demi Langkah: Cara Diagnosis Situs Lambat
Follow this order every time. Don't skip to solutions before you know the cause.Ikuti urutan ini setiap kali. Jangan langsung ke solusi sebelum tahu penyebabnya.
1
Check if the site loads at allCek apakah situs bisa dibuka sama sekali
If there's a 500/503 error, check for downtime first. A down site will always fail speed tests — that's expected. Use the hPanel downtime guide before anything else.Kalau ada error 500/503, cek downtime dulu. Situs yang down pasti akan gagal tes kecepatan — itu wajar. Gunakan panduan downtime hPanel sebelum yang lain.
2
Check hPanel resource usageCek penggunaan resource di hPanel
Look at CPU and RAM consumption. If they're maxed out, the problem is resource-level — not a caching issue. Identify which process is consuming (wp-cron.php? index.php? A specific plugin?).Lihat konsumsi CPU dan RAM. Kalau sudah mentok, masalahnya di level resource — bukan masalah caching. Identifikasi proses mana yang boros (wp-cron.php? index.php? Plugin tertentu?).
3
Run a GTMetrix speed testJalankan speed test di GTMetrix
GTMetrix gives a detailed performance report with scores, waterfall breakdown, and specific recommendations. If GTMetrix errors or times out, use hPanel → Websites → Page Speed as the alternative — it's Lighthouse-based and has no timeout limitations.GTMetrix memberikan laporan performa lengkap dengan skor, waterfall breakdown, dan rekomendasi spesifik. Kalau GTMetrix error atau timeout, gunakan hPanel → Websites → Page Speed sebagai alternatif — berbasis Lighthouse dan tidak ada batasan timeout.
4
Check CDN statusCek status CDN
Is CDN enabled? Is it in Development Mode (bypasses cache)? Is "Under Attack" mode on unintentionally (blocks bots including Google)?Apakah CDN aktif? Apakah dalam Development Mode (bypass cache)? Apakah mode "Under Attack" nyala tidak sengaja (memblokir bot termasuk Google)?
5
Only then — apply optimizationsBaru setelah itu — terapkan optimasi
Once you know the root cause, apply the right fix: caching, CDN, plugin audit, image compression, or plan upgrade as a last resort.Setelah tahu akar masalahnya, terapkan solusi yang tepat: caching, CDN, audit plugin, kompresi gambar, atau upgrade paket sebagai pilihan terakhir.
Optimization toolsAlat optimasi
What Tools Are Available and Who Does WhatAlat Apa yang Tersedia dan Siapa yang Ngerjain Apa
Some fixes are Hostinger's job. Others are the customer's responsibility.Beberapa perbaikan adalah tugas Hostinger. Yang lain adalah tanggung jawab pelanggan.
Caching — what Hostinger providesCaching — apa yang Hostinger sediakan
hPanel
Built-in server cacheCache server bawaan — flush this when customers say "I updated my site but changes aren't showing." hPanel → Websites → Cache.flush ini ketika pelanggan bilang "saya sudah update tapi perubahan tidak muncul." hPanel → Websites → Cache.
CDN
CDN edge cacheCDN edge cache — served from global edge nodes. Use Development Mode to temporarily bypass for testing. Flush from CDN settings.disajikan dari edge node global. Gunakan Development Mode untuk bypass sementara saat testing. Flush dari pengaturan CDN.
WordPress
Caching pluginPlugin caching — LiteSpeed Cache (recommended on Hostinger — leverages server-level cache), WP Rocket, W3 Total Cache. Use only ONE — multiple cache plugins conflict.LiteSpeed Cache (direkomendasikan di Hostinger — memanfaatkan cache server), WP Rocket, W3 Total Cache. Pakai SATU saja — beberapa plugin cache bisa konflik.
Compression & minificationKompresi & minifikasi
CDN
HTML/CSS/JS minificationMinifikasi HTML/CSS/JS — enable directly in Hostinger CDN settings (Optimization tab). No plugin needed.aktifkan langsung di pengaturan Hostinger CDN (tab Optimization). Tidak perlu plugin.
CDN
Smart image optimizationOptimasi gambar otomatis — CDN auto-resizes and converts images to WebP for desktop and mobile. Enable in CDN → Optimization.CDN otomatis resize dan ubah gambar ke WebP untuk desktop dan mobile. Aktifkan di CDN → Optimization.
Resource optimization — customer's responsibilityOptimasi resource — tanggung jawab pelanggan
🖼️
Optimize images before uploadingOptimasi gambar sebelum upload — use Squoosh, TinyPNG, or ShortPixel. Oversized images are the #1 cause of slow page loads.gunakan Squoosh, TinyPNG, atau ShortPixel. Gambar terlalu besar adalah penyebab #1 halaman lambat.
🔌
Audit and remove unused pluginsAudit dan hapus plugin yang tidak dipakai — each plugin adds PHP overhead. One bad plugin can slow the entire site.setiap plugin menambah overhead PHP. Satu plugin bermasalah bisa memperlambat seluruh situs.
⏰
Replace wp-cron with a real cron jobGanti wp-cron dengan cron job sungguhan — wp-cron fires on every page visit, adding server load unnecessarily. Replace with a system cron in hPanel.wp-cron berjalan di setiap kunjungan halaman, menambah beban server yang tidak perlu. Ganti dengan system cron di hPanel.
Hostinger CDNHostinger CDN
CDN Features: Speed + Security in OneFitur CDN: Kecepatan + Keamanan Sekaligus
Hostinger CDN does two things at once — makes sites faster and filters malicious traffic.Hostinger CDN punya dua fungsi sekaligus — bikin situs lebih cepat dan filter traffic jahat.
Speed featuresFitur kecepatan
Speed
Global edge deliveryEdge delivery global — content served from nearest Cloudflare node.konten disajikan dari node Cloudflare terdekat.
Speed
Auto image optimizationOptimasi gambar otomatis — resize + WebP for desktop and mobile.resize + WebP untuk desktop dan mobile.
Speed
HTML/CSS/JS minificationMinifikasi HTML/CSS/JS — strip whitespace and comments.hapus spasi dan komentar berlebih.
Note
Development ModeDevelopment Mode — bypasses cache entirely. Turn OFF after testing!bypass cache sepenuhnya. Matikan setelah testing!
Security featuresFitur keamanan
Security
DDoS protectionProteksi DDoS — filters botnet traffic before it hits the origin server.filter traffic botnet sebelum mencapai server origin.
Security
Security levelsLevel keamanan — Low / Medium / High / Under Attack. Higher = more visitors challenged.Low / Medium / High / Under Attack. Makin tinggi = makin banyak pengunjung di-challenge.
Security
IP & country blockingBlokir IP & negara — block specific IPs or countries. Can also allowlist-only mode.blokir IP atau negara tertentu. Bisa juga mode allowlist saja.
Security
TLS 1.3 enforcementPaksa TLS 1.3 — optional — restricts to latest encryption protocol.opsional — membatasi hanya ke protokol enkripsi terbaru.
CDN securityKeamanan CDN
"Under Attack" Mode — What It Is and When to Use ItMode "Under Attack" — Apa Itu dan Kapan Pakai
A powerful DDoS shield — but it has a significant side effect you must know.Perisai DDoS yang kuat — tapi ada efek samping penting yang harus kamu tahu.
Think of it like a security checkpoint at a venue entrance. When Under Attack mode is on, every single visitor — human or bot — gets stopped and screened before entering. It stops the attackers, but it also slows down everyone else, including Google's search bots. Bayangkan kayak pemeriksaan keamanan di pintu masuk venue. Saat mode Under Attack aktif, setiap pengunjung — manusia atau bot — dihentikan dan diperiksa sebelum masuk. Itu menghentikan penyerang, tapi juga memperlambat semua orang, termasuk bot pencarian Google.
How to enable itCara mengaktifkan
1
hPanel → Websites → Dashboard → CDNhPanel → Websites → Dashboard → CDN
2
Check CDN is active. If not, enable it first.Pastikan CDN aktif. Kalau belum, aktifkan dulu.
3
Click Manage → Security tab → Dropdown → "I'm Under Attack"Klik Manage → tab Security → Dropdown → "I'm Under Attack"
4
Visitors will see: "Checking your browser before accessing. Just a moment…"Pengunjung akan melihat: "Checking your browser before accessing. Just a moment…"
This is the browser challenge page. It stops automated bots cold.Ini halaman tantangan browser. Ini menghentikan bot otomatis seketika.
✅ When to enableKapan aktifkan Site is being hammered with sudden bot traffic. Getting 503 errors from a flood of requests. Unexplained massive traffic spike. Situs diserang traffic bot mendadak. Error 503 dari banjir request. Lonjakan traffic besar yang tidak bisa dijelaskan.
❌ Don't leave it onJangan dibiarkan aktif After the attack subsides. It blocks search engine bots — Google cannot crawl or index your site while this mode is on. It will hurt SEO. Setelah serangan berhenti. Ini memblokir bot mesin pencari — Google tidak bisa merayapi atau mengindeks situs selama mode ini aktif. Akan merusak SEO.
Testing toolsAlat pengujian
What to Do When GTMetrix / PageSpeed FailsApa yang Harus Dilakukan Saat GTMetrix / PageSpeed Gagal
A failed test often means the site is too slow — not that the tool is broken.Test yang gagal sering berarti situsnya terlalu lambat — bukan alatnya yang rusak.
GTMetrix / PageSpeed Insights timing out doesn't always mean the tool is down. It often means the page took so long to respond that the testing service gave up. The slowness IS the problem. GTMetrix / PageSpeed Insights timeout bukan selalu berarti alatnya down. Sering artinya halaman terlalu lama merespons sampai layanan pengujian menyerah. Kelambatannya ADALAH masalahnya.
Common reasons tests failAlasan umum test gagal
⏱️
Site is too slow to respondSitus terlalu lambat merespons — test times out waiting for the page. The slowness is the root cause.test timeout menunggu halaman. Kelambatannya adalah akar masalahnya.
🔒
CDN "Under Attack" mode is onMode CDN "Under Attack" aktif — testing tools are automated bots — they get blocked by the browser challenge page.alat pengujian adalah bot otomatis — mereka diblokir oleh halaman tantangan browser.
❌
Site itself is down (503)Situs sedang down (503) — a down site always fails. Check this first before blaming the test tool.situs yang down pasti gagal. Cek ini dulu sebelum menyalahkan alat test.
🌐
GTMetrix/PSI service itself is downLayanan GTMetrix/PSI sedang down — rare but possible. Check if both tools fail, not just one.jarang tapi mungkin. Cek apakah kedua alat gagal, bukan hanya satu.
The step-by-step fixLangkah penanganan
1
Check if site loads in a browser firstCek apakah situs bisa dibuka di browser dulu
No error? Site is up. Test failure is a performance issue, not downtime.Tidak ada error? Situs masih up. Kegagalan test adalah masalah performa, bukan downtime.
2
Check CDN: is "Under Attack" mode on?Cek CDN: apakah mode "Under Attack" aktif?
If yes, disable it and retry. Testing bots are blocked by the challenge page.Kalau iya, nonaktifkan dan coba lagi. Bot pengujian diblokir oleh halaman tantangan.
3
Use Chrome DevTools Lighthouse insteadGunakan Chrome DevTools Lighthouse sebagai gantinya
No timeout limitations. Works locally. Open Chrome → F12 → Lighthouse tab → Analyze page load. Share the screenshot with the customer.Tidak ada batasan timeout. Bekerja secara lokal. Buka Chrome → F12 → tab Lighthouse → Analyze page load. Share screenshot ke pelanggan.
Real case studyStudi kasus nyata
Case: Staging Site Slow + Fatal Memory ErrorKasus: Staging Lambat + Fatal Error Memory
A real conversation showing diagnosis, wrong turns, and the correct resolution path.Percakapan nyata yang menunjukkan diagnosis, jalan yang salah, dan jalur penyelesaian yang benar.
Customer
Staging is too slow. Fatal error: Allowed memory size of 3221225472 bytes exhausted during Woodmart demo import. Staging lambat banget. Fatal error: Allowed memory size of 3221225472 bytes exhausted waktu import demo Woodmart.
Kodee (AI bot)
Your staging site hit the maximum PHP memory limit (3 GB — already at plan max). The Woodmart demo import is too heavy. Cancel it, deactivate all plugins except the theme, and try a lighter demo or import in smaller steps. Staging kamu udah kena batas maksimum PHP memory (3 GB — sudah di batas paket). Import demo Woodmart terlalu berat. Batalkan, nonaktifkan semua plugin kecuali theme, dan coba demo yang lebih ringan atau import bertahap.
Specialist
Server node is healthy — no congestion. The real cause: wp-cron.php running on every page visit, and index.php overloaded by the heavy import. Fix: replace wp-cron with a real cron job, optimize the website, and consider upgrading the plan only after optimization. Server node sehat — tidak ada kongesti. Penyebab sebenarnya: wp-cron.php berjalan di setiap kunjungan halaman, dan index.php kelebihan beban dari import berat. Solusi: ganti wp-cron dengan cron job sungguhan, optimalkan website, dan pertimbangkan upgrade paket hanya setelah optimasi.
Key lessons from this casePelajaran utama dari kasus ini
✅
hPanel showed 20% usage; SSH showed 90% CPU.hPanel menunjukkan 20% usage; SSH menunjukkan 90% CPU. Dashboard averages mislead. Always look at per-process data.Rata-rata dashboard bisa menyesatkan. Selalu lihat data per proses.
✅
The server was healthy — the problem was 100% on the customer's side.Server sehat — masalah 100% ada di sisi pelanggan. Heavy demo import + wp-cron triggering on every load.Import demo berat + wp-cron terpicu di setiap load halaman.
✅
Memory was already at plan max (3 GB).Memory sudah di batas maksimum paket (3 GB). Raising it further was NOT the answer — optimizing the import process was.Menaikkannya lagi bukan jawabannya — mengoptimalkan proses import adalah solusinya.
✅
CDN was recommended as an additional stepCDN direkomendasikan sebagai langkah tambahan — not as the solution to the underlying resource problem.bukan sebagai solusi untuk masalah resource yang mendasar.
Customer fixesPerbaikan dari pelanggan
15 Speed Fixes Customers Can Do Themselves15 Perbaikan Kecepatan yang Bisa Dilakukan Pelanggan Sendiri
When the slowness is on their side — here's your checklist to guide them. Source: Hostinger Speed Optimization Guide.Kalau lambatnya dari sisi mereka — ini checklist buat panduan pelanggan. Sumber: Panduan Optimasi Kecepatan Hostinger.
Think of these as a doctor's prescription. You diagnosed the problem — now hand them the actionable steps. Most of these cost nothing and can be done without touching the server. Anggap ini kayak resep dokter. Kamu sudah diagnosis masalahnya — sekarang kasih langkah-langkah yang bisa mereka kerjakan. Sebagian besar gratis dan bisa dilakukan tanpa perlu akses server.
Images & mediaGambar & media
1
Compress images before uploadingKompres gambar sebelum upload — use TinyPNG, Squoosh, or ShortPixel. Images are the #1 cause of slow pages.gunakan TinyPNG, Squoosh, atau ShortPixel. Gambar adalah penyebab #1 halaman lambat.
2
Use WebP format instead of PNG/JPGGunakan format WebP daripada PNG/JPG — same quality, 25–35% smaller file size. Hostinger CDN auto-converts to WebP.kualitas sama, ukuran file 25–35% lebih kecil. Hostinger CDN otomatis konversi ke WebP.
3
Enable lazy loadingAktifkan lazy loading — load images only when they scroll into view, not all at once on page load.muat gambar hanya saat masuk ke layar, bukan semua sekaligus saat halaman dibuka.
4
Never upload videos directly to the siteJangan upload video langsung ke situs — embed from YouTube or Vimeo instead. Local video files destroy server performance.embed dari YouTube atau Vimeo. File video lokal merusak performa server.
Code & pluginsKode & plugin
5
Minify CSS, JavaScript & HTMLMinify CSS, JavaScript & HTML — removes whitespace and comments from code. Enable in Hostinger CDN → Optimization, or via a caching plugin.menghapus spasi dan komentar dari kode. Aktifkan di Hostinger CDN → Optimization, atau lewat plugin caching.
6
Reduce and audit pluginsKurangi dan audit plugin — every plugin adds PHP overhead. Deactivate and delete anything unused.setiap plugin menambah overhead PHP. Nonaktifkan dan hapus yang tidak dipakai.
7
Avoid excessive animationsHindari animasi berlebihan — complex animations demand more rendering resources, especially on mobile and older devices.animasi kompleks butuh lebih banyak resource rendering, terutama di mobile dan perangkat lama.
8
Replace wp-cron with a real cron jobGanti wp-cron dengan cron job sungguhan — wp-cron fires on every single page visit. A real cron job runs on a schedule instead, reducing load significantly.wp-cron terpicu di setiap kunjungan halaman. Cron job sungguhan berjalan terjadwal, mengurangi beban secara signifikan.
Caching & deliveryCaching & pengiriman
9
Enable a caching pluginAktifkan plugin caching — LiteSpeed Cache is recommended on Hostinger. Use only one — multiple cache plugins conflict with each other.LiteSpeed Cache direkomendasikan di Hostinger. Pakai satu saja — beberapa plugin cache bisa konflik.
10
Enable Hostinger CDNAktifkan Hostinger CDN — serves content from the nearest global server. Also handles auto image optimization and minification for free.sajikan konten dari server global terdekat. Juga menangani optimasi gambar otomatis dan minifikasi secara gratis.
11
Use browser cachingGunakan browser caching — tells returning visitors' browsers to store static files locally so repeat visits load almost instantly.memberitahu browser pengunjung yang kembali untuk menyimpan file statis secara lokal sehingga kunjungan ulang hampir instan.
Database & serverDatabase & server
12
Clean up the databaseBersihkan database — delete post revisions, spam comments, and transients. Plugins like WP-Optimize automate this.hapus revisi post, komentar spam, dan transients. Plugin seperti WP-Optimize bisa otomasi ini.
13
Reduce redirectsKurangi redirect — every redirect adds an extra round-trip request. Fix broken links and remove unnecessary redirect chains.setiap redirect menambah extra round-trip request. Perbaiki link rusak dan hapus rantai redirect yang tidak perlu.
14
Enable HTTPS / SSLAktifkan HTTPS / SSL — modern browsers load HTTPS sites faster due to HTTP/2 support. Free SSL is included on all Hostinger plans.browser modern memuat situs HTTPS lebih cepat karena dukungan HTTP/2. SSL gratis sudah termasuk di semua paket Hostinger.
15
Upgrade the hosting plan — as a last resortUpgrade paket hosting — sebagai pilihan terakhir — only after all optimizations above are done. More resources help only when the code is already clean.hanya setelah semua optimasi di atas sudah dilakukan. Resource lebih banyak hanya membantu kalau kodenya sudah bersih.
SummaryRingkasan
Key TakeawaysPoin Penting yang Harus Diingat
Everything you need to remember in one place.Semua yang perlu kamu ingat dalam satu halaman.
🔍 Diagnose before you fixDiagnosa sebelum perbaiki
Always establish: is this our infrastructure, or the customer's code/content? The answer changes everything.Selalu tentukan dulu: ini infrastruktur kita, atau kode/konten pelanggan? Jawabannya mengubah segalanya.
🌐 CDN = speed + securityCDN = kecepatan + keamanan
Enable CDN early. It handles global delivery, image optimization, minification, and DDoS protection all in one.Aktifkan CDN lebih awal. CDN menangani pengiriman global, optimasi gambar, minifikasi, dan proteksi DDoS sekaligus.
🚨 "Under Attack" mode — use and removeMode "Under Attack" — pakai lalu matikan
It stops DDoS attacks but blocks Google crawling. Only enable during an attack, then disable once it's over.Menghentikan serangan DDoS tapi memblokir Google. Aktifkan hanya saat serangan, lalu nonaktifkan setelah selesai.
⏱️ GTMetrix fails = site too slowGTMetrix gagal = situs terlalu lambat
Don't blame the tool first. Check: is the site up? Is Under Attack mode on? Use Lighthouse in Chrome DevTools as the fallback.Jangan langsung salahkan alatnya. Cek: situs masih up? Mode Under Attack aktif? Gunakan Lighthouse di Chrome DevTools sebagai alternatif.
⏰ wp-cron is a hidden performance killerwp-cron adalah pembunuh performa tersembunyi
It runs on every page visit, not on a schedule. Replace it with a real cron job in hPanel for any busy site.Berjalan di setiap kunjungan halaman, bukan terjadwal. Ganti dengan cron job sungguhan di hPanel untuk situs yang ramai.
📈 Upgrade plan = last resort onlyUpgrade paket = pilihan terakhir
More resources help only if the code is already clean. Always optimize first — plugins, images, cron — before recommending an upgrade.Resource lebih banyak hanya membantu kalau kodenya sudah bersih. Selalu optimasi dulu — plugin, gambar, cron — sebelum rekomendasikan upgrade.
The correct order, always: Is it down? → Check resources → PHP X-Ray → CDN status → Apply the right fix → Upgrade only if truly needed. Urutan yang benar, selalu: Apakah down? → Cek resource → PHP X-Ray → Status CDN → Terapkan solusi yang tepat → Upgrade hanya kalau benar-benar perlu.
Navigate: ← → arrow keys  ·  or use the buttons above Navigasi: ← → tombol panah  ·  atau pakai tombol di atas