Key takeaways
- Static pages are fast because nothing is built per request.
- With no database or admin login, the attack surface is much smaller.
- Hosting is cheap or free and scales easily.
- The cost is manual editing, which suits small, rarely-changing sites.
What “static” means here
This site has no database and no content management system. Every page is a finished HTML file, styled with one stylesheet and enhanced by small JavaScript files. When you open a page, the server simply sends the file; nothing is assembled on demand. The only server-side pieces are a small function behind the optional AI chat and the hosting provider’s form handling for the contact form.
What the static approach buys
- Speed: there is no database query or template rendering per request, so pages reach the browser quickly and score well on Core Web Vitals, which supports SEO.
- Security: with no database, no login screen and no server plugins, there is far less to attack. Many common WordPress-style compromises simply don’t apply.
- Reliability and cost: static files are trivial to cache and serve, so hosting is cheap or free and handles traffic spikes well.
- Control: I decide every tag, header and line of markup, which makes accessibility and technical SEO easier to get right.
The trade-offs
Adding content means editing HTML directly instead of filling in a form. That is fine for a portfolio with a fixed set of pages updated occasionally. It scales badly for a site publishing daily, and it’s harder for non-technical collaborators to edit. Dynamic features such as contact forms, search and chat need a service or a small serverless function. On this site the contact form and the AI assistant each call a tiny server-side script on the same host, so the pages themselves stay static and the API key never reaches the browser.
When a CMS or generator is the better choice
- You publish frequently or have several editors.
- You need user accounts, comments or e-commerce.
- You want templates so a design change updates hundreds of pages at once. A static-site generator keeps the speed benefits while adding templating.
If you do choose WordPress, follow a hardening checklist from day one.
Privacy by design in the tools
The browser-based utilities on the Tools page follow the same philosophy. They run client-side with the Web Crypto API and plain JavaScript, so nothing you type is uploaded to a server.
Frequently asked questions
Is a static site good for SEO?
Yes. Fast, crawlable pages with clean markup are an excellent foundation, though content and links still decide rankings.
Can a static site have a contact form?
Yes. A small server-side script on your host, or a third-party form service, can handle submissions without turning the whole site into a CMS.
Is static hosting free?
Many hosts offer free or very cheap plans suitable for portfolios. Check current limits for your traffic.
Can I move from static to WordPress later?
Yes, though you’d rebuild templates and migrate content. Plan URL redirects so existing links and rankings carry over.
Keep reading
A Practical Technical SEO Checklist for Small Static Sites
The short, concrete checklist I used on this portfolio: crawlability, structured data, performance and metadata, plus how to verify each step.
Read article →A Practical WordPress Hardening Checklist
Most WordPress compromises come from basics being skipped. This checklist covers updates, logins, backups and security headers.
Read article →Image Optimization for SEO and Speed
Images are usually the heaviest part of a page. Modern formats, responsive sizes, explicit dimensions and honest alt text cover most of the gain.
Read article →