Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Install script ran successfully
Server metrics [RAM: ▲0.03MB] [CPU: ▼4.17ms] Passed 4 tests
A check of server-side resources used by Wp Awesome Timeline
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.50 ▲0.03 | 33.64 ▼4.85 |
Dashboard /wp-admin | 3.33 ▲0.03 | 43.45 ▼2.47 |
Posts /wp-admin/edit.php | 3.38 ▲0.03 | 46.01 ▼3.35 |
Add New Post /wp-admin/post-new.php | 5.91 ▲0.03 | 89.77 ▼6.01 |
Media Library /wp-admin/upload.php | 3.25 ▲0.03 | 33.35 ▼2.40 |
Timelines /wp-admin/edit.php?post_type=wp-timeline | 3.30 | 34.35 |
Add New /wp-admin/post-new.php?post_type=wp-timeline | 3.37 | 46.77 |
Server storage [IO: ▲0.01MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 4 new files
Database: no new tables, 6 new options
New WordPress options |
---|
can_compress_scripts |
widget_recent-posts |
db_upgraded |
widget_theysaidso_widget |
widget_recent-comments |
theysaidso_admin_options |
Browser metrics Passed 4 tests
A check of browser resources used by Wp Awesome Timeline
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,832 ▲86 | 13.27 ▼1.11 | 1.53 ▼0.18 | 44.58 ▲3.47 |
Dashboard /wp-admin | 2,230 ▲39 | 5.77 ▲0.76 | 99.70 ▼1.42 | 39.34 ▼3.76 |
Posts /wp-admin/edit.php | 2,116 ▲24 | 2.06 ▲0.02 | 40.02 ▼0.19 | 36.13 ▼4.51 |
Add New Post /wp-admin/post-new.php | 1,537 ▲23 | 17.47 ▼0.10 | 641.82 ▼40.55 | 55.56 ▲1.12 |
Media Library /wp-admin/upload.php | 1,418 ▲33 | 4.22 ▼0.01 | 97.98 ▼12.99 | 43.68 ▼2.25 |
Timelines /wp-admin/edit.php?post_type=wp-timeline | 1,080 | 1.93 | 33.04 | 29.58 |
Add New /wp-admin/post-new.php?post_type=wp-timeline | 2,163 | 7.56 | 160.90 | 59.68 |
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 did not uninstall successfully, leaving 6 options in the database
- widget_recent-posts
- widget_recent-comments
- db_upgraded
- theysaidso_admin_options
- widget_theysaidso_widget
- can_compress_scripts
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though no errors were found, 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
The following issues need your attention
- 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/wp-awesome-timeline/awesome-timeline.php:13
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser errors were detected
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
Attributes that require attention:
- Screenshots: Please add images for these screenshots: #1 (This is the first screen shot), #2 (This is the second screen shot), #3 (This is the third screen shot), #4 (This is the fourth screen shot), #5 (This is the fifth screen shot)
- Plugin Name: Please specify the plugin name on the first line (
=== wp-awesome-timeline ===
)
wp-awesome-timeline/awesome-timeline.php 92% from 13 tests
The main file in "Wp Awesome Timeline" v. 1.0 serves as a complement to information provided in readme.txt and as the entry point to the plugin
You should first fix the following items:
- Main file name: The principal plugin file should be the same as the plugin slug ("wp-awesome-timeline.php" instead of "awesome-timeline.php")
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
Good job! No executable or dangerous file extensions detected240 lines of code in 2 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 1 | 50 | 3 | 181 |
PHP | 1 | 13 | 7 | 59 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.06 |
Average class complexity | 2.00 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 2.00 |
Average method complexity | 1.25 |
▷ 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 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
No PNG files were detected