Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Install script ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼4.61ms] Passed 4 tests
This is a short check of server-side resources used by Special Box for Content
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.03 | 50.60 ▲10.23 |
Dashboard /wp-admin | 3.32 ▲0.01 | 45.26 ▼7.37 |
Posts /wp-admin/edit.php | 3.37 ▲0.01 | 44.37 ▼3.69 |
Add New Post /wp-admin/post-new.php | 5.90 ▲0.01 | 81.54 ▼9.93 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 33.84 ▲2.55 |
Special Box Styling /wp-admin/options-general.php?page=special_box_for_content | 3.21 | 31.57 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 2 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
can_compress_scripts |
widget_recent-posts |
widget_recent-comments |
db_upgraded |
theysaidso_admin_options |
Browser metrics Passed 4 tests
Special Box for Content: an overview of browser usage
There were no issues detected in relation to browser resource usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,806 ▲49 | 13.32 ▼1.06 | 4.35 ▲2.15 | 44.95 ▼4.60 |
Dashboard /wp-admin | 2,210 ▲22 | 4.84 ▼1.06 | 109.77 ▲7.04 | 38.69 ▼1.61 |
Posts /wp-admin/edit.php | 2,093 ▲4 | 2.00 ▼0.06 | 38.95 ▲3.27 | 34.48 ▼1.25 |
Add New Post /wp-admin/post-new.php | 1,517 ▼3 | 17.75 ▼5.27 | 672.39 ▲16.85 | 56.50 ▲9.03 |
Media Library /wp-admin/upload.php | 1,395 ▲10 | 4.23 ▲0.01 | 98.87 ▼4.54 | 43.30 ▼1.98 |
Special Box Styling /wp-admin/options-general.php?page=special_box_for_content | 1,058 | 2.18 | 24.40 | 31.30 |
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
The following items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-posts
- widget_recent-comments
- db_upgraded
- widget_theysaidso_widget
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 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
Please fix the following items
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/special-box-for-content/specialtext.php:22
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
No browser issues were found
Optimizations
Plugin configuration 83% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
These attributes need to be fixed:
- Tags: You are using too many tags: 12 tag instead of maximum 10
- Screenshots: Add a description for screenshot #3 in special-box-for-content/assets to your readme.txt
special-box-for-content/specialtext.php 77% from 13 tests
The main file in "Special Box for Content" v. 1... 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: If Twitter did it, so should we! Keep the description under 140 characters (currently 223 characters long)
- Version: Plugin version number should only contain digits separated by dots (ex. "1.0.3" instead of "1...")
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("special-box-for-content.php" instead of "specialtext.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Everything looks great! No dangerous files found in this plugin173 lines of code in 1 file:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 43 | 12 | 173 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
No cyclomatic complexity issues were detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.00 |
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 | 7 | |
▷ Named functions | 7 | 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 Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
PNG images were not found in this plugin