Benchmarks
Plugin footprint 82% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Install script ran successfully
Server metrics [RAM: ▲2.48MB] [CPU: ▼283.98ms] Passed 4 tests
Server-side resources used by Woostify Sites Library
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 5.18 ▲1.67 | 73.76 ▲13.59 |
Dashboard /wp-admin | 6.28 ▲2.87 | 57.74 ▲12.02 |
Posts /wp-admin/edit.php | 6.46 ▲2.82 | 63.92 ▲11.97 |
Add New Post /wp-admin/post-new.php | 9.53 ▲2.56 | 138.31 ▼1,173.51 |
Media Library /wp-admin/upload.php | 6.22 ▲2.93 | 61.52 ▲27.45 |
Woostify Sites Library /wp-admin/themes.php?page=woostify-sites | 6.30 | 37.86 |
Server storage [IO: ▲85.61MB] [DB: ▲0.00MB] 67% from 3 tests
Analyzing filesystem and database footprints of this plugin
These are issues you should consider
- Filesystem usage must be lower than 25MB (currently using 85.61MB)
Filesystem: 639 new files
Database: no new tables, 2 new options
New WordPress options |
---|
elementor_disable_typography_schemes |
elementor_disable_color_schemes |
Browser metrics Passed 4 tests
Checking browser requirements for Woostify Sites Library
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 5,035 ▲1,281 | 15.89 ▲0.44 | 7.07 ▲0.19 | 2.53 ▼0.76 |
Dashboard /wp-admin | 4,142 ▲1,255 | 6.44 ▼0.14 | 164.56 ▼10.45 | 184.77 ▼11.91 |
Posts /wp-admin/edit.php | 3,924 ▲1,239 | 3.44 ▲0.01 | 72.70 ▼3.04 | 161.28 ▼11.81 |
Add New Post /wp-admin/post-new.php | 2,881 ▲1,242 | 18.57 ▼1.92 | 526.20 ▼84.03 | 176.01 ▼19.17 |
Media Library /wp-admin/upload.php | 2,920 ▲1,225 | 5.78 ▲0.07 | 171.12 ▼3.98 | 235.57 ▼34.85 |
Woostify Sites Library /wp-admin/themes.php?page=woostify-sites | 1,668 | 2.76 | 35.14 | 92.15 |
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
- This plugin does not fully uninstall, leaving 2 options in the database
- elementor_disable_color_schemes
- elementor_disable_typography_schemes
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though everything seems fine, this is not an exhaustive test
SRP 0% 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 take a closer look at the following
- 1× PHP files output text when accessed directly:
- > /wp-content/plugins/woostify-sites-library/assets/images/spinner.php
- 97× GET requests to PHP files have triggered server-side errors or warnings (only 10 are shown):
- > PHP Fatal error
Uncaught Error: Class 'Monolog\\Handler\\AbstractHandler' not found in wp-content/plugins/woostify-sites-library/vendor/monolog/monolog/src/Monolog/Handler/NullHandler.php:24
- > PHP Fatal error
Uncaught Error: Class 'Monolog\\Formatter\ormalizerFormatter' not found in wp-content/plugins/woostify-sites-library/vendor/monolog/monolog/src/Monolog/Formatter/JsonFormatter.php:25
- > PHP Fatal error
Uncaught Error: Class 'Monolog\\Handler\\AbstractProcessingHandler' not found in wp-content/plugins/woostify-sites-library/vendor/monolog/monolog/src/Monolog/Handler/CouchDBHandler.php:22
- > PHP Fatal error
Uncaught Error: Class 'Monolog\\Formatter\ormalizerFormatter' not found in wp-content/plugins/woostify-sites-library/vendor/monolog/monolog/src/Monolog/Formatter/ScalarFormatter.php:20
- > PHP Fatal error
Uncaught Error: Class 'Monolog\\Handler\\AbstractProcessingHandler' not found in wp-content/plugins/woostify-sites-library/vendor/monolog/monolog/src/Monolog/Handler/LogglyHandler.php:24
- > PHP Fatal error
Uncaught Error: Class 'Monolog\\Formatter\ormalizerFormatter' not found in wp-content/plugins/woostify-sites-library/vendor/monolog/monolog/src/Monolog/Formatter/WildfireFormatter.php:23
- > PHP Fatal error
Uncaught Error: Call to undefined function Woostify\\CTF7\\add_filter() in wp-content/plugins/woostify-sites-library/includes/ctf7/class-import-export.php:51
- > PHP Fatal error
Uncaught Error: Class 'Monolog\\Handler\\SocketHandler' not found in wp-content/plugins/woostify-sites-library/vendor/monolog/monolog/src/Monolog/Handler/SlackHandler.php:25
- > PHP Fatal error
Uncaught Error: Interface 'Monolog\\Processor\\ProcessorInterface' not found in wp-content/plugins/woostify-sites-library/vendor/monolog/monolog/src/Monolog/Processor/TagProcessor.php:19
- > PHP Fatal error
Uncaught Error: Interface 'Monolog\\Processor\\ProcessorInterface' not found in wp-content/plugins/woostify-sites-library/vendor/monolog/monolog/src/Monolog/Processor/UidProcessor.php:21
- > 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)
Everything seems fine on the user side
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 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
3 plugin tags: theme demos, demo, one click import
woostify-sites-library/woostify-sites.php 92% from 13 tests
The main PHP file in "Woostify Sites Library" ver. 1.3.9 adds more information about the plugin and also serves as the entry point for this plugin
It is important to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("woostify-sites-library.php" instead of "woostify-sites.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
There were no executable files found in this plugin272,089 lines of code in 221 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
XML | 19 | 2,747 | 2,319 | 236,645 |
PHP | 145 | 4,414 | 9,242 | 19,460 |
CSS | 8 | 1,204 | 7 | 5,567 |
SVG | 4 | 16 | 6 | 5,529 |
Sass | 27 | 429 | 70 | 2,383 |
JavaScript | 5 | 207 | 53 | 1,117 |
JSON | 8 | 3 | 0 | 761 |
Markdown | 5 | 205 | 0 | 627 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.39 |
Average class complexity | 17.52 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 290.00 |
Average method complexity | 3.17 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 34.00 |
Code structure | ||
---|---|---|
Namespaces | 16 | |
Interfaces | 9 | |
Traits | 4 | |
Classes | 131 | |
▷ Abstract classes | 7 | 5.34% |
▷ Concrete classes | 124 | 94.66% |
▷ Final classes | 1 | 0.81% |
Methods | 1,129 | |
▷ Static methods | 76 | 6.73% |
▷ Public methods | 765 | 67.76% |
▷ Protected methods | 236 | 20.90% |
▷ Private methods | 128 | 11.34% |
Functions | 42 | |
▷ Named functions | 21 | 50.00% |
▷ Anonymous functions | 21 | 50.00% |
Constants | 65 | |
▷ Global constants | 6 | 9.23% |
▷ Class constants | 59 | 90.77% |
▷ Public constants | 59 | 100.00% |
Plugin size 0% from 2 tests
Image compression 0% from 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
17 PNG files occupy 9.14MB with 7.90MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
(invalid) demos/demo-13/demo-13.png | 163.20KB | 0.00KB | ▼ 100.00% |
assets/images/logo-icon.png | 3.79KB | 1.37KB | ▼ 64.02% |
demos/demo-6/demo-6.png | 251.90KB | 81.05KB | ▼ 67.82% |
(invalid) demos/demo-17/demo-17.png | 270.61KB | 0.00KB | ▼ 100.00% |
(invalid) demos/demo-14/demo-14.png | 23.26KB | 0.00KB | ▼ 100.00% |