How to diagnose (quick checks)

Before changing anything, gather data. The following quick tests will reveal where the problem lies.

1. Ping & traceroute from Nigeria — high RTT or routing detours suggest network latency. Use a Lagos-based testing VM or an online tool that can test from African locations.
2. GTmetrix / PageSpeed Insights — run both mobile and desktop tests. Note TTFB, LCP, CLS, and the waterfall to spot slow resources.
3. DNS performance — use WhatsMyDNS and DNS propagation tools; check WHOIS and the current nameservers.
4. Server logs & metrics — check cPanel/hosting dashboard for CPU spikes, IO wait, and memory usage. These show resource saturation.
5. Real user monitoring — use Google Analytics (Core Web Vitals) or a RUM provider to see how real Nigerian users experience the site.

Hosting & DNS — highest impact fixes

Most major wins come from choosing the right hosting location and resources. Here’s how to prioritise fixes:

1. Move to a nearby / local data centre

If your current host is in Europe or the US and your main audience is Nigerian, latency adds up. Hosting locally (or at least in West Africa) reduces RTT and TTFB dramatically. NairaHost provides servers tuned for Nigerian traffic.

2. Upgrade when CPU / RAM are saturated

Use cPanel or your hosting dashboard to check CPU, RAM and disk IO graphs. If these spike under routine traffic, upgrade to VPS or a higher shared plan to avoid throttling.

3. Use fast, reliable nameservers & reduce DNS hops

Slow DNS adds delay before the browser even requests your page. Use authoritative, fast DNS, or Cloudflare DNS for acceleration. When migrating, temporarily reduce TTL to 300 seconds to speed propagation.

Image & media optimisation

Images often account for the largest bytes transferred on a page. Fix them and your LCP and total page size will drop quickly.

Compress & convert to modern formats

Convert images to WebP or AVIF where supported. Use tools like Squoosh, ImageMagick, or a hosted optimizer like ShortPixel.

Serve responsive images

Use `srcset` and `sizes` so mobile devices get smaller images. Example markup:

Lazy-load offscreen media

Use `loading="lazy"` for images and videos to reduce initial page weight. Performance plugins can enable advanced lazy-loading (deferred offscreen image decoding).

Caching, CDN & compression

Caching and a CDN are the most important distribution techniques: caching reduces server work, CDN brings assets closer to users.

Browser caching & far-future headers

Set Cache-Control headers with long expiry for static assets and use cache-busting file names when assets change.

Server-side full-page caching

Use Varnish, LiteSpeed or Nginx FastCGI caching to serve ready-made HTML without hitting PHP or DB for most pages.

Choose a CDN with African nodes

Cloudflare can help, but for Nigerian traffic consider CDNs with West African POPs (BunnyCDN or regional providers) for maximum improvement.

Enable Brotli/GZIP

Brotli typically compresses better than GZIP for text assets. Enable at the server or CDN layer.

Front-end code & render-blocking fixes

Even with a fast server, bad front-end code can ruin perceived speed. Focus on these problems and fixes:

• Defer/async non-critical JS — use `defer` or `async` to prevent blocking HTML parsing.
• Inline critical CSS — inline just enough CSS to render above-the-fold content quickly and load the rest asynchronously.
• Reduce font load — preload a single critical font and set `font-display:swap`.
• Reduce DOM complexity — avoid deeply nested DOM nodes and excessive CSS selectors that slow rendering.

Database & back-end tuning

Slow database queries can bottleneck dynamic pages. Use these techniques:

• Remove unnecessary revisions & transients in WordPress to reduce DB size.
• Index frequently queried columns, but avoid over-indexing.
• Use object caching (Redis or Memcached) to cache DB-heavy requests.
• Monitor slow queries via `slow_query_log` and optimize them with `EXPLAIN`.

For high-traffic sites, separate DB onto its own instance or add read replicas to scale reads.

Third-party scripts & ads

Third-party scripts (analytics, chat, ads) are common culprits. Audit each script’s impact using the browser performance profiler and remove or defer heavy ones.

Strategies

• Load critical third-party scripts asynchronously or after `DOMContentLoaded`.
• Use a consent/opt-in banner so tracking scripts load only after permission.
• Replace heavy widgets with lighter alternatives or server-side rendered components.

Testing, monitoring & KPIs

Measure improvements. Key metrics to track:

• TTFB — server responsiveness
• LCP — perceived load time
• CLS — visual stability
• INP or FID — interactivity
• Page weight & requests — aim to reduce both

Tools: PageSpeed Insights, GTmetrix, WebPageTest, and Real User Monitoring via Google Analytics or a RUM vendor.

Zero-downtime migration plan to NairaHost

If hosting location or saturated resources are the core issues, a local migration is often the fastest path to improvement. Use this tested zero-downtime plan:

1. Full backup — files + DB (cPanel full backup or plugin backup).
2. Staging — restore to a staging subdomain on NairaHost and verify functionality.
3. Recreate email accounts on the new host to prevent mail interruptions.
4. Test thoroughly — all forms, payments, and scripts.
5. Reduce TTL — set DNS TTL to 300s a few hours before the switch.
6. Swap DNS — update nameservers or A records; monitor propagation with WhatsMyDNS.
7. Keep old hosting active for 48–72 hours as a safety buffer.

FAQ

Resources & Related Guides

• Web Hosting Plans — NairaHost
• VPS Hosting
• Domain Registration
• NairaHost Blog
• Contact Support