MODX pdoTools Configuration and Site Optimization

MODX pdoTools Configuration and Site Optimization

We configure pdoTools for MODX websites, replacing standard snippets with high-performance alternatives to reduce page generation time from seconds to milliseconds. Our team installs, configures, and tunes pdoResources, pdoMenu, pdoPage, pdoParser, and related tools, delivering measurable speed improvements on sites of any size. We have optimized 10+ MODX sites and regularly cut page generation time by 85 to 95 percent. Clients see lower server costs and better Core Web Vitals scores immediately after deployment.

Standard MODX snippets such as getResources and Wayfinder use the xPDO ORM layer, which generates many small database queries per page. On a page with 20 resources and a navigation menu, this can mean 50 to 100 database queries. pdoTools replaces these with optimized PDO-based queries, typically reducing query count by 90 percent.

What's Included in Our pdoTools Optimization Setup

We deliver pdoTools configuration as a turnkey service. The scope covers:

• Install pdoTools via MODX Package Manager
• Replace standard getResources, getPage, and Wayfinder calls with pdoResources, pdoPage, and pdoMenu
• Configure TV loading via &prepareTVs=1 to replace N+1 queries with single JOIN queries
• Enable per-component caching with unique cache keys that include filter parameters
• Set up pdoParser to replace the standard MODX parser for 20–40% faster tag processing
• Configure pdoSitemap for fast sitemap generation on large sites
• Profile before-and-after performance to document the improvement

How Does pdoTools Speed Up MODX?

Standard getResources makes one database query per resource to load TV values. A list of 20 products with 3 TVs each means 60 additional queries just for TV data. pdoResources loads all TV values with a single JOIN query regardless of list size.

pdoMenu handles navigation even more efficiently. The full site navigation tree, including active state detection and class assignments, loads in one or two queries instead of the recursive queries that Wayfinder generates.

After switching a typical 50-page MODX site from standard snippets to pdoTools, our clients see page generation times drop from 800–1500ms to 80–200ms. For sites with heavy traffic this translates directly to lower server costs and better Core Web Vitals scores.

pdoResources Configuration

[[pdoResources?
    &parents=`5`
    &resources=`-10`
    &showHidden=`0`
    &sortby=`menuindex`
    &sortdir=`ASC`
    &limit=`10`
    &includeTVs=`product_price,product_image`
    &prepareTVs=`1`
    &processTVs=`1`
    &tpl=`productCard`
    &tvPrefix=``
    &cache=`1`
    &cacheTime=`1800`
]]

The &prepareTVs=1 parameter loads all TV values with a single JOIN query. The &cache=1 and &cacheTime=1800 parameters cache the rendered output for 30 minutes, bypassing database queries entirely on cached requests.

pdoPage for Pagination

[[!pdoPage?
    &element=`pdoResources`
    &parents=`5`
    &limit=`12`
    &tpl=`productCard`
    &includeTVs=`product_price,product_image`
    &pageNavVar=`page.nav`
    &cacheKey=`catalog_[[+GET.page:default=1]]`
]]
[[!+page.nav]]

pdoPage generates pagination navigation automatically and handles the page GET parameter. The cache key includes the current page number so each pagination page has its own cache entry.

pdoMenu for Site Navigation

[[pdoMenu?
    &startId=`0`
    &level=`2`
    &sortby=`menuindex`
    &tplOuter=`@INLINE <ul class="nav">[[+wrapper]]</ul>`
    &tpl=`@INLINE <li class="[[+classes]]"><a href="[[+link]]">[[+menutitle]]</a>[[+wrapper]]</li>`
    &tplInner=`@INLINE <ul class="nav__sub">[[+wrapper]]</ul>`
    &hereClass=`active`
    &parentClass=`has-children`
    &cache=`1`
    &cacheTime=`3600`
]]

Menu caching is critical. Navigation is among the most expensive MODX queries, as it must traverse the resource tree on every page. With &cache=1 and &cacheTime=3600, the menu HTML renders once per hour per cache variation.

How Is pdoTools Optimization Delivered?

1. Profile the current site with a baseline measurement of queries per page and page generation time
2. Identify the highest-impact snippet replacements
3. Replace standard snippets with pdoTools equivalents, one template at a time
4. Verify template rendering matches the original output
5. Enable caching and verify cache key uniqueness for filtered views

Our team has experience with 10+ MODX projects across e-commerce, news portals, and corporate sites. Contact us to discuss your site structure, and we will estimate the potential performance gain before starting work.

How We Deliver

We start with a baseline profile. We identify the slowest page loads. We prioritize by impact. We replace snippets one at a time. We verify output matches the original. We enable caching. We confirm the new baseline. We document all changes for your team.

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.