TRADEWORKS / WEBSITE DEVELOPMENT

Bespoke HTML websites.
A considered alternative
to WordPress.

A clear, manageable website built around your services. We review your current site before recommending improvements or a static-first rebuild—WordPress may still be the right fit.

Request a Website Review Explore our website development services

Less complexity. More purpose.

Your website should help people understand your business and take the next step. It should not require a complicated technical stack simply to explain your services. A theme, page builder, overlapping plugins and third-party scripts can each add work to the page and another dependency to maintain. Database queries and uncached processing can also affect delivery. None of those problems is inevitable: a carefully built WordPress website can be fast, stable and straightforward to manage.

The useful question is whether the architecture fits the job. If your team mainly needs service information, case studies and a reliable enquiry route, a static-first approach may offer a more direct foundation. If several editors publish daily, manage memberships or depend on established CMS tools, retaining a content management system may be the better decision.

We review what is genuinely needed before proposing a replacement. Sometimes the right answer is to remove redundant plugins, improve hosting or simplify an existing site. A rebuild should solve an identified business problem, with the ongoing editing arrangements understood from the start.

Built around your business.

TradeWorks develops bespoke HTML5 websites with hand-written responsive CSS and minimal, purposeful JavaScript. We do not use WordPress or website builders for these builds. Ordinary public content can be served as HTML without a database query or CMS request on every visit. That gives us direct control over page structure, styling, assets and the functionality we choose to include.

We optimise images and typography, plan useful navigation and integrate technical SEO into development. Semantic headings, form labels, meaningful links and keyboard access belong in the build rather than being added as finishing touches. A restrained dependency footprint also makes it easier to understand what the website loads and why.

Static-first does not mean static in experience. Responsive navigation, accessible FAQs and carefully scoped interactions can work with lightweight JavaScript. Contact forms may use a maintained server-side handler. We agree responsibilities for updates, backups, security and content changes, so the website remains useful after its first launch.

Choose the right foundation.

Both approaches can support a professional business website. The differences become clearer when you consider the people maintaining the site and the features customers actually use. Compare the practical trade-offs below; none is a promise of a particular result.

Frequent independent publishing is a genuine reason to choose WordPress. A bespoke HTML website can involve more developer time for routine changes unless a suitable publishing workflow is included. We discuss that trade-off openly and assess ownership costs over time, rather than compare only the launch price.

On a small screen, scroll the table sideways to compare both approaches.

WordPress and bespoke HTML: practical trade-offs
Consideration WordPress Bespoke HTML
Architecture PHP and a database normally generate content; caching can serve prepared pages. Prepared HTML serves ordinary content; dynamic features are scoped separately.
Performance Can perform well with suitable themes, caching, assets and hosting. A lean starting point, still dependent on images, scripts and implementation.
Security Maintain core, themes, plugins, accounts, PHP and hosting. Fewer CMS components; hosting, forms, scripts and access still need protection.
Updates and dependencies Coordinate compatibility and test updates across the installed stack. Maintain the selected code and any dependencies; no CMS update cycle.
Maintenance Budget for administration, backups, updates and troubleshooting. Budget for code, content updates, testing, backups and server maintenance.
Editing and publishing Useful for frequent independent editing and multiple contributors. Developer involvement is usual unless an editing workflow is agreed.
Customisation Themes and plugins can accelerate features; bespoke work may still be needed. Direct control over markup and styling; functionality requires scoped development.
SEO Strong results are possible with good content and technical implementation. Direct metadata and structure control; no automatic ranking advantage.
Scalability Established publishing, catalogue and membership ecosystems. Static delivery scales well; complex applications may need additional systems.
Hosting A supported PHP/database environment and appropriate caching. Static content has modest hosting needs; forms may still require PHP.
Total ownership cost Consider licences, hosting, maintenance, editorial time and development. Consider initial development, content changes, hosting and ongoing support.

Security is an ongoing responsibility.

WordPress normally uses PHP and a database, as its official requirements explain. Our public content pages can be delivered as static HTML, reducing the need for a CMS runtime for those requests. That is a design choice about dependencies, not a guarantee against cyberattacks. Compromised hosting, stolen credentials, vulnerable scripts and unsafe form handling can affect either approach.

October 2026 advisory — checked 28 October 2026. The UK NCSC notice identifies CVE-2026-109618 and CVE-2026-109619: PHP request-memory handling flaws that can enable unauthenticated remote code execution under certain conditions. These are PHP issues, not vulnerabilities exclusive to WordPress. Whether a particular deployment was exposed requires assessment of its runtime and patch status.

The PHP security announcement lists fixed releases 8.2.35, 8.3.36, 8.4.27 and 8.5.12. Earlier supported-branch releases need the relevant update; legacy versions require vendor advice or migration. Subsequent PHP notices address a specific session-upload configuration and updated Windows builds. Hosting providers should review the current official guidance, including vendor backports, rather than rely on a version label alone.

TradeWorks may still use PHP for contact-form processing. Those handlers, their libraries and the underlying server software must be maintained and patched. We do not describe static HTML as immune, or assume that every WordPress website has been compromised. Access controls, backups, monitoring and a clear maintenance agreement remain essential.

Performance you can measure.

Core Web Vitals describe aspects of real user experience. Largest Contentful Paint (LCP) concerns the main visible content loading; Interaction to Next Paint (INP) concerns responsiveness to interaction; Cumulative Layout Shift (CLS) concerns unexpected movement. They are useful development objectives, not scores we can promise before testing a real deployment.

Our work considers mobile layouts, appropriately sized images, deliberate font loading, efficient JavaScript and caching. Reserving image space helps layout stability. Limiting unnecessary scripts can reduce competing work on the main thread. Keeping critical content in HTML helps users receive useful information without waiting for an elaborate application to start.

