Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Install script ran successfully
Server metrics [RAM: ▲0.05MB] [CPU: ▼7.99ms] Passed 4 tests
This is a short check of server-side resources used by Sync media with AWS S3 CloudFront
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.51 ▲0.05 | 39.90 ▼0.86 |
| Dashboard /wp-admin | 3.35 ▲0.05 | 44.61 ▼2.29 |
| Posts /wp-admin/edit.php | 3.40 ▲0.04 | 51.41 ▼3.82 |
| Add New Post /wp-admin/post-new.php | 5.95 ▲0.06 | 89.52 ▼4.81 |
| Media Library /wp-admin/upload.php | 3.27 ▲0.04 | 32.77 ▼21.02 |
| AWS S3 Sync /wp-admin/tools.php?page=sync-media-with-aws-s3-cloudfront/templates/main_page_s3.php | 3.27 | 31.31 |
Server storage [IO: ▲15.94MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 1,396 new files
Database: 1 new table, 7 new options
| New tables |
|---|
| wp_s3_sync_smwas3c |
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-comments |
| widget_recent-posts |
| widget_theysaidso_widget |
| db_upgraded |
| theysaidso_admin_options |
| option_smwas3c |
Browser metrics Passed 4 tests
A check of browser resources used by Sync media with AWS S3 CloudFront
Minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,808 ▲51 | 14.74 ▲0.37 | 1.84 ▼0.29 | 43.54 ▼0.99 |
| Dashboard /wp-admin | 2,214 ▲32 | 5.87 ▲0.02 | 103.37 ▼0.51 | 35.13 ▼6.59 |
| Posts /wp-admin/edit.php | 2,100 ▲11 | 2.02 ▼0.02 | 40.63 ▲0.57 | 34.35 ▲2.74 |
| Add New Post /wp-admin/post-new.php | 1,525 ▼17 | 23.38 ▲4.92 | 672.22 ▲37.47 | 55.10 ▼5.39 |
| Media Library /wp-admin/upload.php | 1,393 ▲5 | 4.21 ▲0.02 | 97.66 ▼8.92 | 42.08 ▼3.52 |
| AWS S3 Sync /wp-admin/tools.php?page=sync-media-with-aws-s3-cloudfront/templates/main_page_s3.php | 1,077 | 1.71 | 27.36 | 26.69 |
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
You still need to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- theysaidso_admin_options
- widget_recent-posts
- db_upgraded
- can_compress_scripts
- 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
Good news, no errors were detected
SRP 50% 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
Almost there! Just fix the following items
- 587× GET requests to PHP files trigger server-side errors or Error 500 responses (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'Aws\\Exception\\AwsException' not found in wp-content/plugins/sync-media-with-aws-s3-cloudfront/aws/Aws/CloudWatchLogs/Exception/CloudWatchLogsException.php:9
- > PHP Fatal error
Uncaught Error: Class 'Aws\\Exception\\AwsException' not found in wp-content/plugins/sync-media-with-aws-s3-cloudfront/aws/Aws/WafRegional/Exception/WafRegionalException.php:9
- > PHP Fatal error
Uncaught Error: Class 'Aws\\Exception\\AwsException' not found in wp-content/plugins/sync-media-with-aws-s3-cloudfront/aws/Aws/Personalize/Exception/PersonalizeException.php:9
- > PHP Fatal error
Uncaught Error: Class 'Aws\\AwsClient' not found in wp-content/plugins/sync-media-with-aws-s3-cloudfront/aws/Aws/CostandUsageReportService/CostandUsageReportServiceClient.php:17
- > PHP Fatal error
Uncaught Error: Interface 'Psr\\Http\\Message\\RequestInterface' not found in wp-content/plugins/sync-media-with-aws-s3-cloudfront/aws/Psr/Http/Message/ServerRequestInterface.php:43
- > PHP Fatal error
Uncaught Error: Class 'Aws\\AbstractConfigurationProvider' not found in wp-content/plugins/sync-media-with-aws-s3-cloudfront/aws/Aws/Sts/RegionalEndpoints/ConfigurationProvider.php:45
- > PHP Fatal error
Uncaught Error: Class 'Aws\\AwsClient' not found in wp-content/plugins/sync-media-with-aws-s3-cloudfront/aws/Aws/GroundStation/GroundStationClient.php:59
- > PHP Fatal error
Uncaught Error: Class 'Aws\\Exception\\AwsException' not found in wp-content/plugins/sync-media-with-aws-s3-cloudfront/aws/Aws/ElasticInference/Exception/ElasticInferenceException.php:9
- > PHP Fatal error
Uncaught Error: Class 'Aws\\Exception\\AwsException' not found in wp-content/plugins/sync-media-with-aws-s3-cloudfront/aws/Aws/NetworkManager/Exception/NetworkManagerException.php:9
- > PHP Fatal error
Uncaught Error: Class 'Aws\\AwsClient' not found in wp-content/plugins/sync-media-with-aws-s3-cloudfront/aws/Aws/Cloud9/Cloud9Client.php:29
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There were no browser issues found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
9 plugin tags: aws, media, link, image, s3...
sync-media-with-aws-s3-cloudfront/sync-media-with-AWS-S3-CloudFront.php 85% from 13 tests
This is the main PHP file of "Sync media with AWS S3 CloudFront" version 1.0.5, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
Please take the time to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("sync-media-with-aws-s3-cloudfront.php" instead of "sync-media-with-AWS-S3-CloudFront.php")
- Description: Please don't use more than 140 characters for the plugin description (currently 170 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
There were no executable files found in this plugin38,562 lines of code in 1,394 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1,387 | 6,127 | 30,273 | 33,392 |
| Markdown | 4 | 1,862 | 0 | 4,788 |
| JavaScript | 1 | 24 | 6 | 309 |
| CSS | 1 | 8 | 0 | 57 |
| SVG | 1 | 0 | 0 | 16 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
There are no cyclomatic complexity problems detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.37 |
| Average class complexity | 5.31 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 84.00 |
| Average method complexity | 2.44 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 27.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 473 | |
| Interfaces | 38 | |
| Traits | 17 | |
| Classes | 695 | |
| ▷ Abstract classes | 11 | 1.58% |
| ▷ Concrete classes | 684 | 98.42% |
| ▷ Final classes | 12 | 1.75% |
| Methods | 2,205 | |
| ▷ Static methods | 318 | 14.42% |
| ▷ Public methods | 1,520 | 68.93% |
| ▷ Protected methods | 115 | 5.22% |
| ▷ Private methods | 570 | 25.85% |
| Functions | 412 | |
| ▷ Named functions | 76 | 18.45% |
| ▷ Anonymous functions | 336 | 81.55% |
| Constants | 199 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 199 | 100.00% |
| ▷ Public constants | 199 | 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 images were found in this plugin