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
This plugin's installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼5.32ms] Passed 4 tests
An overview of server-side resources used by EventTracking for StatPress
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.46 ▲0.00 | 37.90 ▼1.23 |
| Dashboard /wp-admin | 3.31 ▲0.00 | 43.95 ▲1.47 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 42.69 ▼2.07 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 77.91 ▼19.45 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 35.57 ▲3.78 |
Server storage [IO: ▲0.06MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 16 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-comments |
| db_upgraded |
| theysaidso_admin_options |
| widget_recent-posts |
| widget_theysaidso_widget |
Browser metrics Passed 4 tests
This is an overview of browser requirements for EventTracking for StatPress
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,789 ▲28 | 14.39 ▲0.11 | 2.07 ▲0.39 | 43.77 ▼1.47 |
| Dashboard /wp-admin | 2,198 ▲18 | 5.61 ▼0.03 | 83.15 ▼2.95 | 39.67 ▲1.69 |
| Posts /wp-admin/edit.php | 2,097 ▼3 | 2.03 ▲0.07 | 35.39 ▼7.33 | 32.71 ▼7.52 |
| Add New Post /wp-admin/post-new.php | 1,526 ▼0 | 23.68 ▲0.47 | 677.19 ▲90.43 | 51.84 ▼1.11 |
| Media Library /wp-admin/upload.php | 1,397 ▼6 | 4.21 ▲0.02 | 102.11 ▲6.25 | 42.86 ▲0.06 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- widget_recent-comments
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- widget_recent-posts
- db_upgraded
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
The following issues need your attention
- 2× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function trailingslashit() in wp-content/plugins/eventtracking-for-statpress/dl-checker-function.php:22
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/eventtracking-for-statpress/view/DlCheckerTop.php:2
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There were no browser issues found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 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
These attributes need your attention:
- Plugin Name: Write the name of your plugin instead of "Plugin Name" on the first line (
=== eventtracking-for-statpress ===) - Tested up to: Invalid version format
eventtracking-for-statpress/dl-checker-function.php 92% from 13 tests
Analyzing the main PHP file in "EventTracking for StatPress" version 0.6
It is important to fix the following:
- Main file name: Name the main plugin file the same as the plugin slug ("eventtracking-for-statpress.php" instead of "dl-checker-function.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
Success! There were no dangerous files found in this plugin251 lines of code in 7 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 5 | 86 | 97 | 141 |
| CSS | 1 | 1 | 0 | 70 |
| PO File | 1 | 10 | 2 | 40 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
This plugin has no cyclomatic complexity issues
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.17 |
| Average class complexity | 3.50 |
| ▷ Minimum class complexity | 1.00 |
| ▷ Maximum class complexity | 6.00 |
| Average method complexity | 1.56 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 4.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 2 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 2 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 9 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 9 | 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 | 2 | |
| ▷ Global constants | 2 | 100.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
1 PNG file occupies 0.04MB with 0.04MB in potential savings
Potential savings
| Compression of 1 random PNG file using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| clock-frame.png | 41.24KB | 0.73KB | ▼ 98.22% |