Performance depends on implementation, hosting, network conditions and third-party services as well as architecture. A heavy static site can be slow; a well-optimised WordPress site can perform well. We use testing to find actual bottlenecks and review field data when enough visits are available. Google’s Web Vitals guidance explains the measures and the distinction between lab and real-user evidence.

Clear to customers. Understandable to search.

Useful content is the starting point for SEO, answer engine optimisation (AEO) and generative engine optimisation (GEO). We plan crawlable semantic HTML, logical headings, descriptive metadata and relevant internal links. Canonical URLs identify preferred addresses, while an XML sitemap supports discovery. Structured data should describe the visible business and page accurately.

Clear service and location information helps customers decide whether you can help them. Practical answers, original expertise and accessible text are more useful than repeating place names or filling a page with fashionable terminology. Our SEO and content and AEO and GEO services connect those foundations with your commercial priorities.

Google does not rank a website higher simply because it uses HTML rather than WordPress. Neither approach guarantees rankings, AI recommendations or citations. We preserve useful existing content, review discoverability and make the website easier to understand, then assess the work in the context of the market and the business.

Built for businesses with a clear service to explain.

Glazing and window installation companies often need to distinguish reactive work, planned installations and specialist services. Locksmith and security businesses may need clear coverage, service boundaries and credible project information. Plumbers, drainage contractors and electrical contractors need customers to understand the work offered and how to request an assessment.

Pest-control, professional cleaning and property maintenance companies can benefit from concise service information, useful questions and an enquiry route that collects the right context. Care homes and healthcare-related organisations may need more detailed location and service content, with particular care over accessibility, accuracy and any sensitive information.

The industry label does not determine the technology. Publishing frequency, integrations, staff responsibilities and regulatory requirements matter more. A straightforward service website and a frequently updated multi-editor resource can call for different solutions, even within the same sector. We scope the system around those practical requirements.

Experience behind the recommendation.

Our existing portfolio shows how branding, development and ongoing support connect. For Medicrest, Robert’s relationship dates from 2013; the refreshed group website, bringing together four care-home sections, launched in November 2025. That is a completed build with continuing marketing and hosting support.

We built the existing Instant Glass website and have worked with David Ford since 2021. Its new design is described as a rebuild in progress, not a finished redesign. The Instant Windows & Doors, Taylorglaze, Premier Security London and Tailored Cleaning Solutions stories provide further context for the work.

These examples demonstrate the relationships and scope documented in our portfolio. They are not evidence of a universal performance uplift or a claim that every project replaced WordPress. We assess your current website on its own merits and do not invent traffic figures, security results or testimonials to support a recommendation.

A rebuild with continuity.

An existing website can contain years of useful content and valuable addresses. Our process treats migration as part of development. We agree the scope, ownership and launch responsibilities before work begins; the details depend on your website rather than a fixed promise for every project.

  1. Review the starting point

    Discuss your objectives, publishing needs and current website. Review relevant search data and practical concerns before deciding whether optimisation or rebuilding is appropriate.

  2. Inventory URLs and content

    Record existing addresses, valuable pages, assets and forms. Identify what should stay, what needs improvement and any functionality that must be preserved.

  3. Design and develop responsively

    Plan the hierarchy, build the agreed visual direction and adapt it for different screens. Existing branding is retained or refined only within the agreed brief.

  4. Plan the content and SEO migration

    Map old and new content, retain valuable URLs where possible and define redirects where necessary. Check metadata, internal links, canonicals and the intended XML sitemap.

  5. Build the enquiry journey

    Develop and test navigation, forms and any integrations within scope. Confirm validation, privacy information, spam protection and the editing arrangements before launch.

  6. Test and prepare

    Check keyboard access, responsive layouts, content, links and agreed browsers. Review performance and functionality, with clear responsibility for any issues found.

  7. Launch with control

    Back up the existing site, prepare the deployment and check redirects and essential journeys after publication. Launch is a planned change, not simply replacing a folder.

  8. Maintain and review

    Agree responsibility for updates, server software, backups and monitoring. Review search and performance information as evidence becomes available and the business develops.

A few useful answers.

Does every WordPress website need replacing?

No. A well-maintained site may already meet your requirements. A review can recommend targeted improvements or continued maintenance instead of a rebuild.

Can my team still edit the content?

We agree that before development. Direct HTML changes normally need developer input; an appropriate publishing workflow can be scoped if independent editing is essential.

Will moving to HTML improve our rankings?

Technology alone does not guarantee rankings. Content quality, crawlability, migration decisions and many other factors influence search performance.

Can we keep our current web addresses?

Where practical, yes. We inventory existing URLs and plan any necessary redirects before launch. Final routing depends on the agreed content structure.

Can we retain a booking system or other integration?

We review each requirement, including provider terms, data handling and technical dependencies. Functionality is retained or replaced only after its feasibility and scope are agreed.

Is your current website working as hard as your business?

Tell us what your business does, where the website falls short and how your team manages it. We can recommend whether optimisation, maintenance improvements or a bespoke rebuild deserves a closer look. You do not need to arrive with a preferred technology: the purpose of the review is to establish a sensible next step.

The scope, timing and any fee for a detailed review will be agreed before work begins. Please do not include passwords, customer records or other sensitive information.

Request your website review

Tell us about your website and the main reason for your review. We’ll get back to you to discuss the next steps.

Include https:// at the beginning, for example https://example.co.uk.

Choose the closest match; we can discuss other concerns too.

We use your details to respond to your enquiry. Read our Privacy notice and Cookie information. This form uses Google reCAPTCHA for spam protection, which loads when you submit. Google’s Privacy Policy and Terms of Service apply when it is enabled.