Benchmarks
Plugin footprint 23% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Please fix the following installer errors
- Install procedure validation failed for this plugin
- > Notice in wp-content/plugins/custom-search-results/index.php+26
Constant WP_DEBUG already defined
Server metrics [RAM: ▼1.73MB] [CPU: ▼49.70ms] Passed 4 tests
This is a short check of server-side resources used by Custom Search Results
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.26 ▼1.20 | 6.06 ▼35.97 |
Dashboard /wp-admin | 2.28 ▼1.03 | 7.10 ▼45.99 |
Posts /wp-admin/edit.php | 2.28 ▼1.08 | 8.47 ▼38.88 |
Add New Post /wp-admin/post-new.php | 2.28 ▼3.61 | 7.99 ▼77.97 |
Media Library /wp-admin/upload.php | 2.28 ▼0.95 | 8.44 ▼26.00 |
Custom Results /wp-admin/admin.php?page=wesp-plugin-customsearches | 2.28 | 6.45 |
Custom Search Results /wp-admin/admin.php?page=wesp-plugin | 2.28 | 6.54 |
Custom Post Types /wp-admin/admin.php?page=wesp-plugin-customposttypes | 2.28 | 7.96 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 9 new files
Database: 3 new tables, 10 new options
New tables |
---|
wp_wesp_search_logging |
wp_wesp_custom_searches |
wp_wesp_custom_results |
New WordPress options |
---|
can_compress_scripts |
widget_recent-posts |
widget_theysaidso_widget |
wesp_db_version |
wesp_searchtype_post |
recovery_mode_email_last_sent |
widget_recent-comments |
wesp_searchtype_page |
db_upgraded |
theysaidso_admin_options |
Browser metrics Passed 4 tests
Custom Search Results: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,831 ▲96 | 13.31 ▼1.07 | 4.24 ▲2.18 | 46.40 ▲1.05 |
Dashboard /wp-admin | 2,237 ▲52 | 5.85 ▼0.01 | 111.14 ▲3.68 | 41.35 ▼1.34 |
Posts /wp-admin/edit.php | 2,120 ▲31 | 2.06 ▲0.06 | 39.64 ▼0.13 | 36.19 ▲1.39 |
Add New Post /wp-admin/post-new.php | 685 ▼839 | 1.73 ▼21.27 | 22.17 ▼673.86 | 5.89 ▼53.71 |
Media Library /wp-admin/upload.php | 1,422 ▲43 | 4.21 ▲0.05 | 97.44 ▼2.74 | 43.42 ▼3.87 |
Custom Results /wp-admin/admin.php?page=wesp-plugin-customsearches | 868 | 2.02 | 21.62 | 24.54 |
Custom Search Results /wp-admin/admin.php?page=wesp-plugin | 865 | 3.95 | 45.75 | 43.10 |
Custom Post Types /wp-admin/admin.php?page=wesp-plugin-customposttypes | 962 | 2.05 | 23.03 | 24.67 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 25% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
The following items require your attention
- Uninstall procedure had uncaught errors
- > Notice in wp-content/plugins/custom-search-results/index.php+26
Constant WP_DEBUG already defined
- The uninstall procedure failed, leaving 3 tables in the database
- wp_wesp_custom_results
- wp_wesp_search_logging
- wp_wesp_custom_searches
- This plugin does not fully uninstall, leaving 10 options in the database
- wesp_searchtype_page
- widget_theysaidso_widget
- widget_recent-posts
- wesp_searchtype_post
- db_upgraded
- can_compress_scripts
- recovery_mode_email_last_sent
- widget_recent-comments
- theysaidso_admin_options
- wesp_db_version
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Almost there, just fix the following server-side errors
- 4 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=wesp-plugin-customposttypes
- > Notice in wp-content/plugins/custom-search-results/index.php+26
Constant WP_DEBUG already defined
- 6 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=wesp-plugin-customposttypes
- > User notice in wp-includes/functions.php+5905
Function add_submenu_page was called incorrectly. The seventh parameter passed to add_submenu_page() should be numeric representing menu position. Please see Debugging in WordPress for more information. (This message was added in version 5.3.0.)
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
The following issues need your attention
- 8× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/custom-search-results/crawl.php
- > /wp-content/plugins/custom-search-results/post.php
- > /wp-content/plugins/custom-search-results/index.php
- > /wp-content/plugins/custom-search-results/init.php
- > /wp-content/plugins/custom-search-results/admin.php
- > /wp-content/plugins/custom-search-results/common.php
- > /wp-content/plugins/custom-search-results/search.php
- > /wp-content/plugins/custom-search-results/charts.php
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser issues were found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
These attributes need your attention:
- Tags: You are using too many tags: 11 tag instead of maximum 10
custom-search-results/index.php 85% from 13 tests
"Custom Search Results" version 1.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
Please take the time to fix the following:
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
- Main file name: It is recommended to name the main PHP file as the plugin slug ("custom-search-results.php" instead of "index.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
Everything looks great! No dangerous files found in this plugin1,277 lines of code in 8 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 8 | 81 | 202 | 1,277 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.23 |
Average class complexity | 5.00 |
▷ Minimum class complexity | 4.00 |
▷ Maximum class complexity | 6.00 |
Average method complexity | 2.00 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 4.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 8 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 8 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 40 | |
▷ Named functions | 40 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 1 | |
▷ Global constants | 1 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
No PNG files were detected