Development
Web development services for fast, secure business sites
Development is where good designs turn slow, leaky and hard to change. We build sites that load fast on a mid-range phone, pass a security header scan and send every lead to the right place.
How we choose the stack
We pick the technology after two questions. Who will change the content, and how often? What does the site have to do besides show pages: take bookings, show a catalogue, log clients into a portal?
A marketing site that changes a few times a month is best built static with Astro. Pages are generated ahead of time and served from a CDN close to the visitor, with no database on the live server to attack. A site with logged-in areas, live data or an app inside it suits Next.js. A team that publishes every week and wants to do it alone is better off on WordPress, built lean.
Whatever the stack, the rest of this page applies. Speed, security, tracking and languages are part of the build, never extras bolted on at the end.
Built into every site
Pages rendered ahead of time
Static or server-rendered HTML with as little JavaScript as possible, so pages appear fast even on a weak mobile connection. See speed optimisation.
Strict security headers
Content-Security-Policy, Strict-Transport-Security, Referrer-Policy, Permissions-Policy and the rest, set and tested before launch.
Self-hosted fonts
Fonts served from your own domain. Faster, and no visitor’s IP address goes to a third party just to draw a letter.
Structured data
JSON-LD for your organisation, services, locations, articles and FAQs, generated from the content so it never drifts out of date.
Multilingual and right-to-left
French, English and Arabic with their own URLs and hreflang tags, and layouts written in logical CSS so Arabic mirrors cleanly.
Forms wired to the CRM
Our booking forms drop in with one embed snippet. Each lead reaches Napexy CRM with its source and campaign.
Astro, Next.js and WordPress compared
| Astro | Next.js | WordPress | |
|---|---|---|---|
| Best for | Marketing and content sites | Sites with logged-in areas, apps or live data | Teams that edit pages themselves every week |
| Who edits content | Developers, or a headless CMS we add | Developers, or a headless CMS we add | Your team, in the WordPress editor |
| Upkeep | Little: no database or plug-ins on the live site | Framework and dependency updates | Core, theme and plug-in updates, ideally every week |
| Main risk | Content changes depend on someone technical | More moving parts to host and secure | Plug-in sprawl and missed updates |
How a build runs
Specification
Pages, templates, integrations and a tracking plan written down before any code.
Build in staging
Code in Git, deployed to a hidden staging site you can review at any time.
Content and translation
Content entered in each language, with structured data generated from it.
Quality checks
Real phones, each language, every form, every tracking event, keyboard navigation and speed on a throttled connection.
Launch
DNS, redirects, Search Console, security headers and certificates checked on the live domain the same day.
Handover
Documentation, access to the code repository and hosting, and a maintenance plan if you want one.
Integrations we wire up
- Booking and qualification forms connected to your team calendar
- Napexy CRM, with the source and campaign of every lead
- WhatsApp click-to-chat links tagged by page and campaign
- The Meta pixel on the site, with qualified leads sent back through the Conversions API by our revenue attribution
- Google Analytics and Tag Manager, with a consent banner where the law requires one
- Google Search Console and Bing Webmaster Tools
- Payment, delivery and stock systems for online stores
- Other tools through our integrations
Frequently asked questions
Do you build web apps as well as websites?
Yes. We build our own software, a CRM, booking forms and a unified inbox, so client portals, booking tools and internal dashboards are familiar work. We scope them separately from a marketing site.
Why not use a page builder?
Page builders load their scripts and styles on every page, used or not, and that weight lands on your visitors’ phones. They are fine for a quick test page. For a site you will keep for years, we build proper templates.
Where will the site be hosted?
Static sites go on a global CDN, which serves each visitor from a nearby location. Sites that need a server get one sized for their traffic, with backups and monitoring. We check load times from the countries where your buyers are.
Can we update content without a developer?
Yes. On WordPress your team uses the editor. On Astro or Next.js we can connect a headless CMS, so you edit text and images in a simple interface while the code stays protected.
How do you handle security?
Fewer moving parts first: static pages where possible, no unused plug-ins, strict security headers, HTTPS everywhere and admin access with two-factor login. After launch, updates and monitoring are part of maintenance.
Last updated · By the Napexy team
Keep reading
Tell us where you want to grow.
A 30-minute call with a strategist. You get a plan in plain words and a fixed quote, whether or not you work with us.