Websites

Custom ASP.NET Core site vs WordPress: which to choose?

By Jérôme Stéphan · October 7, 2026 · Reading time: 7 min

Read in: Español · English · Français

Many small business websites are built with WordPress, and they work. But when someone asks me why their site is slow, why it keeps getting attacked or why Google doesn't show it, the answer usually lies in how it's built. Here I compare, with figures and real cases, a typical WordPress site with a custom ASP.NET Core site, the Microsoft technology I work with. I'll also say when WordPress is still a good choice.

Speed: what the data says

According to the HTTP Archive Core Web Vitals Technology Report (real Chrome user data, CrUX), as reported by Search Engine Journal on 27 May 2026 using April data, around half of WordPress sites (about 49%) get a good Core Web Vitals score: last of the 7 platforms compared.

49%of WordPress sites with a good Core Web Vitals score (April 2026)
2.63 MBmedian page weight of a WordPress site

Why does WordPress tend to be slower?

ASP.NET Core works differently: the C# code is compiled, it runs on Kestrel, Microsoft's web server, and the HTML is generated on the server with only what that page needs. You control every byte that reaches the browser.

Real case: Bosques de Loncotraro

Bosques de Loncotraro is a set of cabins between Villarrica and Pucón. Their old site was WordPress with a booking plugin (WP Booking Calendar). I rebuilt it in ASP.NET Core, with its own booking system and Webpay payments. In practice:

Server response time is about 300 ms (Lighthouse on mobile, 7 October 2026).

Custom doesn't mean perfect: this site, jeromestephan.com, is also built in ASP.NET Core: about 250 ms server response and 10 requests for the home page (Lighthouse on mobile, 7 October 2026). But while measuring for this article, I found my profile photo weighed 787 KB as a PNG; as a WebP it now weighs 56 KB. And Google Fonts were loading in a way that blocked the first render; they now load without blocking. The technology gives you control, but you still have to measure with PageSpeed Insights or Lighthouse.

Security: fewer parts, fewer doors

According to Patchstack's State of WordPress Security in 2026 report, 11,334 new vulnerabilities were found in the WordPress ecosystem in 2025, up 42% on the previous year. 91% were in plugins and 9% in themes.

A custom ASP.NET Core site has no third-party plugins or themes, and no /wp-admin, /wp-login.php or /xmlrpc.php for bots to attack. The attack surface comes down to the code written for that site plus the framework Microsoft maintains. My .NET sites receive WordPress attack probes every day and block them immediately. I go into detail in is WordPress safe?.

Indexing: what Google receives

With HTML generated on the server, Google gets the full text on the first request, without depending on JavaScript rendering. It's the opposite of builders that assemble the page with JavaScript only, as I explain in sites built with AI or Wix. On top of that, I have full control over:

Switching platforms doesn't have to cost you rankings either: the old WordPress addresses on Bosques (for example /wpbc-booking or /pagar-reservas) redirect with a 301 to the new pages (/reservar). If Google isn't showing your pages, read why Google isn't indexing a site and Google Search Console step by step.

Quick comparison

Typical WordPressCustom ASP.NET Core
Page generationPHP and database on every visit, unless cachedCompiled code, HTML tailored to each page
CSS and JavaScript weightBuilds up with each theme and pluginOnly what's needed
Attack surfaceWide: plugins, themes, /wp-adminSmall: the site's code and the framework
Technical SEO controlPartial, depends on pluginsFull
Upfront costLowHigher
Editing it yourselfVery easyDepends on what's built

When does WordPress make sense?

To be fair: for a simple blog or a brochure site, WordPress works well with good hosting, a few well-maintained plugins and regular updates.

A custom site costs more upfront. In return, you pay for exactly what you need, with no plugin licences, and maintenance is handled by the developer. It makes most sense when the site is a working tool for your business: bookings, payments, several languages or a database.

In short

With ASP.NET Core you control speed, security and what Google reads, as long as you measure (here's how I do it with AI, Search Console, Analytics and Bing). Want to know how your current site compares? Get in touch and I'll review it for free, or explore my website, custom software and SEO services.

How does your current site compare?

I'll review your current site for free (speed, security and Google indexing) and tell you, with no strings attached, whether to improve it or move to a custom site.

Get my free comparisonMessage me on WhatsApp
WhatsApp