Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Installer ran successfully
Server metrics [RAM: ▼0.01MB] [CPU: ▲0.41ms] Passed 4 tests
An overview of server-side resources used by Wordpress Amazon S3 Plugin
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.39 ▼0.07 | 35.36 ▼5.30 |
Dashboard /wp-admin | 3.31 ▲0.01 | 47.99 ▲1.51 |
Posts /wp-admin/edit.php | 3.36 ▲0.01 | 50.17 ▲4.26 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 88.74 ▲1.17 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 37.36 ▲7.11 |
Amazon S3 /wp-admin/plugins.php?page=s3plugin-options | 3.30 | 31.10 |
Server storage [IO: ▲9.48MB] [DB: ▲0.01MB] 67% from 3 tests
Analyzing filesystem and database footprints of this plugin
Please try to fix the following items
- Illegal file modification found: 144 files (2.25KB) outside of "wp-content/plugins/wp-s3/" and "wp-content/uploads/"
- (new file) wp-content/s3temp/0/0b/0bb/index.php
- (new file) wp-content/s3temp/0/00/003/index.php
- (new file) wp-content/s3temp/0/0e/0e0/index.php
- (new file) wp-content/s3temp/0/0b/0bb/0bbbb99686a33f1519254d15093f4eab.txt
- (new file) wp-content/s3temp/0/0e/0e0/0e00b15b7ce51bf87d96b9e8a28444c4.txt
- (new file) wp-content/s3temp/0/00/index.php
- (new file) wp-content/s3temp/0/0b/index.php
- (new file) wp-content/s3temp/0/00/006/006d417d3dadd84923ed16aad76f15b9.txt
- (new file) wp-content/s3temp/0/00/003/0038a73c6c631ecfcb8ae8676729399d.txt
- (new file) wp-content/s3temp/0/00/006/index.php
- ...
Filesystem: 897 new files
Database: 1 new table, 6 new options
New tables |
---|
wp_s3_image_queue |
New WordPress options |
---|
widget_recent-comments |
widget_theysaidso_widget |
can_compress_scripts |
db_upgraded |
widget_recent-posts |
theysaidso_admin_options |
Browser metrics Passed 4 tests
Checking browser requirements for Wordpress Amazon S3 Plugin
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,829 ▲83 | 14.48 ▲0.08 | 2.04 ▲0.28 | 43.70 ▲0.28 |
Dashboard /wp-admin | 2,213 ▲31 | 5.85 ▼0.01 | 102.49 ▼0.12 | 38.95 ▼4.74 |
Posts /wp-admin/edit.php | 2,093 ▲4 | 2.04 ▲0.05 | 38.92 ▲1.03 | 34.45 ▼0.93 |
Add New Post /wp-admin/post-new.php | 1,539 ▲19 | 23.30 ▼0.05 | 640.49 ▼47.83 | 55.27 ▼3.95 |
Media Library /wp-admin/upload.php | 1,395 ▲4 | 4.20 ▼0.06 | 98.36 ▼4.97 | 43.68 ▼3.56 |
Amazon S3 /wp-admin/plugins.php?page=s3plugin-options | 1,157 | 2.18 | 22.81 | 27.85 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.01MB] 50% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
Please fix the following items
- The plugin did not uninstall successfully, leaving 1 table in the database
- wp_s3_image_queue
- Zombie WordPress options were found after uninstall: 6 options
- db_upgraded
- theysaidso_admin_options
- widget_recent-comments
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Please take a closer look at the following
- 377× GET requests to PHP files trigger server-side errors or Error 500 responses (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Promise\\PromisorInterface' not found in wp-content/plugins/wp-s3/aws/GuzzleHttp/Pool.php:19
- > PHP Fatal error
Uncaught Error: Class 'Aws\\Exception\\AwsException' not found in wp-content/plugins/wp-s3/aws/Aws/StorageGateway/Exception/StorageGatewayException.php:9
- > PHP Fatal error
Uncaught Error: Class 'Aws\\Exception\\AwsException' not found in wp-content/plugins/wp-s3/aws/Aws/CloudWatchLogs/Exception/CloudWatchLogsException.php:9
- > PHP Fatal error
Trait 'Aws\\Api\\Parser\\PayloadParserTrait' not found in wp-content/plugins/wp-s3/aws/Aws/Api/ErrorParser/XmlErrorParser.php on line 10
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/wp-s3/s3-options.php:11
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Exception\\GuzzleException' not found in wp-content/plugins/wp-s3/aws/GuzzleHttp/Exception/SeekException.php:9
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Promise\\PromisorInterface' not found in wp-content/plugins/wp-s3/aws/Aws/Waiter.php:22
- > PHP Fatal error
Uncaught Error: Interface 'Aws\\Crypto\\MetadataStrategyInterface' not found in wp-content/plugins/wp-s3/aws/Aws/S3/Crypto/HeadersMetadataStrategy.php:7
- > PHP Fatal error
Uncaught Error: Interface 'GuzzleHttp\\Promise\\PromisorInterface' not found in wp-content/plugins/wp-s3/aws/Aws/S3/Transfer.php:18
- > PHP Fatal error
Uncaught Error: Class 'Aws\\Api\\Shape' not found in wp-content/plugins/wp-s3/aws/Aws/Api/ListShape.php:7
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
10 plugin tags: amazon, uploads, performance, bandwidth, s3...
wp-s3/s3.php 85% from 13 tests
The principal PHP file in "Wordpress Amazon S3 Plugin" v. 1.6 is loaded by WordPress automatically on each request
The following require your attention:
- Description: Please don't use more than 140 characters for the plugin description (currently 305 characters long)
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("wp-s3.php" instead of "s3.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
Everything looks great! No dangerous files found in this plugin29,422 lines of code in 895 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 891 | 4,970 | 21,398 | 26,610 |
Markdown | 4 | 1,046 | 0 | 2,812 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.37 |
Average class complexity | 6.23 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 91.00 |
Average method complexity | 2.46 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 27.00 |
Code structure | ||
---|---|---|
Namespaces | 286 | |
Interfaces | 27 | |
Traits | 13 | |
Classes | 476 | |
▷ Abstract classes | 8 | 1.68% |
▷ Concrete classes | 468 | 98.32% |
▷ Final classes | 10 | 2.14% |
Methods | 1,855 | |
▷ Static methods | 219 | 11.81% |
▷ Public methods | 1,292 | 69.65% |
▷ Protected methods | 90 | 4.85% |
▷ Private methods | 473 | 25.50% |
Functions | 364 | |
▷ Named functions | 67 | 18.41% |
▷ Anonymous functions | 297 | 81.59% |
Constants | 146 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 146 | 100.00% |
▷ Public constants | 146 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
No PNG files were detected