Not every website should be WordPress. A concrete contractor in Minnesota does not publish daily, does not need a content team, and does not want a plugin update to be the thing that takes their quote form offline in March when the season starts.
New Image Concrete is built as a static site using Astro, served from nginx, with no database and no content management system behind it. This explains why, what the trade-off actually is, and when a static build is the wrong answer.
Key Takeaways
- A static site has no database and no server-side application, which removes the most common causes of a small business site breaking or being hacked.
- The trade-off is real: editing requires a rebuild, so a static site suits businesses whose content is stable, not ones that publish weekly.
- For a seasonal local trade, the quote form is the entire site. Everything else exists to get a visitor to it with enough confidence to fill it in.
- Local service pages need to name the towns served, because that is how the searches are phrased.
What Does New Image Concrete Do?
New Image Concrete is a concrete contractor based in Cottage Grove, Minnesota, serving the Saint Paul area. Their work covers driveways, patios, stamped concrete and foundations, and they also handle snow services, which matters in that climate.
The site is deliberately short. Services, work, testimonials, a quote request, a booking confirmation and an FAQ section. There is no blog, no resource library and no gated content.
Why Build a Local Contractor’s Site Without WordPress?
Because the things WordPress is good at are things this business does not need, and the things it costs are things this business feels.
WordPress earns its complexity when content changes often and non-technical people need to change it. A contractor’s service list is stable for years. The photographs change a few times a season. The phone number almost never changes.
Against that, a WordPress site brings a database, a PHP application, a theme and a set of plugins that all need maintaining. For a business with no in-house technical person, each of those is a way for the site to break quietly. The most common failure we see on small trade sites is not a hack or a crash: it is a contact form plugin that stopped delivering email months ago and nobody noticed, because nobody was watching the one thing the site exists to do.
What a static build actually removes
Astro produces plain HTML, CSS and JavaScript files at build time. The server hands those files to the visitor. There is no database query, no template rendering and no application code running per request.
That removes several whole categories of problem at once:
- No database means no database corruption, no connection errors under load, and nothing for an SQL injection to target.
- No plugins means no plugin update breaking the site, and no abandoned plugin becoming a vulnerability.
- No admin login means no brute-force login attacks, which are the single most common attack against small WordPress sites.
- Speed comes for free rather than needing caching layers, because there is nothing to cache. The page is already a file.
What it costs
Honesty matters more than advocacy here, because the trade-off is genuine.
Editing a static site is not the same as editing WordPress. There is no admin dashboard where the owner logs in and changes a paragraph. A change means editing source and rebuilding the site. That can be made easy, but it is never as easy as WordPress, and for a business that wants to publish content regularly it is the wrong choice.
We say this plainly to clients before choosing the approach, because the day someone wants to add a blog is the day the decision gets tested. If regular publishing is likely, WordPress is usually the better call even though it needs more maintenance.
What Matters on a Local Trade Website?
One thing, mostly: getting a qualified visitor to a quote request without friction.
The quote form is the product
The site’s primary action is a free quote request, and it appears early rather than being tucked at the end of a long scroll. There is a dedicated confirmation state after booking, which sounds minor and is not. A form that submits and leaves the visitor on the same page looks broken, and people submit twice or phone to check it arrived.
Proof before persuasion
Two sections carry the trust argument: a work section showing completed jobs, and client testimonials. For a trade where the customer is letting strangers dig up their driveway, photographs of finished work do more than any amount of copy about quality and reliability.
Name the places you serve
The site names Cottage Grove and the Saint Paul area explicitly, including in the page title. Local searches are phrased as “concrete contractor near me” or “stamped concrete Cottage Grove”, and a site that never names its towns cannot match the second kind.
The caution here is that this only works when the pages say something true and specific about each location. Five near-identical pages with the town name swapped are thin content, and search engines have been good at spotting that for years.
When Is a Static Site the Wrong Answer?
When the client wants to publish regularly, when content needs to be edited by several people, when the site needs user accounts or a shop, or when a third-party tool the business depends on assumes WordPress.
Any one of those usually tips the decision. A static build is an excellent fit for a stable brochure-and-quote site for a local trade, and a poor fit for almost anything that grows content weekly.
Frequently Asked Questions
Is a static website better than WordPress?
Neither is better in general. A static site is faster and has a far smaller maintenance and security surface. WordPress is far easier to edit and extend. The right answer depends on how often your content changes and who changes it.
Can I edit a static website myself?
Not in the way you edit WordPress. There is no admin dashboard by default. It can be connected to an editing interface, but if self-editing is a priority from the start, that is an argument for a content management system rather than against a static build.
Do static sites rank well in search?
They can rank as well as any other site. Search engines index HTML, and a static site serves HTML quickly. Rankings come from content, structure and relevance, not from the build method, though fast pages help.
What happens when I want to add a blog later?
It is possible, and it is a rebuild rather than a switch. This is the main reason we ask about publishing plans before choosing the approach rather than after.
Choosing Between Approaches?
If you run a local trade and your site exists mainly to show your work and take quote requests, you may not need the machinery you are currently maintaining.
See more of our builds in our portfolio, read how we decide on our process page, or get in touch to talk it through.
