Y

YOGI’S VPS

MANAGED WORDPRESS
INFRASTRUCTURE

WordPress Infrastructure Review

One Page Snapshot

ESP32S

esp32s.com

Prepared by:Brandon CopelandWordPress Infrastructure Lead
QCK SEO

Date:August 8, 2026

Overall Infrastructure Health

76 / 100

ESP32S has a modern WooCommerce storefront with strong lab performance,
excellent SEO fundamentals and a relatively lightweight network payload.
The largest opportunity is not a full rebuild—it is correcting the slow
real-world server response, optimizing how above-the-fold product imagery
is loaded, and cleaning up several accessibility and frontend code issues.

⌁

Infrastructure Scorecard

▦

Infrastructure

★★★★☆

8/10

WooCommerce, WoodMart, Elementor, Perfmatters and Cloudflare

◴

Performance

★★★★☆

8/10

88 mobile PSI, but real-user Core Web Vitals currently fail

⬟

Security

★★★☆☆

6/10

HTTPS present, but CSP, HSTS and frame protections need work

🛒

WooCommerce

★★★★☆

8/10

Modern catalog, strong PDP structure and multiple payment options

⌕

SEO Foundation

★★★★★

10/10

Perfect Lighthouse SEO score

♿

Accessibility

★★★★☆

7/10

86 score with contrast, touch target and link-label issues

Top 3 Opportunities

1

Improve Real-World Server Response

The lab test is strong, but actual mobile users are seeing a 2.5-second
TTFB and 3.1-second LCP, causing Core Web Vitals to fail. That gap suggests
the site is capable of loading quickly once resources arrive, but the
initial response experienced by real visitors needs attention.

2

Fix LCP Product Image Loading

The product image identified as the Largest Contentful Paint element
is being lazy-loaded. Lighthouse measured more than 3.2 seconds of
resource-load delay before that image begins loading. Excluding the
first visible product images from lazy loading and adding high fetch
priority should improve perceived speed.

3

Clean Up Accessibility & Frontend Errors

Product cards have undersized touch targets, low-contrast text and
image links without discernible names. The site also logs WoodMart
JavaScript errors related to an undefined theme module. These are
contained fixes that can improve usability and frontend reliability.

Things We Like

✓Strong mobile Lighthouse performance score of 88
✓Perfect Lighthouse SEO score
✓Very low 0 ms Total Blocking Time
✓Minimal 0.001 lab layout shift
✓Modern WooCommerce product and checkout experience

Potential Business Impact

⚡Faster initial load for real mobile shoppers
↗Lower abandonment before products become visible
▥Better product-card accessibility
⬟More reliable WooCommerce interactions
✓Stronger conversion from existing organic traffic

PageSpeed Insights Mobile

88
/100
Mobile PSI

Real-User LCP

3.1s

Needs Improvement

Lighthouse itself performs well with a 3.0-second LCP, 1.8-second FCP,
0 ms Total Blocking Time and only 526 KiB transferred. The concern is
the real-user dataset, where TTFB reaches 2.5 seconds and LCP reaches
3.1 seconds, causing the Core Web Vitals assessment to fail.

☷

Recommended Next Step

Schedule a complimentary 30-minute Infrastructure Review.

I’ll walk through:

Why real-user TTFB is significantly slower than the lab test
How Perfmatters lazy loading is delaying the LCP product image
Which WoodMart and Elementor assets can be cleaned up
Which accessibility and security fixes should be prioritized first

No obligation.

☆

If I Could Only Fix One Thing…

I’d start here:

Fix the real-user TTFB and above-the-fold image loading sequence.

Reason:
The frontend is already relatively efficient—only 526 KiB transferred
and 0 ms blocking time in the Lighthouse run. The biggest opportunity
is getting the initial document and first visible product imagery to
visitors sooner. That directly addresses the current Core Web Vitals
failure without requiring a redesign.