Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
Installer ran successfully
Server metrics [RAM: ▲0.06MB] [CPU: ▼7.22ms] Passed 4 tests
An overview of server-side resources used by Page Expiration Robot - Countdown Timer
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.51 ▲0.05 | 42.12 ▼2.01 |
Dashboard /wp-admin | 3.36 ▲0.06 | 51.75 ▲2.92 |
Posts /wp-admin/edit.php | 3.47 ▲0.12 | 48.60 ▼0.82 |
Add New Post /wp-admin/post-new.php | 5.96 ▲0.08 | 88.85 ▼23.99 |
Media Library /wp-admin/upload.php | 3.28 ▲0.05 | 39.02 ▼2.07 |
Create New Campaign /wp-admin/admin.php?page=page_expiration_robot_saas_add | 3.25 | 31.80 |
Timers /wp-admin/admin.php?page=page_expiration_robot_saas | 3.25 | 31.47 |
Open PER Everywhere /wp-admin/admin.php?page=page_expiration_robot_saasopenSAAS | 3.25 | 31.39 |
Help /wp-admin/admin.php?page=page_expiration_robot_saas_help | 3.25 | 34.82 |
Settings /wp-admin/admin.php?page=page_expiration_robot_saas_settings | 3.26 | 27.35 |
Server storage [IO: ▲0.04MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 11 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
theysaidso_admin_options |
widget_recent-posts |
db_upgraded |
widget_theysaidso_widget |
can_compress_scripts |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Page Expiration Robot - Countdown Timer
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,831 ▲70 | 14.11 ▼0.09 | 1.98 ▼0.17 | 47.30 ▲1.16 |
Dashboard /wp-admin | 2,234 ▲57 | 5.60 ▲0.07 | 99.40 ▲7.63 | 87.65 ▲41.52 |
Posts /wp-admin/edit.php | 2,139 ▲42 | 2.13 ▲0.14 | 35.31 ▼2.54 | 33.98 ▼4.99 |
Add New Post /wp-admin/post-new.php | 1,563 ▲26 | 23.02 ▲4.77 | 709.27 ▲20.58 | 72.11 ▲2.37 |
Media Library /wp-admin/upload.php | 1,442 ▲45 | 4.27 ▲0.04 | 101.45 ▼5.37 | 71.33 ▲29.05 |
Create New Campaign /wp-admin/admin.php?page=page_expiration_robot_saas_add | 1,613 | 2.36 | 29.90 | 34.31 |
Timers /wp-admin/admin.php?page=page_expiration_robot_saas | 1,613 | 2.35 | 28.15 | 40.58 |
Open PER Everywhere /wp-admin/admin.php?page=page_expiration_robot_saasopenSAAS | 875 | 2.73 | 32.96 | 49.79 |
Help /wp-admin/admin.php?page=page_expiration_robot_saas_help | 749 | 1.60 | 6.53 | 30.81 |
Settings /wp-admin/admin.php?page=page_expiration_robot_saas_settings | 926 | 2.01 | 23.43 | 25.45 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
The following items require your attention
- The uninstall procedure has failed, leaving 6 options in the database
- widget_recent-posts
- widget_theysaidso_widget
- db_upgraded
- theysaidso_admin_options
- widget_recent-comments
- can_compress_scripts
Smoke tests 50% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
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
The following issues need your attention
- 4× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Call to undefined function admin_url() in wp-content/plugins/page-expiration-robot/campaigns.php:58
- > PHP Fatal error
Uncaught Error: Call to undefined function admin_url() in wp-content/plugins/page-expiration-robot/newCampaign.php:50
- > PHP Fatal error
Uncaught Error: Class 'PageExpirationRobotSAAS' not found in wp-content/plugins/page-expiration-robot/settings.php:7
- > PHP Fatal error
Uncaught Error: Call to undefined function plugin_dir_url() in wp-content/plugins/page-expiration-robot/page-expiration-robot-saas.php:24
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | This is just a short smoke test looking for browser issues
Please fix the following browser errors
- 3 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=page_expiration_robot_saas_settings
- > Network (severe)
https://pageexpirationrobot.com/v2/wp-content/uploads/2014/10/New-Logo.png - Failed to load resource: the server responded with a status of 403 (Forbidden)
- > GET request to /wp-admin/admin.php?page=page_expiration_robot_saasopenSAAS
- > Other (warning) in unknown
https://www.google.com/adsense/domains/caf.js 218 Unrecognized feature: 'attribution-reporting'.
- > GET request to /wp-admin/admin.php?page=page_expiration_robot_saas_help
- > Network (severe)
https://pageexpirationrobot.helpscoutdocs.com/collection/120-web-app-faq - Failed to load resource: the server responded with a status of 404 (Not Found)
Optimizations
Plugin configuration 87% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file is an important file in your plugin as it is parsed by WordPress.org to prepare the public listing of your plugin
Attributes that require attention:
- Tags: You are using too many tags: 40 tag instead of maximum 10
- Screenshots: These screenshots do not have images: #1 (Page Expiration Robot options overview.), #2 (Evergreen scarcity options)
page-expiration-robot/page-expiration-robot-saas.php 85% from 13 tests
"Page Expiration Robot - Countdown Timer" version 3.2.1's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
It is important to fix the following:
- Description: If Twitter did it, so should we! Keep the description under 140 characters (currently 175 characters long)
- Main file name: Name the main plugin file the same as the plugin slug ("page-expiration-robot.php" instead of "page-expiration-robot-saas.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
No dangerous file extensions were detected385 lines of code in 7 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 4 | 174 | 11 | 281 |
JavaScript | 2 | 50 | 2 | 93 |
CSS | 1 | 4 | 0 | 11 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.26 |
Average class complexity | 12.00 |
▷ Minimum class complexity | 12.00 |
▷ Maximum class complexity | 12.00 |
Average method complexity | 1.65 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 5.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 | 17 | |
▷ Static methods | 0 | 0.00% |
▷ 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
Often times overlooked, PNG files can occupy unnecessary space in your plugin
2 PNG files occupy 0.00MB with 0.00MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
images/hourglass_plus.png | 0.60KB | 0.48KB | ▼ 19.61% |
images/per_icon.png | 0.60KB | 0.48KB | ▼ 19.61% |