Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.04MB] [CPU: ▼5.25ms] Passed 4 tests
This is a short check of server-side resources used by Page Builder Companion
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.51 ▲0.04 | 33.60 ▼6.38 |
Dashboard /wp-admin | 3.35 ▲0.04 | 43.93 ▼5.49 |
Posts /wp-admin/edit.php | 3.40 ▲0.04 | 45.18 ▲0.09 |
Add New Post /wp-admin/post-new.php | 5.93 ▲0.04 | 88.13 ▼9.21 |
Media Library /wp-admin/upload.php | 3.27 ▲0.04 | 34.22 ▲0.66 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 13 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
db_upgraded |
widget_recent-posts |
widget_theysaidso_widget |
theysaidso_admin_options |
can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for Page Builder Companion
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,790 ▲28 | 14.67 ▲0.32 | 1.79 ▲0.07 | 42.41 ▼2.54 |
Dashboard /wp-admin | 2,195 ▲18 | 5.60 ▲0.03 | 86.48 ▼16.62 | 44.24 ▼1.40 |
Posts /wp-admin/edit.php | 2,174 ▲74 | 2.00 ▲0.01 | 41.87 ▲5.11 | 36.87 ▼1.28 |
Add New Post /wp-admin/post-new.php | 1,532 ▲3 | 23.14 ▼0.33 | 611.93 ▼37.78 | 50.10 ▼7.84 |
Media Library /wp-admin/upload.php | 1,400 ▲6 | 4.22 ▼0.06 | 98.84 ▼1.39 | 41.49 ▼0.79 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- can_compress_scripts
- widget_theysaidso_widget
- widget_recent-posts
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
Smoke tests 75% from 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 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
The following issues need your attention
- 4× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_header() in wp-content/plugins/page-builder-companion/templates/pbc-no-sidebar.php:5
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/page-builder-companion/templates/helpers.php:28
- > PHP Fatal error
Uncaught Error: Call to undefined function page_builder_companion_minimal_get_header() in wp-content/plugins/page-builder-companion/templates/pbc-no-header-and-footer.php:5
- > PHP Fatal error
Uncaught Error: Call to undefined function get_header() in wp-content/plugins/page-builder-companion/templates/pbc-full-width.php:5
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
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 is important because it is parsed by WordPress.org for the public listing of your plugin
4 plugin tags: templates, fullwidth, elementor, pagebuilder
page-builder-companion/page-builder-companion.php 92% from 13 tests
The main file in "Page Builder Companion" v. 1.2.2 serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please make the necessary changes and fix the following:
- Description: Please keep the plugin description shorter than 140 characters (currently 172 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
There were no executable files found in this plugin236 lines of code in 10 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 6 | 80 | 41 | 180 |
CSS | 3 | 6 | 2 | 52 |
JavaScript | 1 | 0 | 0 | 4 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.22 |
Average class complexity | 15.00 |
▷ Minimum class complexity | 15.00 |
▷ Maximum class complexity | 15.00 |
Average method complexity | 2.40 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 4.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 | 10 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 10 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 4 | |
▷ Named functions | 4 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 4 | |
▷ Global constants | 4 | 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
No PNG images were found in this plugin