Benchmarks
Plugin footprint 65% 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: ▼1.86MB] [CPU: ▼54.92ms] Passed 4 tests
An overview of server-side resources used by Simple Google Font Adder
Server-side resource usage in normal parameters
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 2.13 ▼1.33 | 5.63 ▼37.51 |
Dashboard /wp-admin | 2.15 ▼1.15 | 7.14 ▼46.00 |
Posts /wp-admin/edit.php | 2.15 ▼1.20 | 7.02 ▼43.49 |
Add New Post /wp-admin/post-new.php | 2.15 ▼3.74 | 4.85 ▼92.66 |
Media Library /wp-admin/upload.php | 2.15 ▼1.08 | 5.55 ▼31.96 |
Server storage [IO: ▲0.05MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
No storage issues were detected
Filesystem: 7 new files
Database: no new tables, 8 new options
New WordPress options |
---|
theysaidso_admin_options |
db_upgraded |
widget_theysaidso_widget |
widget_recent-posts |
widget_recent-comments |
can_compress_scripts |
gfont_url |
gfont_name |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Simple Google Font Adder
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,829 ▲68 | 14.35 ▼0.02 | 1.99 ▲0.28 | 24.46 ▼19.12 |
Dashboard /wp-admin | 2,213 ▲33 | 5.49 ▼0.18 | 84.95 ▼3.03 | 48.20 ▲4.68 |
Posts /wp-admin/edit.php | 2,124 ▲21 | 2.02 ▲0.01 | 34.68 ▼10.99 | 37.74 ▼0.75 |
Add New Post /wp-admin/post-new.php | 1,701 ▲164 | 22.06 ▲3.91 | 583.95 ▼36.94 | 53.11 ▼16.88 |
Media Library /wp-admin/upload.php | 1,424 ▲27 | 4.21 ▲0.06 | 94.59 ▼13.62 | 55.09 ▲9.40 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 50% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
Please fix the following items
- Uninstall procedure had uncaught errors
- > User notice in wp-includes/functions.php+5905
Function wp_register_style was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or login_enqueue_scripts hooks. This notice was triggered by the prefix_bootstrap handle. Please see Debugging in WordPress for more information. (This message was added in version 3.3.0.)
- Zombie WordPress options were found after uninstall: 8 options
- theysaidso_admin_options
- db_upgraded
- can_compress_scripts
- gfont_name
- widget_recent-posts
- widget_recent-comments
- widget_theysaidso_widget
- gfont_url
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
The following issues need your attention
- 1× PHP files perform the task of outputting text when accessed with GET requests:
- > /wp-content/plugins/simple-google-font-adder/uninstall.php
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)
No browser errors were detected
Optimizations
Plugin configuration 96% 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
3 plugin tags: google font, add google font, add google font editor
simple-google-font-adder/add_gfont.php 92% from 13 tests
The main PHP file in "Simple Google Font Adder" ver. 1.0 adds more information about the plugin and also serves as the entry point for this plugin
Please take the time to fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("simple-google-font-adder.php" instead of "add_gfont.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
Good job! No executable or dangerous file extensions detected284 lines of code in 3 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 2 | 35 | 99 | 219 |
PO File | 1 | 20 | 20 | 65 |
PHP code Passed 2 tests
This is a short overview of cyclomatic complexity and code structure for this plugin
No complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.20 |
Average class complexity | 6.00 |
▷ Minimum class complexity | 6.00 |
▷ Maximum class complexity | 6.00 |
Average method complexity | 2.67 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 6.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 | 3 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 3 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 12 | |
▷ Named functions | 12 | 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
All PNG images should be compressed to minimize bandwidth usage for end users
PNG images were not found in this plugin