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.15MB] [CPU: ▼3.40ms] Passed 4 tests
Server-side resources used by Custom Metadata Manager
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.60 ▲0.14 | 39.00 ▼5.03 |
Dashboard /wp-admin | 3.44 ▲0.14 | 47.52 ▼1.93 |
Posts /wp-admin/edit.php | 3.57 ▲0.21 | 55.34 ▲7.53 |
Add New Post /wp-admin/post-new.php | 6.05 ▲0.17 | 96.40 ▼9.11 |
Media Library /wp-admin/upload.php | 3.36 ▲0.13 | 38.99 ▲2.48 |
Server storage [IO: ▲0.31MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 25 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
widget_theysaidso_widget |
widget_recent-comments |
theysaidso_admin_options |
db_upgraded |
can_compress_scripts |
Browser metrics Passed 4 tests
Checking browser requirements for Custom Metadata Manager
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲65 | 13.32 ▼1.06 | 1.84 ▼0.04 | 41.05 ▼6.65 |
Dashboard /wp-admin | 2,206 ▲18 | 4.87 ▼0.07 | 108.15 ▲1.03 | 40.71 ▼8.40 |
Posts /wp-admin/edit.php | 2,107 ▲18 | 2.25 ▲0.23 | 39.30 ▲0.36 | 35.77 ▲4.69 |
Add New Post /wp-admin/post-new.php | 1,538 ▼4 | 23.42 ▲5.20 | 632.78 ▼15.89 | 51.00 ▼5.23 |
Media Library /wp-admin/upload.php | 1,391 ▲6 | 4.24 ▲0.05 | 95.93 ▼5.56 | 43.14 ▼0.37 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- db_upgraded
- widget_recent-posts
- widget_recent-comments
- widget_theysaidso_widget
- can_compress_scripts
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check 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 applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please fix the following
- 2× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function apply_filters() in wp-content/plugins/custom-metadata/custom_metadata.php:84
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/custom-metadata/custom_metadata_examples.php:27
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser issues were found
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
These attributes need your attention:
- Screenshots: These screenshots have no corresponding images in /assets: #1 (Write easy, intuitive and WordPress-like code to add new fields.), #2 (Custom Metadata Manager supports many field types with an easy way to render your own.), #3 (Adding custom columns is also easy. You can go with a default display, or specify your own output callback)
custom-metadata/custom_metadata.php 92% from 13 tests
The entry point to "Custom Metadata Manager" version 0.7.1 is a PHP file that has certain tags in its header comment area
You should first fix the following items:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("custom-metadata.php" instead of "custom_metadata.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Success! There were no dangerous files found in this plugin1,264 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 254 | 181 | 857 |
CSS | 2 | 33 | 67 | 293 |
JavaScript | 2 | 5 | 16 | 114 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.44 |
Average class complexity | 155.00 |
▷ Minimum class complexity | 155.00 |
▷ Maximum class complexity | 155.00 |
Average method complexity | 3.26 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 38.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 68 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 68 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 6 | |
▷ Named functions | 6 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 3 | |
▷ Global constants | 3 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
15 compressed PNG files occupy 0.02MB
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
css/images/ui-bg_glass_75_e6e6e6_1x400.png | 0.11KB | 0.14KB | 0.00% |
css/images/ui-bg_highlight-soft_75_cccccc_1x100.png | 0.10KB | 0.17KB | 0.00% |
css/images/ui-bg_flat_0_aaaaaa_40x100.png | 0.18KB | 0.08KB | ▼ 51.67% |
css/images/calendar.png | 0.25KB | 0.28KB | 0.00% |
css/images/ui-icons_454545_256x240.png | 4.27KB | 4.11KB | ▼ 3.78% |