Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
This plugin's installer ran successfully
Server metrics [RAM: ▼0.33MB] [CPU: ▼14.86ms] Passed 4 tests
Server-side resources used by Add newest post link after content
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.43 ▼0.03 | 32.41 ▼14.25 |
Dashboard /wp-admin | 3.31 ▲0.01 | 53.10 ▲0.02 |
Posts /wp-admin/edit.php | 3.36 ▲0.01 | 51.19 ▲3.25 |
Add New Post /wp-admin/post-new.php | 4.60 ▼1.28 | 45.26 ▼46.17 |
Media Library /wp-admin/upload.php | 3.23 ▲0.01 | 36.06 ▲0.97 |
Server storage [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
The plugin installed successfully
Filesystem: 2 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-posts |
widget_theysaidso_widget |
can_compress_scripts |
widget_recent-comments |
theysaidso_admin_options |
db_upgraded |
Browser metrics Passed 4 tests
An overview of browser requirements for Add newest post link after content
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,789 ▲28 | 14.35 ▼0.00 | 1.80 ▼0.27 | 46.95 ▲4.68 |
Dashboard /wp-admin | 2,198 ▲18 | 5.61 ▲0.02 | 81.53 ▼6.13 | 37.58 ▼6.37 |
Posts /wp-admin/edit.php | 2,100 ▲3 | 1.98 ▼0.01 | 40.61 ▲2.37 | 36.16 ▲4.39 |
Add New Post /wp-admin/post-new.php | 1,526 ▼15 | 22.93 ▲0.02 | 682.36 ▼3.35 | 57.97 ▼0.57 |
Media Library /wp-admin/upload.php | 1,394 ▼6 | 4.19 ▼0.01 | 102.30 ▼3.85 | 47.38 ▲2.49 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
It is recommended to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- theysaidso_admin_options
- widget_theysaidso_widget
- widget_recent-comments
- widget_recent-posts
- db_upgraded
- can_compress_scripts
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 | The single-responsibility principle applies for WordPress plugins as well - please make sure your PHP files perform no actions when accessed directly
Please fix the following items
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_filter() in wp-content/plugins/add-newest-post-link-after-content/Add-newest-post-link-after-content.php:30
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There were no browser issues found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
These attributes need your attention:
- Screenshots: Screenshot #1 (/assets/screenshot.png) image not found
- Screenshots: A description for screenshot #0 is required in add-newest-post-link-after-content/assets to your readme.txt
add-newest-post-link-after-content/Add-newest-post-link-after-content.php 92% from 13 tests
The main PHP script in "Add newest post link after content" version 1.0 is automatically included on every request by WordPress
Please make the necessary changes and fix the following:
- Main file name: The principal plugin file should be the same as the plugin slug ("add-newest-post-link-after-content.php" instead of "Add-newest-post-link-after-content.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
There were no executable files found in this plugin21 lines of code in 1 file:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 1 | 1 | 8 | 21 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.00 |
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 | 2 | |
▷ Named functions | 2 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
No PNG files were detected