In brief: A static website delivers pre-created files without needing to assemble every page from a database on request. It can still contain interactive elements in the browser.
How I use a Static website in practice
I assess a Static website in the context of the whole page. The heading, text, controls, speed and feedback must together explain what can be done and what will follow. First I fix obstacles that prevent the task; decoration and effects come only after the fundamentals work.
What to watch out for
A component is not complete merely because it works with a mouse. With a Static website, I check the keyboard, contrast, zoom, screen reader, slow network and no-script state. Accessibility and performance are not add-ons; they are part of the same experience.
Questions for decision-making
- What task does the person want to complete on the page?
- Where might they hesitate, make a mistake or lose context?
- Does the solution work on mobile, with a keyboard and on a slow network?
- Which signal will show that the change really helped?