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
Install script ran successfully
Server metrics [RAM: ▲0.02MB] [CPU: ▲0.90ms] Passed 4 tests
Server-side resources used by Daily Fortune Telling Cards
This plugin does not affect your website's performance
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.48 ▲0.02 | 41.87 ▲1.31 |
Dashboard /wp-admin | 3.33 ▲0.02 | 53.71 ▲2.82 |
Posts /wp-admin/edit.php | 3.38 ▲0.02 | 52.33 ▼3.87 |
Add New Post /wp-admin/post-new.php | 5.91 ▲0.02 | 99.28 ▲3.33 |
Media Library /wp-admin/upload.php | 3.25 ▲0.02 | 41.30 ▲4.17 |
Server storage [IO: ▲0.02MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
This plugin was installed successfully
Filesystem: 5 new files
Database: no new tables, 8 new options
New WordPress options |
---|
widget_theysaidso_widget |
can_compress_scripts |
widget_recent-comments |
widget_recent-posts |
power_daily_cards_plugin_version |
theysaidso_admin_options |
db_upgraded |
power_fortune_telling_cards_plugin_option |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Daily Fortune Telling Cards
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,817 ▲56 | 14.73 ▲0.35 | 1.67 ▼0.18 | 42.77 ▼5.97 |
Dashboard /wp-admin | 2,221 ▲24 | 5.84 ▼0.01 | 101.98 ▼31.65 | 41.61 ▼16.51 |
Posts /wp-admin/edit.php | 2,100 ▼3 | 1.96 ▼0.01 | 36.75 ▼2.19 | 34.27 ▼4.84 |
Add New Post /wp-admin/post-new.php | 1,546 ▲6 | 22.94 ▲4.79 | 623.56 ▼36.40 | 78.92 ▲6.45 |
Media Library /wp-admin/upload.php | 1,397 ▼0 | 4.24 ▲0.04 | 97.93 ▼11.42 | 45.81 ▼4.16 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
It is recommended to fix the following
- Zombie WordPress options were found after uninstall: 8 options
- db_upgraded
- widget_theysaidso_widget
- power_fortune_telling_cards_plugin_option
- power_daily_cards_plugin_version
- widget_recent-comments
- can_compress_scripts
- widget_recent-posts
- theysaidso_admin_options
Smoke tests 75% 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)
Everything seems fine, however 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
- 2× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
Uncaught Error: Call to undefined function register_uninstall_hook() in wp-content/plugins/daily-fortune-telling-cards/unistall.php:7
- > PHP Fatal error
Uncaught Error: Call to undefined function add_shortcode() in wp-content/plugins/daily-fortune-telling-cards/functions.php:79
- > 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 93% from 29 tests
readme.txt Passed 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
9 plugin tags: fortune telling cards, sun signs, star sign, daily horoscopes, tarot...
daily-fortune-telling-cards/index.php 85% from 13 tests
The main PHP script in "Daily Fortune Telling Cards" version 1.3.5 is automatically included on every request by WordPress
Please make the necessary changes and fix the following:
- Text Domain: Since WordPress version 4.6 the text domain is optional; if specified, it must be the same as the plugin slug
- Main file name: It is recommended to name the main PHP file as the plugin slug ("daily-fortune-telling-cards.php" instead of "index.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | Executable files are considered dangerous and should not be included with any WordPress plugin
No dangerous file extensions were detected112 lines of code in 4 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 3 | 16 | 42 | 105 |
CSS | 1 | 0 | 1 | 7 |
PHP code Passed 2 tests
Cyclomatic complexity and code structure are the fingerprint of this plugin
Everything seems fine, there were no complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.30 |
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 | 5 | |
▷ Named functions | 5 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 4 | |
▷ Global constants | 4 | 100.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
There were not PNG files found in your plugin