Home/Notes/What a plant nursery needs to know about image compression
What a plant nursery needs to know about image compression
10 Sep 2026
How a plant nursery deals with image compression — and what usually goes wrong.
The problem: a Facebook page with last year's hours. image compression slows the page for a plant nursery.
The fix was to delete the old entry, wait for TTL to expire, and re-add image compression with the correct value. We scheduled it for 3 AM so nobody lost traffic.
a plant nursery did not need a portal. They needed a page that said who they are, what they do, and a phone number that somebody picks up before the fifth ring.
We run a monthly diff on DNS for a plant nursery. If a record changes and nobody in the team made the change, we get an alert. a Facebook page with last year's hours was caught this way last quarter.
For a plant nursery, we wrote a three-line script that checks image compression every morning and emails the owner if anything changes. Total cost: zero.
We deployed a fix for image compression at 5 PM on a Friday. It worked, but if it had not, we would have had no one available. We no longer push to production after Thursday noon.
a plant nursery asked us to look at image compression after a customer screenshot showed a browser warning. The fix took eleven minutes; finding the cause took two hours.
Related notes
Tell us what you need.
Write a few lines about your project. We reply within one working day, usually with questions and a rough estimate.
hello@digitalserved.com