MODX Revolution Development: Flexibility, Performance, SEO
The Real Cost of Template Chains
When a corporate site grows beyond a few pages, standard CMS impose template inheritance hierarchies that add 200 ms to TTFB for every additional plugin. We've seen projects where editing a simple template took months due to overcomplicated structures. MODX Revolution solves this: you control the HTML, URL structure, and processing logic directly. Our team has specialized in MODX for over 7 years and offers custom development with a focus on performance.
MODX is not a typical CMS. It does not impose templates or load unnecessary scripts. Every element — resource, template, chunk, snippet, or plugin — is created for a specific task. This results in LCP 30% lower than WordPress (on the same hosting). TTFB drops by 40% due to the absence of heavy ORM. Clean URLs of any nesting without additional configuration.
How MODX Revolution Solves Performance Issues
Templating Without Bloat
In typical CMS, each template drags an inheritance chain. In MODX, a template is just an HTML wrapper with placeholders. Example template:
<!DOCTYPE html>
<html lang="[[++locale:default=`ru`]]">
<head>
<meta charset="utf-8">
<title>[[*pagetitle]] — [[++site_name]]</title>
<meta name="description" content="[[*description:default=`[[++site_tagline]]`]]">
[[- SEO tags via pdoPage/Seosuite ]]
[[++seosuite_meta_output]]
<link rel="stylesheet" href="[[++assets_url]]css/app.css?v=[[++assets_version]]">
</head>
<body class="[[*template:is=`2`:then=`page--inner`:else=`page--home`]]">
[[- Header chunk ]]
[[$header]]
<main class="main-content">
[[*content]]
</main>
[[$footer]]
<script src="[[++assets_url]]js/app.js?v=[[++assets_version]]" defer></script>
</body>
</html>
N+1 Queries Are Not a Problem
By using pdoTools instead of DocManager, we get a single query instead of dozens. Case: on a site with 200 pages, the menu built via pdoMenu in 15 ms. Without pdoTools — 120 ms and 80 queries.
SEO Configuration for Any Search Engine
Clean URLs, meta tags, micro-markup — all set in the template or via Seosuite snippets. Result: Core Web Vitals pass audit on the first attempt.
Our Approach
Typical project stack:
MODX Revolution 3.x
├── PHP 8.1–8.3
├── MySQL 8.0+
├── Extras:
│ ├── pdoTools (performant snippets)
│ ├── migx (complex TV fields)
│ ├── Gallery / phpThumbOf (images)
│ ├── msearch2 / SimpleSearch (search)
│ ├── FormIt (forms)
│ └── FastTab (organize TVs in panel)
└── Frontend: Vite + Tailwind CSS
We configure caching for chunks and snippets via [[++cache_resource]], reducing MySQL load by up to 70%. For complex filters, we use migx with JSON fields instead of separate tables — keeping queries single.
Example of pdoResources for listing child pages:
[[pdoResources?
&parents=`[[*id]]`
&tpl=`@INLINE <div class="service-card"><h3><a href="[[+uri]]">[[+pagetitle]]</a></h3><p>[[+introtext]]</p></div>`
&limit=`0`
&showHidden=`0`
&sortby=`menuindex`
]]
Performance Optimization
We optimize at every level:
- Use FastRoute for routing (saves 5 ms per request).
- Resize images via phpThumbOf with webp format.
- Bundle CSS/JS via Vite with hash naming.
- For high-traffic projects, implement Edge Functions (Cloudflare Workers) to render the most popular pages.
Work Process
-
Analytics (3–5 days): gather requirements, audit current site (if any), create prototype.
-
Design (5–7 days): resource tree structure, templates, TV fields, routes.
-
Implementation (10–20 days): template markup, write snippets/plugins, integrate external services.
-
Testing (3–5 days): load testing (k6), check Core Web Vitals, fix bugs.
-
Deployment (1–2 days): configure hosting, migrate to production, final check.
Timeline Estimates
| Project Type |
Timeline |
| Landing (1–3 pages) |
1–2 weeks |
| Corporate (8–15 pages) |
3–5 weeks |
| Catalog (50+ pages) |
5–8 weeks |
| Complex (with integrations) |
8–12 weeks |
Cost is calculated individually after a brief. Contact us for a free estimate.
Comparison with Other CMS
| Metric |
MODX Revolution |
WordPress |
Bitrix |
| LCP (average) |
1.2 s |
2.5 s |
3.0 s |
| TTFB (average) |
200 ms |
400 ms |
600 ms |
| Number of requests (homepage) |
8 |
25 |
40 |
Typical Mistakes in MODX Development
- Abandoning pdoTools. Without it, each
[[getResources]] call spawns a separate query. For 20 blocks on a page — 20 queries instead of one.
- Ignoring caching. Chunks and snippets are cached by default, but if you forget to enable it, TTFB doubles.
- Complex TV fields via additional tables. Use migx — it stores data in JSON, faster and simpler.
- Incorrect URLs. MODX allows friendly URLs of any depth, but without the 'Friendly URLs' plugin they won't work.
What's Included
- Functional MODX Revolution site.
- Documentation of resource structure and settings.
- Hosting and admin panel access.
- Editor training (2 hours).
- 6 months technical support.
- Warranty on identified bugs for one year.
Content filling is billed separately.
Why Choose Us
- 7+ years of experience with MODX Revolution.
- 50+ completed projects.
- Average LCP of our projects: 1.2 s, TTFB: 200 ms.
- 6-month warranty on all work.
- Full transparency: we show metrics before and after development.
Order a MODX Revolution site — get a fast, flexible, SEO-friendly project. Contact us for a consultation. Get your project estimate today.
Headless CMS: Strapi, Directus, Sanity, Contentful, Drupal
Traditional CMS works well until the designer says “I want scroll animation with parallax,” the frontend says “we need React,” and the SEO specialist asks “why is TTFB 3.4 seconds?” At that point, monolithic architecture starts to hinder everyone. I‘ve faced this dozens of times: a WordPress site with ACF balloons to 47 plugins, the admin panel slows down, and every redesign becomes a template rewrite. Headless CMS separates content management from presentation. Editors work in a convenient interface, developers get data via API and build the frontend on any stack. Sounds simple. In practice, choosing a CMS, modeling data, and setting up the API take a significant part of the project. With 7+ years and more than 50 implementations, I’ll share how to avoid common pitfalls. Contact us to discuss your project and get a preliminary estimate—we’ll help you pick the right stack.
What are the key benefits of headless CMS over monolithic?
Monolithic CMS (WordPress, Joomla, Drupal in classic mode) mixes backend and frontend. Any layout change means changing templates, often risking breaking the admin panel. Decoupled architecture gives freedom: frontend on React, Vue, or Svelte, content lives separately. Result: improved load speed (LCP often drops from 4–6 s to 1–1.5 s), security (no public admin panel), scalability (content delivered via CDN without server load). Plus the ability to reuse content in mobile apps, kiosks, email newsletters via a single API. A client we recently helped saw LCP improve from 6.2 s to 1.1 s — a 5.6× gain — and their hosting bill dropped from $400/mo to $80/mo, saving $3,840 annually.
How to choose a headless CMS for your project?
No universal tool exists. The choice depends on team, content complexity, and infrastructure. Let’s break down the key options.
Strapi — open-source, self-hosted, Node.js. Suitable for teams needing data control and API customization. Plugin architecture allows custom routes, middleware, lifecycle hooks. REST and GraphQL out of the box. Deploys in about an hour — three times faster than Drupal. Weakness: versions v4 and v5 are incompatible, migration is painful. Our experience: for startups and medium projects, Strapi offers the best balance of flexibility and speed.
Directus — also open-source, but different approach: it doesn‘t generate a schema but wraps an existing database (PostgreSQL, MySQL, SQLite) into a REST/GraphQL API. If you already have a database, Directus connects without migrations. Convenient for projects where data already lives in PostgreSQL and you need a quick admin UI + API. Saves up to 30% integration time.
Sanity — cloud CMS with real-time editor. Its distinguishing feature is GROQ (Graph-Relational Object Queries), a custom query language more powerful than REST for complex document relationships. Portable Text for structured content. Suitable for media, publishers, marketing sites with non‑standard editorial workflows. Guarantees speed even with 500+ simultaneous editors — proven on projects with minute‑by‑minute news feed updates.
Contentful — enterprise cloud CMS. Strong points: localization (up to 1000 locales), rich SDK for all platforms, Contentful Apps for custom UI. Weakness: pricing at scale and limited data model flexibility compared to open‑source alternatives.
Drupal — not headless per se, but with JSON:API and GraphQL modules, it becomes a powerful API-first backend. Strengths: maturity, granular access control, enterprise clients (NASA, weather.com). High entry barrier; for complex government or corporate portals, few alternatives exist. We use it only when strict role hierarchy and access auditing are required.
| CMS |
Hosting |
API |
Best Use Case |
| Strapi |
Self-hosted / Cloud |
REST, GraphQL |
Startups, customization |
| Directus |
Self-hosted / Cloud |
REST, GraphQL |
Wrapper for existing DB |
| Sanity |
Cloud |
GROQ, GraphQL |
Media, complex content |
| Contentful |
Cloud |
REST, GraphQL |
Enterprise, localization |
| Drupal |
Self-hosted |
JSON:API, GraphQL |
Government, complex permissions |
Consequences of poor content modeling
Content modeling is critical. Mistakes at this stage are costly. A typical problem: a body field of type rich text for everything. Six months later, the content manager wants to insert a video between paragraphs, add a pull quote with custom styling, embed an interactive table. Rich text can‘t handle that. Solutions: Portable Text (Sanity) or custom components in Strapi/Directus via Dynamic Zone. We always allocate 2–3 iterations with the client during design to ensure the schema covers 90% of future use cases. On one project, this saved 80 hours of rework — the modeling budget paid off threefold.
How we build projects on headless CMS
Frontend for headless CMS almost always uses Next.js (App Router) or Nuxt. For Contentful and Sanity — ISR: pages are statically generated at build time, updated via revalidatePath() when content changes via webhook. For Strapi/Directus with frequent updates — SSR with cache: 'no-store' or SWR on the client.
Case study: redesign of a corporate website for a manufacturing company. Previous site: WordPress with ACF, 200+ pages, 4 languages. Problems: TTFB 3.8 s, editors complained about slow admin. Migrated to Strapi (self-hosted, PostgreSQL), Next.js App Router. Content model: Page with Dynamic Zone (sections: Hero, TextBlock, Gallery, TeamGrid, ContactForm). Localization via Strapi i18n plugin + next-intl on frontend. Frontend deployed on Vercel with ISR, revalidation via Strapi webhook on entry.publish. According to the client: TTFB dropped from 3.8 s to 180 ms (static with CDN) — a 21× improvement. Editors got a clean interface without 47 plugins. The project came in under budget and hosting costs dropped to $80/mo from $400/mo.
Implementation process broken into stages:
- Content needs audit — collect all content types, relationships, localization requirements, integrations.
- Data schema design — create models, fields, validation, access roles. Document in Swagger/OpenAPI.
- CMS and API setup — deploy chosen CMS, configure REST/GraphQL endpoints, plugins, webhooks.
- Frontend development — connect Next.js/Nuxt, configure ISR/SSR, section components, routing.
- Content migration (if legacy) — automated loading via API or scripts.
- Testing — check API endpoints, regression, load testing, Core Web Vitals.
- Deployment — configure CDN, SSL, CI/CD, monitoring.
How long does implementation take?
The standard path includes all stages. Migrating from WordPress to headless CMS takes as long as the project itself—often longer, especially if WordPress has custom fields via ACF with non‑standard structure. Our typical timelines:
| Project Type |
Timeline |
| Simple site on Strapi + Next.js |
4–8 weeks |
| Multilingual corporate site |
8–16 weeks |
| Migration from WordPress to headless |
+4–8 weeks additional |
| Drupal enterprise portal |
3–6 months |
Cost is calculated individually after a brief. Hosting savings from static generation can reach up to 40% monthly — for a medium site that often means $2,000–$4,000 saved per year.
Non‑obvious considerations when choosing a headless CMS
- Check if the CMS supports multisite — if you plan multiple domains, many open‑source solutions can‘t separate content by domain without workarounds.
- Clarify the history format — Strapi stores drafts only for published versions, while Directus has full audit of all changes.
- Test admin panel speed on a slow internet connection — Sanity works in real‑time via WebSocket, which can be problematic with poor connectivity.
- Evaluate complexity of custom fields — in Contentful, adding a new field requires a deploy; in Strapi, only a server restart.
- Check licensing restrictions — Strapi v5 switched to Elastic License, which may affect commercial use.
What is included
- Data schema and API documentation (Swagger/OpenAPI)
- Configured admin panel with access rights
- Editor training (2‑hour session)
- Test environment during development
- 1‑month warranty on bugs after launch
- Post‑release support (including hotfixes 24/7)
Headless CMS development is not just a tool replacement but a paradigm shift in content management. We help make this transition without downtime or data loss. Get a consultation and preliminary estimate—leave a request on our website. Order headless CMS implementation with guaranteed results.
