Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.01MB] [CPU: ▼6.52ms] Passed 4 tests
This is a short check of server-side resources used by LGPDY
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.00 | 39.98 ▼9.22 |
| Dashboard /wp-admin | 3.32 ▲0.01 | 51.56 ▲2.18 |
| Posts /wp-admin/edit.php | 3.37 ▲0.01 | 49.44 ▼6.18 |
| Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 90.57 ▼11.56 |
| Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 43.13 ▲0.90 |
Server storage [IO: ▲1.50MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 29 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_recent-comments |
| widget_recent-posts |
| widget_theysaidso_widget |
| db_upgraded |
| can_compress_scripts |
| theysaidso_admin_options |
Browser metrics Passed 4 tests
Checking browser requirements for LGPDY
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,851 ▲90 | 13.76 ▲0.60 | 2.29 ▲0.46 | 42.90 ▼5.67 |
| Dashboard /wp-admin | 2,216 ▲13 | 5.77 ▼0.07 | 103.25 ▼0.20 | 38.77 ▼1.33 |
| Posts /wp-admin/edit.php | 2,107 ▲7 | 1.96 ▼0.01 | 35.21 ▼1.76 | 36.78 ▼1.42 |
| Add New Post /wp-admin/post-new.php | 1,529 ▼16 | 17.62 ▼5.73 | 631.23 ▼0.58 | 60.00 ▼13.09 |
| Media Library /wp-admin/upload.php | 1,407 ▲7 | 4.14 ▼0.04 | 111.14 ▼1.02 | 47.72 ▼0.27 |
| LGPDY /wp-admin/options-general.php?page=lgpdy-configurações | 798 | 2.02 | 27.59 | 31.22 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
You still need to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-posts
- db_upgraded
- can_compress_scripts
- widget_recent-comments
- widget_theysaidso_widget
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Please take a closer look at the following
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/lgpdy/lgpdy-wordpress.php:63
- > 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 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
Attributes that need to be fixed:
- Screenshots: A description for screenshot #2 is missing in lgpdy/assets to your readme.txt
lgpdy/lgpdy-wordpress.php 92% from 13 tests
"LGPDY" version 0.0.4's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
Please make the necessary changes and fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("lgpdy.php" instead of "lgpdy-wordpress.php")
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
Success! There were no dangerous files found in this plugin153 lines of code in 4 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 3 | 8 | 10 | 117 |
| Markdown | 1 | 19 | 0 | 36 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.05 |
| 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 | 8 | |
| ▷ Named functions | 5 | 62.50% |
| ▷ Anonymous functions | 3 | 37.50% |
| Constants | 0 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
16 PNG files occupy 1.28MB with 0.75MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/icon-256x256.png | 45.23KB | 19.89KB | ▼ 56.02% |
| assets/lgpdy-wordpress.png | 1.48KB | 0.60KB | ▼ 59.59% |
| assets/images/banner-1544x500.png | 419.21KB | 163.30KB | ▼ 61.05% |
| assets/images/icon-256x256.png | 45.23KB | 19.89KB | ▼ 56.02% |
| assets/images/lgpdy-wordpress.png | 1.48KB | 0.60KB | ▼ 59.59% |