Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Installer ran successfully
Server metrics [RAM: ▲0.04MB] [CPU: ▼2.67ms] Passed 4 tests
Analyzing server-side resources used by Fixed Future Posts
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.51 ▲0.05 | 42.15 ▼5.01 |
Dashboard /wp-admin | 3.34 ▲0.04 | 44.16 ▼6.63 |
Posts /wp-admin/edit.php | 3.39 ▲0.04 | 45.13 ▼1.28 |
Add New Post /wp-admin/post-new.php | 5.92 ▲0.04 | 92.46 ▲2.26 |
Media Library /wp-admin/upload.php | 3.26 ▲0.03 | 35.92 ▲3.18 |
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 |
---|
db_upgraded |
can_compress_scripts |
widget_theysaidso_widget |
widget_recent-posts |
widget_recent-comments |
theysaidso_admin_options |
Browser metrics Passed 4 tests
Checking browser requirements for Fixed Future Posts
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲43 | 13.20 ▼1.08 | 4.39 ▲2.09 | 43.70 ▼3.23 |
Dashboard /wp-admin | 2,206 ▲21 | 4.78 ▼0.33 | 103.00 ▼11.80 | 38.44 ▼6.02 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.03 ▼0.00 | 34.62 ▼2.88 | 32.76 ▼0.81 |
Add New Post /wp-admin/post-new.php | 1,533 ▼9 | 23.28 ▲5.14 | 648.46 ▲7.65 | 49.60 ▼18.09 |
Media Library /wp-admin/upload.php | 1,388 ▲6 | 4.24 ▼0.02 | 96.30 ▼5.99 | 40.85 ▼3.55 |
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
- Zombie WordPress options were found after uninstall: 6 options
- can_compress_scripts
- db_upgraded
- theysaidso_admin_options
- widget_recent-posts
- widget_theysaidso_widget
- widget_recent-comments
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
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Almost there! Just 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/fixed-future-posts/fixed-future-posts.php:73
- > 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, but this is not an exhaustive test
Optimizations
Plugin configuration 93% from 29 tests
readme.txt Passed 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
2 plugin tags: posts, future
fixed-future-posts/fixed-future-posts.php 85% from 13 tests
The principal PHP file in "Fixed Future Posts" v. 1.0.0 is loaded by WordPress automatically on each request
It is important to fix the following:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 141 characters long)
- Domain Path: The domain path folder does not exist ("/languages")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
There were no executable files found in this plugin163 lines of code in 1 file:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 1 | 21 | 163 |
PHP code Passed 2 tests
An overview 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.89 |
Average class complexity | 58.00 |
▷ Minimum class complexity | 58.00 |
▷ Maximum class complexity | 58.00 |
Average method complexity | 6.18 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 16.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 | 11 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 8 | 72.73% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 3 | 27.27% |
Functions | 0 | |
▷ Named functions | 0 | 0.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 6 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 6 | 100.00% |
▷ Public constants | 6 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
There were not PNG files found in your plugin