WordPress Performance Audit: Diagnosis and Optimization Plan

A client launched an e-commerce site on WordPress with the Avada theme and 50+ plugins. Google PageSpeed shows TTFB of 1.2 seconds and LCP of 6 seconds. Users complain about slow loading, conversion dropped by 20%. We conducted a WordPress performance audit and found: wp_options autoload is overloaded (3 MB of data), MySQL lacks indexes on the postmeta table, and OPcache is disabled. We fixed it in 2 days — load time dropped to 1.5 seconds, conversion recovered. Only measurement gives the right vector for optimization.

A WordPress performance audit is a comprehensive diagnosis of both server-side and client-side parts. We check PHP configuration (OPcache, memory limit), MySQL (indexes, slow queries), caching (page cache, object cache), frontend (CSS/JS bundles, images), and web server configuration (HTTP/2, brotli). Without such an audit, optimization at random can worsen the situation by adding new problems. Based on the results, we create a plan with priorities and precise instructions.

Why Optimization Without an Audit Is Ineffective

Many try to speed up a site blindly: enable plugins, compress images, switch hosting. Without accurate data, it's shooting in the dark. An audit reveals exactly what slows down: the server, database, plugins, or frontend. We started with a project that loaded in 8 seconds. After the audit, we found wp_options autoload overloaded, MySQL without indexes, and OPcache disabled. We fixed it in 2 days — load time dropped to 1.5 seconds. Only measurement gives the right vector.

What Tools We Use

External (simulate the user):

• Google PageSpeed Insights — Core Web Vitals assessment, recommendations
• GTmetrix — waterfall chart, filmstrip, test regions
• WebPageTest — detailed HAR, video capture, testing from different locations
• Lighthouse CLI — run from command line for automation

Internal (server side):

• Query Monitor — plugin for SQL queries, hooks, PHP time
• New Relic APM — PHP profiler
• Blackfire — detailed function profiling

Note: For reproducible results, use Lighthouse CLI with the --headless flag. Redis cache is 5 times more efficient than file-based cache.

How We Measure Metrics

Measure baseline metrics before optimization:

# Lighthouse CLI
npx lighthouse https://yourdomain.com \
    --output json \
    --output-path ./audit-before.json \
    --chrome-flags="--headless"

# TTFB via curl
curl -o /dev/null -s -w "TTFB: %{time_starttransfer}s\nTotal: %{time_total}s\n" \
    https://yourdomain.com

Analyze server time with Query Monitor: install the plugin, open any page, check Total query time (target < 50 ms), Number of queries (target < 30), slow queries (> 5 ms each), duplicate queries.

Analyze PHP and MySQL: enable slow log for PHP-FPM and slow query log for MySQL.

# Enable PHP-FPM slow log
; /etc/php/8.3/fpm/pool.d/www.conf
slowlog = /var/log/php-fpm-slow.log
request_slowlog_timeout = 2s

-- Enable slow query log
SET GLOBAL slow_query_log = ON;
SET GLOBAL long_query_time = 0.5;
SET GLOBAL slow_query_log_file = '/var/log/mysql/slow.log';

-- Analyze with mysqldumpslow
mysqldumpslow -s t -t 10 /var/log/mysql/slow.log

What Is TTFB and How to Improve It

TTFB is time to first byte. If it is > 200 ms, the server or DB is slow. Main causes: no OPcache, no page cache, slow hosting. We enable OPcache, set up Redis, implement FastCGI cache — TTFB drops to 50–100 ms.

Typical Problems and Their Impact

Core Web Vitals: Target Values

According to Google Search Central, these metrics are key for ranking. LCP (Largest Contentful Paint) should be under 2.5 seconds. LCP is a critical speed metric.

Step-by-Step Audit Plan

1. Gather metrics using Lighthouse CLI, PageSpeed Insights, and WebPageTest.
2. Analyze server side with Query Monitor, slow logs, and PHP profiler.
3. Identify bottlenecks: slow queries, cache configuration, heavy plugins.
4. Create a report with priorities and concrete instructions for each issue.
5. Test fixes and re-measure to confirm improvements.

What's Included in the Report

• Measured metrics before optimization
• List of issues with priorities (critical, important, improvements)
• Specific recommendations for each issue (with code or settings)
• Projected result after fixes (expected load time reduction)
• Documentation of results, access (if needed), maintenance recommendations

Timeline and Pricing

A WordPress performance audit with a report and recommendations takes 1–2 days. Pricing is calculated individually based on complexity and scope. After optimization, clients save up to 30% on hosting and support. Get a consultation or order an audit — we will help improve your site's performance.

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.