Home/Notes/Managing page weight at a restaurant
Managing page weight at a restaurant
15 Mar 2024
How a restaurant deals with page weight — and what usually goes wrong.
The problem: a staging URL left in the sitemap. page weight slows the page for a restaurant.
After the move, a staging URL left in the sitemap broke search indexing for a restaurant. Google kept serving the old pages for another nineteen days.
WordPress can handle page weight with a plugin. But the plugin adds JavaScript, a dashboard, and a support ticket when it conflicts with the next update. We wrote four lines of config instead.
For a restaurant, the boring path won: HTTPS, a backup that we have restored once on purpose, and a calendar reminder for page weight.
We deployed a fix for page weight 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.
The most expensive outage for a restaurant was not a hack — it was a staging URL left in the sitemap. Nobody attacked anything. The config just drifted.
Related work on this site follows the same principle: one job, a real inbox, no theatre. a restaurant did not need four analytics dashboards to know that Tuesdays are slow.
DNS propagation is not instant, but it is not magic either. We explained to a restaurant that the TTL on the old page weight record was 86 400 seconds — twenty-four 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