Benchmarks
Plugin footprint 65% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | The install procedure must perform silently
Installer ran successfully
Server metrics [RAM: ▼1.92MB] [CPU: ▼58.47ms] Passed 4 tests
Analyzing server-side resources used by SocialEars
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.06 ▼1.40 | 4.38 ▼42.81 |
Dashboard /wp-admin | 2.08 ▼1.22 | 6.03 ▼48.45 |
Posts /wp-admin/edit.php | 2.09 ▼1.27 | 5.98 ▼46.78 |
Add New Post /wp-admin/post-new.php | 2.08 ▼3.80 | 5.20 ▼95.84 |
Media Library /wp-admin/upload.php | 2.08 ▼1.14 | 5.77 ▼32.28 |
Social Ears Analyze /wp-admin/options-general.php?page=social-ears | 2.09 | 6.70 |
Server storage [IO: ▲0.03MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
There were no storage issued detected upon installing this plugin
Filesystem: 5 new files
Database: no new tables, 7 new options
New WordPress options |
---|
theysaidso_admin_options |
se_option |
widget_theysaidso_widget |
db_upgraded |
can_compress_scripts |
widget_recent-posts |
widget_recent-comments |
Browser metrics Passed 4 tests
SocialEars: an overview of browser usage
Normal browser usage
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,880 ▲119 | 13.46 ▼0.91 | 9.05 ▲7.27 | 41.63 ▼2.18 |
Dashboard /wp-admin | 2,200 ▲23 | 5.54 ▼0.11 | 89.44 ▼11.97 | 37.90 ▼4.62 |
Posts /wp-admin/edit.php | 2,111 ▲11 | 2.00 ▲0.04 | 41.07 ▲5.81 | 35.85 ▼2.00 |
Add New Post /wp-admin/post-new.php | 6,228 ▲4,699 | 25.86 ▲2.76 | 931.86 ▲275.87 | 52.27 ▲0.38 |
Media Library /wp-admin/upload.php | 1,408 ▲8 | 4.27 ▲0.05 | 100.40 ▼11.99 | 48.78 ▼1.73 |
Social Ears Analyze /wp-admin/options-general.php?page=social-ears | 830 | 2.01 | 24.57 | 28.71 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% 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 cannot be uninstalled
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the content-analyze handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- The uninstall procedure has failed, leaving 6 options in the database
- widget_theysaidso_widget
- widget_recent-comments
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-posts
- db_upgraded
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Smoke test failed, please fix the following
- > GET request to /wp-admin/options-general.php?page=social-ears
- > User notice in wp-includes/functions.php+5905
Function wp_enqueue_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the content-analyze handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
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 have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/social-analytics-and-content-seo-using-socialears/se_content.php:15
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine, but this is not an exhaustive test
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
It's important to format your readme.txt file correctly as it is parsed for the public listing of your plugin
These attributes need to be fixed:
- Tags: There are too many tags (14 tag instead of maximum 10)
- Plugin Name: You should set the name of your plugin on the first line (
=== social-analytics-and-content-seo-using-socialears ===
)
social-analytics-and-content-seo-using-socialears/se_content.php 92% from 13 tests
The principal PHP file in "SocialEars" v. 1.0.6 is loaded by WordPress automatically on each request
You should first fix the following items:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("social-analytics-and-content-seo-using-socialears.php" instead of "se_content.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Everything looks great! No dangerous files found in this plugin135 lines of code in 2 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 24 | 40 | 105 |
JavaScript | 1 | 11 | 0 | 30 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.15 |
Average class complexity | 2.00 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 2.00 |
Average method complexity | 1.33 |
▷ 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 | 3 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 3 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 6 | |
▷ Named functions | 6 | 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
2 PNG files occupy 0.02MB with 0.01MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/ears.png | 0.26KB | 0.14KB | ▼ 48.71% |
images/logo.png | 15.51KB | 4.51KB | ▼ 70.92% |