Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
Installer ran successfully
Server metrics [RAM: ▲0.00MB] [CPU: ▼3.21ms] Passed 4 tests
This is a short check of server-side resources used by BeatGig WordPress Plugin
Normal server usage
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.47 ▲0.00 | 39.06 ▼2.98 |
| Dashboard /wp-admin | 3.31 ▲0.01 | 51.78 ▼2.16 |
| Posts /wp-admin/edit.php | 3.36 ▲0.00 | 47.16 ▼1.45 |
| Add New Post /wp-admin/post-new.php | 5.89 ▲0.01 | 90.94 ▼6.25 |
| Media Library /wp-admin/upload.php | 3.23 ▲0.00 | 35.66 ▲1.47 |
Server storage [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 3 tests
A short overview of filesystem and database impact
There were no storage issued detected upon installing this plugin
Filesystem: 2 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| widget_theysaidso_widget |
| widget_recent-comments |
| theysaidso_admin_options |
| widget_recent-posts |
| can_compress_scripts |
| db_upgraded |
Browser metrics Passed 4 tests
This is an overview of browser requirements for BeatGig WordPress Plugin
There were no issues detected in relation to browser resource usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,790 ▲28 | 14.34 ▲0.07 | 1.67 ▼0.08 | 43.21 ▼0.51 |
| Dashboard /wp-admin | 2,192 ▲12 | 5.62 ▲0.08 | 82.30 ▼10.24 | 37.95 ▲0.48 |
| Posts /wp-admin/edit.php | 2,100 ▼0 | 1.94 ▼0.06 | 36.28 ▼3.28 | 34.35 ▲0.63 |
| Add New Post /wp-admin/post-new.php | 6,227 ▲4,701 | 21.90 ▼1.68 | 875.83 ▲221.86 | 72.27 ▲21.63 |
| Media Library /wp-admin/upload.php | 1,400 ▼0 | 4.15 ▼0.00 | 96.98 ▼1.08 | 42.40 ▲1.32 |
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
- Zombie WordPress options were found after uninstall: 6 options
- widget_theysaidso_widget
- db_upgraded
- widget_recent-posts
- widget_recent-comments
- can_compress_scripts
- theysaidso_admin_options
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though everything seems fine, this is not an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | SRP (Single-Responsibility Principle) - PHP files must act as libraries and never output text or perform any action when accessed directly in a browser
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_shortcode() in wp-content/plugins/beatgig-calendar-embed/embed.php:35
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser issues were found
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 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
These attributes need to be fixed:
- Tags: Too many tags (43 tag instead of maximum 10); only the first 5 tags are used in your directory listing
beatgig-calendar-embed/embed.php 85% from 13 tests
"BeatGig WordPress Plugin" version 0.2'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:
- Text Domain: If you choose to specify the text domain, it must be the same as the plugin slug; optional since WordPress version 4.6
- Main file name: The principal plugin file should be the same as the plugin slug ("beatgig-calendar-embed.php" instead of "embed.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
Success! There were no dangerous files found in this plugin20 lines of code in 1 file:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| PHP | 1 | 7 | 8 | 20 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
No cyclomatic complexity issues were detected for this plugin
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.38 |
| 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 | 1 | |
| ▷ Named functions | 1 | 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
Using a strong compression for your PNG files is a great way to speed-up your plugin
No PNG files were detected