Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed gracefully, with no errors
Server metrics [RAM: ▼0.63MB] [CPU: ▼11.69ms] Passed 4 tests
Analyzing server-side resources used by Build Trigger for Gatsby
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 37.48 ▼3.22 |
Dashboard /wp-admin | 3.38 ▲0.08 | 46.47 ▲1.13 |
Posts /wp-admin/edit.php | 3.49 ▲0.14 | 48.96 ▲3.21 |
Add New Post /wp-admin/post-new.php | 3.23 ▼2.66 | 41.94 ▼46.03 |
Media Library /wp-admin/upload.php | 3.30 ▲0.07 | 35.29 ▲1.37 |
Build Trigger for Gatsby /wp-admin/tools.php?page=build-trigger-for-gatsby | 3.24 | 32.08 |
Server storage [IO: ▲0.02MB] [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: 6 new files
Database: no new tables, 7 new options
New WordPress options |
---|
ztbtfg_build_count |
widget_theysaidso_widget |
theysaidso_admin_options |
db_upgraded |
widget_recent-comments |
can_compress_scripts |
widget_recent-posts |
Browser metrics Passed 4 tests
Checking browser requirements for Build Trigger for Gatsby
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,809 ▲63 | 13.24 ▼1.05 | 1.62 ▲0.01 | 40.07 ▼4.31 |
Dashboard /wp-admin | 2,218 ▲30 | 4.86 ▼0.04 | 98.64 ▼12.35 | 38.48 ▼3.03 |
Posts /wp-admin/edit.php | 2,101 ▲9 | 2.05 ▲0.02 | 41.08 ▼0.03 | 34.40 ▼1.82 |
Add New Post /wp-admin/post-new.php | 1,536 ▼6 | 23.00 ▲4.70 | 689.42 ▲20.93 | 58.68 ▲1.36 |
Media Library /wp-admin/upload.php | 1,400 ▲12 | 4.22 ▼0.01 | 95.62 ▼13.99 | 43.67 ▲0.80 |
Build Trigger for Gatsby /wp-admin/tools.php?page=build-trigger-for-gatsby | 835 | 2.22 | 25.39 | 31.66 |
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
- The uninstall procedure has failed, leaving 7 options in the database
- widget_recent-posts
- widget_recent-comments
- ztbtfg_build_count
- db_upgraded
- theysaidso_admin_options
- can_compress_scripts
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Please fix the following server-side errors
- 6 occurences, only the last one shown
- > GET request to /wp-admin/tools.php?page=build-trigger-for-gatsby
- > Notice in wp-content/plugins/build-trigger-gatsby/inc/admin/class.ztbtfg.admin.php+183
Trying to access array offset on value of type bool
SRP Passed 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
The SRP test was a success
User-side errors Passed 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Everything seems fine on the user side
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 94% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
These attributes need to be fixed:
- Donate link: Please fix this invalid url: "'';"
build-trigger-gatsby/build-trigger-for-gatsby.php 85% from 13 tests
This is the main PHP file of "Build Trigger for Gatsby" version 1.0.2, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
It is important to 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: Please rename the main PHP file in this plugin to the plugin slug ("build-trigger-gatsby.php" instead of "build-trigger-for-gatsby.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
Good job! No executable or dangerous file extensions detected359 lines of code in 5 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 4 | 106 | 129 | 309 |
JavaScript | 1 | 15 | 5 | 50 |
PHP code Passed 2 tests
This plugin's cyclomatic complexity and code structure detailed below
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.39 |
Average class complexity | 10.67 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 22.00 |
Average method complexity | 2.71 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 11.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 3 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 3 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 17 | |
▷ Static methods | 1 | 5.88% |
▷ Public methods | 17 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 3 | |
▷ Named functions | 1 | 33.33% |
▷ Anonymous functions | 2 | 66.67% |
Constants | 8 | |
▷ Global constants | 8 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
PNG files should be compressed to save space and minimize bandwidth usage
There were not PNG files found in your plugin