What is a static site?
A static site is a website whose pages are built once, in advance, and then served to every visitor exactly as they were built. Nothing is assembled while the visitor waits, so pages load fast, and there is far less to break, to attack, or to keep patched than on a site that builds each page on request.
Why it matters to a shop
A customer standing outside your door on mobile data gives a slow page about three seconds before walking into the shop next door. A static site also has no login screen and no database for anyone to break into, which is why you never get the midnight email saying your site is serving malware to your own customers. The limit is just as real: a purely static site cannot take an order, hold a reservation, or store a customer record on its own.
Three things to decide
- Write down what the site must actually do. If people only need to read — menu, hours, address, photos, how to find you — static is enough, and it will be the fastest and least fragile thing you can have.
- If you need to take orders, hold bookings, or store customer details, a static site is not enough on its own — those need a system that can write information down and keep it, which means a database behind the site. Decide that before you pick a tool, not after the site is built.
- Test on your own phone with Wi-Fi off, on mobile data. Office broadband will lie to you, and so will the editor preview — open the published address, not the draft.
Common mistake: Assuming static means you cannot change it. You edit the content whenever you like; the site is simply rebuilt afterwards, usually in seconds.