Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.07MB] [CPU: ▼2.67ms] Passed 4 tests
Analyzing server-side resources used by Nextlevel Portfolio Custom Post
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.53 ▲0.07 | 45.26 ▲0.14 |
Dashboard /wp-admin | 3.37 ▲0.07 | 54.46 ▲4.03 |
Posts /wp-admin/edit.php | 3.49 ▲0.13 | 50.94 ▼1.12 |
Add New Post /wp-admin/post-new.php | 5.95 ▲0.06 | 91.41 ▼8.46 |
Media Library /wp-admin/upload.php | 3.29 ▲0.06 | 38.22 ▼1.23 |
Portfolios /wp-admin/edit.php?post_type=portfolios | 3.34 | 38.47 |
Add New /wp-admin/post-new.php?post_type=portfolios | 3.44 | 58.37 |
Portfolio Categories /wp-admin/edit-tags.php?taxonomy=portfolio-category&post_type=portfolios | 3.29 | 37.99 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin installed successfully
Filesystem: 6 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
can_compress_scripts |
widget_theysaidso_widget |
widget_recent-posts |
widget_recent-comments |
db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Nextlevel Portfolio Custom Post
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,823 ▲62 | 14.17 ▼0.12 | 1.77 ▼0.27 | 46.25 ▲2.55 |
Dashboard /wp-admin | 2,226 ▲49 | 5.63 ▲0.02 | 103.00 ▲10.13 | 45.49 ▲1.62 |
Posts /wp-admin/edit.php | 2,131 ▲31 | 2.03 ▼0.10 | 35.42 ▼3.86 | 35.32 ▼2.20 |
Add New Post /wp-admin/post-new.php | 1,562 ▲36 | 23.31 ▲0.17 | 674.54 ▼2.59 | 78.25 ▲12.79 |
Media Library /wp-admin/upload.php | 1,428 ▲28 | 4.17 ▼0.04 | 101.28 ▼11.63 | 45.66 ▼1.58 |
Portfolios /wp-admin/edit.php?post_type=portfolios | 1,143 | 1.97 | 34.85 | 31.06 |
Add New /wp-admin/post-new.php?post_type=portfolios | 2,672 | 7.87 | 174.96 | 74.14 |
Portfolio Categories /wp-admin/edit-tags.php?taxonomy=portfolio-category&post_type=portfolios | 1,305 | 2.12 | 25.15 | 30.05 |
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
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-comments
- widget_recent-posts
- db_upgraded
- theysaidso_admin_options
- can_compress_scripts
- widget_theysaidso_widget
Smoke tests Passed 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though everything seems fine, this is not an exhaustive test
SRP Passed 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
Congratulations! This plugin passed the SRP test
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
3 plugin tags: portfolio, nextlevel, custom post
nextlevel-portfolio-custom-post/npcp-cutom-post.php 92% from 13 tests
The main file in "Nextlevel Portfolio Custom Post" v. 1.0.2 serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please take the time to fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("nextlevel-portfolio-custom-post.php" instead of "npcp-cutom-post.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
Everything looks great! No dangerous files found in this plugin149 lines of code in 3 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 3 | 65 | 44 | 149 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.39 |
Average class complexity | 6.00 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 10.00 |
Average method complexity | 1.91 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 10.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 11 | |
▷ Static methods | 1 | 9.09% |
▷ Public methods | 10 | 90.91% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 1 | 9.09% |
Functions | 2 | |
▷ Named functions | 2 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 2 | |
▷ Global constants | 2 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
PNG images were not found in this plugin