AirLift Performance

Making WordPress fast for everyone

[AirLift Performance @airliftoff]

HPOS changes where WooCommerce order data is authoritative.

Before enabling it, check extension support, allow synchronisation to finish, and verify old and new orders.

Treating HPOS as a universal speed switch is a good way to turn performance work into recovery work.

[AirLift Performance @airliftoff]

A slow checkout request may be waiting on a server you do not control: shipping, tax, payment, fraud checks or another API.

Which external service has caused the hardest WooCommerce delay you have had to diagnose?

[AirLift Performance @airliftoff]

Page cache can serve a finished public page.

Logged-in pages, filters, admin screens and personalised requests still need WordPress to build a response. That is where object caching may reduce repeated database work.

Different cache. Different job.

[AirLift Performance @airliftoff]

Increasing PHP memory may prevent a crash. It does not create another PHP worker.

If requests are queuing, ask about worker usage, CPU, database time and request duration.

A larger ceiling does not make slow work finish faster.

[AirLift Performance @airliftoff]

A WooCommerce store can feel fast while its operations run late.

Action Scheduler handles background work like emails, stock updates and service notifications. If that queue grows, the storefront may stay green while the business falls behind.

Performance has a backstage.

[AirLift Performance @airliftoff]

A fast WooCommerce homepage can hide a slow store.

Search, filters, product variations, cart updates and checkout all do different work.

If you test only the homepage, you’re measuring the easiest part of the buying journey and calling the whole shop fast.

[AirLift Performance @airliftoff]

Compressing a 4000px image doesn’t make it the right image for a 400px space.

The visitor still downloads far more pixels than the design can show.

Good image optimisation asks:

How heavy is the file?
How large does it actually need to be?

[AirLift Performance @airliftoff]

Changed the logo. Cleared the WordPress cache. Old logo still showing.

That doesn’t automatically mean the plugin failed.

The browser or CDN may still have its own cached copy.

A WordPress page can be remembered in more places than the dashboard can clear.

[AirLift Performance @airliftoff]

A fast page with a dead hamburger menu isn’t fast.

When delayed JavaScript leaves the button visible before the menu code is ready, Airlift provides an immediate fallback—then hands control back once the original script loads.

Visitors tap. The menu opens. As it should.

[AirLift Performance @airliftoff]

Lazy loading every image can make the most important image arrive late.

Your logo or hero image may be needed immediately. Delaying it forces the browser to wait for something already visible.

Lazy loading is for what’s further down the page-not everything with an image tag.

[AirLift Performance @airliftoff]

Sites are getting faster consistently. We will be getting more folks onboard soon.