MODX Optimization: From Diagnostics to Production

MODX Acceleration: From Diagnostics to Production

We integrate and optimize MODX Revolution to achieve lightning-fast performance. With 10+ years of experience and 100+ successful MODX acceleration projects, our team brings load times down to 200 ms and ensures Core Web Vitals pass. Hosting resource savings after optimization typically reach 30–50%, saving clients up to $500 per month on server costs. Get a consultation on MODX optimization—contact us for a free audit.

How to Identify MODX Bottlenecks

The first step is to understand what slows down. MODX logs slow queries if you enable it in core/config/config.inc.php:

define('MODX_CONFIG_KEY', 'config');
// in System Settings:
// log_level = 4 (DEBUG)
// log_target = FILE

A more precise tool is xDebug + Blackfire or just EXPLAIN in MySQL/MariaDB for queries that MODX generates during page rendering. Typical problems:

• modResource reads all fields, including content, even when only pagetitle is needed
• getResources without limit runs SELECT * on all child resources
• Snippets without &cache=1 execute on every request

Experienced engineers also check PHP-FPM and OPcache settings—often the bottleneck is not MODX itself but the environment configuration. Optimization investments usually pay back within 2–3 months by lowering server load.

Caching at the MODX Level

System cache is stored in core/cache/. For production, ensure the directory has permissions 755 and is not mounted via tmpfs without sufficient size.

Optimal System Settings:

Why Redis Beats File Cache

For Redis cache, install the Redis package (modmore or similar) and add to core/config/config.inc.php:

$config_options = [
    'cache_path' => MODX_CORE_PATH . 'cache/',
    'cache_default_handler' => 'xPDORedisCache',
    'cache_xpdo_handler'    => 'xPDORedisCache',
    'redis_host' => '127.0.0.1',
    'redis_port' => 6379,
    'redis_db'   => 0,
];

After switching to Redis, TTFB drops by 30–50% on high-traffic sites because disk stat() operations on cache files disappear. Comparison:

According to Redis, in-memory data storage significantly speeds up read operations. In practice, this cuts server resource costs by 30–40%.

Optimizing Snippets and pdoTools

Uncached calls [[!SnippetName]] are the main cause of slowness. Audit by searching templates and chunks: grep -r '\[\[!' across the elements folder. Rules:

• If a snippet does not depend on session/cart/user — make it cacheable: [[SnippetName? &cache="1" &cacheExpires="3600"]]
• getResources, pdoTools are cached via the built-in &cache parameter
• FormIt and Login — always uncached, move to separate chunks

pdoTools instead of getResources is critical for sites with large catalogs. pdoTools uses JOIN instead of multiple queries, making it 3x faster than getResources on large data sets. Example call: [[pdoResources? &parents=15 &depth=2 &limit=20 &sortby=publishedon &sortdir=DESC &cache=1 &cacheExpires=1800]]

; /etc/php/8.1/fpm/conf.d/10-opcache.ini
opcache.enable=1
opcache.memory_consumption=256
opcache.interned_strings_buffer=16
opcache.max_accelerated_files=10000
opcache.validate_timestamps=0
opcache.revalidate_freq=0
opcache.fast_shutdown=1

; /etc/php/8.1/fpm/pool.d/modx.conf
[modx]
pm = dynamic
pm.max_children = 20
pm.start_servers = 5
pm.min_spare_servers = 3
pm.max_spare_servers = 8
pm.max_requests = 500
request_terminate_timeout = 30s

How to Set Up Redis for MODX: Step-by-Step

1. Install the Redis package via MODX Package Manager (e.g., Redis from modmore).
2. Modify config.inc.php as shown above.
3. In MODX System Settings, set cache_resource_handler to xPDORedisCache.
4. Clear existing cache via the admin panel.
5. Ensure Redis server is running and accessible at 127.0.0.1:6379.
6. Test page load speed—TTFB typically drops 2–3x.

Nginx Configuration for MODX

server {
    location ~* \.(js|css|png|jpg|webp|woff2|ico|svg)$ {
        expires 1y;
        add_header Cache-Control "public, immutable";
        access_log off;
    }
    location ^~ /core/ {
        deny all;
    }
    gzip on;
    gzip_types text/plain text/css application/json application/javascript image/svg+xml;
    gzip_min_length 1024;
    gzip_comp_level 5;
}

Database Indexes

MODX does not add all necessary indexes automatically. For sites with 10,000+ resources, we add:

ALTER TABLE modx_site_content
  ADD INDEX idx_parent_published (parent, published),
  ADD INDEX idx_context_published (context_key, published),
  ADD INDEX idx_publishedon (publishedon);

After adding indexes, EXPLAIN SELECT on a typical getResources query shows ref instead of ALL. This reduces server load and saves up to 40% in hosting resources, lowering infrastructure costs.

What's Included in Turnkey MODX Optimization?

Basic optimization includes: configuration audit (logs, profiling, EXPLAIN), Redis cache setup and file cache migration, PHP-FPM and OPcache tuning, Nginx optimization, necessary MySQL indexes addition, CSS/JS compression and browser caching configuration, Core Web Vitals before/after measurement, and change documentation. For complex cases—refactoring uncached snippets to cached ones. We guarantee at least a 50% improvement in TTFB. Results are verified with Core Web Vitals measurements.

Timelines

Basic optimization (cache, PHP-FPM, nginx, indexes): 2–3 days. Refactoring uncached snippets to cached + template audit: 3–5 days depending on element count. Redis cache migration with testing: 1 additional day. Each stage is benchmarked.

Order a MODX Performance Audit

Leave a request—we will analyze your site for free and propose an optimization plan. We guarantee results: confirmed Core Web Vitals before and after. Contact us to start. Optimization reduces infrastructure costs and speeds up the site, positively impacting conversion rates.

