Businesses asking me for a website often arrive with a strong opinion either way. Some have heard WordPress is outdated or insecure. Others have heard custom code is expensive and locks them into one developer. Both views have some truth and a lot of exaggeration.
I build both. AgriDev and Alpha Green are WordPress sites built with Elementor, so their teams edit content without code. The admin and backends for products like NeonTask and Pro Clean+ are Next.js. The choice depends on what the site has to do and who will run it.
What each option really is
WordPress with Elementor is a content management system with a visual page builder on top. Your team logs in, edits text, swaps images, adds blog posts and builds new pages by dragging sections around. A developer sets up the design system, templates and structure so that editing stays consistent.
A custom Next.js site is a React application built specifically for your needs. Content can live in the code, in a headless CMS, or in your own database. It can be a fast marketing site, a full web application, or both.
Choose WordPress when
Your team will update the content regularly. News, projects, services, team members, blog posts. WordPress is built for exactly this, and Elementor lets non-technical staff change layouts without calling a developer for every edit. On AgriDev, for example, the home, about, services, projects, blog and contact pages are all editable by the team.
The site is mainly informational. Explaining who you are, what you do, showing your work and collecting enquiries. This covers most business websites: service companies, NGOs, agricultural and industrial firms, consultancies, clinics.
You want common features without custom development. Contact forms, multilingual content, SEO metadata, galleries and blogs are available as mature plugins.
You may change developers later. WordPress is widely known, so another developer can pick up the site.
Choose a custom Next.js build when
The site is really an application. User accounts, bookings, dashboards, calculators, customer portals or anything with business rules. Bending WordPress into an application with many plugins usually ends in a slow, fragile site. I explain this difference in website vs web app.
Performance is a priority. A well-built Next.js site can serve pre-rendered pages that load very quickly. WordPress can be fast too, but it takes discipline with plugins, caching and images.
You need tight integration with your own systems. If the site reads from your API, shares components with your app or sits next to an admin panel, a single React and Next.js codebase keeps things consistent.
The design is highly custom. Unusual interactions and animation are easier to build exactly in code than through a page builder.
Editing content on a custom site
A common worry is that a custom site means calling the developer to change a phone number. It does not have to. Options include:
- A headless CMS, where editors use a friendly interface and the Next.js site pulls the content.
- An admin panel built into your app, if the content is really data (services, prices, locations).
- Markdown files in the repository, for teams comfortable with that. This site's blog works that way.
The trade-off: a headless CMS gives editors fields and content, but not free page building. If your marketing team wants to design new landing pages by themselves every week, WordPress with Elementor is the better fit.
Security and maintenance
WordPress is not insecure by nature. Most WordPress compromises come from outdated plugins, abandoned add-ons, weak admin passwords and cheap hosting with no isolation. A maintained WordPress site with few, well-chosen plugins, updates, backups and strong logins is solid. A neglected one is a risk.
A custom Next.js site has a smaller attack surface for content pages, especially when pages are static. But it still has dependencies that need updates, and anything with a backend needs the same care as any application.
Either way, someone has to look after it. Budget for maintenance from the start.
Speed
WordPress speed depends on hosting, caching, image handling and plugin count. On AgriDev, image-heavy pages are kept fast with page caching. That is usually enough for a business site.
Next.js gives you more control: static generation, image optimization, code splitting and fine-grained caching. For sites where every bit of speed matters, such as large content sites or landing pages for paid traffic, that control is valuable.
Cost over time
WordPress usually costs less to launch for a content site, because the CMS, editor and common features already exist. Costs come later through plugin licences, updates and occasional fixes when updates conflict.
A custom build costs more upfront for a simple site, because more is built by hand, but it can cost less over time for complex needs, because you are not fighting plugins to do things they were not designed for.
Multilingual sites
Many businesses in the Middle East need English and Arabic, and some need French too. On WordPress this is handled with a multilingual plugin, and the page builder layouts must be checked in right-to-left mode, since a section that looks balanced in English can feel off when mirrored. On Next.js, languages are part of the routing, with a URL per language and translation files or CMS fields per language. Both work. What matters is that each language has its own crawlable URL and that the Arabic version is designed, not just translated. See building bilingual Arabic and English apps and websites.
Hosting
WordPress needs PHP and a MySQL database, which most hosts provide. Good managed WordPress hosting handles updates and caching for you. A Next.js site can be hosted as static files, on a platform built for it, or in a Docker container on your own server. I cover the options in hosting a business website.
A quick decision guide
- Brochure site, blog, team edits often: WordPress with Elementor.
- Marketing site plus an app, portal or dashboard: Next.js, possibly with a headless CMS.
- Bookings, accounts or business rules at the centre: custom web app, often Next.js with an API.
- Unsure: start from who edits content and how often. That usually decides it.
Sometimes the right answer is both: a WordPress marketing site that the team edits freely, linking to a custom Next.js application for logged-in users.
Questions to ask whoever builds your site
- Who will own the hosting, domain and admin accounts? It should be you.
- Which plugins or libraries are used, and why?
- How are updates and backups handled?
- Can my team edit the content I need to edit, without breaking the design?
- How fast is the site on a mobile phone on mobile data?
If you are deciding how to build your website, see my work and get in touch. I can tell you which option fits once I know what your site needs to do.