Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
This plugin's installer ran successfully
Server metrics [RAM: ▲0.05MB] [CPU: ▼4.13ms] Passed 4 tests
Server-side resources used by WP Intro.JS Plugin
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.52 ▲0.06 | 39.86 ▲1.24 |
| Dashboard /wp-admin | 3.38 ▲0.03 | 48.32 ▼10.33 |
| Posts /wp-admin/edit.php | 3.41 ▲0.05 | 49.78 ▲6.04 |
| Add New Post /wp-admin/post-new.php | 5.96 ▲0.07 | 78.61 ▼5.25 |
| Media Library /wp-admin/upload.php | 3.30 ▲0.07 | 32.57 ▼2.16 |
Server storage [IO: ▲0.21MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
There were no storage issued detected upon installing this plugin
Filesystem: 15 new files
Database: 1 new table, 8 new options
| New tables |
|---|
| wp_wpintrojs_tours |
| New WordPress options |
|---|
| db_upgraded |
| can_compress_scripts |
| widget_recent-posts |
| theysaidso_admin_options |
| widget_theysaidso_widget |
| wpintrojs_page_register |
| wpintrojs_db_version |
| widget_recent-comments |
Browser metrics Passed 4 tests
This is an overview of browser requirements for WP Intro.JS Plugin
This plugin has a minimal impact on browser resources
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,946 ▲200 | 13.98 ▼0.38 | 10.40 ▲8.80 | 41.77 ▲2.85 |
| Dashboard /wp-admin | 2,224 ▲44 | 5.59 ▲0.02 | 95.83 ▲8.36 | 42.12 ▲1.89 |
| Posts /wp-admin/edit.php | 2,136 ▲36 | 2.28 ▲0.26 | 38.94 ▲2.60 | 35.70 ▼1.05 |
| Add New Post /wp-admin/post-new.php | 1,556 ▲30 | 23.30 ▼0.07 | 663.62 ▼9.77 | 37.46 ▼22.41 |
| Media Library /wp-admin/upload.php | 1,429 ▲29 | 4.37 ▲0.28 | 95.34 ▼16.47 | 39.26 ▼10.61 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
These items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- theysaidso_admin_options
- widget_recent-comments
- db_upgraded
- widget_recent-posts
- widget_theysaidso_widget
- can_compress_scripts
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
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 fix the following
- 1× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/wp-intro-js-tours/wpintrojs.php
- 10× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to a member function get_row() on null in wp-content/plugins/wp-intro-js-tours/components/code_generator.php:14
- > PHP Warning
Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in wp-content/plugins/wp-intro-js-tours/components/hints.php on line 3
- > PHP Fatal error
require_once(): Failed opening required 'ABSPATHwp-admin/includes/class-wp-list-table.php' (include_path='.:/usr/share/php') in wp-content/plugins/wp-intro-js-tours/components/tours_class.php on line 3
- > PHP Warning
require_once(ABSPATHwp-admin/includes/class-wp-list-table.php): failed to open stream: No such file or directory in wp-content/plugins/wp-intro-js-tours/components/tours_class.php on line 3
- > PHP Warning
Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in wp-content/plugins/wp-intro-js-tours/components/tours_class.php on line 3
- > PHP Fatal error
require_once(): Failed opening required 'ABSPATHwp-admin/includes/class-wp-list-table.php' (include_path='.:/usr/share/php') in wp-content/plugins/wp-intro-js-tours/components/hints.php on line 3
- > PHP Warning
Use of undefined constant ABSPATH - assumed 'ABSPATH' (this will throw an Error in a future version of PHP) in wp-content/plugins/wp-intro-js-tours/components/steps.php on line 3
- > PHP Fatal error
require_once(): Failed opening required 'ABSPATHwp-admin/includes/class-wp-list-table.php' (include_path='.:/usr/share/php') in wp-content/plugins/wp-intro-js-tours/components/steps.php on line 3
- > PHP Warning
require_once(ABSPATHwp-admin/includes/class-wp-list-table.php): failed to open stream: No such file or directory in wp-content/plugins/wp-intro-js-tours/components/hints.php on line 3
- > PHP Warning
require_once(ABSPATHwp-admin/includes/class-wp-list-table.php): failed to open stream: No such file or directory in wp-content/plugins/wp-intro-js-tours/components/steps.php on line 3
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
There were no browser issues found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
9 plugin tags: hint, welcome, cfuze, step, help...
wp-intro-js-tours/wpintrojs.php 77% from 13 tests
"WP Intro.JS Plugin" version 1.1'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:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("wp-intro-js-tours.php" instead of "wpintrojs.php")
- Description: The description should be shorter than 140 characters (currently 142 characters long)
- Text Domain: The text domain is optional since WordPress version 4.6; if you do specify it, it must be the same as the plugin slug
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
Success! There were no dangerous files found in this plugin2,145 lines of code in 10 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| CSS | 3 | 42 | 48 | 1,229 |
| PHP | 5 | 80 | 33 | 897 |
| JavaScript | 2 | 0 | 1 | 19 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
Great job! No cyclomatic complexity issues were detected in this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.41 |
| Average class complexity | 17.00 |
| ▷ Minimum class complexity | 17.00 |
| ▷ Maximum class complexity | 17.00 |
| Average method complexity | 2.00 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 8.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 | 16 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 16 | 100.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 19 | |
| ▷ Named functions | 19 | 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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
4 PNG files occupy 0.09MB with 0.04MB in potential savings
Potential savings
| Compression of 4 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/screenshot-2.PNG | 16.03KB | 7.98KB | ▼ 50.25% |
| assets/screenshot-4.PNG | 17.92KB | 9.71KB | ▼ 45.77% |
| assets/screenshot-1.PNG | 35.92KB | 18.55KB | ▼ 48.36% |
| assets/screenshot-3.PNG | 18.37KB | 9.78KB | ▼ 46.76% |