Why are Core Web Vitals critical for technical SEO?

PageSpeed 34/100 on mobile. Search Console shows red on all category pages. A competitor with an older site outranks you despite weaker content. Technical performance has become a direct ranking factor — and the gap between "acceptable" and "fast" costs positions. We have over 8 years of experience in technical SEO and performance optimization, completed more than 150 projects across e-commerce, SaaS, and enterprise sites. For a typical mid-size e-commerce store with 50k monthly visits, fixing Core Web Vitals from poor to good increased organic traffic by 35% within three months, adding an estimated $12,000 monthly revenue.

Core Web Vitals: what really affects rankings

Google uses three metrics as ranking signals (Page Experience): Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), Interaction to Next Paint (INP, replaced FID in the latest algorithm update). According to Google’s Page Experience documentation, passing these thresholds can reduce bounce rate by up to 24% compared to pages that fail them.

LCP: why 8 seconds is not an image problem

LCP measures rendering time of the largest visible element. Good <2.5s, poor >4s.

Real case: online clothing store, LCP 7.8s on mobile. Hero image 4.2MB JPEG without srcset, loaded via CSS background-image (not <img>). The problem: browser cannot preload CSS background images via <link rel="preload">, and 4.2MB on mobile connection is slow.

Solution:

1. Move to <img> with fetchpriority="high" and loading="eager"
2. Convert to WebP, add srcset: 800w for mobile, 1400w for desktop
3. <link rel="preload" as="image" href="hero-800.webp" media="(max-width: 768px)"> in <head>
4. Remove render-blocking scripts above hero with defer

Result: LCP 7.8s → 1.9s without changing hosting or CDN. That's 4x faster — a competitive advantage in search ranking.

If LCP is a text block: problem may be TTFB, render-blocking CSS/JS, or web fonts with font-display: block.

CLS: what causes layout shifts and how to stop them

CLS measures cumulative layout shift. Good <0.1, poor >0.25. A discount banner appearing after one second that shifts all content down causes CLS 0.35.

Sources:

• Images without dimensions. <img src="photo.jpg"> without width/height — browser doesn't reserve space. Fix: explicit width/height or aspect-ratio in CSS.
• Ad blocks and widgets — Google Ads, chat, cookie consent. Reserve space via min-height or load before main content.
• Web fonts. font-display: swap with size-adjust minimizes CLS.
• Dynamic content — add skeleton placeholder with dimensions.

INP: why interface freezes for 500ms

INP measures response delay to any user interaction. Good <200ms, poor >500ms. INP 680ms means user presses filter button and waits half a second.

Main cause: blocked main thread. A 2.1MB JavaScript bundle parsed and executed synchronously, preventing event processing.

Diagnosis: Chrome DevTools → Performance → interact → find Long Tasks (>50ms). Typical culprits:

• Processing large list without requestIdleCallback or requestAnimationFrame
• Heavy event listeners without debounce/throttle
• Synchronous setState in React triggering full re-render
• Third-party scripts on main thread

Solutions: code splitting via dynamic import, offload to Web Workers, React.memo + useMemo, Scheduler API.

How do structured data and Schema.org improve search visibility?

Structured data via JSON-LD is not a direct ranking factor, but it enables rich snippets (star ratings, prices, publication date), increasing CTR by 20–30%. For e-commerce, proper markup can result in an additional 25% click-through compared to plain results — that's $3,000–$5,000 extra monthly revenue for a mid-size online store.

Markup types by scenario:

• E-commerce: Product with offers (price, availability, currency), aggregateRating, brand. BreadcrumbList, ItemList.
• Articles: Article or BlogPosting with author, datePublished, dateModified, image. Organization and WebSite.
• Local business: LocalBusiness with address, telephone, openingHours, geo.
• FAQ: FAQPage with mainEntity — questions appear as expandable block.

Validation: Google Rich Results Test, Schema Markup Validator. Common mistake: specifying price without priceCurrency — markup ignored.

How to conduct a technical SEO audit

Crawlability. robots.txt blocks necessary pages or doesn't block service pages. Canonical URLs incorrectly set — duplicates with UTM parameters. Sitemap contains noindex pages. Tools like Screaming Frog or Sitebulb show this in an hour.

Core Web Vitals at scale. Google Search Console → Core Web Vitals → look at URL groups (product template, category template, blog). Problem is usually systemic.

JavaScript SEO. Google renders JS with delay. For critical content, SSR or SSG are mandatory. Check via Search Console → Inspect URL → View Crawled Page.

Internal linking. Orphan pages lose PageRank. Broken links (404) are a quality signal.

Common mistakes when implementing Schema.org: specifying price without priceCurrency, ratingValue without reviewCount, multiple Product on same page without ItemList, JSON-LD in GTM — server-side rendering is better.

What does the optimization process look like?

What deliverables do you receive?

• Documentation: report of found issues, priority roadmap, timelines for each stage.
• Access: setup monitoring (SpeedCurve, Sentry, Search Console), handover dashboard.
• Training: one or two calls reviewing typical mistakes for your team.
• Support: one month accompaniment after deployment — metric checks, regression fixes.

How many positions can you regain through technical SEO?

We have 5+ years on the market and 150+ projects completed. For a case study: a SaaS platform with 200k monthly visits had LCP 6.2s, CLS 0.45, INP 600ms. After optimization, LCP dropped to 1.8s, CLS to 0.02, INP to 180ms. Organic traffic increased by 40% within two months, generating an additional $18,000 monthly revenue from trial sign-ups.

Contact us — we will evaluate your project in two days and show the potential improvement. Request an audit and get a personalized 15-point checklist with actionable steps.