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
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.01MB] [CPU: ▼2.24ms] Passed 4 tests
A check of server-side resources used by Awesome Tool Tip
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 39.59 ▼2.42 |
Dashboard /wp-admin | 3.31 ▲0.01 | 46.49 ▼2.70 |
Posts /wp-admin/edit.php | 3.36 ▲0.01 | 44.48 ▼1.89 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 86.50 ▼0.36 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 33.65 ▼1.95 |
Server storage [IO: ▲0.24MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 8 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
widget_recent-comments |
theysaidso_admin_options |
widget_recent-posts |
db_upgraded |
can_compress_scripts |
Browser metrics Passed 4 tests
Checking browser requirements for Awesome Tool Tip
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,802 ▲31 | 13.30 ▼1.06 | 1.92 ▼0.08 | 43.57 ▼1.71 |
Dashboard /wp-admin | 2,206 ▲17 | 4.83 ▼0.15 | 100.72 ▼8.01 | 38.01 ▼0.31 |
Posts /wp-admin/edit.php | 2,086 ▼3 | 2.06 ▲0.07 | 35.31 ▼1.16 | 33.21 ▼4.07 |
Add New Post /wp-admin/post-new.php | 1,533 ▲14 | 23.45 ▲0.35 | 683.51 ▲30.51 | 62.65 ▲3.08 |
Media Library /wp-admin/upload.php | 1,391 ▲6 | 4.18 ▲0.01 | 98.54 ▼4.11 | 42.27 ▼5.91 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
The following items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- db_upgraded
- widget_recent-comments
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
- 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
Even though everything seems fine, this is not 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 fix the following items
- 2× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_basename() in wp-content/plugins/awesome-tool-tip/awesome_tool_tip_main.php:13
- > PHP Warning
Use of undefined constant WP_PLUGIN_URL - assumed 'WP_PLUGIN_URL' (this will throw an Error in a future version of PHP) in wp-content/plugins/awesome-tool-tip/awesome_tool_tip_main.php on line 13
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There were no browser issues found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
Attributes that need to be fixed:
- Contributors: Plugin contributors not specified
- Screenshots: These screenshots require images: #1 (Demo Screenshots 1.), #2 (Demo Screenshots 2.), #3 (admin panel plugin option.)
awesome-tool-tip/awesome_tool_tip_main.php 92% from 13 tests
"Awesome Tool Tip" version 1.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
The following require your attention:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("awesome-tool-tip.php" instead of "awesome_tool_tip_main.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
There were no executable files found in this plugin101 lines of code in 4 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 1 | 15 | 2 | 73 |
PHP | 1 | 20 | 11 | 17 |
SVG | 2 | 0 | 0 | 11 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.00 |
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 | 2 | |
▷ Named functions | 2 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
3 PNG files occupy 0.23MB with 0.15MB in potential savings
Potential savings
Compression of 3 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
Screenshot-3.png | 75.82KB | 29.32KB | ▼ 61.33% |
Screenshot-1.png | 78.69KB | 27.28KB | ▼ 65.34% |
Screenshot-2.png | 80.88KB | 29.31KB | ▼ 63.76% |