Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.05MB] [CPU: ▼3.72ms] Passed 4 tests
This is a short check of server-side resources used by Automater
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.54 ▲0.08 | 42.88 ▲1.59 |
| Dashboard /wp-admin | 3.39 ▲0.09 | 49.32 ▼5.85 |
| Posts /wp-admin/edit.php | 3.44 ▲0.08 | 53.22 ▲2.22 |
| Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 93.10 ▼6.46 |
| Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 35.53 ▼4.17 |
Server storage [IO: ▲0.93MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 296 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| theysaidso_admin_options |
| db_upgraded |
| widget_recent-comments |
| widget_recent-posts |
| widget_theysaidso_widget |
| can_compress_scripts |
Browser metrics Passed 4 tests
Automater: 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,806 ▲35 | 13.26 ▼1.12 | 1.73 ▼0.77 | 42.74 ▼1.85 |
| Dashboard /wp-admin | 2,209 ▲21 | 5.83 ▼0.02 | 107.44 ▼2.66 | 41.57 ▼3.98 |
| Posts /wp-admin/edit.php | 2,098 ▲9 | 2.04 ▲0.04 | 40.30 ▲3.24 | 38.66 ▲3.65 |
| Add New Post /wp-admin/post-new.php | 1,548 ▲34 | 18.32 ▲0.90 | 656.33 ▼40.42 | 51.38 ▼9.75 |
| Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.31 ▲0.14 | 101.31 ▼14.89 | 41.02 ▼10.70 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-posts
- can_compress_scripts
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
The following issues need your attention
- 129× PHP files trigger server-side errors or warnings when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'AutomaterSDK\\Response\\BaseResponse' not found in wp-content/plugins/automater-pl/vendor/automater-pl/rest-php-sdk/src/Response/CreateDatabaseResponse.php:4
- > PHP Fatal error
Uncaught Error: Class 'AutomaterSDK\\Request\\BaseRequest' not found in wp-content/plugins/automater-pl/vendor/automater-pl/rest-php-sdk/src/Request/AddCodesRequest.php:4
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Container\\ContainerExceptionInterface' not found in wp-content/plugins/automater-pl/vendor/container-interop/container-interop/src/Interop/Container/Exception/ContainerException.php:13
- > PHP Fatal error
Uncaught Error: Interface 'Doctrine\\Common\\Collections\\Expr\\Expression' not found in wp-content/plugins/automater-pl/vendor/doctrine/collections/lib/Doctrine/Common/Collections/Expr/CompositeExpression.php:10
- > PHP Fatal error
Uncaught Error: Interface 'DI\\Definition\\Definition' not found in wp-content/plugins/automater-pl/vendor/php-di/php-di/src/DI/Definition/StringDefinition.php:16
- > PHP Fatal error
Uncaught Error: Interface 'Doctrine\\Common\\Collections\\Collection' not found in wp-content/plugins/automater-pl/vendor/doctrine/collections/lib/Doctrine/Common/Collections/AbstractLazyCollection.php:14
- > PHP Fatal error
Uncaught Error: Class 'DI\\Definition\\FactoryDefinition' not found in wp-content/plugins/automater-pl/vendor/php-di/php-di/src/DI/Definition/DecoratorDefinition.php:11
- > PHP Fatal error
Uncaught Error: Interface 'Invoker\\ParameterResolver\\ParameterResolver' not found in wp-content/plugins/automater-pl/vendor/php-di/php-di/src/DI/Invoker/FactoryParameterResolver.php:18
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\StreamInterface' not found in wp-content/plugins/automater-pl/vendor/guzzlehttp/psr7/src/DroppingStream.php:10
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\MessageInterface' not found in wp-content/plugins/automater-pl/vendor/psr/http-message/src/ResponseInterface.php:20
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser issues were found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
5 plugin tags: woocomerce, ebay, allegro, automation, automater
automater-pl/automater.php 85% from 13 tests
The principal PHP file in "Automater" v. 0.2.2 is loaded by WordPress automatically on each request
The following require your attention:
- Main file name: The principal plugin file should be the same as the plugin slug ("automater-pl.php" instead of "automater.php")
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
No dangerous file extensions were detected20,505 lines of code in 278 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 247 | 3,625 | 8,881 | 17,756 |
| JSON | 19 | 0 | 0 | 1,398 |
| Markdown | 5 | 543 | 0 | 1,019 |
| YAML | 3 | 10 | 0 | 152 |
| PO File | 1 | 33 | 39 | 105 |
| XML | 2 | 14 | 4 | 66 |
| make | 1 | 4 | 0 | 9 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.40 |
| Average class complexity | 9.12 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 153.00 |
| Average method complexity | 2.35 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 27.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 45 | |
| Interfaces | 37 | |
| Traits | 2 | |
| Classes | 185 | |
| ▷ Abstract classes | 7 | 3.78% |
| ▷ Concrete classes | 178 | 96.22% |
| ▷ Final classes | 16 | 8.99% |
| Methods | 1,363 | |
| ▷ Static methods | 157 | 11.52% |
| ▷ Public methods | 1,152 | 84.52% |
| ▷ Protected methods | 28 | 2.05% |
| ▷ Private methods | 183 | 13.43% |
| Functions | 232 | |
| ▷ Named functions | 119 | 51.29% |
| ▷ Anonymous functions | 113 | 48.71% |
| Constants | 144 | |
| ▷ Global constants | 41 | 28.47% |
| ▷ Class constants | 103 | 71.53% |
| ▷ Public constants | 103 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
No PNG files were detected