Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.00MB] [CPU: ▼5.93ms] Passed 4 tests
Analyzing server-side resources used by FetchApp
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 37.61 ▲0.95 |
Dashboard /wp-admin | 3.31 ▲0.00 | 44.61 ▼9.74 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 43.23 ▼8.38 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 80.00 ▼6.54 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 37.17 ▲1.22 |
Server storage [IO: ▲0.17MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 32 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
widget_recent-posts |
can_compress_scripts |
theysaidso_admin_options |
widget_recent-comments |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
An overview of browser requirements for FetchApp
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,789 ▲28 | 14.21 ▼0.20 | 1.62 ▼0.02 | 38.89 ▼1.26 |
Dashboard /wp-admin | 2,198 ▲30 | 5.62 ▲0.10 | 81.44 ▼11.63 | 38.24 ▼1.97 |
Posts /wp-admin/edit.php | 2,100 ▼0 | 2.00 ▲0.02 | 34.54 ▼0.37 | 30.16 ▼7.72 |
Add New Post /wp-admin/post-new.php | 1,526 ▼3 | 24.00 ▲0.86 | 637.74 ▼64.64 | 54.60 ▲4.25 |
Media Library /wp-admin/upload.php | 1,403 ▲3 | 4.23 ▲0.07 | 98.36 ▲3.21 | 41.72 ▼0.05 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
The following items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_theysaidso_widget
- db_upgraded
- widget_recent-comments
- can_compress_scripts
- widget_recent-posts
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please fix the following
- 15× PHP files trigger server-side errors or warnings when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'FetchApp\\Tests\\FetchAppBaseTest' not found in wp-content/plugins/fetchapp-for-woocommerce/libraries/fetchapp-php-2.0/tests/ProductTest.php:11
- > PHP Warning
include_once(): Failed opening 'EnumEmulator.class.php' for inclusion (include_path='.:/usr/share/php') in wp-content/plugins/fetchapp-for-woocommerce/libraries/fetchapp-php-2.0/src/FetchApp/API/FileType.php on line 13
- > PHP Fatal error
Uncaught Error: Class 'PHPUnit\\Framework\\TestCase' not found in wp-content/plugins/fetchapp-for-woocommerce/libraries/fetchapp-php-2.0/tests/FetchAppBaseTest.php:14
- > PHP Warning
include_once(EnumEmulator.class.php): failed to open stream: No such file or directory in wp-content/plugins/fetchapp-for-woocommerce/libraries/fetchapp-php-2.0/src/FetchApp/API/FileType.php on line 13
- > PHP Fatal error
Uncaught Error: Class 'FetchApp\\Tests\\FetchAppBaseTest' not found in wp-content/plugins/fetchapp-for-woocommerce/libraries/fetchapp-php-2.0/tests/OrderItemTest.php:10
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/fetchapp-for-woocommerce/zz_fetchappwp_carts/wc_fetchapp.class.php:13
- > PHP Fatal error
Uncaught Error: Class 'FetchApp\\API\\EnumEmulator' not found in wp-content/plugins/fetchapp-for-woocommerce/libraries/fetchapp-php-2.0/src/FetchApp/API/OrderStatus.php:15
- > PHP Fatal error
Uncaught Error: Class 'FetchApp\\Tests\\FetchAppBaseTest' not found in wp-content/plugins/fetchapp-for-woocommerce/libraries/fetchapp-php-2.0/tests/AccountTest.php:8
- > PHP Fatal error
Uncaught Error: Call to undefined function apply_filters() in wp-content/plugins/fetchapp-for-woocommerce/fetchapp.php:13
- > PHP Fatal error
Uncaught Error: Class 'FetchApp\\Tests\\FetchAppBaseTest' not found in wp-content/plugins/fetchapp-for-woocommerce/libraries/fetchapp-php-2.0/tests/APITest.php:7
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
These attributes need to be fixed:
- Plugin Name: You should set the name of your plugin on the first line (
=== fetchapp-for-woocommerce ===
)
fetchapp-for-woocommerce/fetchapp.php 92% from 13 tests
This is the main PHP file of "FetchApp" version 1.9.2, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("fetchapp-for-woocommerce.php" instead of "fetchapp.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
Good job! No executable or dangerous file extensions detected3,953 lines of code in 28 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 25 | 962 | 1,311 | 3,270 |
Markdown | 2 | 133 | 0 | 651 |
JSON | 1 | 0 | 0 | 32 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.16 |
Average class complexity | 12.71 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 93.00 |
Average method complexity | 1.86 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 29.00 |
Code structure | ||
---|---|---|
Namespaces | 2 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 24 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 24 | 100.00% |
▷ Final classes | 7 | 29.17% |
Methods | 325 | |
▷ Static methods | 19 | 5.85% |
▷ Public methods | 325 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 1 | |
▷ Named functions | 1 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 18 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 18 | 100.00% |
▷ Public constants | 18 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
1 PNG file occupies 0.00MB with 0.00MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/logo.png | 2.24KB | 0.76KB | ▼ 65.98% |