Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
This plugin's installer ran successfully
Server metrics [RAM: ▲0.37MB] [CPU: ▼5.03ms] Passed 4 tests
An overview of server-side resources used by Lava Ajax Search
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.87 ▲0.41 | 43.81 ▲6.06 |
Dashboard /wp-admin | 3.70 ▲0.40 | 48.51 ▼1.57 |
Posts /wp-admin/edit.php | 3.75 ▲0.40 | 55.75 ▲4.82 |
Add New Post /wp-admin/post-new.php | 6.22 ▲0.34 | 85.91 ▼20.59 |
Media Library /wp-admin/upload.php | 3.56 ▲0.34 | 37.91 ▼2.79 |
Lava Ajax Search /wp-admin/options-general.php?page=lava-ajax-search | 3.59 | 39.15 |
Server storage [IO: ▲0.37MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
The plugin installed successfully
Filesystem: 47 new files
Database: 1 new table, 6 new options
New tables |
---|
wp_keyword_stack |
New WordPress options |
---|
can_compress_scripts |
widget_recent-comments |
widget_theysaidso_widget |
widget_recent-posts |
theysaidso_admin_options |
db_upgraded |
Browser metrics Passed 4 tests
Lava Ajax Search: an overview of browser usage
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,808 ▲62 | 13.58 ▼0.79 | 1.66 ▼0.69 | 40.52 ▼9.44 |
Dashboard /wp-admin | 2,213 ▲25 | 4.83 ▼1.07 | 112.12 ▼2.31 | 46.65 ▲7.31 |
Posts /wp-admin/edit.php | 2,093 ▲4 | 2.02 ▲0.01 | 41.49 ▲0.08 | 36.56 ▲1.26 |
Add New Post /wp-admin/post-new.php | 1,535 ▲7 | 23.33 ▼0.18 | 603.10 ▼51.53 | 63.84 ▲15.78 |
Media Library /wp-admin/upload.php | 1,389 ▲7 | 4.25 ▲0.07 | 102.11 ▼9.06 | 44.59 ▲0.62 |
Lava Ajax Search /wp-admin/options-general.php?page=lava-ajax-search | 1,089 | 2.03 | 38.74 | 29.12 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
It is recommended to fix the following
- The plugin did not uninstall successfully, leaving 1 table in the database
- wp_keyword_stack
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-posts
- db_upgraded
- widget_recent-comments
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
Smoke tests 75% 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)
The smoke test was a success, however most plugin functionality was not tested
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Almost there! Just fix the following items
- 2× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/lava-ajax-search/templates/template-results.php:4
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/lava-ajax-search/templates/template-admin-index.php:1
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser issues were found
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
10 plugin tags: shortcode, user search, buddypress, relevance search, live...
lava-ajax-search/lava-ajax-search.php 92% from 13 tests
The primary PHP file in "Lava Ajax Search" version 1.1.9 is used by WordPress to initiate all plugin functionality
Please take the time to fix the following:
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
No dangerous file extensions were detected3,172 lines of code in 35 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 24 | 469 | 70 | 2,297 |
Sass | 2 | 45 | 0 | 342 |
CSS | 3 | 1 | 16 | 308 |
JavaScript | 5 | 27 | 4 | 219 |
JSON | 1 | 0 | 0 | 6 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.34 |
Average class complexity | 12.26 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 71.00 |
Average method complexity | 2.93 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 28.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 19 | |
▷ Abstract classes | 2 | 10.53% |
▷ Concrete classes | 17 | 89.47% |
▷ Final classes | 0 | 0.00% |
Methods | 108 | |
▷ Static methods | 10 | 9.26% |
▷ Public methods | 89 | 82.41% |
▷ Protected methods | 9 | 8.33% |
▷ Private methods | 10 | 9.26% |
Functions | 2 | |
▷ Named functions | 1 | 50.00% |
▷ Anonymous functions | 1 | 50.00% |
Constants | 4 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 4 | 100.00% |
▷ Public constants | 4 | 100.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
2 PNG files occupy 0.00MB with 0.00MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/dist/images/no-image.png | 1.09KB | 0.16KB | ▼ 85.07% |
assets/src/images/no-image.png | 1.09KB | 0.16KB | ▼ 85.07% |