Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▼6.14ms] Passed 4 tests
A check of server-side resources used by Enduring Word Bible Commentary
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.49 ▲0.03 | 42.25 ▲2.33 |
Dashboard /wp-admin | 3.33 ▲0.03 | 52.87 ▲6.38 |
Posts /wp-admin/edit.php | 3.38 ▲0.02 | 45.81 ▼4.41 |
Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 84.59 ▼19.41 |
Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 35.04 ▼3.06 |
Server storage [IO: ▲0.71MB] [DB: ▲0.10MB] Passed 3 tests
A short overview of filesystem and database impact
There were no storage issued detected upon installing this plugin
Filesystem: 32 new files
Database: 1 new table, 6 new options
New tables |
---|
wp_enduringword |
New WordPress options |
---|
widget_recent-comments |
widget_theysaidso_widget |
widget_recent-posts |
can_compress_scripts |
db_upgraded |
theysaidso_admin_options |
Browser metrics Passed 4 tests
Enduring Word Bible Commentary: an overview of browser usage
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,926 ▲191 | 13.70 ▼0.86 | 7.93 ▲6.34 | 42.26 ▼0.43 |
Dashboard /wp-admin | 2,220 ▲31 | 4.91 ▼0.04 | 96.93 ▼13.42 | 76.09 ▲35.69 |
Posts /wp-admin/edit.php | 2,100 ▲8 | 2.06 ▲0.02 | 35.81 ▼3.74 | 32.63 ▼1.65 |
Add New Post /wp-admin/post-new.php | 1,677 ▲144 | 20.05 ▼2.99 | 709.92 ▲72.82 | 63.11 ▲10.77 |
Media Library /wp-admin/upload.php | 1,396 ▲5 | 4.11 ▼0.07 | 98.37 ▼3.60 | 65.49 ▲23.05 |
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
These items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_theysaidso_widget
- theysaidso_admin_options
- db_upgraded
- can_compress_scripts
- widget_recent-posts
- widget_recent-comments
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Even though everything seems fine, this is not an exhaustive test
SRP 0% from 2 tests
🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please take a closer look at the following
- 1× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/enduring-word-bible-commentary/enduring_word.php
- 7× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to a member function query() on null in wp-content/plugins/enduring-word-bible-commentary/Includes/end_word_insert_enduringword_bible.php:7
- > PHP Notice
Trying to get property 'prefix' of non-object in wp-content/plugins/enduring-word-bible-commentary/Includes/end_word_insert_enduringword_bible.php on line 4
- > PHP Warning
Use of undefined constant ENDURINGWORD_MEDIA_URL - assumed 'ENDURINGWORD_MEDIA_URL' (this will throw an Error in a future version of PHP) in wp-content/plugins/enduring-word-bible-commentary/Templates/admin-settings.php on line 3
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/enduring-word-bible-commentary/Includes/end_word_function.php:22
- > PHP Warning
Use of undefined constant ENDURINGWORD_MEDIA_URL - assumed 'ENDURINGWORD_MEDIA_URL' (this will throw an Error in a future version of PHP) in wp-content/plugins/enduring-word-bible-commentary/Templates/end_word_widget.php on line 3
- > PHP Fatal error
Uncaught Error: Call to undefined function settings_fields() in wp-content/plugins/enduring-word-bible-commentary/Templates/admin-settings.php:6
- > PHP Fatal error
Uncaught Error: Call to undefined function esc_attr() in wp-content/plugins/enduring-word-bible-commentary/Templates/end_word_widget.php:5
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
There were no browser issues found
Optimizations
Plugin configuration 90% 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
10 plugin tags: commentary, enduring word, david, chapter, verse...
enduring-word-bible-commentary/enduring_word.php 77% from 13 tests
"Enduring Word Bible Commentary" version 1.2.0's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
Please take the time to fix the following:
- Text Domain: The text domain follows the same naming rules as the plugin slug: lowercase characters and dashes
- Description: Keep the plugin description shorter than 140 characters (currently 143 characters long)
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("enduring-word-bible-commentary.php" instead of "enduring_word.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short review of files and their extensions; it is not recommended to include executable files
Everything looks great! No dangerous files found in this plugin1,562 lines of code in 10 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 5 | 32 | 10 | 1,475 |
CSS | 3 | 9 | 2 | 53 |
JavaScript | 2 | 0 | 5 | 34 |
PHP code Passed 2 tests
This is a very shot review of cyclomatic complexity and code structure
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.30 |
Average class complexity | 2.00 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 2.00 |
Average method complexity | 1.07 |
▷ 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 | 14 | |
▷ Static methods | 3 | 21.43% |
▷ Public methods | 12 | 85.71% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 2 | 14.29% |
Functions | 4 | |
▷ Named functions | 4 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 6 | |
▷ Global constants | 6 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size 50% from 2 tests
Image compression 50% from 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
19 PNG files occupy 0.54MB with 0.38MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
Screenshots/screenshot-2.png | 39.10KB | 11.62KB | ▼ 70.28% |
Screenshots/screenshot-5.png | 91.73KB | 25.14KB | ▼ 72.60% |
Assets/media/enduring-word-logo.png | 18.17KB | 7.29KB | ▼ 59.90% |
Assets/media/close.png | 4.00KB | 1.38KB | ▼ 65.45% |
Assets/media/radio-btn.png | 5.60KB | 0.66KB | ▼ 88.24% |