Benchmarks
Plugin footprint 23% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Please fix the following installer errors
- The plugin cannot be installed
- > Deprecated in wp-content/plugins/wp-page-extension/wp-page_extension.php+10
Methods with the same name as their class will not be constructors in a future version of PHP; wp_fake_url has a deprecated constructor
Server metrics [RAM: ▼1.61MB] [CPU: ▼52.10ms] Passed 4 tests
This is a short check of server-side resources used by WP Page Extension
This plugin does not affect your website's performance
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 2.38 ▼1.08 | 4.69 ▼34.80 |
| Dashboard /wp-admin | 2.40 ▼0.90 | 6.28 ▼48.28 |
| Posts /wp-admin/edit.php | 2.40 ▼0.96 | 6.76 ▼46.54 |
| Add New Post /wp-admin/post-new.php | 2.40 ▼3.49 | 7.09 ▼78.78 |
| Media Library /wp-admin/upload.php | 2.40 ▼0.83 | 6.35 ▼29.58 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
No storage issues were detected
Filesystem: 4 new files
Database: 1 new table, 9 new options
| New tables |
|---|
| page_fake_url |
| New WordPress options |
|---|
| can_compress_scripts |
| widget_recent-posts |
| extension_enabled |
| widget_theysaidso_widget |
| db_upgraded |
| widget_recent-comments |
| theysaidso_admin_options |
| extFlag |
| current_extension |
Browser metrics Passed 4 tests
A check of browser resources used by WP Page Extension
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,800 ▲65 | 13.61 ▼0.76 | 1.70 ▲0.07 | 46.07 ▲2.62 |
| Dashboard /wp-admin | 2,209 ▲24 | 6.02 ▼0.02 | 99.66 ▼6.40 | 42.77 ▼3.35 |
| Posts /wp-admin/edit.php | 2,092 ▲3 | 2.05 ▲0.04 | 39.96 ▼0.28 | 35.81 ▼3.34 |
| Add New Post /wp-admin/post-new.php | 1,372 ▼163 | 21.52 ▼2.09 | 528.82 ▼185.77 | 60.40 ▲4.41 |
| Media Library /wp-admin/upload.php | 1,388 ▼0 | 4.22 ▲0.05 | 97.61 ▼9.51 | 42.76 ▼2.16 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 25% 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 cannot be uninstalled
- > Deprecated in wp-content/plugins/wp-page-extension/wp-page_extension.php+10
Methods with the same name as their class will not be constructors in a future version of PHP; wp_fake_url has a deprecated constructor
- Zombie tables were found after uninstall: 1 table
- page_fake_url
- This plugin did not uninstall successfully, leaving 6 options in the database
- can_compress_scripts
- widget_theysaidso_widget
- theysaidso_admin_options
- db_upgraded
- widget_recent-comments
- widget_recent-posts
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP 0% 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 items
- 1× PHP files perform the action of outputting non-empty strings when accessed directly:
- > /wp-content/plugins/wp-page-extension/view/plugin_view.php
- 1× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-page-extension/wp-page_extension.php:13
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
Attributes that need to be fixed:
- Tags: There are too many tags (14 tag instead of maximum 10)
- Screenshots: Screenshot #1 (Page Settings) image not found
wp-page-extension/wp-page_extension.php 92% from 13 tests
The principal PHP file in "WP Page Extension" v. 1.1 is loaded by WordPress automatically on each request
You should first fix the following items:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("wp-page-extension.php" instead of "wp-page_extension.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | A short check of programming languages and file extensions; no executable files are allowed
There were no executable files found in this plugin654 lines of code in 2 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 2 | 146 | 29 | 654 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
No complexity issues detected
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.50 |
| Average class complexity | 165.00 |
| ▷ Minimum class complexity | 165.00 |
| ▷ Maximum class complexity | 165.00 |
| Average method complexity | 15.91 |
| ▷ Minimum method complexity | 1.00 |
| ▷ Maximum method complexity | 96.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 | 11 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 11 | 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
There were not PNG files found in your plugin