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
Install script ran successfully
Server metrics [RAM: ▼0.67MB] [CPU: ▼16.35ms] Passed 4 tests
Server-side resources used by ThumbSniper
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.02 | 43.68 ▲1.10 |
Dashboard /wp-admin | 3.33 ▲0.03 | 46.62 ▼1.68 |
Posts /wp-admin/edit.php | 3.38 ▲0.03 | 47.42 ▲1.12 |
Add New Post /wp-admin/post-new.php | 3.12 ▼2.77 | 36.95 ▼64.92 |
Media Library /wp-admin/upload.php | 3.25 ▲0.03 | 35.06 ▲0.10 |
ThumbSniper /wp-admin/options-general.php?page=thumbsniper | 3.22 | 32.68 |
Server storage [IO: ▲0.15MB] [DB: ▲0.07MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 23 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
widget_theysaidso_widget |
theysaidso_admin_options |
db_upgraded |
widget_recent-posts |
can_compress_scripts |
Browser metrics Passed 4 tests
A check of browser resources used by ThumbSniper
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,863 ▲128 | 13.59 ▼1.09 | 6.62 ▲4.61 | 44.97 ▲2.13 |
Dashboard /wp-admin | 2,210 ▲25 | 4.80 ▼1.01 | 98.26 ▼1.88 | 38.07 ▼5.47 |
Posts /wp-admin/edit.php | 2,109 ▲20 | 2.24 ▲0.21 | 39.21 ▼5.02 | 38.81 ▲0.44 |
Add New Post /wp-admin/post-new.php | 6,458 ▲4,916 | 19.99 ▲1.86 | 893.54 ▲277.43 | 63.73 ▲8.10 |
Media Library /wp-admin/upload.php | 1,404 ▲13 | 4.19 ▼0.00 | 98.53 ▲2.92 | 40.75 ▼0.77 |
ThumbSniper /wp-admin/options-general.php?page=thumbsniper | 1,094 | 1.85 | 25.97 | 31.68 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
These items require your attention
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_recent-posts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-comments
- can_compress_scripts
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking 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 | 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
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/thumbsniper/thumbsniper.php:35
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
Please fix the following attributes:
- Tags: You are using too many tags: 12 tag instead of maximum 10
- Screenshots: Screenshot #1 (This screenshot shows a tooltip preview which is shown while holding the mouse cursor over the WordPress.org hyperlink.) image required
thumbsniper/thumbsniper.php Passed 13 tests
The main file in "ThumbSniper" v. 2.9.7 serves as a complement to information provided in readme.txt and as the entry point to the plugin
99 characters long description:
This plugin dynamically shows preview screenshots of hyperlinks as tooltips on your WordPress site.
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
There were no executable files found in this plugin1,453 lines of code in 17 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 13 | 349 | 381 | 1,307 |
JSON | 3 | 0 | 0 | 79 |
Markdown | 1 | 11 | 0 | 67 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.42 |
Average class complexity | 25.00 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 115.00 |
Average method complexity | 3.09 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 40.00 |
Code structure | ||
---|---|---|
Namespaces | 4 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 8 | |
▷ Abstract classes | 2 | 25.00% |
▷ Concrete classes | 6 | 75.00% |
▷ Final classes | 0 | 0.00% |
Methods | 93 | |
▷ Static methods | 36 | 38.71% |
▷ Public methods | 83 | 89.25% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 10 | 10.75% |
Functions | 2 | |
▷ Named functions | 1 | 50.00% |
▷ Anonymous functions | 1 | 50.00% |
Constants | 1 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 1 | 100.00% |
▷ Public constants | 1 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
1 PNG file occupies 0.04MB with 0.02MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-1.png | 44.08KB | 19.33KB | ▼ 56.15% |