Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
The plugin installed gracefully, with no errors
Server metrics [RAM: ▼0.61MB] [CPU: ▼14.45ms] Passed 4 tests
Server-side resources used by Post To SEO
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.53 ▲0.07 | 36.64 ▼5.25 |
Dashboard /wp-admin | 3.38 ▲0.08 | 42.27 ▼4.20 |
Posts /wp-admin/edit.php | 3.50 ▲0.14 | 46.33 ▲2.15 |
Add New Post /wp-admin/post-new.php | 3.23 ▼2.65 | 36.71 ▼50.51 |
Media Library /wp-admin/upload.php | 3.31 ▲0.08 | 36.88 ▲3.19 |
PostToSEO /wp-admin/options-general.php?page=PostToSEO | 3.25 | 31.23 |
Server storage [IO: ▲0.31MB] [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, 6 new options
New WordPress options |
---|
widget_recent-comments |
db_upgraded |
widget_recent-posts |
can_compress_scripts |
theysaidso_admin_options |
widget_theysaidso_widget |
Browser metrics Passed 4 tests
A check of browser resources used by Post To SEO
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,804 ▲47 | 14.76 ▲0.38 | 1.64 ▼0.43 | 43.58 ▼10.61 |
Dashboard /wp-admin | 2,210 ▲24 | 5.88 ▲0.92 | 102.80 ▼13.79 | 39.35 ▲0.55 |
Posts /wp-admin/edit.php | 2,090 ▲1 | 2.05 ▲0.07 | 36.29 ▲0.74 | 32.25 ▼3.57 |
Add New Post /wp-admin/post-new.php | 6,577 ▲5,057 | 23.46 ▲0.60 | 915.61 ▲242.23 | 63.87 ▲7.58 |
Media Library /wp-admin/upload.php | 1,395 ▲7 | 4.22 ▼0.05 | 95.72 ▼2.38 | 43.38 ▼4.43 |
PostToSEO /wp-admin/options-general.php?page=PostToSEO | 806 | 2.03 | 23.67 | 25.66 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Verifying that this plugin uninstalls completely without leaving any traces
It is recommended to fix the following
- Zombie WordPress options detected upon uninstall: 6 options
- can_compress_scripts
- widget_recent-comments
- db_upgraded
- widget_theysaidso_widget
- widget_recent-posts
- theysaidso_admin_options
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
These server-side errors were triggered
- 2 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=PostToSEO
- > Notice in wp-content/plugins/post-to-seo/index.php+90
Trying to access array offset on value of type null
SRP 50% from 2 tests
🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions
Please fix the following
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function is_admin() in wp-content/plugins/post-to-seo/index.php:11
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine, but this is not an exhaustive test
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
7 plugin tags: post, tags, seo, search engine optimisation, post seo...
post-to-seo/index.php 92% from 13 tests
This is the main PHP file of "Post To SEO" version 1.0, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
Please make the necessary changes and fix the following:
- Main file name: It is recommended to name the main PHP file as the plugin slug ("post-to-seo.php" instead of "index.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
Good job! No executable or dangerous file extensions detected345 lines of code in 2 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 48 | 30 | 285 |
JavaScript | 1 | 13 | 0 | 60 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
There were no cyclomatic complexity issued detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.34 |
Average class complexity | 8.00 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 15.00 |
Average method complexity | 1.80 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 5.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 17 | |
▷ Static methods | 5 | 29.41% |
▷ Public methods | 17 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 0 | |
▷ Named functions | 0 | 0.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
All PNG images should be compressed to minimize bandwidth usage for end users
2 PNG files occupy 0.29MB with 0.19MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/screenshot-1.png | 155.67KB | 53.35KB | ▼ 65.73% |
assets/screenshot-2.png | 141.84KB | 49.92KB | ▼ 64.80% |