Key takeaways
- A static site is fast, cheap to host and has a small attack surface, but needs a plan for forms and dynamic features.
- WordPress is powerful, and most problems come from skipped updates, weak logins and unused plugins.
- Performance and accessibility are part of the build, not a final polish step.
- Pick the simplest tool that does the job, and know when to move up.
What this topic covers
I build and experiment with websites using hand-written HTML, CSS and vanilla JavaScript, and I also work with WordPress. This portfolio is a no-framework, no-build-step static site, so it is easy to host anywhere, easy to audit and easy to keep fast. The articles below explain the trade-offs and the checklists I follow.
Articles on this topic
Why Local Businesses Need a Professional Website
Control, trust and search visibility, even if you already have a Facebook page.
Read article →Why This Portfolio Is a Static Site (And What That Trade-off Buys)
Plain HTML, CSS and JavaScript on any ordinary web host: what it buys in speed, security and cost, what it costs in convenience, and when to choose something else.
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 →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 →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 →How I approach a build
- Semantic HTML first. Proper landmarks, headings and labels give accessibility and SEO a solid base.
- Mobile-first CSS. Start with the small screen, then enhance for larger ones, and respect
prefers-reduced-motion. - Small, deferred JavaScript. Only what a page needs, loaded without blocking rendering.
- Security by default. Security headers, a restrictive Content Security Policy and no secrets in browser code.
- Dynamic features on the server. Things such as a contact form or an AI chat call a tiny server-side script, so the page stays static and any API key stays private.
WordPress, kept safe
For clients and projects that need a CMS, WordPress is a sensible choice. The hardening checklist covers updates, logins, backups, file permissions and headers. Speed matters there too, which is why the image optimization guide is relevant to every build.
Frequently asked questions
Static site or WordPress?
If content changes rarely and you value speed and simplicity, a static site is hard to beat. If non-technical people need to edit content often, a CMS such as WordPress is usually more practical.
Can a static site have a contact form or chat?
Yes. A small server-side script can receive the form or relay chat requests while the pages themselves stay static.
Do you build sites for others?
You can contact me with your idea and requirements. I will tell you honestly whether I can help; prices and timelines depend on the project.