matomo-org / matomo-org/matomo-for-wordpress
Some Matomo options are autoloaded when they should not, and it increases the plugin performance footprint
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 145
- Forks
- 35
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 6
Description
Autoloaded options are loaded on every page.
Here's an example of our keys which are loaded on every page:
select option_name from wp_options where autoload = 'yes' and option_name like '%matomo%;
Some of them should not be loaded on every page. We should review which options are autoloaded to reduce our plugin performance footprint.
Some others plugins examples which have the same problem:
https://wordpress.org/support/topic/auto_load-set-to-yes/
It should be related to the update_option method.
One of our users complained about it.
https://secure.helpscout.net/conversation/2070076335/3051962?folderId=4753515
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the update_option entry point and inspect the Matomo-related entries returned by the wp_options query. Determine which options need not be autoloaded, then verify that the selected options no longer contribute to the plugin's every-page performance footprint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100