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.74MB] [CPU: ▲3.40ms] Passed 4 tests
A check of server-side resources used by Build a House
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 4.22 ▲0.75 | 43.91 ▲2.81 |
Dashboard /wp-admin | 4.04 ▲0.74 | 52.86 ▲2.44 |
Posts /wp-admin/edit.php | 4.10 ▲0.74 | 51.19 ▲6.06 |
Add New Post /wp-admin/post-new.php | 6.76 ▲0.88 | 88.04 ▲2.29 |
Media Library /wp-admin/upload.php | 3.96 ▲0.74 | 52.61 ▲15.90 |
Contractors /wp-admin/edit.php?post_type=ibh_contractor | 4.02 | 45.37 |
Configuration /wp-admin/edit.php?post_type=ibh_expence&page=iworks_build_a_house_index | 3.89 | 47.20 |
Events /wp-admin/edit.php?post_type=ibh_event | 4.02 | 45.09 |
Expences /wp-admin/edit.php?post_type=ibh_expence | 4.02 | 41.16 |
Breakdowns /wp-admin/edit-tags.php?taxonomy=iworks_build_a_house_breakdown&post_type=ibh_expence | 3.96 | 38.22 |
Add New expence /wp-admin/post-new.php?post_type=ibh_expence | 4.10 | 56.52 |
Server storage [IO: ▲0.59MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 75 new files
Database: no new tables, 7 new options
New WordPress options |
---|
iworks_build_a_house_cache_stamp |
widget_theysaidso_widget |
db_upgraded |
can_compress_scripts |
widget_recent-comments |
theysaidso_admin_options |
widget_recent-posts |
Browser metrics Passed 4 tests
Build a House: an overview of browser usage
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,837 ▲76 | 14.25 ▼0.15 | 1.79 ▼0.46 | 43.07 ▼4.40 |
Dashboard /wp-admin | 2,232 ▲55 | 5.54 ▼0.05 | 82.87 ▼15.85 | 40.51 ▼1.72 |
Posts /wp-admin/edit.php | 2,140 ▲43 | 2.00 ▼0.01 | 33.62 ▼2.18 | 36.67 ▲2.34 |
Add New Post /wp-admin/post-new.php | 1,688 ▲160 | 23.32 ▲0.22 | 586.70 ▼90.08 | 55.38 ▼0.55 |
Media Library /wp-admin/upload.php | 1,440 ▲46 | 4.13 ▼0.15 | 99.30 ▲0.85 | 43.92 ▲2.68 |
Contractors /wp-admin/edit.php?post_type=ibh_contractor | 1,218 | 9.64 | 171.09 | 26.17 |
Configuration /wp-admin/edit.php?post_type=ibh_expence&page=iworks_build_a_house_index | 1,108 | 9.83 | 80.02 | 34.21 |
Events /wp-admin/edit.php?post_type=ibh_event | 1,226 | 9.71 | 77.59 | 26.01 |
Expences /wp-admin/edit.php?post_type=ibh_expence | 1,246 | 9.57 | 75.87 | 27.67 |
Breakdowns /wp-admin/edit-tags.php?taxonomy=iworks_build_a_house_breakdown&post_type=ibh_expence | 1,320 | 2.12 | 25.96 | 29.88 |
Add New expence /wp-admin/post-new.php?post_type=ibh_expence | 2,215 | 11.27 | 234.64 | 66.10 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
You still need to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- theysaidso_admin_options
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
- widget_recent-comments
- widget_recent-posts
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Good news, no errors were detected
SRP 50% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please take a closer look at the following
- 14× PHP files trigger server errors when accessed directly (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/build-a-house/assets/template-parts/block/expences-breakdown-table-header.php:1
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_kses_post() in wp-content/plugins/build-a-house/includes/iworks/rate/templates/widgets/support.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/build-a-house/assets/template-parts/block/expences-breakdown-table-body-row.php:1
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_kses_post() in wp-content/plugins/build-a-house/includes/iworks/rate/templates/widgets/donate.php:1
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/build-a-house/includes/iworks/rate/templates/plugins/og.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/build-a-house/assets/template-parts/block/expences-section-table-header.php:1
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_parse_args() in wp-content/plugins/build-a-house/includes/iworks/rate/rate.php:69
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/build-a-house/assets/template-parts/block/expences-section-table-body-row.php:1
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html() in wp-content/plugins/build-a-house/assets/template-parts/block/expences-breakdown-table-footer.php:5
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/build-a-house/includes/iworks/rate/templates/thanks.php:7
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Please take a look at the following user-side issues
- > GET request to /wp-admin/edit.php?post_type=ibh_contractor
- > Javascript (severe) in unknown
/wp-admin/edit.php?post_type=ibh_contractor 369:9 Uncaught SyntaxError: Unexpected token '-'
- > GET request to /wp-admin/edit.php?post_type=ibh_expence&page=iworks_build_a_house_index
- > Javascript (severe) in unknown
/wp-admin/edit.php?post_type=ibh_expence&page=iworks_build_a_house_index 297:9 Uncaught SyntaxError: Unexpected token '-'
- > GET request to /wp-admin/edit.php?post_type=ibh_event
- > Javascript (severe) in unknown
/wp-admin/edit.php?post_type=ibh_event 370:9 Uncaught SyntaxError: Unexpected token '-'
- > GET request to /wp-admin/edit.php?post_type=ibh_expence
- > Javascript (severe) in unknown
/wp-admin/edit.php?post_type=ibh_expence 371:9 Uncaught SyntaxError: Unexpected token '-'
- > GET request to /wp-admin/post-new.php?post_type=ibh_expence
- > Javascript (severe) in unknown
/wp-admin/post-new.php?post_type=ibh_expence 2032:9 Uncaught SyntaxError: Unexpected token '-'
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
5 plugin tags: home, logger, build, house, construction
build-a-house/build-a-house.php Passed 13 tests
The main file in "Build a House" v. 1.0.7 serves as a complement to information provided in readme.txt and as the entry point to the plugin
68 characters long description:
Build a House allows to log expenses and events during construction.
Code Analysis 97% from 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
No dangerous file extensions were detected5,819 lines of code in 55 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 24 | 287 | 975 | 3,538 |
CSS | 11 | 49 | 43 | 846 |
JavaScript | 13 | 65 | 108 | 635 |
PO File | 1 | 220 | 268 | 472 |
Markdown | 2 | 69 | 0 | 138 |
Sass | 1 | 8 | 0 | 138 |
JSON | 1 | 0 | 0 | 39 |
SVG | 2 | 0 | 0 | 13 |
PHP code 50% from 2 tests
This is a very shot review of cyclomatic complexity and code structure
Please tend to the following items
- Cyclomatic complexity of methods should be reduced to less than 100 (currently 192)
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.50 |
Average class complexity | 72.50 |
▷ Minimum class complexity | 9.00 |
▷ Maximum class complexity | 387.00 |
Average method complexity | 4.51 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 192.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 8 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 8 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 163 | |
▷ Static methods | 1 | 0.61% |
▷ Public methods | 118 | 72.39% |
▷ Protected methods | 12 | 7.36% |
▷ Private methods | 33 | 20.25% |
Functions | 6 | |
▷ Named functions | 6 | 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
12 PNG files occupy 0.07MB with 0.02MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/externals/datepicker/css/images/ui-icons_ffffff_256x240.png | 6.15KB | 4.17KB | ▼ 32.13% |
includes/iworks/options/assets/styles/images/ui-icons_777777_256x240.png | 6.94KB | 4.18KB | ▼ 39.78% |
assets/externals/datepicker/css/images/ui-icons_777777_256x240.png | 6.83KB | 4.17KB | ▼ 38.92% |
assets/externals/datepicker/css/images/ui-icons_777620_256x240.png | 4.44KB | 4.17KB | ▼ 6.02% |
assets/externals/datepicker/css/images/ui-icons_444444_256x240.png | 6.83KB | 4.17KB | ▼ 38.86% |