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 successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.06MB] [CPU: ▼3.75ms] Passed 4 tests
Analyzing server-side resources used by Analyse Uploads
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.53 ▲0.07 | 42.98 ▲0.14 |
Dashboard /wp-admin | 3.37 ▲0.06 | 42.94 ▼6.15 |
Posts /wp-admin/edit.php | 3.42 ▲0.06 | 44.00 ▼1.32 |
Add New Post /wp-admin/post-new.php | 5.95 ▲0.06 | 84.06 ▼4.56 |
Media Library /wp-admin/upload.php | 3.29 ▲0.06 | 32.01 ▼2.98 |
Server storage [IO: ▲1.20MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 12 new files
Database: no new tables, 7 new options
New WordPress options |
---|
theysaidso_admin_options |
jpn_au_themefile |
db_upgraded |
widget_recent-comments |
widget_recent-posts |
widget_theysaidso_widget |
can_compress_scripts |
Browser metrics Passed 4 tests
Analyse Uploads: an overview of browser usage
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,820 ▲63 | 13.26 ▼1.15 | 4.74 ▲2.51 | 44.86 ▼8.16 |
Dashboard /wp-admin | 2,226 ▲38 | 5.86 ▲0.96 | 96.48 ▼19.55 | 39.09 ▼5.07 |
Posts /wp-admin/edit.php | 2,109 ▲20 | 2.05 ▲0.04 | 33.70 ▼2.68 | 34.00 ▲1.15 |
Add New Post /wp-admin/post-new.php | 1,531 ▼2 | 23.08 ▲0.06 | 671.03 ▼16.86 | 48.64 ▼2.84 |
Media Library /wp-admin/upload.php | 1,411 ▲26 | 4.20 ▲0.02 | 94.15 ▼9.59 | 40.57 ▼1.92 |
Uninstaller [IO: ▲3.50MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
The following items require your attention
- This plugin did not uninstall successfully, leaving 7 options in the database
- widget_theysaidso_widget
- jpn_au_themefile
- db_upgraded
- widget_recent-comments
- theysaidso_admin_options
- can_compress_scripts
- widget_recent-posts
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
The smoke test was a success, however most plugin functionality was not tested
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
The following issues need your attention
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function register_activation_hook() in wp-content/plugins/analyse-uploads/jpn-analyse-uploads.php:15
- > 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 90% 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
8 plugin tags: media library, analyse uploads, cleaner, analysis, prune...
analyse-uploads/jpn-analyse-uploads.php 77% from 13 tests
The main PHP file in "Analyse Uploads" ver. 0.5 adds more information about the plugin and also serves as the entry point for this plugin
The following require your attention:
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
- Domain Path: The domain path folder was not found ("/languages")
- Main file name: The principal plugin file should be the same as the plugin slug ("analyse-uploads.php" instead of "jpn-analyse-uploads.php")
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 detected3,320 lines of code in 5 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
SVG | 1 | 0 | 0 | 2,671 |
PHP | 1 | 49 | 17 | 350 |
CSS | 2 | 42 | 4 | 290 |
Markdown | 1 | 6 | 0 | 9 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
No cyclomatic complexity issues were detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.27 |
Average class complexity | 0.00 |
▷ Minimum class complexity | 0.00 |
▷ Maximum class complexity | 0.00 |
Average method complexity | 0.00 |
▷ Minimum method complexity | 0.00 |
▷ Maximum method complexity | 0.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 0 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 0 | 0.00% |
▷ Final classes | 0 | 0.00% |
Methods | 0 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 0 | 0.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 16 | |
▷ Named functions | 16 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 0 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
PNG images were not found in this plugin