Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Installer ran successfully
Server metrics [RAM: ▲0.11MB] [CPU: ▼6.70ms] Passed 4 tests
An overview of server-side resources used by EyeOne
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.53 ▲0.07 | 32.35 ▼9.89 |
Dashboard /wp-admin | 3.41 ▲0.10 | 54.79 ▼1.26 |
Posts /wp-admin/edit.php | 3.52 ▲0.17 | 55.97 ▼0.66 |
Add New Post /wp-admin/post-new.php | 6.02 ▲0.14 | 94.90 ▼14.99 |
Media Library /wp-admin/upload.php | 3.35 ▲0.12 | 43.11 ▲4.80 |
Server storage [IO: ▲0.07MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
The plugin installed successfully
Filesystem: 25 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
db_upgraded |
theysaidso_admin_options |
widget_theysaidso_widget |
widget_recent-comments |
can_compress_scripts |
Browser metrics Passed 4 tests
An overview of browser requirements for EyeOne
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,830 ▲69 | 14.22 ▼0.13 | 2.41 ▲0.50 | 37.24 ▼4.53 |
Dashboard /wp-admin | 2,239 ▲71 | 5.64 ▼0.02 | 89.78 ▼10.70 | 42.68 ▼3.22 |
Posts /wp-admin/edit.php | 2,148 ▲48 | 2.00 ▲0.00 | 40.74 ▼1.73 | 33.01 ▼5.26 |
Add New Post /wp-admin/post-new.php | 6,254 ▲4,725 | 25.89 ▲2.32 | 889.62 ▲302.77 | 53.96 ▲3.64 |
Media Library /wp-admin/upload.php | 1,441 ▲41 | 4.21 ▲0.03 | 103.59 ▼4.54 | 43.06 ▼1.63 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- db_upgraded
- widget_theysaidso_widget
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Please fix the following
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html_e() in wp-content/plugins/eyeone/admin/partials/eyeone-admin-settings-display.php:8
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser issues were found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is undoubtedly the most important file in your plugin, preparing it for public listing on WordPress.org
These attributes need to be fixed:
- Contributors: Contributors not specified
- Screenshots: Please add descriptions for these screenshots #1, #2, #3, #4 in eyeone/assets to your readme.txt
eyeone/eyeone-plugin.php 92% from 13 tests
"EyeOne" version 1.1.0's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
You should first fix the following items:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("eyeone.php" instead of "eyeone-plugin.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
Good job! No executable or dangerous file extensions detected814 lines of code in 18 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 11 | 97 | 58 | 574 |
PO File | 1 | 28 | 0 | 101 |
CSS | 1 | 15 | 0 | 76 |
JavaScript | 2 | 4 | 1 | 37 |
SVG | 3 | 0 | 2 | 26 |
PHP code Passed 2 tests
A brief analysis of cyclomatic complexity and code structure for this plugin
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.31 |
Average class complexity | 7.43 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 40.00 |
Average method complexity | 2.18 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 18.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 7 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 7 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 38 | |
▷ Static methods | 2 | 5.26% |
▷ Public methods | 33 | 86.84% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 5 | 13.16% |
Functions | 5 | |
▷ Named functions | 5 | 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
PNG images were not found in this plugin