The WooCommerce REST API is increasingly used for headless storefronts (React, Next.js, Vue), mobile apps, and third-party integrations like ERP and POS systems. But out of the box, API performance is significantly worse than frontend page loads.
Default API authentication adds overhead to every request.
Frequently Asked Questions
Why is the WooCommerce REST API slow by default?
The WooCommerce REST API has several default performance issues: OAuth 1.0a authentication adds 50-100ms per request for signature verification and nonce checking, API responses include all available fields even when only a subset is needed (over-fetching), no server-level response caching is configured out of the box, and database queries are not optimised for the bulk data patterns typical of API consumers (mobile apps, headless frontends, ERP integrations). For a headless storefront making 10-20 API calls per page, the cumulative overhead can add 1-3 seconds to page generation time.
How do I improve WooCommerce REST API performance?
Key optimisations: use JWT authentication instead of OAuth 1.0a (reduces per-request overhead to near zero), implement server-side response caching for product catalogue endpoints that change infrequently (category listings, product details), use the _fields parameter to request only the specific fields your application needs, implement pagination with controlled page sizes rather than fetching all products in one request, and consider Redis-based API response caching at the application level for read-heavy endpoints. Ensure your hosting provides sufficient PHP workers for concurrent API consumers alongside regular visitor traffic.
Can WooCommerce REST API responses be cached?
Product catalogue endpoints can be cached — product listings, individual product details, and category trees change only when products are updated. Implement object-level caching via Redis with cache invalidation triggered on product save/update hooks. Cart, order, and customer endpoints must never be cached — they contain user-specific data that changes on every interaction. For headless storefronts, consider a dedicated caching layer between your frontend application and the WooCommerce API that caches catalogue responses with appropriate TTLs and invalidation logic.
What is the difference between WooCommerce REST API and GraphQL for headless stores?
The WooCommerce REST API is the built-in option requiring no additional setup, with full documentation and broad tool support. It over-fetches data by default (returns all fields even when only a few are needed), increasing payload size and parse time. GraphQL (via WPGraphQL with WooCommerce extension) allows precise field selection per query, reducing payload size by 40-70% for typical use cases and eliminating multiple API calls through query composition. GraphQL adds implementation complexity but is the better performance choice for headless WooCommerce with complex data requirements.
How does hosting affect WooCommerce REST API performance?
API performance is entirely server-side — unlike page loads, API responses receive no benefit from page caching. Every API request hits PHP and the database directly. Hosting factors that directly affect API performance: PHP worker count (concurrent API consumers from mobile apps, headless frontends, and integrations share workers with regular visitor traffic), CPU speed (authentication processing, query execution, JSON serialisation are all CPU-bound), Redis availability (object caching for product data reduces database load for product catalogue queries), and NVMe storage speed (order and customer data queries benefit from fast storage I/O).
OAuth 1.0a signature verification and nonce checking add 50-100ms per request. For a headless storefront making 10-20 API calls per page, that’s 500-2000ms of authentication overhead alone.
API responses
Uncached by default because WordPress marks REST API responses as dynamic. This means every API request executes the full WordPress bootstrap, runs all relevant queries, and generates a fresh response — even for data that hasn’t changed in hours.
Response payload size
Another issue. The default product endpoint returns every field for every product, even if the client only needs name, price, and image. A product listing API call might return 500KB of JSON when 50KB would suffice.
WP Pro Host optimises WooCommerce API performance with: application-key authentication that bypasses OAuth overhead, intelligent API response caching with automatic invalidation on data changes, Nginx-level response compression, and guidance on implementing GraphQL for payload-efficient queries.