Benchmarks
Plugin footprint 58% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
These installer errors require your attention
- The plugin cannot be installed
- > User deprecated in wp-includes/functions.php+5453
Function get_page_by_title is deprecated since version 6.2.0! Use WP_Query instead.
Server metrics [RAM: ▲0.59MB] [CPU: ▲0.38ms] Passed 4 tests
Server-side resources used by Postcodes4U Address Finder
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 4.06 ▲0.60 | 43.44 ▼0.70 |
| Dashboard /wp-admin | 3.90 ▲0.59 | 53.21 ▲1.47 |
| Posts /wp-admin/edit.php | 4.01 ▲0.65 | 48.28 ▼0.71 |
| Add New Post /wp-admin/post-new.php | 6.48 ▲0.59 | 90.52 ▲1.46 |
| Media Library /wp-admin/upload.php | 3.82 ▲0.59 | 39.86 ▲8.38 |
| Postcodes4U /wp-admin/options-general.php?page=pc4u-options | 3.80 | 35.05 |
Server storage [IO: ▲1.61MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 28 new files
Database: no new tables, 9 new options
| New WordPress options |
|---|
| widget_recent-comments |
| can_compress_scripts |
| postcodes4u_page_title |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-posts |
| postcodes4u_page_id |
| postcodes4u_page_name |
Browser metrics Passed 4 tests
Checking browser requirements for Postcodes4U Address Finder
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,833 ▲76 | 13.39 ▼0.91 | 1.94 ▼0.03 | 43.73 ▼5.65 |
| Dashboard /wp-admin | 2,207 ▲22 | 5.87 ▲0.02 | 108.69 ▼9.23 | 42.18 ▼0.97 |
| Posts /wp-admin/edit.php | 2,096 ▲7 | 1.97 ▼0.05 | 35.38 ▼0.64 | 30.92 ▼2.46 |
| Add New Post /wp-admin/post-new.php | 1,536 ▲8 | 22.93 ▼0.02 | 568.70 ▼107.57 | 59.02 ▼1.32 |
| Media Library /wp-admin/upload.php | 1,386 ▼2 | 4.30 ▲0.13 | 98.96 ▼1.75 | 41.98 ▼3.70 |
| Postcodes4U /wp-admin/options-general.php?page=pc4u-options | 1,186 | 2.03 | 22.94 | 28.24 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
These items require your attention
- Zombie WordPress options were found after uninstall: 6 options
- widget_recent-comments
- widget_theysaidso_widget
- db_upgraded
- can_compress_scripts
- theysaidso_admin_options
- 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 0% 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
- 2× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/postcodes4u-address-finder/includes/gf_integration.php
- > /wp-content/plugins/postcodes4u-address-finder/includes/cf7_integration.php
- 5× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/postcodes4u-address-finder/includes/display-functions.php:156
- > PHP Fatal error
Uncaught Error: Call to undefined function register_activation_hook() in wp-content/plugins/postcodes4u-address-finder/postcodes4U.php:18
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/postcodes4u-address-finder/includes/woo_integration.php:18
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/postcodes4u-address-finder/includes/scripts.php:17
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/postcodes4u-address-finder/includes/admin-page.php:416
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser errors were detected
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
Please fix the following attributes:
- Screenshots: These screenshots require images: #1 (Simple interface to add your Postcodes4U details), #2 (Works with ContactForm7 and GravityForms), #3 (Works with WooCommerce Checkout and Account Pages), #4 (Easy setup for postcode Lookup in ContactForm7), #5 (Easy setup for postcode Lookup in GravityForms), #6 (Compatable with GravityForms 2.5.x - 2.7.x), #7 (Includes Our own Contact form with Postcodes4U Postcode Lookup), #8 (In all cases, like WooCommerce, use our Simple address look up for for Postcodes4U), #9 (With Simple address selection)
- Tags: You are using too many tags: 12 tag instead of maximum 10
postcodes4u-address-finder/postcodes4U.php 85% from 13 tests
The main file in "Postcodes4U Address Finder" v. 1.5.31.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please take the time to fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("postcodes4u-address-finder.php" instead of "postcodes4U.php")
- Requires at least: Required version must be the same as the one declared in readme.txt ("3.0.1" instead of "3.0")
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
Success! There were no dangerous files found in this plugin6,577 lines of code in 16 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 2 | 685 | 1,030 | 4,072 |
| PHP | 12 | 453 | 583 | 2,412 |
| CSS | 2 | 32 | 18 | 93 |
PHP code 50% from 2 tests
This plugin's cyclomatic complexity and code structure detailed below
These items need your attention
- Method cyclomatic complexity has to be reduced to less than 100 (currently 128)
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.54 |
| Average class complexity | 81.00 |
| ▷ Minimum class complexity | 7.00 |
| ▷ Maximum class complexity | 225.00 |
| Average method complexity | 6.71 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 128.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 3 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 3 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 42 | |
| ▷ Static methods | 9 | 21.43% |
| ▷ Public methods | 42 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 38 | |
| ▷ Named functions | 38 | 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
1 PNG file occupies 0.08MB with 0.05MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| PC4u_1_5.png | 79.03KB | 30.84KB | ▼ 60.97% |