Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Installer ran successfully
Server metrics [RAM: ▲0.07MB] [CPU: ▼15.02ms] Passed 4 tests
Server-side resources used by WP Lucky Search
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 57.21 ▲0.26 | 11,112,823.88 ▲8,185.17 |
Dashboard /wp-admin | 3.42 ▲0.03 | 49.71 ▼21.24 |
Posts /wp-admin/edit.php | 3.53 ▲0.13 | 53.23 ▼4.83 |
Add New Post /wp-admin/post-new.php | 6.00 ▲0.07 | 90.51 ▼32.90 |
Media Library /wp-admin/upload.php | 3.34 ▲0.07 | 36.79 ▼1.11 |
WP Lucky Search /wp-admin/options-general.php?page=wpls | 3.31 | 33.55 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
There were no storage issued detected upon installing this plugin
Filesystem: 7 new files
Database: no new tables, 6 new options
New WordPress options |
---|
theysaidso_admin_options |
widget_recent-posts |
widget_theysaidso_widget |
widget_recent-comments |
can_compress_scripts |
db_upgraded |
Browser metrics Passed 4 tests
An overview of browser requirements for WP Lucky Search
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,902 ▲156 | 13.43 ▼1.21 | 8.08 ▲6.43 | 39.19 ▼3.46 |
Dashboard /wp-admin | 2,202 ▲28 | 5.62 ▲0.02 | 85.28 ▼9.41 | 39.19 ▼0.58 |
Posts /wp-admin/edit.php | 2,104 ▲25 | 2.02 ▼0.01 | 35.37 ▼1.20 | 30.23 ▼5.35 |
Add New Post /wp-admin/post-new.php | 1,528 ▲2 | 23.77 ▲0.28 | 692.84 ▲32.85 | 70.59 ▲10.15 |
Media Library /wp-admin/upload.php | 1,404 ▲7 | 4.14 ▼0.04 | 94.18 ▼2.09 | 41.23 ▼5.53 |
WP Lucky Search /wp-admin/options-general.php?page=wpls | 914 | 2.02 | 23.46 | 30.79 |
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
Please fix the following items
- This plugin did not uninstall successfully, leaving 6 options in the database
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
- widget_recent-posts
- db_upgraded
- can_compress_scripts
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Smoke test failed, please fix the following
- 12 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=wpls
- > Warning in wp-content/plugins/easy-age-verifier/lib/extras/wpApi.php+48
file_get_contents(): php_network_getaddresses: getaddrinfo failed: Name or service not known
- 12 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=wpls
- > Warning in wp-content/plugins/easy-age-verifier/lib/extras/wpApi.php+48
file_get_contents(http://www.fillyourtaproom.com/wp-json/wp/v2/posts?per_page=10): failed to open stream: php_network_getaddresses: getaddrinfo failed: Name or service not known
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× PHP files trigger errors when accessed directly with GET requests:
- > PHP Notice
Trying to get property 'wpls_textdomain' of non-object in wp-content/plugins/wp-lucky-search/lib/admin/class-wpls-admin.php on line 26
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-lucky-search/lib/admin/class-wpls-admin.php:31
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_path() in wp-content/plugins/wp-lucky-search/wp-lucky-search.php:26
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/wp-lucky-search/lib/class-wpls-main.php:102
- > 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 on the user side
Optimizations
Plugin configuration 93% 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:
- Tags: You are using too many tags: 12 tag instead of maximum 10
wp-lucky-search/wp-lucky-search.php 92% from 13 tests
The entry point to "WP Lucky Search" version 1.0 is a PHP file that has certain tags in its header comment area
It is important to fix the following:
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Success! There were no dangerous files found in this plugin285 lines of code in 5 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 3 | 76 | 244 | 225 |
Markdown | 1 | 30 | 0 | 37 |
JavaScript | 1 | 4 | 7 | 23 |
PHP code Passed 2 tests
An overview 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.27 |
Average class complexity | 8.67 |
▷ Minimum class complexity | 4.00 |
▷ Maximum class complexity | 12.00 |
Average method complexity | 2.15 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 9.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 | 20 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 20 | 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 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
No PNG files were detected