Benchmarks
Plugin footprint 58% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
You still need to fix the following installer errors
- This plugin did not install gracefully
- > Parse error in wp-content/plugins/top-button/index.php+104
syntax error, unexpected end of file
Server metrics [RAM: ▲0.00MB] [CPU: ▼1.41ms] Passed 4 tests
An overview of server-side resources used by Top But(ton)
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.46 ▲0.00 | 48.91 ▲3.72 |
Dashboard /wp-admin | 3.31 ▲0.00 | 46.60 ▼1.29 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 47.71 ▲0.56 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 94.30 ▼5.08 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 34.28 ▲0.19 |
Server storage [IO: ▲0.01MB] [DB: ▲0.07MB] Passed 3 tests
Input-output and database impact of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 6 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
db_upgraded |
widget_recent-comments |
theysaidso_admin_options |
widget_theysaidso_widget |
can_compress_scripts |
Browser metrics Passed 4 tests
A check of browser resources used by Top But(ton)
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲65 | 13.22 ▼1.59 | 1.83 ▼0.04 | 43.37 ▼0.10 |
Dashboard /wp-admin | 2,203 ▲18 | 4.87 ▲0.03 | 99.36 ▼7.39 | 40.57 ▼2.04 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.05 ▲0.04 | 38.94 ▲4.08 | 37.97 ▲2.05 |
Add New Post /wp-admin/post-new.php | 1,542 ▲11 | 18.24 ▼5.26 | 596.41 ▲2.53 | 68.49 ▲13.54 |
Media Library /wp-admin/upload.php | 1,391 ▲12 | 4.21 ▼0.02 | 96.28 ▼2.82 | 41.69 ▲0.59 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.07MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
Please fix the following items
- This plugin did not uninstall successfully, leaving 6 options in the database
- theysaidso_admin_options
- widget_recent-posts
- can_compress_scripts
- db_upgraded
- widget_theysaidso_widget
- widget_recent-comments
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
The smoke test was a success, however most plugin functionality was not tested
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
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Parse error
syntax error, unexpected end of file in wp-content/plugins/top-button/index.php on line 104
- > PHP Parse error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine on the user side
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
3 plugin tags: button, top button, scroll
top-button/index.php 92% from 13 tests
This is the main PHP file of "Top But(ton)" version 1.0, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
Please make the necessary changes and fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("top-button.php" instead of "index.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
Everything looks great! No dangerous files found in this plugin121 lines of code in 3 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 24 | 10 | 70 |
CSS | 1 | 2 | 1 | 38 |
JavaScript | 1 | 5 | 0 | 13 |
PHP code Passed 2 tests
Analyzing 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.16 |
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 | 4 | |
▷ Named functions | 4 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 0 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.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/images/up_small.png | 1.08KB | 0.39KB | ▼ 64.23% |
assets/images/up.png | 1.14KB | 0.51KB | ▼ 55.26% |