Benchmarks
Plugin footprint 82% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.03MB] [CPU: ▼3.36ms] Passed 4 tests
An overview of server-side resources used by Cursor Trail
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 38.07 ▼1.46 |
Dashboard /wp-admin | 3.34 ▲0.03 | 48.92 ▼1.88 |
Posts /wp-admin/edit.php | 3.39 ▲0.03 | 57.02 ▲2.09 |
Add New Post /wp-admin/post-new.php | 5.92 ▲0.03 | 92.36 ▼10.14 |
Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 39.23 ▲0.05 |
Cursor Trail /wp-admin/options-general.php?page=cursor-trail | 3.23 | 32.71 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] 67% from 3 tests
How much does this plugin use your filesystem and database?
It is recommended to fix the following issues
- Illegal file modification detected: 1 file (4.00KB) outside of "wp-content/plugins/cursor-trail/" and "wp-content/uploads/"
- (new file) wp-content/mgd_mirror/mgd_maximinodotpy-gitdown-test-repository
Filesystem: 5 new files
Database: no new tables, 7 new options
New WordPress options |
---|
theysaidso_admin_options |
can_compress_scripts |
db_upgraded |
widget_theysaidso_widget |
widget_recent-comments |
widget_recent-posts |
cursor_trail_options |
Browser metrics Passed 4 tests
An overview of browser requirements for Cursor Trail
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,822 ▲61 | 13.26 ▼0.98 | 2.02 ▲0.21 | 46.45 ▲1.49 |
Dashboard /wp-admin | 2,225 ▲22 | 4.89 ▼1.00 | 111.51 ▲7.12 | 43.58 ▼3.37 |
Posts /wp-admin/edit.php | 2,104 ▲4 | 1.99 ▼0.00 | 39.78 ▲2.54 | 38.34 ▲3.52 |
Add New Post /wp-admin/post-new.php | 1,548 ▲22 | 23.34 ▲5.71 | 662.30 ▼57.58 | 61.71 ▲1.03 |
Media Library /wp-admin/upload.php | 1,404 ▲4 | 4.22 ▲0.00 | 96.58 ▼6.45 | 45.64 ▲0.37 |
Cursor Trail /wp-admin/options-general.php?page=cursor-trail | 988 | 2.05 | 27.83 | 49.42 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
You still need to fix the following
- Zombie WordPress options were found after uninstall: 7 options
- widget_theysaidso_widget
- db_upgraded
- widget_recent-comments
- widget_recent-posts
- theysaidso_admin_options
- cursor_trail_options
- can_compress_scripts
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
- 2× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/cursor-trail/cursor-trail.php:59
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/cursor-trail/cursor-trail-admin.php:6
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
There were no browser issues found
Optimizations
Plugin configuration 97% 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 require attention:
- Screenshots: A description for screenshot #2 is required in cursor-trail/assets to your readme.txt
cursor-trail/cursor-trail.php Passed 13 tests
The primary PHP file in "Cursor Trail" version 1.1 is used by WordPress to initiate all plugin functionality
84 characters long description:
Add a cursor trail to your website mouse pointer, with custom pointer image and url.
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
Success! There were no dangerous files found in this plugin195 lines of code in 2 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 11 | 25 | 195 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
This plugin has no cyclomatic complexity problems
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.37 |
Average class complexity | 12.00 |
▷ Minimum class complexity | 12.00 |
▷ Maximum class complexity | 12.00 |
Average method complexity | 3.75 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 12.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 1 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 1 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 4 | |
▷ Static methods | 4 | 100.00% |
▷ Public methods | 4 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 2 | |
▷ Named functions | 2 | 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
PNG files should be compressed to save space and minimize bandwidth usage
2 compressed PNG files occupy 0.00MB
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
valentines.png | 0.41KB | 0.32KB | ▼ 21.43% |
pointer.png | 0.27KB | 0.32KB | 0.00% |