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
Installer ran successfully
Server metrics [RAM: ▼0.00MB] [CPU: ▼5.59ms] Passed 4 tests
Analyzing server-side resources used by Better Datelines
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.01 | 38.66 ▼1.43 |
| Dashboard /wp-admin | 3.31 ▼0.03 | 43.99 ▼16.93 |
| Posts /wp-admin/edit.php | 3.36 ▲0.01 | 46.32 ▲1.15 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 92.50 ▼5.13 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 36.88 ▲3.54 |
Server storage [IO: ▲0.28MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
This plugin installed successfully
Filesystem: 5 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| can_compress_scripts |
| theysaidso_admin_options |
| widget_recent-comments |
| db_upgraded |
| widget_recent-posts |
Browser metrics Passed 4 tests
Checking browser requirements for Better Datelines
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲54 | 13.26 ▼1.03 | 1.81 ▼0.02 | 43.23 ▼0.82 |
| Dashboard /wp-admin | 2,206 ▲17 | 4.84 ▼0.21 | 107.59 ▼2.85 | 44.66 ▲1.04 |
| Posts /wp-admin/edit.php | 2,089 ▼0 | 2.05 ▼0.01 | 39.80 ▲4.49 | 34.71 ▼4.15 |
| Add New Post /wp-admin/post-new.php | 1,519 ▼0 | 23.12 ▼0.08 | 660.51 ▼10.40 | 51.51 ▼14.20 |
| Media Library /wp-admin/upload.php | 1,391 ▼0 | 4.21 ▼0.02 | 95.03 ▼9.07 | 42.89 ▼4.44 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
It is recommended to fix the following
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
- db_upgraded
- widget_recent-comments
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
The smoke test was a success, however most plugin functionality was not tested
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 take a closer look at the following
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/better-datelines/better-datelines.php:26
- > 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)
No browser errors were detected
Optimizations
Plugin configuration 97% from 29 tests
readme.txt 94% from 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
These attributes need to be fixed:
- Screenshots: Screenshot #1 (Screenshot of a post with a dateline) image required
better-datelines/better-datelines.php Passed 13 tests
"Better Datelines" version 0.1's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
106 characters long description:
Use meta field to store dateline so that datelines aren't included in autoexcerpts and the_content as well
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
Everything looks great! No dangerous files found in this plugin54 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 17 | 37 | 49 |
| Markdown | 1 | 4 | 0 | 5 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.24 |
| Average class complexity | 7.00 |
| ▷ Minimum class complexity | 7.00 |
| ▷ Maximum class complexity | 7.00 |
| Average method complexity | 2.00 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 4.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 | 6 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 6 | 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 | 3 | |
| ▷ Global constants | 0 | 0.00% |
| ▷ Class constants | 3 | 100.00% |
| ▷ Public constants | 3 | 100.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Often times overlooked, PNG files can occupy unnecessary space in your plugin
2 PNG files occupy 0.27MB with 0.19MB in potential savings
Potential savings
| Compression of 2 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| screenshot-2.png | 116.19KB | 34.17KB | ▼ 70.60% |
| screenshot-1.png | 164.81KB | 57.52KB | ▼ 65.10% |