Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.04MB] [CPU: ▼130.34ms] Passed 4 tests
Analyzing server-side resources used by Persistent Forking (WordPress plugin)
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.91 ▲0.08 | 45.91 ▲4.29 |
Dashboard /wp-admin | 3.10 ▲0.05 | 40.31 ▲0.22 |
Posts /wp-admin/edit.php | 3.15 ▲0.05 | 40.45 ▼0.50 |
Add New Post /wp-admin/post-new.php | 5.46 ▲0.03 | 118.88 ▼525.36 |
Media Library /wp-admin/upload.php | 3.04 ▲0.04 | 36.37 ▲5.08 |
Server storage [IO: ▲0.61MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
No storage issues were detected
Filesystem: 11 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
An overview of browser requirements for Persistent Forking (WordPress plugin)
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,826 ▲254 | 17.69 ▲2.22 | 29.74 ▲18.40 | 49.45 ▼7.02 |
Dashboard /wp-admin | 2,973 ▲42 | 5.92 ▼0.04 | 139.98 ▼31.14 | 113.75 ▼5.57 |
Posts /wp-admin/edit.php | 2,758 ▲22 | 2.70 ▲0.01 | 66.89 ▼2.81 | 93.30 ▼1.81 |
Add New Post /wp-admin/post-new.php | 1,612 ▲31 | 17.34 ▼0.56 | 470.21 ▲78.48 | 141.57 ▲31.39 |
Media Library /wp-admin/upload.php | 1,807 ▼3 | 5.07 ▲0.03 | 164.41 ▼6.95 | 135.92 ▲10.89 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
Uninstaller ran successfully
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check 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
Please take a closer look at the following
- 5× PHP files trigger errors when accessed directly with GET requests:
- > PHP Notice
Trying to get property 'ID' of non-object in wp-content/plugins/persistent-forking/templates/admin_metabox.php on line 6
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/persistent-forking/persistent-forking.php:35
- > PHP Fatal error
Uncaught Error: Call to undefined function add_query_arg() in wp-content/plugins/persistent-forking/templates/public_fork_box.php:11
- > PHP Notice
Undefined index: post in wp-content/plugins/persistent-forking/templates/admin_metabox.php on line 5
- > PHP Fatal error
Uncaught Error: Call to undefined function get_post_meta() in wp-content/plugins/persistent-forking/templates/admin_metabox.php:7
- > PHP Notice
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
3 plugin tags: forking, posts, forks
persistent-forking/persistent-forking.php Passed 13 tests
The main PHP file in "Persistent Forking (WordPress plugin)" ver. 1.0 adds more information about the plugin and also serves as the entry point for this plugin
98 characters long description:
Enable contributors to create permanent forks of existing posts.Visualise the family of any fork.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
Good job! No executable or dangerous file extensions detected637 lines of code in 8 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 3 | 19 | 154 | 320 |
SVG | 1 | 1 | 1 | 201 |
JavaScript | 2 | 6 | 29 | 78 |
CSS | 2 | 6 | 4 | 38 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.40 |
Average class complexity | 23.00 |
▷ Minimum class complexity | 23.00 |
▷ Maximum class complexity | 23.00 |
Average method complexity | 3.00 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 7.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 | 11 | |
▷ Static methods | 11 | 100.00% |
▷ Public methods | 11 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 0 | |
▷ Named functions | 0 | 0.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
Using a strong compression for your PNG files is a great way to speed-up your plugin
1 compressed PNG file occupies 0.00MB
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/fork_icon.png | 0.45KB | 0.59KB | 0.00% |