Benchmarks
Plugin footprint 40% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The following installer errors require your attention
- This plugin did not install gracefully
- > Deprecated in wp-content/plugins/tag-counter/tags.php+19
Methods with the same name as their class will not be constructors in a future version of PHP; WP_Widget_Tags_Count has a deprecated constructor
Server metrics [RAM: ▼1.71MB] [CPU: ▼48.49ms] Passed 4 tests
An overview of server-side resources used by Tag counter
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.28 ▼1.18 | 16.58 ▼25.26 |
Dashboard /wp-admin | 2.30 ▼1.00 | 11.39 ▼41.91 |
Posts /wp-admin/edit.php | 2.30 ▼1.05 | 11.15 ▼39.25 |
Add New Post /wp-admin/post-new.php | 2.30 ▼3.58 | 10.59 ▼85.20 |
Media Library /wp-admin/upload.php | 2.30 ▼0.93 | 10.61 ▼27.58 |
Server storage [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
This plugin was installed successfully
Filesystem: 4 new files
Database: no new tables, 7 new options
New WordPress options |
---|
can_compress_scripts |
theysaidso_admin_options |
widget_recent-posts |
widget_recent-comments |
widget_tags-count-widget |
widget_theysaidso_widget |
db_upgraded |
Browser metrics Passed 4 tests
An overview of browser requirements for Tag counter
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,800 ▲54 | 13.30 ▼1.00 | 1.80 ▼0.06 | 42.92 ▼0.10 |
Dashboard /wp-admin | 2,206 ▲21 | 4.85 ▼1.00 | 115.31 ▲7.46 | 42.09 ▲0.88 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 1.99 ▼0.05 | 35.34 ▼4.98 | 34.74 ▼2.72 |
Add New Post /wp-admin/post-new.php | 1,533 ▲12 | 23.07 ▼0.21 | 638.24 ▼23.62 | 63.18 ▼1.70 |
Media Library /wp-admin/upload.php | 1,385 ▼3 | 4.20 ▼0.01 | 98.53 ▼23.53 | 46.55 ▼2.54 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
The following items require your attention
- Uninstall procedure had uncaught errors
- > User deprecated in wp-includes/functions.php+5546
The called constructor method for WP_Widget class in WP_Widget_Tags_Count is deprecated since version 4.3.0! Use __construct() instead.
- The uninstall procedure has failed, leaving 7 options in the database
- theysaidso_admin_options
- widget_recent-posts
- can_compress_scripts
- widget_theysaidso_widget
- db_upgraded
- widget_tags-count-widget
- widget_recent-comments
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
The following issues need your attention
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/tag-counter/tags.php:12
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
Everything seems fine on the user side
Optimizations
Plugin configuration 96% from 29 tests
readme.txt Passed 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
5 plugin tags: counter, tags, count, tag, widget
tag-counter/tags.php 92% from 13 tests
"Tag counter" version 0.2's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
It is important to fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("tag-counter.php" instead of "tags.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | There should be no dangerous file extensions present in any WordPress plugin
Good job! No executable or dangerous file extensions detected60 lines of code in 2 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 8 | 8 | 38 |
PO File | 1 | 3 | 4 | 22 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.05 |
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 | 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
PNG files should be compressed to save space and minimize bandwidth usage
No PNG files were detected