Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
This plugin's installer ran successfully
Server metrics [RAM: ▼0.16MB] [CPU: ▼154.37ms] Passed 4 tests
This is a short check of server-side resources used by Before After Content
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.85 ▲0.13 | 37.23 ▲7.62 |
| Dashboard /wp-admin | 2.98 ▼0.08 | 34.30 ▼14.44 |
| Posts /wp-admin/edit.php | 3.04 ▼0.07 | 34.68 ▼16.33 |
| Add New Post /wp-admin/post-new.php | 4.98 ▼0.46 | 83.09 ▼583.05 |
| Media Library /wp-admin/upload.php | 2.99 ▼0.02 | 30.66 ▼3.64 |
Server storage [IO: ▲0.93MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
No storage issues were detected
Filesystem: 19 new files
Database: no new tables, 1 new option
| New WordPress options |
|---|
| recovery_mode_email_last_sent |
Browser metrics Passed 4 tests
Before After Content: an overview of browser usage
This plugin renders optimally with no browser resource issues detected
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 1,875 ▼1,697 | 13.25 ▼2.08 | 11.39 ▼0.89 | 59.07 ▲4.87 |
| Dashboard /wp-admin | 1,119 ▼1,812 | 2.11 ▼3.81 | 47.55 ▼113.48 | 48.91 ▼89.96 |
| Posts /wp-admin/edit.php | 1,148 ▼1,591 | 1.87 ▼0.83 | 35.27 ▼32.96 | 49.34 ▼54.52 |
| Add New Post /wp-admin/post-new.php | 609 ▼1,074 | 2.20 ▼16.56 | 19.06 ▼371.00 | 22.64 ▼105.12 |
| Media Library /wp-admin/upload.php | 961 ▼846 | 2.25 ▼2.78 | 48.84 ▼114.66 | 54.40 ▼76.56 |
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
These items require your attention
- This plugin did not uninstall successfully, leaving 1 option in the database
- recovery_mode_email_last_sent
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
Good news, no errors were detected
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
Please fix the following
- 2× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/before-after-content/includes/options.php:5
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/before-after-content/includes/scripts-enque.php:11
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
There were no browser issues found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
You should put a lot of thought into formatting readme.txt as it is used by WordPress.org to prepare the public listing of your plugin
Please fix the following attributes:
- Plugin Name: Please replace "Plugin Name" with the name of your plugin on the first line (
=== before-after-content ===) - Screenshots: Please add images for these screenshots: #1 (After Content Image Example), #2 (After Content Example), #3 (Before Content Image Example), #4 (Before Content Example), #5 (Control Panel Example One), #6 (Control Panel Example Two)
before-after-content/before-after-content.php 92% from 13 tests
The main file in "Before After Content" v. 2.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
Please make the necessary changes and fix the following:
- Description: The description should be shorter than 140 characters (currently 215 characters long)
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of programming languages used in this plugin; dangerous file extensions are not allowed
No dangerous file extensions were detected539 lines of code in 8 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 7 | 68 | 44 | 481 |
| CSS | 1 | 15 | 6 | 58 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.22 |
| Average class complexity | 3.00 |
| ▷ Minimum class complexity | 3.00 |
| ▷ Maximum class complexity | 3.00 |
| Average method complexity | 1.50 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 2.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 1 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 1 | 100.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 4 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 4 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 11 | |
| ▷ Named functions | 11 | 100.00% |
| ▷ Anonymous functions | 0 | 0.00% |
| Constants | 4 | |
| ▷ Global constants | 4 | 100.00% |
| ▷ Class constants | 0 | 0.00% |
| ▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
All PNG images should be compressed to minimize bandwidth usage for end users
6 PNG files occupy 0.89MB with 0.62MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-4.png | 74.79KB | 22.81KB | ▼ 69.50% |
| screenshot-3.png | 170.67KB | 49.94KB | ▼ 70.74% |
| screenshot-6.png | 177.22KB | 53.72KB | ▼ 69.69% |
| screenshot-1.png | 174.42KB | 54.67KB | ▼ 68.66% |
| screenshot-5.png | 183.67KB | 56.35KB | ▼ 69.32% |