Block theme, head to head
Ollie Theme vs Next.js: WordPress at Its Best, Tested Against Code
What happens when WordPress does nearly everything right? Ollie skips the page builder, takes its styles from theme.json and loads CSS one block at a time. That makes it the fairest opponent a Next.js build can face, and the most useful one to study before you choose.
October 7, 2026 · 11 min read
The short answer
Ollie is a free, carefully built block theme for the WordPress Site Editor, with Ollie Pro patterns from $89 a year as of October 2026. Choose it for a brochure site or small shop your team edits visually. Pick Next.js when speed, custom features, integrations or high traffic decide revenue and you want no plugin stack.
On this page
- A block theme that leaves the page builder at home
- Ollie Pro, and the plugins that join it anyway
- When WordPress core moves, Ollie's menus move with it
- The ledger: Ollie at its best against compiled code
- Pattern library or codebase: picking your side
- Exporting blocks: why Ollie content travels well
- Keep the taste, lose the trapdoors: Athena CMS
- Five Ollie owners, five different answers
A block theme that leaves the page builder at home
Most WordPress comparisons are lopsided because the theme shows up carrying a page builder, an add-on pack and a slider. Ollie arrives with none of them. It is a block theme built for the Site Editor by two developers, Mike McAlister and Patrick Posner, and it treats WordPress core as the builder. Global colors, type and spacing live in theme.json. Layouts come from patterns made of core blocks. Its marketing says no expensive page builder plugin is required, and for once the code underneath agrees.
The engineering is careful. Ollie enqueues one style.css on the front end, then registers small per-block stylesheets with wp_enqueue_block_style(), so a page without a given block never downloads that block's CSS. Five full style variations ship free (Agency, Creator, eCommerce, Startup and Studio), with seven color presets, ten typography presets, fifteen templates and 115 pattern files. On wordpress.org it holds a rating of 100 out of 100 from 36 ratings. The Ollie review goes further into setup and design.
One charming flaw: Ollie cannot agree with itself on the count. Its stylesheet header promises over 50 patterns, the readme says over 60, and the folder holds 115 files. Underpromising is a rare vice in the theme business.
Ollie Pro, and the plugins that join it anyway
The free theme is complete on its own. Ollie Pro sells speed of assembly: a cloud library of more than 200 patterns and over 30 full page designs, a Setup Wizard, the Menu Designer, priority support, a video library, Figma files and a Slack community. As of October 2026 the plans are billed yearly:
- Creator: $89 a year for one site.
- Freelancer: $149 a year for ten sites, the plan Ollie marks as most popular.
- Agency: $299 a year for 100 sites.
The plans are yearly subscriptions, the pricing page notes automatic annual renewal, and no lifetime option is offered. Ollie's pricing page says patterns you have already placed keep working if the subscription lapses, which is the honest policy: once inserted, a pattern is ordinary blocks in your content. A 14-day money-back guarantee covers second thoughts. We could not confirm whether renewals bill at the same price, so ask before you budget on it.
Then the rest of the site moves in. A real Ollie site still wants a form plugin, an SEO plugin for search titles and the XML sitemap, often a caching layer, and the free Ollie Menu Designer plugin (6,000+ installs) for the dropdown, mega and mobile menus that Ollie's menu patterns pair with. A shop adds WooCommerce. The theme stays lean while the site grows lumps around it. That is not Ollie's fault, and it is not something Ollie can prevent.
When WordPress core moves, Ollie's menus move with it
Building on core blocks carries a cost that classic themes pay differently. Ollie's header is a pattern holding the core Navigation block, set to open submenus on click. After WordPress 7.1 arrived, the block began marking its mobile submenus as expanded, and Ollie sites showed every submenu open at once. The fix came in Ollie 1.6.3 on September 2, 2026, with a plain changelog line about submenus opening already expanded on WordPress 7.1.
The episode sums up the block-theme bargain. Ollie's team responded quickly, with three releases between July and September 2026, and the readme now says tested up to 7.1. Still, the theme's behavior depends on code it does not own, released on a schedule it does not set, and the theme is maintained by a team of two. If your header matters on a Tuesday morning, you are trusting three calendars: WordPress core, Ollie, and every plugin touching the page.
- Mobile menus. Submenus that open expanded or refuse to close: Ollie mobile menu not working.
- Plugin CSS collisions. Ollie's styles have stretched Forminator's consent checkbox across most of its row, a conflict reported on the support forum. More in Ollie layout broken.
- Typography gone missing. Ten typography presets mean ten ways for a font to vanish after an edit or a move: Ollie fonts not loading.
- Shop display questions. Support threads ask about missing subtotals and the order of variations and add-ons on WooCommerce pages.
- Site Editor drift. Template edits saved in the database override the theme's files, so an update can appear to do nothing: block editor not matching the theme.
The ledger: Ollie at its best against compiled code
The first column is Ollie as owners actually run it: the theme, perhaps Ollie Pro, Menu Designer and the usual plugins. Next to it stands a Next.js site written from scratch, and beside that the same site run through Athena CMS, editor and agents included. Ollie earns better marks here than most themes do, which is the point of including it.
| Ollie + plugins | Next.js build | Next.js + Athena CMS | |
|---|---|---|---|
| Performance | theme.json styles plus per-block CSS that loads only when a block renders | Server Components send little JavaScript; pages prerendered | Same output; the editor lives away from the public site |
| Core Web Vitals | A strong start; fonts, hero images and plugins still decide the score | next/font serves type from your own domain; next/image picks the size per screen | Same, and Argus reports pages that slow down |
| Hosting requirements | Ordinary WordPress hosting: PHP, MySQL and a cache layer | Static files on a CDN, functions for forms | Same setup; Athena holds the content |
| Security | Small theme surface; the exposure sits in core, login and plugins | The public site has no login page at all | Same, and Aegis looks for intrusions every day |
| Plugin dependency | Menu Designer, forms, SEO and caching plugins fill the gaps | No runtime plugins; features compiled into the build | No plugins; chores go to named agents |
| Maintenance | Core, theme and plugins update separately, as 7.1 showed | Dependencies upgraded on a branch, tested, then shipped | Same, with routine checks automated |
| Updates | Three Ollie releases between July and September 2026 | Released when ready, not when core moves | Edits go live without a code change |
| SEO | Clean block markup; metadata needs an SEO plugin | Titles, canonicals and redirects set per route in code | Iris handles titles; Ariadne threads internal links |
| Schema | Supplied by whichever SEO plugin you install | Typed structured data for each page template | Same, refreshed whenever content changes |
| Page speed | Vendor says blazing-fast; real results depend on patterns and plugins | Only the code each route needs reaches the browser | Unchanged by anything an editor does |
| Mobile performance | Core Navigation block menus; 7.1 briefly expanded every submenu | Menus written and tested at each breakpoint | Same, with Harmonia checking accessibility |
| Custom development | Patterns, block styles and theme.json; PHP for anything deeper | Any feature a web app can carry | Any, with fields modeled on your content |
| CMS usability | Site Editor: capable, though templates and parts confuse some owners | Edits go through a developer unless a CMS is attached | Plain fields, live preview, every version kept |
| Ecommerce | WooCommerce templates for shop, product, cart and checkout included | Checkout coded to order, or a commerce provider's API | Built-in store and Stripe-billed memberships |
| Scalability | The usual WordPress ceiling: caching and server size | CDN-served pages absorb traffic spikes | Same, with no cache plugin to babysit |
| Hosting cost | Low on modest hosting while traffic stays modest | Usage-based and often small for static pages | Same footprint, with no Pro renewal or plugin licenses |
| Development cost | Low: free theme, Pro from $89 a year as of October 2026 | Custom build, higher up front | Quoted as one fixed figure once we audit the site |
| Long-term maintenance | Pro auto-renews yearly; a two-person team tracks core changes | One codebase that changes when you decide | Low, with agents on watch |
| Content editing | Edit blocks in place; a global style change can touch every page | Through the connected CMS | Fields and preview, with no sitewide style accidents |
| Integrations | A plugin for each outside service, each with a settings screen | API connections written into the codebase | Same, and Zeus can build banners from live feeds |
| API support | WordPress REST API; block content stored as HTML with comments | Route handlers ship with the framework | Same, serving Athena content to any route |
| Headless CMS capability | WordPress can serve content headless, though Ollie's design would not travel | Takes content from whichever headless CMS you prefer | No separate CMS to bolt on; Athena already is one |
Read the Performance and CMS rows together. Ollie closes much of the speed gap that builder themes open, and its Site Editor is a genuine visual tool. The gap that remains is structural: Ollie still runs on PHP, a database and a plugin stack, and its editing power includes the power to restyle every page by accident. Our Ollie speed guide shows how to measure your own pages.
The third option
Athena CMS, with AI agents on staff.
Not a theme and not a blank Next.js repo. The content system we put behind every custom site: plain fields, a real preview, every version kept, and AI agents that handle the chores a plugin only nags you about.
- PicassoImages
- ApolloSite analysis
- AresCompetitor watch
- PrometheusContent holes
- AtlasPage depth and structure
- DelphiAI search visibility
and 12 more agents. Two come with Athena; the rest are monthly add-ons.
Pattern library or codebase: picking your side
When Ollie is the better choice
- Ten to twenty brochure pages assembled from patterns in an afternoon
- A team that likes visual editing in the Site Editor and wants no page builder license
- A budget that stretches to an $89 Pro plan (as of October 2026) but stops well short of custom development
- A small WooCommerce shop that fits Ollie's shop, cart and checkout templates
- A marketing team that needs to change pages, colors and menus itself, today
When Next.js is the better choice
- A lead-generation site where form handling, tracking and speed are the product
- Programmatic SEO, where page counts run into the hundreds and each page comes from a data row
- A SaaS marketing site that shares components and logins with the app
- A membership area with login levels and recurring billing
- Dashboards, calculators or multi-step forms that outgrow blocks
- Pages where a core update rearranging your menu is not an acceptable risk
Most Ollie owners will find themselves in the left column, and they should feel good about it. A block theme this tidy is the right tool for a lot of small sites. The right column is for businesses whose website has quietly become a product, not a brochure.
Exporting blocks: why Ollie content travels well
Ollie sites are among the easier WordPress sites to move, and the reason is the same thing that makes Ollie good. Content is stored as core block markup, HTML with structured comments, not as a builder's private format or a pile of shortcodes. A migration script can read a heading block, a columns block or an image block and map it to clean fields without guessing.
The harder parts sit outside post content. Site Editor changes to templates, template parts and global styles live in the database as their own records, and they must be read alongside the theme files to know what the live site really looks like. Menus built with Menu Designer get rebuilt as code. WooCommerce products and orders move as data. The Ollie to Next.js migration plan covers each piece, with redirects for every changed URL.
There is a middle path. WordPress can stay as the editor while Next.js renders the public site, a setup explained in keeping WordPress as the CMS. For an Ollie site it makes less sense than usual: the Site Editor's visual output would not carry across, so editors would lose the very thing they chose Ollie for.
Keep the taste, lose the trapdoors: Athena CMS
An Ollie owner usually picked it for taste: clean design, no builder clutter, editing that feels close to the page. Athena CMS keeps that spirit and removes the trapdoors. Editors get plain fields and a real preview of the page as it will publish. Every version is kept. There is no global styles panel where one change quietly restyles the whole site, and no core release that can reshuffle the menu.
The chores a block theme leaves to plugins go to agents with one job each. Iris drafts search titles, meta descriptions and the cards shown when a page is shared. Ariadne finds and inserts internal links. Atlas flags orphan and thin pages. Apollo reviews each page and ranks what to fix. For sites with paying members, Athena membership areas bill through Stripe subscriptions, with login levels set per area.
Five Ollie owners, five different answers
Freelance designer or small studio
Ollie with the Freelancer plan is efficient and tasteful. Stay unless a client needs features blocks cannot hold.
Local service business chasing leads
Ollie can look the part. If paid leads depend on load time and form reliability, a Next.js build earns its cost.
Small online shop
Ollie's WooCommerce templates handle a modest catalog. Big catalogs and custom pricing point to Next.js.
Startup or SaaS company
Ollie even ships a Startup variation. Your marketing site will still want the app's components and sign-in, which is Next.js work.
Content publisher
Blocks are pleasant to write in. Programmatic pages and heavy internal linking favor Next.js with Athena.
Compare WordPress's own default theme in Twenty Twenty-Five vs Next.js, or browse every WordPress vs Next.js comparison. If the right-hand column won, our rebuild service begins with a free audit and finishes with a fixed quote. If Ollie stays, our theme customization team can tune it without breaking the Site Editor.
Questions people ask before they call
Ollie is quick for a WordPress theme, and the vendor calls it blazing-fast, but it still runs on PHP and a database with whatever plugins you add. Next.js builds pages ahead of time and ships only the code each route needs. A tuned Ollie site can perform well; a Next.js build holds that performance as the site grows. The Ollie speed guide shows how to test yours.
No. The free theme includes five style variations, 115 pattern files and WooCommerce templates. Pro adds a cloud library of 200+ patterns, 30+ page designs, the Setup Wizard and priority support, starting at $89 a year (as of October 2026) for a single site. Ollie says patterns already placed keep working if you stop paying, and there is a 14-day refund window.
After WordPress 7.1, mobile submenus in Ollie's Navigation block opened already expanded, all at once. Ollie 1.6.3, released September 2, 2026, fixed it. If your site still shows the problem, update the theme, clear every cache, and check for header edits saved in the Site Editor. The Ollie mobile menu guide has the steps.
Yes. Ollie includes block templates for the product archive, single product, cart, checkout, order confirmation, product search and coming-soon page, plus its own WooCommerce patterns in place of WooCommerce's. That suits a modest shop. Custom pricing, B2B rules or a large catalog are where a Next.js store pulls ahead.
Usually easier. Ollie content is core block markup, which maps cleanly to structured fields, while builder themes store layouts in proprietary formats. The extra work is reading Site Editor customizations saved in the database and rebuilding menus. Every URL is kept or pointed at its new home with a permanent redirect, so rankings have a clear path to follow.
Keep reading
- The default, tested fairlyTwenty Twenty-Five vs Next.js: Plain WordPress Against a Custom BuildTwenty Twenty-Five vs Next.js across 22 rows: the free default block theme against a custom build, and the sites where the free theme wins.
- Theme vs frameworkAstra vs Next.js: A Light Theme, a Heavy Stack and a Custom BuildAstra vs Next.js, row by row: the 2026 AI bundles, the 3-site Pro cap, Elementor and Spectra, real failure modes, and when Astra is still the smart buy.
- New owner, old questionKadence vs Next.js: A Block-First Theme Under New Owners, Against Custom CodeKadence vs Next.js after the Liquid Web shake-up: Kadence Blocks, the new $99 to $499 plans, known issues, and which businesses should stay or move.
- WordPress at its leanestGeneratePress vs Next.js: The Fairest Fight WordPress Can OfferGeneratePress vs Next.js, argued fairly: a sub-10kb theme, a $59 license for 500 sites, the coming template engine, and where a custom build still wins.
- A Customizer theme, weighedBlocksy vs Next.js: A Great Free Theme Against a Site With No Plugins at AllBlocksy vs Next.js compared on 22 rows: the free header builder, Companion and Pro, lifetime licenses, the 2.1.5x regressions and when to stay put.
- The Elementor stack, weighedHello Elementor vs Next.js: The Empty Theme and the Builder That Fills ItHello Elementor vs Next.js on 22 rows: the 6KB vs 30KB claims, Theme Builder dependency, Elementor's real weight, and when the builder is the right call.
- Everything in WordPress vs Next.jsSee the section
Find out if Ollie can carry your next year
Tell us about the site and what you want it to do next. You get an honest read on whether Ollie can handle it, and a fixed price if it cannot.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.