Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▲0.05MB] [CPU: ▼10.99ms] Passed 4 tests
Analyzing server-side resources used by woo-popup
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.43 ▼0.04 | 26.56 ▼17.33 |
Dashboard /wp-admin | 3.38 ▲0.08 | 49.82 ▼7.26 |
Posts /wp-admin/edit.php | 3.50 ▲0.14 | 55.04 ▼3.71 |
Add New Post /wp-admin/post-new.php | 5.96 ▲0.08 | 89.60 ▼15.66 |
Media Library /wp-admin/upload.php | 3.31 ▲0.08 | 45.08 ▲5.69 |
Server storage [IO: ▲0.56MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin installed successfully
Filesystem: 87 new files
Database: no new tables, 7 new options
New WordPress options |
---|
widget_recent-comments |
can_compress_scripts |
woo-popup_options |
theysaidso_admin_options |
db_upgraded |
widget_theysaidso_widget |
widget_recent-posts |
Browser metrics Passed 4 tests
Checking browser requirements for woo-popup
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,807 ▲61 | 14.11 ▼0.09 | 1.68 ▼0.18 | 39.90 ▼3.14 |
Dashboard /wp-admin | 2,214 ▲34 | 5.65 ▲0.10 | 92.91 ▲5.21 | 38.78 ▼0.68 |
Posts /wp-admin/edit.php | 2,116 ▲13 | 2.00 ▲0.04 | 40.24 ▼0.51 | 35.29 ▼0.00 |
Add New Post /wp-admin/post-new.php | 1,539 ▲11 | 23.05 ▼0.08 | 691.55 ▼11.44 | 65.46 ▼1.46 |
Media Library /wp-admin/upload.php | 1,410 ▲10 | 4.20 ▼0.08 | 97.90 ▼9.36 | 42.72 ▼4.02 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
These items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-posts
- db_upgraded
- widget_recent-comments
- widget_theysaidso_widget
- can_compress_scripts
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
The following issues need your attention
- 2× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function get_option() in wp-content/plugins/woo-popup/public/views/public.php:18
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_html() in wp-content/plugins/woo-popup/admin/views/admin.php:19
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser errors were detected
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
Attributes that require attention:
- Screenshots: Please add an image for screenshot #1 (No screenshots yet)
woo-popup/woo-popup.php 92% from 13 tests
This is the main PHP file of "woo-popup" version 1.3.4, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
You should first fix the following items:
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
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
No dangerous file extensions were detected937 lines of code in 17 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 7 | 140 | 390 | 470 |
CSS | 3 | 9 | 2 | 178 |
SVG | 2 | 0 | 0 | 112 |
PO File | 2 | 14 | 14 | 89 |
JavaScript | 3 | 14 | 12 | 88 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
There were no cyclomatic complexity issued detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.30 |
Average class complexity | 18.00 |
▷ Minimum class complexity | 11.00 |
▷ Maximum class complexity | 25.00 |
Average method complexity | 2.31 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 8.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 | 26 | |
▷ Static methods | 7 | 26.92% |
▷ Public methods | 21 | 80.77% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 5 | 19.23% |
Functions | 0 | |
▷ Named functions | 0 | 0.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 1 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 1 | 100.00% |
▷ Public constants | 1 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
34 PNG files occupy 0.34MB with 0.10MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
public/assets/images/chosen-sprite@2x.png | 0.85KB | 0.83KB | ▼ 2.99% |
public/assets/images/prettyPhoto/light_rounded/btnNext.png | 1.38KB | 1.14KB | ▼ 17.29% |
public/assets/images/prettyPhoto/dark_rounded/contentPattern.png | 0.13KB | 0.09KB | ▼ 25.38% |
public/assets/images/prettyPhoto/default/default_thumb.png | 1.50KB | 0.61KB | ▼ 59.47% |
public/assets/images/prettyPhoto/facebook/sprite.png | 4.13KB | 2.26KB | ▼ 45.33% |