Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.25MB] [CPU: ▲2.83ms] Passed 4 tests
This is a short check of server-side resources used by LWS Tools
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.77 ▲0.31 | 43.64 ▲0.37 |
Dashboard /wp-admin | 3.59 ▲0.29 | 50.87 ▲0.83 |
Posts /wp-admin/edit.php | 3.64 ▲0.28 | 52.82 ▲8.18 |
Add New Post /wp-admin/post-new.php | 6.11 ▲0.22 | 100.73 ▲3.65 |
Media Library /wp-admin/upload.php | 3.45 ▲0.22 | 41.25 ▲6.45 |
Server storage [IO: ▲2.40MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin was installed successfully
Filesystem: 226 new files
Database: no new tables, 6 new options
New WordPress options |
---|
db_upgraded |
widget_recent-posts |
widget_theysaidso_widget |
widget_recent-comments |
theysaidso_admin_options |
can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for LWS Tools
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,883 ▲148 | 13.62 ▼0.76 | 1.80 ▼0.03 | 36.73 ▼9.68 |
Dashboard /wp-admin | 2,267 ▲79 | 5.88 ▲1.02 | 105.22 ▼1.34 | 74.54 ▲33.71 |
Posts /wp-admin/edit.php | 2,147 ▲58 | 1.99 ▼0.10 | 37.52 ▼1.84 | 33.42 ▼1.70 |
Add New Post /wp-admin/post-new.php | 1,584 ▲51 | 23.17 ▼0.09 | 696.76 ▲102.59 | 49.85 ▼7.02 |
Media Library /wp-admin/upload.php | 1,440 ▲49 | 4.18 ▲0.01 | 98.47 ▲0.06 | 70.61 ▲26.98 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-posts
- can_compress_scripts
- db_upgraded
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
The smoke test was a success, however most plugin functionality was not tested
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 fix the following
- 13× GET requests to PHP files trigger server-side errors or Error 500 responses (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/lws-tools/view/notifications.php:6
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/lws-tools/view/mysql.php:1
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_nonce_field() in wp-content/plugins/lws-tools/view/optimisation.php:2
- > PHP Fatal error
Uncaught Error: Call to undefined function wp_nonce_field() in wp-content/plugins/lws-tools/view/security.php:2
- > PHP Warning
Invalid argument supplied for foreach() in wp-content/plugins/lws-tools/view/update_htaccess.php on line 3
- > PHP Warning
Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in wp-content/plugins/lws-tools/view/change_htaccess.php on line 18
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/lws-tools/view/tabs.php:5
- > PHP Fatal error
Uncaught Error: Call to undefined function __() in wp-content/plugins/lws-tools/view/server.php:3
- > PHP Notice
Undefined variable: opts in wp-content/plugins/lws-tools/view/update_htaccess.php on line 3
- > PHP Notice
Undefined variable: up_to_date in wp-content/plugins/lws-tools/view/notifications.php on line 6
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
No browser errors were detected
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
Attributes that require attention:
- Screenshots: Please add descriptions for these screenshots #8, #9 in lws-tools/assets to your readme.txt
lws-tools/lws-tools.php Passed 13 tests
The main file in "LWS Tools" v. 2.4.5 serves as a complement to information provided in readme.txt and as the entry point to the plugin
45 characters long description:
Optimize and modify your website's parameters
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
Good job! No executable or dangerous file extensions detected30,701 lines of code in 186 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 56 | 5,298 | 15,910 | 18,696 |
CSS | 44 | 273 | 227 | 7,029 |
PHP | 12 | 289 | 261 | 3,075 |
SVG | 73 | 4 | 68 | 1,413 |
PO File | 1 | 238 | 247 | 488 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.35 |
Average class complexity | 0.00 |
▷ Minimum class complexity | 0.00 |
▷ Maximum class complexity | 0.00 |
Average method complexity | 0.00 |
▷ Minimum method complexity | 0.00 |
▷ Maximum method complexity | 0.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 0 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 0 | 0.00% |
▷ Final classes | 0 | 0.00% |
Methods | 0 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 0 | 0.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 59 | |
▷ Named functions | 39 | 66.10% |
▷ Anonymous functions | 20 | 33.90% |
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
PNG files should be compressed to save space and minimize bandwidth usage
8 compressed PNG files occupy 0.04MB
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
DataTables/DataTables-1.12.1/images/sort_both.png | 0.20KB | 0.29KB | 0.00% |
DataTables/DataTables-1.12.1/images/sort_asc_disabled.png | 0.14KB | 0.25KB | 0.00% |
images/icon-256x256.png | 36.35KB | 9.15KB | ▼ 74.82% |
DataTables/DataTables-1.12.1/images/sort_desc_disabled.png | 0.14KB | 0.25KB | 0.00% |
DataTables/DataTables-1.12.1/images/sort_asc.png | 0.16KB | 0.25KB | 0.00% |