What is a static website?
A static website is made of files that can be served directly to the browser.
The problem
People often use the word website for very different systems. WordPress, PHP and source framework projects may need server logic. A static export can be reviewed as a ZIP and deployed to static hosting.
Simple solution
- Identify static sites by HTML, CSS, JS and image files.
- Check whether PHP, database, login or API routes are required.
- Use the finished export folder for framework projects.
- Review static pages locally before publishing.
- Choose static hosting when server features are not needed.
Common mistakes
- Opening WordPress files as if they were static.
- Sending Next.js source without build output.
- Expecting contact forms without a server.
- Assuming static automatically means privacy-safe.
Checklist
- HTML start page exists
- Assets complete
- No server requirement
- Forms clarified
- External services reviewed
- Hosting matches the technology
FAQ
Is a static website faster?
Often, because less server work is needed. Images, CSS and JavaScript still matter.
Can static websites use JavaScript?
Yes, browser JavaScript is fine when no server features are required.
Do I need a database?
For simple information websites, usually not.