Web hosting for preschools — Nurseries: photograph-heavy pages, read on a phone at bedtime

Nursery websites do a specific job at a specific moment: a parent, usually in the evening, usually on a phone, comparing two or three settings and trying to work out the monthly cost. Everything about that moment rewards a page that appears immediately.

And nursery websites are heavy, for a good reason. Photographs of the rooms, the garden, the staff and the daily routine are what reassure people, and nobody should be advised to remove them.

So the work is to keep every photograph and stop paying full price for it. That is a measurement problem followed by a pipeline problem, and neither requires spending more on hosting.

Three changes cover most of it. Let the platform convert to WebP, which is built in at no extra cost. Serve responsive sizes, so a phone downloads a phone-sized file rather than a scaled-down original. Lazy-load everything below the fold, so a gallery of twenty images costs the visitor only the two they can see.

Retest after each one rather than after all three. It takes ten minutes longer and it tells you which change did the work, which is what you need the next time somebody uploads forty photographs from an open day.

The visit booking form is the uncacheable part: a POST, an availability check, an email. Time the submission itself and confirm the message lands in an inbox, because a parent who thinks the form failed rings the nursery down the road instead.

And use staging. A nursery site is usually edited by whoever has ten minutes, and a clone means an experiment with a new gallery plugin never appears in front of a parent mid-decision. Daily backups sit underneath that, restorable from the panel in minutes.