Disclosure: HostBenchLab may earn a commission if you sign up for Hostinger via links in this test, at no extra cost and with no impact on our data.
Hostinger's strongest performance feature is its LiteSpeed-based stack, but a cache-hit homepage and an uncached WooCommerce action are different workloads. A credible load test must show the Hostinger plan, data-center region, caching configuration, request path, concurrency pattern, and percentile latency.
Platform and plan differences
Premium is commonly promoted around $2–$4 per month on a long term and suits cached blogs. Business adds daily backups, staging, more resources, and current eligibility for object caching based on LiteSpeed Memcached. Cloud Startup and higher products provide greater resource allocations. Verify live prices and limits because Hostinger revises packaging.
Hostinger's Cache Manager controls LiteSpeed server cache. Its documentation distinguishes that from CDN caching and PHP OPcache. For WordPress, LiteSpeed Cache integrates page optimization and purge behavior. Only one WordPress cache plugin should be active.
Editor's Pick. Our team's current top recommendation for this category. (Affiliate link coming soon — we only link programs we've vetted.)
Build a fair test fixture
Install current WordPress with a default block theme, one optimized hero image, a navigation menu, and several content cards. Keep transfer size near 1 MB and remove third-party analytics, ads, and fonts. Use the same PHP version and plugin set on every host.
Document the selected Hostinger data center, plan, test date, WordPress version, LiteSpeed Cache version, CDN state, and whether object cache is enabled. Business and higher plans may have features that Premium lacks; do not report a Business result as generic Hostinger shared hosting.
Test matrix
| Scenario | Cache state | Concurrency | What it tests |
|---|---|---|---|
| Anonymous homepage | Warm HIT | 1, 5, 10, 25 users | LiteSpeed page-cache throughput |
| Interior article | Warm HIT | 1, 5, 10 users | Repeatable cached delivery |
| First request after purge | MISS | 1 user, repeated cycles | WordPress/PHP generation cost |
| Search or safe dynamic endpoint | BYPASS | 1–10 users | PHP, database, and account resources |
| wp-admin action | Authenticated | Single user | Editing responsiveness |
Never load-test a live checkout without permission. Use a staging or disposable site and synthetic data.
Measure baseline TTFB
Run 20–30 requests from a location close to the chosen data center. Capture median, p75, p95, and maximum. Repeat from the audience's region. A cached median below roughly 200–400 ms near-region is a useful target, but the p95 reveals inconsistency that an average conceals.
Purge the page between MISS trials. A single first request is too noisy, so repeat the purge/request cycle. For BYPASS tests, ensure the response truly skips page cache and does not expose private data.
Inspect headers to confirm LiteSpeed cache status. Do not infer HIT or MISS only from speed. CDN, browser cache, DNS, TLS resumption, and connection reuse can all change timing.
Run the load test safely
Use k6 or a comparable tool with a gradual ramp. Begin at one virtual user, increase to five and 10, then proceed only if error rate remains zero and latency is stable. Each virtual user should pause realistically between requests; an infinite tight loop does not resemble browsing.
Record:
- Requests per second.
- Median and p95 latency.
- HTTP 429, 500, 502, 503, and timeout counts.
- Hostinger resource graphs and limit events.
- Cache-hit ratio.
- Response sizes and content validation.
A page cache may serve dozens of concurrent anonymous visitors while an uncached search degrades much earlier. Report both; otherwise the benchmark rewards a workload that never reaches WordPress.
What results would count as good
For a small cached site, look for stable p95 response under one second at expected concurrency and zero errors. For a dynamic route, the acceptable threshold depends on user intent; checkout and admin should remain responsive, while a background export can take longer.
Core Web Vitals add the browser perspective. Google's “good” thresholds at the 75th percentile are LCP at or below 2.5 seconds, INP at or below 200 ms, and CLS at or below 0.1. Hosting influences TTFB and asset delivery, but JavaScript and layout choices heavily affect these metrics.
These are acceptance criteria, not invented Hostinger measurements. Publish raw runs only when the tested account and configuration can be reproduced.
Reading Hostinger's resource behavior
If cache HIT latency remains low but BYPASS p95 climbs, the account is reaching PHP, database, CPU, memory, or entry-process limits. Business or Cloud may help, but first inspect slow queries and plugin behavior.
If both HIT and MISS are slow from a distant region, test nearer the data center and enable the CDN where appropriate. If only LCP is poor, resize the hero image, preload it correctly, and reduce render-blocking CSS. If wp-admin is slow, object caching, database cleanup, and fewer heavy plugins matter more than static CDN delivery.
Hostinger offers temporary performance-boost features on some plans; do not benchmark with a short-lived boost unless it is clearly labeled. Sustainable baseline capacity is what a buyer receives every day.
LiteSpeed configuration checks
Install or retain only one cache plugin. Confirm page cache is on, but exclude carts, checkout, account pages, and personalized cookies. Test purge after editing a post. Separate CSS/JavaScript optimizations should be enabled one at a time because combination and delay settings can break interactive components.
Hostinger's Cache Manager refreshes server cache independently from CDN and PHP OPcache controls. Purging one layer may leave another stale. Document every purge during testing.
Object cache reduces repeated database work; Hostinger's current documentation places it on Web Business or higher and uses LiteSpeed Memcached. It can improve dynamic workloads, but an inefficient query still needs application repair.
Hostinger versus alternatives
Bluehost emphasizes managed caching, Redis object caching across documented WordPress products, Cloudflare, and beginner support. SiteGround exposes NGINX Dynamic Cache headers and includes strong WordPress tooling at a higher renewal. Rocket.net and Kinsta cost much more but provide managed edge and application platforms.
Hostinger's main advantage is the performance-to-introductory-price ratio, especially for several cached sites. The compromise is the long prepayment needed for the lowest rate, higher renewal, chat-first support, and resource variation by tier.
Pros and cons
Pros
- LiteSpeed server caching is integrated into hPanel.
- Multiple data-center choices can reduce origin distance.
- Business adds object cache, staging, and daily backups.
- Low long-term promotional price for multiple sites.
Cons
- Best pricing usually requires a four-year purchase.
- Premium and Business results are not interchangeable.
- Dynamic workloads hit shared-resource limits before cached pages.
- Overlapping cache and optimization settings can cause stale or broken pages.
FAQ
Is Hostinger fast without LiteSpeed Cache?
It can serve a light site adequately, but full-page caching removes most PHP work for anonymous visits and is central to strong shared-hosting performance. Test both HIT and MISS.
Which plan is best for WooCommerce?
Business or Cloud is more appropriate than entry Premium because stores need stronger resources, daily backups, staging, and dynamic performance. Confirm current allowances and test checkout under realistic concurrency.
Does a CDN improve load-test results?
It can improve cached static or edge responses, especially across regions. An origin-focused load test should identify whether the CDN is enabled and include an uncached route.
What error rate is acceptable?
For a planned traffic level, target zero application or server errors. Any repeated 429, 5xx, or timeout response requires investigation before launch.
Verdict
Hostinger is a strong low-cost performer for cacheable WordPress sites because LiteSpeed is integrated through hPanel, while Business adds useful dynamic-site features. Its honest weakness appears on uncached concurrency, where plan resources and plugin efficiency determine capacity. Run the disclosed matrix on your own build, judge p95 and errors rather than the fastest request, and choose Business or Cloud for revenue-critical dynamic traffic.