Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Install script ran successfully
Server metrics [RAM: ▲0.05MB] [CPU: ▼8.67ms] Passed 4 tests
Analyzing server-side resources used by M4WP Portfolio
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.53 ▲0.07 | 36.39 ▼5.15 |
Dashboard /wp-admin | 3.35 ▲0.05 | 49.07 ▼5.90 |
Posts /wp-admin/edit.php | 3.40 ▲0.05 | 53.66 ▲5.39 |
Add New Post /wp-admin/post-new.php | 5.96 ▲0.07 | 85.59 ▼29.01 |
Media Library /wp-admin/upload.php | 3.28 ▲0.05 | 38.81 ▲5.38 |
All Portfolio Items /wp-admin/edit.php?post_type=portfolio | 3.32 | 37.55 |
Portfolio Categories /wp-admin/edit-tags.php?taxonomy=portfolio_category&post_type=portfolio | 3.27 | 36.48 |
Add New Item /wp-admin/post-new.php?post_type=portfolio | 3.39 | 56.88 |
Portfolio Tags /wp-admin/edit-tags.php?taxonomy=portfolio_tag&post_type=portfolio | 3.27 | 35.17 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin was installed successfully
Filesystem: 25 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
theysaidso_admin_options |
can_compress_scripts |
widget_recent-posts |
widget_recent-comments |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
A check of browser resources used by M4WP Portfolio
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,914 ▲153 | 13.42 ▼0.73 | 7.77 ▲5.96 | 43.70 ▼1.67 |
Dashboard /wp-admin | 2,234 ▲60 | 5.55 ▼0.09 | 87.59 ▼3.15 | 39.65 ▼6.87 |
Posts /wp-admin/edit.php | 2,136 ▲36 | 1.96 ▼0.00 | 39.28 ▼2.01 | 36.25 ▼2.44 |
Add New Post /wp-admin/post-new.php | 1,561 ▲35 | 23.11 ▼0.42 | 604.31 ▼48.94 | 66.57 ▲15.47 |
Media Library /wp-admin/upload.php | 1,436 ▲39 | 4.20 ▼0.02 | 102.05 ▼5.57 | 41.82 ▼3.44 |
All Portfolio Items /wp-admin/edit.php?post_type=portfolio | 1,116 | 1.90 | 31.92 | 39.78 |
Portfolio Categories /wp-admin/edit-tags.php?taxonomy=portfolio_category&post_type=portfolio | 1,310 | 2.12 | 27.83 | 30.93 |
Add New Item /wp-admin/post-new.php?post_type=portfolio | 2,495 | 7.76 | 178.58 | 70.29 |
Portfolio Tags /wp-admin/edit-tags.php?taxonomy=portfolio_tag&post_type=portfolio | 1,316 | 2.12 | 26.85 | 30.86 |
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
- Zombie WordPress options were found after uninstall: 6 options
- db_upgraded
- widget_recent-comments
- theysaidso_admin_options
- widget_recent-posts
- widget_theysaidso_widget
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting 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
Please fix the following
- 2× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/m4wp-portfolio/admin/partials/m4wp-portfolio-admin-display.php
- > /wp-content/plugins/m4wp-portfolio/public/partials/m4wp-portfolio-public-display.php
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser errors were detected
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
These attributes need to be fixed:
- Plugin Name: You should set the name of your plugin on the first line (
=== m4wp-portfolio ===
)
m4wp-portfolio/m4wp-portfolio.php Passed 13 tests
The main file in "M4WP Portfolio" v. 1.0.2 serves as a complement to information provided in readme.txt and as the entry point to the plugin
56 characters long description:
Adds the custom post type Portfolio and it's taxonomies.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
Everything looks great! No dangerous files found in this plugin366 lines of code in 19 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 15 | 174 | 601 | 360 |
JavaScript | 2 | 4 | 54 | 6 |
CSS | 2 | 0 | 8 | 0 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.17 |
Average class complexity | 2.80 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 14.00 |
Average method complexity | 1.56 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 14.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 10 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 10 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 32 | |
▷ Static methods | 2 | 6.25% |
▷ Public methods | 27 | 84.38% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 5 | 15.62% |
Functions | 3 | |
▷ Named functions | 3 | 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