Why Is My Website Slow?
A slow website usually comes down to one of five causes: a slow server response, oversized images, render-blocking scripts, a missing page cache or a heavy plugin stack. Measure time to first byte first: under 800 ms points at the page, well above it points at hosting or the database. Fix the biggest cause, then re-measure.
For site owners whose pages feel slow and who want to find the real cause before paying for new hosting or plugins.
knowledge
- Read time
- 4 min
- Sections
- 6
- Updated
- 14 Nov 2026
- Written by
- WebJi® team
Last editorial update: 14 November 2026. Prices follow the dated sources on this page; checkout confirms current charges.
Is the slowness in the server or in the page?
Measure time to first byte (TTFB) first: if the server takes more than about 800 ms to start answering, the delay is in hosting, PHP, caching or the database; if TTFB is low but the page still loads slowly, the browser is struggling with images, fonts and scripts. Fix the wrong half and nothing improves.
curl -o /dev/null -s -w 'TTFB: %{time_starttransfer}s Total: %{time_total}s\n' https://example.in/Run it three times and on three templates — home, a post or product, and a category — because one request can be an outlier. WebJi®'s website speed test gives the same reading without a terminal.
Which speed numbers should you read, and in what order?
Read TTFB, then the three Core Web Vitals — LCP, INP and CLS — then total page weight; the first number narrows down everything after it.
| Metric | Good | A bad value points to |
|---|---|---|
| TTFB | 800 ms or less (poor above 1.8 s) | The host, PHP, missing page cache or slow database queries |
| LCP (Largest Contentful Paint) | 2.5 s or less | A heavy hero image, blocking CSS or slow server response |
| INP (Interaction to Next Paint) | 200 ms or less | Long JavaScript tasks, page-builder and third-party scripts |
| CLS (Cumulative Layout Shift) | 0.1 or less | Images without dimensions, late ads and embeds |
| Page weight | Roughly 1.5 MB or less as a working target | Images, fonts and tracking tags |
PageSpeed Insights shows a lab score and, for URLs with enough traffic, field data from real Chrome users over 28 days. The lab score is a diagnostic; the field data is what Google uses, and the two can disagree — a page can score 95 in the lab and still feel slow on a congested mobile network.
How do you find the cause fastest?
Run the checks that rule out the most first, stop when one explains the delay, fix it and measure again before moving on.
- Upload a 1 KB static HTML file to the same hosting and open it. If that also takes a second, the server is the problem and no plugin will help.
- Compare TTFB on home, a post or product, and a category page. If only search or category pages are slow, suspect database queries.
- Open the browser's Network panel, sort by size and reload. Photos above 300 KB, PNG screenshots and unused font weights are the usual top three.
- On a staging copy, disable plugins one at a time and re-measure the same page after each; turning them all off at once proves nothing.
- Confirm a page cache actually serves HTML (look for a cache "HIT" header) and that most requests hit it.
- Check PHP is a supported 8.x release, autoloaded options are small (under about 1 MB), and old revisions and expired transients are cleaned.
What usually slows down a WordPress site?
Five overlapping faults explain most slow WordPress sites: too many plugins loading assets on every page, oversized photos, third-party widgets, conflicting cache plugins and a bloated database.
- Plugin weight: a page builder plus dozens of plugins, each adding CSS and JavaScript sitewide.
- Oversized images: 4000 px phone photos displayed at 800 px; fix with WebP conversion and resizing.
- Third-party scripts: chat widgets, pixels and embedded maps loading before content.
- Cache conflicts: two cache plugins fighting so neither serves a cached page; see how to clear and configure WordPress cache.
- Database bloat: years of revisions, expired transients and orphaned metadata.
How do you prove the host is the cause?
Hosting is to blame when a static file is slow, TTFB stays high from several locations, every site on the account slows at once, or speed drops at the same hour daily because backups or cron jobs run.
Prove it before migrating. Measure the same three pages for a week at 10 am and 8 pm IST, then repeat the test on a trial account elsewhere. A faster host will not fix 4 MB images, and moving a heavy theme to a faster server only moves the delay. If the host is the limit, see hosting for high-traffic sites or a VPS, which gives dedicated resources from ₹499 a month before 18% GST (WebJi® published pricing; checkout confirms).
What should you avoid when a site feels slow?
Avoid changing several things at once: three cache plugins make things worse, deleting plugins at random breaks features without proving anything, and adding a CDN before compressing images just spreads the same payload.
Change one thing, measure the same page, write the number down and undo the change if it did not help. That habit finds the cause faster than any checklist. If you would rather hand it over, WebJi®'s WordPress speed optimisation service runs this sequence and reports before-and-after numbers.
Frequently asked questions
Do images really slow a website down?
Yes; images are usually the heaviest part of a page. A phone photo can be 4 MB where 150 KB would look the same on screen. Resize to the displayed width, serve WebP or AVIF, lazy-load below the fold and set width and height so the layout does not jump.
Will a caching plugin fix a slow site?
Only if the delay comes from building the page on every request. Caching does little for oversized images, blocking fonts or a slow database query on uncached pages. Install one cache plugin, not several, and confirm it actually serves cached HTML.
How long does a speed fix take to show in Search Console?
Lab tests change immediately, but Core Web Vitals field data uses a rolling 28-day window, so real-user improvements appear gradually. Judge a fix after about four weeks.
Does server location in India matter for speed?
It affects network round trips, which add to TTFB for every uncached request. For a mainly Indian audience, a nearby server or a CDN edge in India helps; see India vs US server hosting.
Thresholds checked against web.dev Core Web Vitals guidance, 15 November 2026 · Reviewed by the WebJi® team, Jaipur.
Ready to get started with WebJi®?
Join 12,000+ businesses across India and overseas. INR pricing, 18% GST shown before payment and 24/7 email support in Hindi and English — average first reply under 60 minutes.