Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.01MB] [CPU: ▼8.95ms] Passed 4 tests
A check of server-side resources used by WoPo Web Screensaver
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 38.19 ▼0.17 |
Dashboard /wp-admin | 3.31 ▲0.01 | 43.76 ▼2.30 |
Posts /wp-admin/edit.php | 3.36 ▲0.01 | 39.52 ▼11.08 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 83.56 ▼22.25 |
Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 34.53 ▲0.75 |
Server storage [IO: ▲1.64MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin was installed successfully
Filesystem: 25 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
widget_recent-comments |
theysaidso_admin_options |
db_upgraded |
can_compress_scripts |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
WoPo Web Screensaver: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,825 ▲79 | 13.26 ▼1.04 | 2.00 ▲0.31 | 44.37 ▼0.34 |
Dashboard /wp-admin | 2,203 ▲15 | 5.86 ▼0.03 | 99.08 ▲0.05 | 40.38 ▼2.33 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.02 ▼0.02 | 35.74 ▼5.94 | 31.35 ▼3.69 |
Add New Post /wp-admin/post-new.php | 1,533 ▲19 | 23.20 ▲5.60 | 655.51 ▼8.35 | 54.42 ▼1.03 |
Media Library /wp-admin/upload.php | 1,388 ▼3 | 4.22 ▼0.01 | 98.05 ▲2.23 | 41.04 ▼5.49 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
Please fix the following items
- This plugin does not fully uninstall, leaving 6 options in the database
- can_compress_scripts
- widget_recent-comments
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- 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)
Even though everything seems fine, this is not an exhaustive test
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
- 1× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wopo-web-screensaver/wopo-web-screensaver.php:21
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Everything seems fine on the user side
Optimizations
Plugin configuration 86% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
These attributes need to be fixed:
- Tags: Please delete some tags, you are using 11 tag instead of maximum 10
wopo-web-screensaver/wopo-web-screensaver.php 77% from 13 tests
The primary PHP file in "WoPo Web Screensaver" version 1.0.0 is used by WordPress to initiate all plugin functionality
It is important to fix the following:
- Requires PHP: Required version must match the one declared in readme.txt ("5.2.4" instead of "7.1")
- Requires at least: Required version must match the one declared in readme.txt ("4.6" instead of "5.2")
- Domain Path: The domain path folder was not found ("/languages")
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
Everything looks great! No dangerous files found in this plugin3,480 lines of code in 13 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 6 | 636 | 292 | 2,507 |
JSON | 3 | 0 | 0 | 713 |
HTML | 1 | 0 | 4 | 163 |
Markdown | 1 | 41 | 0 | 45 |
PHP | 1 | 4 | 14 | 29 |
CSS | 1 | 0 | 0 | 23 |
PHP code Passed 2 tests
Analyzing logical lines of code, cyclomatic complexity, and other code metrics
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.25 |
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 | 3 | |
▷ Named functions | 3 | 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 50% from 2 tests
Image compression 50% from 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
4 PNG files occupy 0.51MB with 0.18MB in potential savings
Potential savings
Compression of 4 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
html/app/images/meta/icon-32x32.png | 0.42KB | 0.26KB | ▼ 38.14% |
html/app/images/textures/candycane.png | 0.53KB | 0.39KB | ▼ 26.33% |
html/app/images/meta/icon-16x16.png | 0.25KB | 0.19KB | ▼ 25.77% |
html/app/images/textures/rusty.png | 518.93KB | 249.70KB | ▼ 51.88% |