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.00MB] [CPU: ▼3.72ms] Passed 4 tests
A check of server-side resources used by Opal Estate Custom Fields
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 40.42 ▼0.45 |
Dashboard /wp-admin | 3.31 ▲0.01 | 44.47 ▼4.90 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 49.52 ▲1.32 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 93.22 ▼8.43 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 33.69 ▼1.10 |
Server storage [IO: ▲0.14MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 34 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
widget_recent-comments |
theysaidso_admin_options |
widget_theysaidso_widget |
can_compress_scripts |
db_upgraded |
Browser metrics Passed 4 tests
A check of browser resources used by Opal Estate Custom Fields
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,810 ▲75 | 13.21 ▼1.15 | 1.74 ▲0.11 | 44.09 ▲0.09 |
Dashboard /wp-admin | 2,216 ▲25 | 5.79 ▲0.90 | 99.42 ▼2.21 | 37.32 ▼6.32 |
Posts /wp-admin/edit.php | 2,098 ▲9 | 2.01 ▲0.01 | 39.45 ▼1.37 | 35.84 ▲1.34 |
Add New Post /wp-admin/post-new.php | 1,543 ▲10 | 23.20 ▼0.03 | 647.89 ▲28.39 | 53.23 ▼2.08 |
Media Library /wp-admin/upload.php | 1,392 ▲10 | 4.24 ▲0.05 | 94.14 ▼8.89 | 45.00 ▲2.50 |
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
Please fix the following items
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-comments
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
- theysaidso_admin_options
- 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
Everything seems fine, however this is by no means an exhaustive test
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
Almost there! Just fix the following items
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function trailingslashit() in wp-content/plugins/opal-estate-custom-fields/loader.php:11
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine on the user side
Optimizations
Plugin configuration 86% 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
Please fix the following attributes:
- Screenshots: These screenshots need descriptions #1, #2, #3, #4, #5 in opal-estate-custom-fields/assets to your readme.txt
opal-estate-custom-fields/opal-estate-custom-fields.php 77% from 13 tests
The primary PHP file in "Opal Estate Custom Fields" version 1.0.5 is used by WordPress to initiate all plugin functionality
It is important to fix the following:
- Requires at least: The required version number must match the one declared in readme.txt ("4.6" instead of "4.9")
- Domain Path: Use only dashes and lowercase characters for the domain path ("languages/")
- Domain Path: Please prefix the domain path with a forward slash character ("/languages/")
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
Everything looks great! No dangerous files found in this plugin2,172 lines of code in 27 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 18 | 304 | 407 | 1,434 |
CSS | 4 | 26 | 5 | 468 |
JavaScript | 3 | 76 | 21 | 250 |
SVG | 1 | 0 | 0 | 19 |
JSON | 1 | 0 | 0 | 1 |
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.35 |
Average class complexity | 15.27 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 57.00 |
Average method complexity | 3.34 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 44.00 |
Code structure | ||
---|---|---|
Namespaces | 3 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 11 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 11 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 68 | |
▷ Static methods | 4 | 5.88% |
▷ Public methods | 58 | 85.29% |
▷ Protected methods | 9 | 13.24% |
▷ Private methods | 1 | 1.47% |
Functions | 9 | |
▷ Named functions | 7 | 77.78% |
▷ Anonymous functions | 2 | 22.22% |
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
No PNG images were found in this plugin