Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.00MB] [CPU: ▼3.53ms] Passed 4 tests
Analyzing server-side resources used by Disable Core Block Patterns
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.00 | 38.82 ▼3.71 |
Dashboard /wp-admin | 3.31 ▲0.00 | 49.16 ▼0.87 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 54.29 ▼1.16 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 91.46 ▼7.59 |
Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 38.21 ▼1.64 |
Server storage [IO: ▲0.12MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin was installed successfully
Filesystem: 5 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
can_compress_scripts |
db_upgraded |
widget_recent-comments |
theysaidso_admin_options |
widget_recent-posts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Disable Core Block Patterns
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,789 ▲28 | 14.74 ▲0.34 | 2.19 ▲0.35 | 44.78 ▲0.53 |
Dashboard /wp-admin | 2,198 ▲21 | 5.56 ▲0.00 | 90.73 ▼2.53 | 42.32 ▼0.82 |
Posts /wp-admin/edit.php | 2,097 ▼6 | 2.02 ▲0.08 | 39.85 ▲4.96 | 38.63 ▲4.70 |
Add New Post /wp-admin/post-new.php | 1,526 ▼2 | 23.40 ▲0.34 | 664.61 ▼26.02 | 65.41 ▼6.93 |
Media Library /wp-admin/upload.php | 1,400 ▲3 | 4.16 ▼0.03 | 114.10 ▲6.19 | 47.38 ▼0.20 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
The following items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-comments
- widget_theysaidso_widget
- theysaidso_admin_options
- can_compress_scripts
- db_upgraded
- widget_recent-posts
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)
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
Almost there! Just fix the following items
- 1× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/disable-core-block-patterns/disable-core-block-patterns.php:27
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
Attributes that require attention:
- Requires at least: Version not formatted correctly
- Screenshots: These screenshots require images: #1 (After pressing the Plus (+) sign to select a new block or pattern to use in the Block (Gutenberg) editor.), #2 (Selecting the Block Patterns tab which is displaying Core Block Patterns only.), #3 (After activation of Disable Core Block Patterns, the patterns tab is gone. Note: if there are any _non_ Core Block Patterns, the tab is shown including your patterns (excluding Core Block Patterns).)
disable-core-block-patterns/disable-core-block-patterns.php 85% from 13 tests
The entry point to "Disable Core Block Patterns" version 1.0.2 is a PHP file that has certain tags in its header comment area
It is important to fix the following:
- Domain Path: The domain path folder was not found ("/languages")
- Text Domain: You no longer need to specify the text domain since WordPress 4.6; it must be the same as the plugin slug
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short glimpse at programming languages used with this plugin and a check that no dangerous files are present
Success! There were no dangerous files found in this plugin17 lines of code in 1 file:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 5 | 23 | 17 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.20 |
Average class complexity | 1.00 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 1.00 |
Average method complexity | 1.00 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 1.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 | 3 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 3 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 0 | |
▷ Named functions | 0 | 0.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 Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
3 PNG files occupy 0.12MB with 0.08MB in potential savings
Potential savings
Compression of 3 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-2.png | 76.41KB | 22.83KB | ▼ 70.12% |
screenshot-3.png | 22.57KB | 9.06KB | ▼ 59.86% |
screenshot-1.png | 24.30KB | 10.22KB | ▼ 57.93% |