Web development

Next.js & React Web Development

We build websites and web applications that load fast and are found in search. Our own site scores 99 out of 100 on mobile, and we can show you exactly how.

Most agency websites are slow, including the agencies selling speed

It is worth checking before you hire anyone. Put your prospective agency's own website into Google PageSpeed Insights and look at the mobile score. A surprising number of web development companies score in the 40s and 50s on their own site.

Ours was 80 in July. That was not good enough, so we fixed it.

The main culprit was a logo file: a 1 MB PNG being downloaded to display a 34 pixel icon. We converted it, routed images properly through the framework, removed two animation libraries we were not really using, and cut the render blocking.

Mobile went from 80 to 99. Largest Contentful Paint dropped from 5.1 seconds to 2.1. Total page weight is now 308 KB.

You can verify that yourself right now. That is the standard we build client sites to, and it is why performance is not a line item we bill extra for. Check our score on PageSpeed Insights.

What we build

Custom web applications

React and Next.js front ends with Laravel or Node.js behind them. Dashboards, portals, booking systems, internal tools, anything that is more software than brochure.

Marketing and business websites

Fast, accessible sites that rank. Built either as Next.js static builds or in WordPress, depending on who needs to edit the content and how often.

E-commerce

WooCommerce stores and custom checkout flows. Product catalogues, payment integration, and the performance work that stops a slow store losing sales. Where the shop needs behaviour the platform does not have, we write the WordPress plugin for it.

Headless CMS builds

Next.js front end with WordPress, Sanity or Strapi behind it. You keep the editing experience your team knows, visitors get a static-fast site.

Progressive web apps

Installable, offline-capable web apps when a native app is more than you need.

API development and integration

REST endpoints, third-party integrations, and connecting your site to CRMs, payment providers and internal systems — including AI and workflow automation where it removes manual work.

Performance rescue

Existing site scoring badly on Core Web Vitals? We audit and fix. This is a standalone service, you do not need a rebuild to hire us for it. Page speed is also one of the six categories our own product CROSignal grades on ecommerce stores.

How we work

  1. Scope

    We work out what the site has to do and, more usefully, what it does not. Half the cost of a typical project sits in features nobody uses.

  2. Fixed quote

    A written scope and a fixed price before any code is written. Changes after that are quoted separately rather than absorbed into a moving deadline.

  3. Build in cycles

    You get a working URL early and it stays deployed throughout, so you are reviewing a real site on a real phone rather than approving screenshots.

  4. Launch

    Redirects mapped from the old URLs, analytics and Search Console verified, Core Web Vitals measured on the live site, and documentation for whoever maintains it.

Next.js, WordPress, or something else

We are not loyal to a stack. The right answer depends on your situation.

Next.js or React makes sense when you need real application behaviour, custom interactions, heavy traffic, or the fastest possible load times. It is what we built ExecWeb on, and what this site runs on.

WordPress makes sense when non-technical people need to publish content daily, when you need a large plugin ecosystem, or when budget matters more than millisecond performance. Most of our delivered work is WordPress, including Iowa LGBTQ Chamber, EduQ and Carved Stone Creations.

Headless, meaning both, makes sense when you want WordPress editing with Next.js speed, and you have the budget for two systems instead of one.

Laravel or Vue comes in for heavier back-end work. ProTranslate runs on it, and if what you are describing is really a SaaS platform, we will point you there instead.

Tell us what the site needs to do and who maintains it. We will recommend a stack and explain the trade-off, including where the cheaper option is the better one.

Front end
React, Next.js, TypeScript, Tailwind CSS
Back end
Laravel, Node.js, PHP 8
Content
WordPress, WooCommerce, Strapi, Sanity, MDX
Data
PostgreSQL, MySQL, Redis
Delivery
Vercel, AWS, Docker, GitHub Actions

Selected work

ExecWeb — website built by Zignites

ExecWeb

Corporate site built in Next.js, TypeScript and Tailwind.

ProTranslate — website built by Zignites

ProTranslate

Translation services platform on Laravel, Vue.js and MySQL.

Iowa LGBTQ Chamber — website built by Zignites

Iowa LGBTQ Chamber

Community and membership platform with event management, built on WordPress.

EduQ — website built by Zignites

EduQ

E-learning platform with WooCommerce for course sales.

How we scope and price a build

We quote against a written scope agreed before anyone writes code. What that scope costs depends on which of these you are actually asking for: a marketing or business site of a handful of pages, an e-commerce store, a headless CMS build, or a custom web application — where the price is driven by the logic behind the screens rather than the number of them.

Smaller pieces of work are quoted the same way. A performance audit and fix on a site you already have is a defined job with a defined output, and ongoing maintenance is a monthly agreement priced against the site it covers. Neither requires a rebuild to be worth doing.

If the requirements are still moving, we scope a paid discovery phase first rather than quoting a number we would have to revise twice. That phase produces something you own and can take elsewhere, which is the point of paying for it.

Send us the brief — or the URL of the site you already have — and you will get a written scope and a fixed price back, with the assumptions it rests on spelled out.

What you get on every build

  • Core Web Vitals passing on mobile

    Not “optimised later” — part of the build, measured on a throttled mobile connection before launch.

  • Technical SEO done properly

    Correct canonicals, per-page metadata, structured data, clean heading hierarchy, XML sitemap. We do not hand over a site that needs an SEO agency to fix afterwards.

  • Accessibility

    We build to WCAG AA. Our own site scores 100.

  • Responsive from the start

    Designed mobile-first, not desktop-shrunk.

  • Source code and ownership

    It is yours. No proprietary builder locking you in.

  • Documentation and a handover walkthrough

    Your team should be able to run the site without us.

Frequently asked questions

How long does a website take?
A business site is typically three to five weeks. E-commerce runs six to ten. Custom applications depend entirely on scope, which is why we scope before quoting rather than after.
Will it actually be fast, or just fast on launch day?
Both. Performance budgets are part of the build, and we test on throttled mobile rather than on a desktop connection. We also tell you which of your requests will cost you speed. Large hero videos and heavy tracking scripts are the usual culprits, and it is your call, but you will know the trade-off before you make it.
Do you design as well as build?
Yes, design and build. If you already have designs in Figma we will work from those.
Can you work on an existing site instead of rebuilding?
Often, yes. We audit it first and give you an honest recommendation. Sometimes the rebuild genuinely is cheaper than fixing accumulated problems, and sometimes a targeted fix gets you 90% of the benefit for a fifth of the cost. We will tell you which.
Who owns the code?
You do, on final payment. Full source, no proprietary lock-in.
Do we need to host with you?
No. We deploy wherever you prefer, Vercel, AWS, or standard hosting. We will recommend based on your stack, but the choice is yours.
Do you handle SEO too?
We handle technical SEO as part of the build: canonicals, metadata, structured data, performance, crawlability. Content strategy and link building are separate work we can quote for.
What if we need changes after launch?
We offer monthly maintenance plans priced against the site, or we quote ad hoc changes as they come up. Neither is mandatory. You own the code and can take it anywhere.

Tell us what you are building

Send us what you have, a brief, a rough idea, or a site that is not working. We will tell you what it would take, which stack fits, and what it would cost. No charge for that conversation.