Benchmarks
Plugin footprint Passed 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: ▲0.25MB] [CPU: ▼135.78ms] Passed 4 tests
A check of server-side resources used by Postem Ipsum
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.09 ▲0.25 | 38.72 ▲5.56 |
Dashboard /wp-admin | 3.32 ▲0.26 | 46.95 ▲1.53 |
Posts /wp-admin/edit.php | 3.43 ▲0.32 | 48.10 ▲6.00 |
Add New Post /wp-admin/post-new.php | 5.68 ▲0.25 | 92.82 ▼551.74 |
Media Library /wp-admin/upload.php | 3.26 ▲0.25 | 36.75 ▲1.55 |
Taxonomy terms /wp-admin/admin.php?page=postem-ipsum-terms-settings | 3.25 | 31.34 |
Users /wp-admin/admin.php?page=postem-ipsum-users-settings | 3.25 | 30.81 |
Generic Posts /wp-admin/admin.php?page=postem-ipsum-general-settings | 3.32 | 32.25 |
Server storage [IO: ▲0.34MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin installed successfully
Filesystem: 31 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
This is an overview of browser requirements for Postem Ipsum
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,754 ▲158 | 15.76 ▲0.15 | 9.68 ▲0.22 | 50.86 ▲3.96 |
Dashboard /wp-admin | 3,012 ▲81 | 5.91 ▼0.36 | 143.54 ▲0.59 | 113.75 ▼2.35 |
Posts /wp-admin/edit.php | 2,778 ▲39 | 2.72 ▲0.00 | 64.24 ▲3.54 | 93.54 ▲6.43 |
Add New Post /wp-admin/post-new.php | 1,708 ▲208 | 18.71 ▲0.14 | 372.38 ▼2.31 | 106.39 ▼7.35 |
Media Library /wp-admin/upload.php | 1,846 ▲39 | 5.03 ▼0.02 | 142.79 ▼15.01 | 123.56 ▼1.89 |
Taxonomy terms /wp-admin/admin.php?page=postem-ipsum-terms-settings | 1,263 | 3.12 | 60.34 | 86.04 |
Users /wp-admin/admin.php?page=postem-ipsum-users-settings | 1,258 | 2.90 | 60.54 | 87.36 |
Generic Posts /wp-admin/admin.php?page=postem-ipsum-general-settings | 2,338 | 2.64 | 83.13 | 89.57 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
This plugin's uninstaller ran successfully
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 no errors were found, this is by no means an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Almost there! Just fix the following items
- 1× PHP files output non-empty strings when accessed directly via GET requests:
- > /wp-content/plugins/postem-ipsum/admin/views/notice.php
- 3× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/postem-ipsum/admin/views/postem_ipsum_woo_settings.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/postem-ipsum/admin/views/postem_ipsum_get_taxonomies.php:1
- > PHP Fatal error
Uncaught Error: Call to undefined function _e() in wp-content/plugins/postem-ipsum/admin/views/postem_ipsum_get_terms.php:1
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
Attributes that need to be fixed:
- Screenshots: Add descriptions for screenshots #1, #2, #3, #4 in postem-ipsum/assets to your readme.txt
postem-ipsum/postem-ipsum.php Passed 13 tests
The principal PHP file in "Postem Ipsum" v. 3.0.1 is loaded by WordPress automatically on each request
47 characters long description:
Plugin to create some random posts from scratch
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
There were no executable files found in this plugin6,230 lines of code in 25 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JavaScript | 3 | 872 | 459 | 2,773 |
PHP | 16 | 552 | 166 | 2,072 |
CSS | 3 | 82 | 176 | 1,048 |
PO File | 2 | 148 | 268 | 326 |
Markdown | 1 | 2 | 0 | 11 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.25 |
Average class complexity | 85.50 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 170.00 |
Average method complexity | 5.12 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 69.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 | 41 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 40 | 97.56% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 1 | 2.44% |
Functions | 2 | |
▷ Named functions | 2 | 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
PNG files should be compressed to save space and minimize bandwidth usage
1 PNG file occupies 0.02MB with 0.01MB in potential savings
Potential savings
Compression of 1 random PNG file using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot.4.png | 18.75KB | 7.81KB | ▼ 58.34% |