Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.19MB] [CPU: ▼274.10ms] Passed 4 tests
This is a short check of server-side resources used by Portfolio Post Type
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.98 ▲0.14 | 35.30 ▼0.55 |
| Dashboard /wp-admin | 3.28 ▲0.23 | 44.56 ▲0.22 |
| Posts /wp-admin/edit.php | 3.34 ▲0.24 | 42.81 ▼1.41 |
| Add New Post /wp-admin/post-new.php | 5.80 ▲0.37 | 95.43 ▼1,086.54 |
| Media Library /wp-admin/upload.php | 3.16 ▲0.16 | 36.53 ▼7.89 |
| Portfolio Categories /wp-admin/edit-tags.php?taxonomy=portfolio_category&post_type=portfolio | 3.16 | 35.72 |
| Portfolio Tags /wp-admin/edit-tags.php?taxonomy=portfolio_tag&post_type=portfolio | 3.16 | 34.47 |
| All Portfolio Items /wp-admin/edit.php?post_type=portfolio | 3.22 | 32.11 |
| Add New Item /wp-admin/post-new.php?post_type=portfolio | 5.80 | 90.98 |
Server storage [IO: ▲0.07MB] [DB: ▲0.01MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin installed successfully
Filesystem: 18 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
A check of browser resources used by Portfolio Post Type
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 3,725 ▲119 | 15.80 ▼0.12 | 7.55 ▼2.46 | 46.75 ▲3.18 |
| Dashboard /wp-admin | 2,975 ▲122 | 6.05 ▲0.19 | 142.18 ▲4.96 | 98.79 ▲0.52 |
| Posts /wp-admin/edit.php | 2,748 ▲42 | 2.70 ▲0.02 | 66.11 ▼5.17 | 86.25 ▲0.04 |
| Add New Post /wp-admin/post-new.php | 1,510 ▼146 | 18.49 ▲0.31 | 372.81 ▼26.09 | 109.84 ▲5.24 |
| Media Library /wp-admin/upload.php | 1,820 ▲48 | 5.02 ▼0.00 | 145.45 ▼28.58 | 103.12 ▼13.25 |
| Portfolio Categories /wp-admin/edit-tags.php?taxonomy=portfolio_category&post_type=portfolio | 1,749 | 2.51 | 62.42 | 60.44 |
| Portfolio Tags /wp-admin/edit-tags.php?taxonomy=portfolio_tag&post_type=portfolio | 1,721 | 2.49 | 60.65 | 61.81 |
| All Portfolio Items /wp-admin/edit.php?post_type=portfolio | 1,492 | 2.63 | 61.87 | 57.69 |
| Add New Item /wp-admin/post-new.php?post_type=portfolio | 5,678 | 16.55 | 473.11 | 104.47 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.01MB] Passed 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
The plugin uninstalled completely, with no zombie files or tables
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though everything seems fine, this is not an exhaustive test
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
Please fix the following items
- 5× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Class 'Gamajo_Post_Type' not found in wp-content/plugins/portfolio-post-type/includes/class-portfolio-post-type-post-type.php:20
- > PHP Fatal error
Uncaught Error: Class 'Gamajo_Taxonomy' not found in wp-content/plugins/portfolio-post-type/includes/class-portfolio-post-type-taxonomy-category.php:20
- > PHP Fatal error
Uncaught Error: Interface 'Gamajo_Registerable' not found in wp-content/plugins/portfolio-post-type/includes/class-gamajo-post-type.php:19
- > PHP Fatal error
Uncaught Error: Class 'Gamajo_Taxonomy' not found in wp-content/plugins/portfolio-post-type/includes/class-portfolio-post-type-taxonomy-tag.php:20
- > PHP Fatal error
Uncaught Error: Interface 'Gamajo_Registerable' not found in wp-content/plugins/portfolio-post-type/includes/class-gamajo-taxonomy.php:19
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser issues were found
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
2 plugin tags: post type, portfolio
portfolio-post-type/portfolio-post-type.php 92% from 13 tests
The primary PHP file in "Portfolio Post Type" version 1.0.1 is used by WordPress to initiate all plugin functionality
You should first fix the following items:
- Text Domain: The text domain must be the same as the plugin slug, although optional since WordPress version 4.6
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
No dangerous file extensions were detected825 lines of code in 14 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 12 | 135 | 683 | 566 |
| PO File | 2 | 108 | 116 | 259 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.25 |
| Average class complexity | 5.27 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 13.00 |
| Average method complexity | 1.98 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 6.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 1 | |
| Traits | 0 | |
| Classes | 10 | |
| ▷ Abstract classes | 2 | 20.00% |
| ▷ Concrete classes | 8 | 80.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 55 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 37 | 67.27% |
| ▷ Protected methods | 15 | 27.27% |
| ▷ Private methods | 3 | 5.45% |
| Functions | 1 | |
| ▷ Named functions | 1 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 2 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 2 | 100.00% |
| ▷ Public constants | 2 | 100.00% |
Plugin size Passed 1 test
Image compression Passed 1 test
All PNG images should be compressed to minimize bandwidth usage for end users
There were not PNG files found in your plugin