WooCommerce Analytics: Add proxy speed module to enhance proxy API performance

[chihsuan]

Related to pfKYZu-2Yt-p2#comment-3041

Proposed changes

This PR introduces a proxy speed module that inspired by Plausible's proxy speed module for WooCommerce Analytics to enhance the proxy API performance.

The module is placed in the mu-plugins directory to prevent unnecessary plugins from being loaded during proxy requests, thereby improving performance.

Other information

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

n/a

Does this pull request change what data or activity we track or use?

n/a

Testing instructions

Confirm proxy speed module is added/removed as Jetpack is activated/deactivated

1. Set up a WordPress site with both Jetpack and WooCommerce installed.
2. Check out and activate this branch of Jetpack.
3. If you have the local WooCommerce Analytics plugin activated, deactivate it. We will add similar logic in Woo Analytics so that the proxy speed module is added/removed as Woo Analytics is activated/deactivated.
4. Deactivate Jetpack. Then, verify that the file wp-content/mu-plugins/woocommerce-analytics-proxy-speed-module.php does not exist.
5. Activate Jetpack. Then, verify that the file wp-content/mu-plugins/woocommerce-analytics-proxy-speed-module.php does exist.
6. (Optional) Repeat steps 4 and 5 to confirm the file is created/removed as Jetpack is activated/deactivated.

Test REST API request

1. Install Code Snippets plugin
2. Add the following code snippet to the site:

function test_add_rest_api( ) {
 error_log( 'test_add_rest_api is called' );
}

add_action( 'rest_api_init', 'test_add_rest_api' );

3. Test request to the cart API:

curl https://your-site.com/wp-json/wc/store/v1/cart

6. Confirm that the test_add_rest_api function is called is logged in the wp-content/debug.log file.
7. Test request to the proxy API

curl -X POST https://your-site.com/wp-json/woocommerce-analytics/v1/track \
  -H "Content-Type: application/json" \
  -d '{
    "event_name": "page_view"
  }'

8. Confirm that the test_add_rest_api function is not called.

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack), and enable the add/wca-proxy-speed-module branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack add/wca-proxy-speed-module

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  
• ✅ Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
3. You can use GitHub's Reviewers functionality to request a review.
4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

---

Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

• WordPress.com Simple releases happen as soon as you deploy your changes after merging this PR (PCYsg-Jjm-p2).
• WoA releases happen weekly.
• Releases to self-hosted sites happen monthly:
  • Scheduled release: October 7, 2025
  • Code freeze: October 6, 2025

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

[jp-launch-control]

Code Coverage Summary

Coverage changed in 2 files.

File	Coverage	Δ%	Δ Uncovered
projects/packages/woocommerce-analytics/src/class-woocommerce-analytics.php	0/59 (0.00%)	0.00%	20 💔
projects/plugins/jetpack/class.jetpack.php	715/2265 (31.57%)	0.12%	0 💚

1 file is newly checked for coverage.

File	Coverage
projects/packages/woocommerce-analytics/src/mu-plugin/woocommerce-analytics-proxy-speed-module.php	0/13 (0.00%) 💔

Full summary · PHP report · JS report

_{If appropriate, add one of these labels to override the failing coverage check: Covered by non-unit tests Use to ignore the Code coverage requirement check when E2Es or other non-unit tests cover the code Coverage tests to be added later Use to ignore the Code coverage requirement check when tests will be added in a follow-up PR I don't care about code coverage for this PR Use this label to ignore the check for insufficient code coveage.}

[Copilot]

Pull Request Overview

This PR introduces a proxy speed module for WooCommerce Analytics to enhance proxy API performance by selectively loading only necessary plugins during proxy requests. The module is inspired by Plausible's implementation and is placed in the mu-plugins directory to prevent unnecessary plugins from being loaded.

Key changes:

• Adds a proxy speed module that filters active plugins for WooCommerce Analytics proxy requests
• Integrates module installation/removal with Jetpack plugin activation/deactivation lifecycle
• Implements file management methods to copy the module to mu-plugins directory and clean up on deactivation

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.

File	Description
class.jetpack.php	Integrates proxy speed module lifecycle with Jetpack activation/deactivation
woocommerce-analytics-proxy-speed-module.php	Core proxy speed module that filters active plugins for performance
class-woocommerce-analytics.php	Adds methods to manage proxy speed module installation and removal
changelog files	Documents the feature addition

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[louwie17]

This looks good and tested well!
Would appreciate a review from @kangzj still given it was his original suggestion, and he said in the P2 comment "We’ll need input and assistance from the ops team for this approach", meaning we should loop in ops for this review as well? or is that a follow up?

[chihsuan]

Would appreciate a review from @kangzj still given it was his original suggestion, and he said in the P2 comment "We’ll need input and assistance from the ops team for this approach", meaning we should loop in ops for this review as well? or is that a follow up?

If I understand correctly, @kangzj suggested that for "CIAB sites," we could work with the ops team to set up a direct proxy at the web server level for optimal performance. This remains a viable option, though it would require some additional effort to implement. However, I think it's nice to have a choice, especially now that we've also added the proxy API with the proxy speed module.

I'd also appreciate a review or feedback from @kangzj. 🙏

[kangzj]

LGTM! You rock 🎸