BuildWeb development

A website is often the most commercially important software a business runs. It is where people find you, judge you and decide whether to get in touch or buy. We treat it accordingly: a deliberate architecture, a content model that fits how your team works, tested code, and performance and search designed in rather than patched on after launch.

That doesn't mean heavy. Most pages should be plain, fast HTML. Where something genuinely needs to be interactive (a configurator, a dashboard, a 3D visual) we add exactly that, and make sure the page still works when it can't run.

What we do

What we build

  1. 01

    Company and marketing sites

    Static-first sites with a content model your team can edit, and an information architecture planned around how people actually search.

  2. 02

    Content platforms

    Publications, resource hubs, documentation and programmatic page systems, structured so hundreds of pages stay consistent and crawlable.

    Technical SEO
  3. 03

    Storefronts

    Shopify themes, headless commerce and the integrations behind them.

    Ecommerce
  4. 04

    Interactive experiences

    Visual and interactive work, including WebGL, that stays fast on a mid-range phone and falls back gracefully when it can't run.

  5. 05

    Web applications and portals

    Logged-in customer portals, dashboards and tools, and the APIs behind them.

    Software development
  6. 06

    Landing-page systems

    Composable page templates so campaigns ship in hours, measured from the first visit.

    Conversion & analytics

What we hold a site to

Agreed before design starts and checked on every release, not measured once at launch. The Core Web Vitals targets are the published thresholds for a good experience.

What we hold a site to
MeasureTargetWhy it matters
Largest Contentful Paint≤ 2.5 sHow quickly the main content appears. Usually decided by the hero image, fonts and server response.
Interaction to Next Paint≤ 200 msHow quickly the page responds to a tap or click. Usually decided by how much JavaScript is running.
Cumulative Layout Shift≤ 0.1Whether things jump around as the page loads. Images and embeds get their space reserved.
AccessibilityWCAG 2.2 AAKeyboard, screen reader, contrast and zoom, tested automatically and by hand.
JavaScriptOnly what the page usesStatic HTML by default; interactive parts load on their own, when they're needed.

Capabilities

Underneath

  • Astro
  • Next.js
  • React
  • TypeScript
  • Shopify
  • Headless CMS
  • Cloudflare

Architecture

  • Static, server and hybrid rendering, chosen per page
  • Headless CMS and content modelling
  • Design systems and component libraries

Performance

  • Budgets for LCP, INP and CLS
  • Image pipelines, font loading and code splitting
  • Edge caching and CDN configuration

Quality

  • Accessibility to WCAG 2.2 AA
  • Automated tests across browsers and devices
  • Security headers and a strict Content Security Policy

Search and measurement

  • Structured data, sitemaps, canonicals and redirects
  • Analytics and event instrumentation, consent-aware
  • Migrations that keep existing rankings

Approach

How it runs

  1. 01

    Discover

    Who the site is for, what it has to achieve, and what already works. Existing traffic and rankings are measured before anything moves.

  2. 02

    Structure

    Information architecture, URL plan and content model, shaped by search demand and by how your team will edit it.

  3. 03

    Design

    Layouts and components designed in the browser at real sizes, mobile first, with accessibility checked as we go.

  4. 04

    Build

    Small, working increments on a preview URL you can use from the first week.

  5. 05

    Launch

    Redirects mapped and tested, analytics verified, monitoring on, with a way to roll back.

  6. 06

    Improve

    Search and conversion work continues against real data, rather than stopping at launch.

Why Northcode

Search, performance and measurement aren't separate workstreams handed to someone else after launch. The people who plan the information architecture write the code, so what was planned is what ships.

What we avoid

  • Page builders and plugin stacks that make every change slower than the last
  • Shipping a framework's worth of JavaScript to render a paragraph
  • Redesigns that quietly throw away years of search history

Contact

Tell us where your software is today.

Whether it’s already live, half-built, fragile, or still an idea, we’ll give you an honest view of what it needs and what can wait.