Home/Notes/image compression: a field note from a small hotel

image compression: a field note from a small hotel

24 Apr 2024

How a small hotel deals with image compression — and what usually goes wrong.

Request small-hotel.c… HTML document Images a Facebook page with… Other assets large files Render visible page

The problem: a Facebook page with last year's hours. image compression slows the page for a small hotel.

Early on we tried to automate image compression for a small hotel with a cron job. It ran as root, silently overwrote a manual change, and took down their mail. Lesson learned.

You do not need a status page if you have never gone down. a small hotel is on month fourteen of zero downtime, and the secret is boring: correct image compression and a host that does not oversell.

If you only touch image compression once a year, a dashboard is extra risk. Files, a mailbox you read, and a person who still answers will outlast any SaaS control panel.

There is a difference between a site that loads and a site that works. image compression is part of the second category for a small hotel.

The job started when a small hotel realised their image compression had been wrong for months. Nobody noticed because the site still loaded.

A form that collects data for a small hotel should say where the message goes. Nine fields and a captcha on a quiet Tuesday will cost you the person who actually wanted to pay.

More notes

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