Benchmarks
Plugin footprint 40% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
It is recommended to fix the following installer errors
- The plugin did not install without errors
- > Warning in wp-admin/includes/plugin.php+294
opendir(wp-content/plugins/woocommerce): failed to open dir: No such file or directory
Server metrics [RAM: ▼1.33MB] [CPU: ▼45.09ms] Passed 4 tests
This is a short check of server-side resources used by Taager
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.66 ▼0.80 | 8.26 ▼28.81 |
| Dashboard /wp-admin | 2.68 ▼0.62 | 11.71 ▼37.63 |
| Posts /wp-admin/edit.php | 2.68 ▼0.68 | 12.04 ▼37.67 |
| Add New Post /wp-admin/post-new.php | 2.68 ▼3.21 | 11.68 ▼76.24 |
| Media Library /wp-admin/upload.php | 2.68 ▼0.55 | 10.18 ▼25.96 |
Server storage [IO: ▲5.70MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 170 new files
Database: 2 new tables, 13 new options
| New tables |
|---|
| wp_taager_provinces |
| wp_taager_zones |
| New WordPress options |
|---|
| theysaidso_admin_options |
| can_compress_scripts |
| widget_theysaidso_widget |
| ta_plugin_version |
| ta_product_import_status |
| ta_products_last_updated_date |
| ta_last_category_filter |
| widget_recent-comments |
| ta_last_name_filter |
| widget_recent-posts |
| ... |
Browser metrics Passed 4 tests
Taager: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,894 ▲132 | 13.44 ▼0.99 | 8.84 ▲7.28 | 35.99 ▼4.61 |
| Dashboard /wp-admin | 2,216 ▲39 | 5.65 ▲0.02 | 97.53 ▲0.43 | 46.11 ▲1.23 |
| Posts /wp-admin/edit.php | 2,121 ▲18 | 2.06 ▲0.07 | 40.28 ▲2.34 | 39.10 ▲3.59 |
| Add New Post /wp-admin/post-new.php | 1,545 ▲19 | 23.29 ▼0.30 | 621.55 ▲18.42 | 51.07 ▲5.97 |
| Media Library /wp-admin/upload.php | 1,424 ▲24 | 4.29 ▲0.16 | 98.56 ▲2.33 | 44.07 ▲1.76 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the following
- Uninstall procedure had uncaught errors
- > Warning in wp-admin/includes/plugin.php+294
opendir(wp-content/plugins/woocommerce): failed to open dir: No such file or directory
- Zombie WordPress options detected upon uninstall: 9 options
- ta_plugin_version
- import_gallery_lists
- widget_theysaidso_widget
- widget_recent-posts
- widget_recent-comments
- ta_products_last_updated_date
- theysaidso_admin_options
- db_upgraded
- can_compress_scripts
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Everything seems fine, however this is by no means an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
The following issues need your attention
- 2× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/taager/includes/mixpanel-php/examples/error_handling.php
- > /wp-content/plugins/taager/includes/mixpanel-php/examples/custom_consumer.php
- 129× PHP files trigger server errors when accessed directly (only 10 are shown):
- > [ Base_MixpanelBase - line 158 ]
Opening socket connection to tcp://api.mixpanel.com:80
- > [ Base_MixpanelBase - line 123 ]
Batch consumption failed!
- > [ Base_MixpanelBase - line 128 ]
added batch back to queue, queue size is now 1
- > [ Base_MixpanelBase - line 135 ]
Batch of 1 consumed, queue size is now 1
- > [ Base_MixpanelBase - line 196 ]
Queued message: {"event":"test_event","properties":{"mp_lib":"php","color":"blue","token":"MIXPANEL_PROJECT_TOKEN","time":1700891146}}
- > [ Base_MixpanelBase - line 135 ]
Batch of 2 consumed, queue size is now 0
- > [ Base_MixpanelBase - line 76 ]
Using token: MIXPANEL_PROJECT_TOKEN
- > [ Base_MixpanelBase - line 135 ]
Batch of 1 consumed, queue size is now 1
- > [ Base_MixpanelBase - line 135 ]
Batch of 1 consumed, queue size is now 1
- > [ Base_MixpanelBase - line 113 ]
Flush called - queue size: 2
- > [ Base_MixpanelBase - line 158 ]
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
Attributes that require attention:
- Screenshots: These screenshots require images: #1 (User login), #2 (Country selection page), #3 (Account page), #4 (Importing products from Taager), #5 (Importing products success), #6 (Imported product), #7 (Updating shipping costs)
taager/taager.php 92% from 13 tests
The principal PHP file in "Taager" v. 1.16.0 is loaded by WordPress automatically on each request
Please take the time to fix the following:
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Good job! No executable or dangerous file extensions detected19,501 lines of code in 113 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| HTML | 24 | 1,633 | 168 | 10,659 |
| PHP | 49 | 911 | 978 | 3,862 |
| CSS | 8 | 122 | 24 | 1,965 |
| JavaScript | 15 | 328 | 489 | 1,682 |
| SVG | 12 | 4 | 24 | 1,006 |
| PO File | 1 | 70 | 69 | 155 |
| Markdown | 1 | 29 | 0 | 104 |
| JSON | 1 | 0 | 0 | 29 |
| XML | 1 | 3 | 0 | 26 |
| YAML | 1 | 3 | 0 | 13 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.26 |
| Average class complexity | 5.59 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 35.00 |
| Average method complexity | 1.73 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 16.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 22 | |
| ▷ Abstract classes | 2 | 9.09% |
| ▷ Concrete classes | 20 | 90.91% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 142 | |
| ▷ Static methods | 1 | 0.70% |
| ▷ Public methods | 112 | 78.87% |
| ▷ Protected methods | 24 | 16.90% |
| ▷ Private methods | 6 | 4.23% |
| Functions | 114 | |
| ▷ Named functions | 113 | 99.12% |
| ▷ Anonymous functions | 1 | 0.88% |
| Constants | 16 | |
| ▷ Global constants | 16 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
20 PNG files occupy 3.08MB with 1.82MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/screenshot-6.png | 1,421.62KB | 278.43KB | ▼ 80.41% |
| includes/mixpanel-php/docs/images/apple-touch-icon-72x72.png | 12.45KB | 5.26KB | ▼ 57.74% |
| includes/mixpanel-php/docs/images/iviewer/iviewer.zoom_zero.png | 1.07KB | 0.14KB | ▼ 87.17% |
| assets/screenshot-2.png | 188.69KB | 54.12KB | ▼ 71.32% |
| includes/mixpanel-php/docs/images/iviewer/iviewer.rotate_right.png | 1.45KB | 1.46KB | 0.00% |