Performance profile · Wineries & Vineyards
Wineries: an archive that keeps growing, and a cache that must cover it
Every vintage you release adds pages that must stay online for years, while your club members and your tasting calendar sit permanently outside the cache.
The short answer
A winery site has a shape almost nothing else does: a slowly growing archive of vintage pages that must stay reachable for years, and a small set of logged-in and live requests — club accounts, tasting availability — that can never be cached at all.
Measure it in those two halves. Archive pages should be cache hits: check the response headers for 'x-litespeed-cache: hit' on a second load, and a nearby visitor should see TTFB comfortably below 200ms. Club and booking requests run the full PHP and database path, so read their timings separately and use a current PHP release, Redis object caching and NVMe storage to make them cheap. All of that is included from $2.42/mo.
By the HostingFast team · Reviewed 12 August 2026
NVMe
NVMe throughout the range
Free
Domain, first year
99.9%
Uptime target, monitored
Flat
Renewal price held
Most sites get bigger by adding blog posts. A winery gets bigger by adding vintages, and each vintage page keeps earning long after the wine has gone — sommeliers, writers and collectors search for specific years, so the page has to stay up and it has to stay quick.
Sitting alongside that archive is the part that cannot be cached: the wine club. A logged-in member sees their own address, their own case history, their own next dispatch, which means the cache steps aside on every one of those requests, by design.
Knowing which half of the site a page belongs to is the whole job here. This page covers how to check, what to change, and where an archive quietly gets expensive.
Confirm the archive is being cached at all
Pick three vintage pages — a current release, one a few years old, one from the far end of the archive — and load each twice. On the second load the response headers should show 'x-litespeed-cache: hit'. If any of them reports a permanent miss, that page is being rebuilt from PHP and the database on every visit, and an archive of a hundred of those is a hundred pages of avoidable work.
The usual cause is a cookie. A plugin that sets one for every visitor makes each request look logged-in, and the cache correctly steps aside. The caching plugin's environment report normally names the offender in one screen, and removing it restores the whole archive at once.
Sold-out pages are the cheapest traffic you own
Marking a vintage unavailable rather than deleting the page is the right decision commercially, and it happens to be the right decision technically too. A sold-out page is pure read traffic: no basket, no stock check, nothing dynamic. Cached, it costs the server almost nothing and it goes on attracting the people who later join the club or book a tasting.
So do not let those pages get heavy. Two or three images, tasting notes as text, and no carousel of related bottles firing a query for each one. An archive is only cheap if the pages in it are.
The club and the calendar sit outside the cache
A wine club member logs in, and from that moment nothing they see can be served from a stored copy. Subscription renewals, address changes, case selection — all live PHP and database work. The same is true of tasting availability, which has to be accurate at the instant somebody asks or two parties book the same session.
Measure those separately from the archive. Log in, open the account page and read the timings; then open the tasting calendar and read its availability request. Redis object caching for the repeated lookups, a current PHP release for the arithmetic, NVMe for the round-trips — and switch PHP per site from the panel so you can trial a release and revert if a subscription plugin objects.
Keep the archive tidy as it grows
Every release adds URLs. Check that the sitemap includes them, that older pages still return a proper response rather than a redirect chain, and that images from six vintages ago are being served as WebP like everything else. Archives rot quietly, and the symptom is a slow page nobody visits often enough to notice.
Do that checking on a clone. Staging lets you re-run an image pass across the whole archive, measure the difference on a sample of pages, and push it once you are satisfied — with a daily backup underneath, in case a bulk operation goes further than you meant.
An archive worth keeping, kept cheap
Vineyard owners, winemakers and cellar door and tasting room operators are building something unusual: a library of pages that goes on earning for a decade. It only works if those pages stay quick as they multiply.
LiteSpeed caching in the server handles the archive. Redis, NVMe and per-site PHP switching handle the club and the calendar, which never cache.
- Cache hits verifiable per URL in the response headers
- Redis object caching for logged-in club requests
- WebP conversion applied across the whole image library
- NVMe storage on every tier, from the entry plan up
Why HostingFast
Standard on every plan
Old pages stay quick
A cached vintage page is served without touching PHP, so an archive that keeps growing does not keep getting more expensive.
Logged-in traffic on real hardware
Club accounts bypass the cache by definition. NVMe, current PHP and Redis object caching are standard, which is where that shows.
Cache state you can audit
Load any archive page twice and read the header. A permanent miss becomes a fixable fact rather than a suspicion.
Bulk work rehearsed on a clone
Staging lets you re-run an image pass over hundreds of vintage pages and measure a sample before it touches the live site.
Free SSL that never lapses
Certificates issue and reissue themselves across every domain on the account, the archive included.
One price, every year
Renewal bills at the rate you ordered at, so a site that grows for a decade does not become a growing invoice.
Quick Start
From order to online
- 1
Sample the archive for cache hits
Three vintage pages, loaded twice each, headers checked. A permanent miss on any of them is the first thing to fix.
- 2
Find the cookie that breaks caching
Run the caching plugin's environment report. One plugin setting a cookie for every visitor can push an entire archive out of cache.
- 3
Time the club and the calendar separately
Log in and read the account page; open the tasting calendar and read the availability request. Neither will ever be a cache hit.
- 4
Re-run the image pipeline over the whole library
WebP output and responsive sizes across old vintages too, measured on a sample of pages before and after.
Built In
Loaded onto every plan
- LiteSpeed caching in the web server, verifiable per URL
- Redis object caching for logged-in and uncacheable requests
- NVMe SSD storage on every tier
- WebP image conversion built in at no extra cost
- Per-site PHP version switching from the control panel
- Staging environments for bulk work on a large archive
- Daily backups with a self-service restore from the panel
- Free SSL on every plan, reissued automatically
- 99.9% uptime as the target, monitored around the clock
- Renewal billed at the rate you ordered at
Frequently Asked
What people ask us most often
Do old vintage pages cost anything to keep online?
Almost nothing, if they are cached. A sold-out page has no basket, no stock check and nothing dynamic on it, so the web server hands over a stored copy without PHP running. Keep them light — tasting notes as text, two or three images, no related-bottle carousel firing a query each — and an archive of a hundred pages is genuinely cheap.
One vintage page shows a cache miss on every load. Why just that one?
Usually something on the page sets a cookie, or a rule you have forgotten excludes it. The caching plugin's environment report will name it. A single uncached page matters less than the pattern: if a plugin is setting a cookie for every visitor site-wide, the whole archive is being rebuilt on every visit.
Can anything be cached for a logged-in club member?
The page shell can be, but not the parts that are theirs — address, case history, next dispatch. That is correct behaviour: you cannot serve one member's account to another. Make those requests cheap instead. Redis object caching, a current PHP release and NVMe storage decide how quickly a member's account page appears.
How do I bring years of old images up to current standards?
On a clone, in bulk, and measured. Staging lets you re-run WebP conversion and responsive sizing across the whole library, sample a dozen pages before and after, then push. Take the daily backup as your safety net, because bulk media operations are the kind that go one step further than intended.
Keep reading
Butchers — Hosting Guide
Weight-based pricing and a seasonal cut-off, timed where it matters.
Carpenters & Joiners — Hosting Guide
A workshop portfolio measured properly, and what the images really cost.
Best Hosting With Free SSL
A shortlist with the reasoning shown, and the trap most buyers walk into.
Web Hosting — Built for Wineries & Vineyards
cPanel hosting on NVMe with SSL, migration and a year-one domain included.
WordPress Hosting
WordPress on LiteSpeed with Redis behind it and a staging clone to test on.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Keep the archive fast as it grows.
LiteSpeed caching, Redis and NVMe from $2.42/mo — with a staging clone for the bulk jobs.
View Web Hosting — Built for Wineries & Vineyards plans