Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▲0.01MB] [CPU: ▼4.96ms] Passed 4 tests
This is a short check of server-side resources used by Force Ping Display with Disqus
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 40.76 ▲0.20 |
Dashboard /wp-admin | 3.31 ▲0.01 | 44.84 ▼2.50 |
Posts /wp-admin/edit.php | 3.36 ▲0.01 | 51.37 ▲4.49 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 82.87 ▼17.02 |
Media Library /wp-admin/upload.php | 3.24 ▲0.01 | 33.83 ▼0.53 |
Server storage [IO: ▲0.00MB] [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: 2 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_theysaidso_widget |
can_compress_scripts |
widget_recent-posts |
widget_recent-comments |
theysaidso_admin_options |
db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Force Ping Display with Disqus
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲54 | 13.25 ▼1.13 | 5.05 ▲3.22 | 43.15 ▼0.37 |
Dashboard /wp-admin | 2,206 ▲32 | 5.87 ▲0.92 | 105.97 ▲3.53 | 41.90 ▼9.12 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.00 ▼0.04 | 39.73 ▼2.07 | 34.44 ▼2.13 |
Add New Post /wp-admin/post-new.php | 1,528 ▼9 | 18.33 ▼4.95 | 622.69 ▲20.40 | 62.47 ▲9.85 |
Media Library /wp-admin/upload.php | 1,385 ▼3 | 4.22 ▲0.01 | 101.53 ▲2.03 | 43.71 ▲1.00 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
You still need to fix the following
- The uninstall procedure has failed, leaving 6 options in the database
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- widget_recent-comments
- can_compress_scripts
- 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
Even though no errors were found, this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Please take a closer look at the following
- 1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/force-ping-display-with-disqus/forceping.php:53
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file describes your plugin functionality and requirements and it is parsed to prepare the your plugin's listing
These attributes need to be fixed:
- Donate link: Please fix this invalid URI: ""
- Plugin Name: "Plugin Name" should be replaced with the name of your plugin on the first line (
=== force-ping-display-with-disqus ===
)
force-ping-display-with-disqus/forceping.php 85% from 13 tests
This is the main PHP file of "Force Ping Display with Disqus" version 0.1, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
Please take the time to fix the following:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 380 characters long)
- Main file name: It is recommended to name the main PHP file as the plugin slug ("force-ping-display-with-disqus.php" instead of "forceping.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
No dangerous file extensions were detected32 lines of code in 1 file:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 13 | 10 | 32 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.19 |
Average class complexity | 0.00 |
▷ Minimum class complexity | 0.00 |
▷ Maximum class complexity | 0.00 |
Average method complexity | 0.00 |
▷ Minimum method complexity | 0.00 |
▷ Maximum method complexity | 0.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 0 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 0 | 0.00% |
▷ Final classes | 0 | 0.00% |
Methods | 0 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 0 | 0.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 1 | |
▷ Named functions | 1 | 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
There were not PNG files found in your plugin