Field Notes · 12

A Go Site and a WordPress Site, in Plain English

A sports car and a motorhome both get you down the road. Six differences between a Go site and a WordPress site, in plain English, and the editor we build for clients who like to make their own changes.

Patrick Jean-Baptiste · November 11, 2026

Clients ask me how a site written in Go differs from a WordPress site. I answer with two vehicles.

A Go site is an electric sports car, custom-built from solid steel. It is welded into one piece and carries no extra weight. It is built for speed and handling.

A WordPress site is a motorhome with snap-on camper extensions, a kitchen and a trailer. You can live in it the first night. It is heavy, and the plumbing, the engine and the wiring all need regular work.

Both get you down the road. Here are six differences.

1. Speed

When a visitor opens a WordPress page, the server starts WordPress from the top. It loads the core, the theme and every active plugin. It asks the database what the post says, which plugins are installed and who commented. Then it assembles the page piece by piece and sends it.

Go is a compiled language. I finish the code, and the computer turns all of it into machine code once. The result is a single program.

When a visitor arrives, that program is already awake and waiting. It serves the page in milliseconds. This site answers in under one.

2. Crowds

Say the national news features your business, and 20,000 people click the link in the same minute.

In WordPress, each visitor needs a PHP worker. Picture a full-time employee with a big desk and an office chair. Each one takes a real slice of the server's memory.

A few hundred show up at once and the memory runs out. Your visitors see "504 Gateway Timeout" or "Error establishing a database connection."

Go has goroutines. Picture assistants so small that thousands of them share one desk. Each one starts with a few kilobytes of memory. A small, cheap server running Go handles tens of thousands of them at once.

3. Hosting and moving

A WordPress site is a Jenga tower. It needs six things to stand:

• A Linux operating system.
• A web server, such as Nginx or Apache.
• The PHP engine and its modules.
• A MySQL database server.
• WordPress core, which is thousands of files.
• Your theme and every plugin.

If one of them falls out of step, the site can break. Moving to a new host means database backups, file paths and server permissions.

A Go site is a lunchbox. The HTML templates, the styling, the images and the logic are compiled into one file. To deploy it, I copy that file to the server and start it. There is no engine to install and almost nothing to break on the way.

4. Security

WordPress runs more than 40 percent of the web. The layout is the same on almost every site, so bots scan for known holes around the clock.

Most of those holes are in plugins. A contact form. A slider. A share button. The author abandons the project or writes sloppy code. A bot finds the hole, injects code into your database or sends your visitors to spam.

A custom Go site has no wp-login.php, no /wp-content/plugins/ folder and no wp_posts table. A bot that knows WordPress finds nothing it recognizes. There is no screen for uploading a plugin, so nobody can install code and run it.

WordPress is a house with forty windows to keep locked. A Go site is a brick wall.

5. Maintenance

A WordPress site needs attention every few weeks. Core updates, theme updates, plugin updates. One plugin update conflicts with another, and you get the White Screen of Death.

Skip the updates for six months to avoid breaking things, and the site becomes an easy target.

A compiled Go program does not change until I change it. No plugin updates itself overnight and breaks your contact form. The server under it still gets its security patches, and that is my job.

6. Hosting cost

Go uses little processor time and little memory. A busy Go site runs on a cloud server that costs $5 a month. (We do not buy or use $5 servers. All of our server hardware is premium.)

A WordPress site with the same traffic often needs managed WordPress hosting, a caching layer and a bigger database server. Each one is a line on the bill.

Side by side

Editing it yourself

WordPress runs that much of the web for one reason. A business owner can log in, click "Add New Page," drop in photos and publish in ten minutes. I give it full credit for that.

A Go site does not come with an admin screen. So we build one.

For clients who like to tinker, we make an editor. You get a login and a screen with the parts you change: hours, prices, a photo, a staff bio, a new post. You save, and the site updates.

The editor holds what your business uses and nothing else. That keeps it easy to learn and hard to break.

Clients who would rather not touch the site send us an email, and the change gets done.

The WordPress side of this, with measurements from my own server, is in WordPress Is a Publishing Tool Masquerading as a Website Builder.