Benchmarks
Plugin footprint 82% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Installer ran successfully
Server metrics [RAM: ▲0.11MB] [CPU: ▼13.06ms] 50% from 4 tests
A check of server-side resources used by Google Webfonts For Woo Framework
Please fix the following
- RAM: Total memory usage should be kept under 10MB (currently 11.98MB on /wp-admin/options-general.php?page=gw-for-wooframework)
- CPU: Total CPU usage must kept under 500.00ms (currently 568.28ms on /wp-admin/options-general.php?page=gw-for-wooframework)
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.50 ▲0.04 | 40.71 ▼2.54 |
Dashboard /wp-admin | 3.44 ▲0.14 | 48.02 ▼2.98 |
Posts /wp-admin/edit.php | 3.55 ▲0.20 | 48.61 ▼1.35 |
Add New Post /wp-admin/post-new.php | 6.02 ▲0.13 | 84.19 ▼45.35 |
Media Library /wp-admin/upload.php | 3.36 ▲0.13 | 39.94 ▲0.88 |
Google Webfonts for Woo Framework /wp-admin/options-general.php?page=gw-for-wooframework | 11.98 | 568.28 |
Server storage [IO: ▲0.11MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin was installed successfully
Filesystem: 7 new files
Database: no new tables, 7 new options
New WordPress options |
---|
db_upgraded |
widget_theysaidso_widget |
widget_recent-posts |
can_compress_scripts |
gwfc_plugin_version |
theysaidso_admin_options |
widget_recent-comments |
Browser metrics Passed 4 tests
This is an overview of browser requirements for Google Webfonts For Woo Framework
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,818 ▲57 | 14.35 ▼0.20 | 1.85 ▲0.07 | 40.62 ▼1.92 |
Dashboard /wp-admin | 2,199 ▲25 | 5.60 ▼0.01 | 91.35 ▼7.74 | 39.36 ▼4.02 |
Posts /wp-admin/edit.php | 2,104 ▲4 | 2.02 ▲0.06 | 36.42 ▼0.70 | 33.40 ▼0.69 |
Add New Post /wp-admin/post-new.php | 1,531 ▲3 | 23.05 ▲0.08 | 674.32 ▲9.45 | 62.77 ▲6.46 |
Media Library /wp-admin/upload.php | 1,407 ▲10 | 4.15 ▼0.07 | 97.50 ▼19.45 | 40.81 ▼9.23 |
Google Webfonts for Woo Framework /wp-admin/options-general.php?page=gw-for-wooframework | 7,138 | 1.40 | 27.58 | 73.97 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
You still need to fix the following
- Zombie WordPress options were found after uninstall: 7 options
- can_compress_scripts
- db_upgraded
- widget_recent-posts
- widget_recent-comments
- widget_theysaidso_widget
- gwfc_plugin_version
- theysaidso_admin_options
Smoke tests 50% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Smoke test failed, please fix the following
- > GET request to /wp-admin/options-general.php?page=gw-for-wooframework
- > User deprecated in wp-includes/functions.php+5463
Function screen_icon is deprecated since version 3.8.0 with no alternative available.
- > GET request to /wp-admin/options-general.php?page=gw-for-wooframework
- > User deprecated in wp-includes/functions.php+5463
Function get_screen_icon is deprecated since version 3.8.0 with no alternative available.
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
- 2× PHP files trigger server-side errors or warnings when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function register_activation_hook() in wp-content/plugins/google-fonts-for-woo-framework/google-webfonts-for-woo-framework.php:79
- > PHP Fatal error
Uncaught Error: Class 'GoogleWebfontsForWooFramework' not found in wp-content/plugins/google-fonts-for-woo-framework/google-webfonts-for-woo-framework-admin.php:7
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
There were no browser issues found
Optimizations
Plugin configuration 93% 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 your attention:
- Screenshots: Screenshot #1 (2.) image missing
google-fonts-for-woo-framework/google-webfonts-for-woo-framework.php 92% from 13 tests
Analyzing the main PHP file in "Google Webfonts For Woo Framework" version 1.6.4
The following require your attention:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("google-fonts-for-woo-framework.php" instead of "google-webfonts-for-woo-framework.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
There were no executable files found in this plugin4,963 lines of code in 6 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
JSON | 2 | 0 | 0 | 4,223 |
PHP | 3 | 223 | 299 | 659 |
JavaScript | 1 | 10 | 17 | 81 |
PHP code Passed 2 tests
Analyzing cyclomatic complexity and code structure
All good! No complexity issues found
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.42 |
Average class complexity | 52.50 |
▷ Minimum class complexity | 16.00 |
▷ Maximum class complexity | 89.00 |
Average method complexity | 4.55 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 15.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 2 | |
▷ Abstract classes | 0 | 0.00% |
▷ Concrete classes | 2 | 100.00% |
▷ Final classes | 0 | 0.00% |
Methods | 29 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 29 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 3 | |
▷ Named functions | 3 | 100.00% |
▷ Anonymous functions | 0 | 0.00% |
Constants | 15 | |
▷ Global constants | 0 | 0.00% |
▷ Class constants | 15 | 100.00% |
▷ Public constants | 15 | 100.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
There were not PNG files found in your plugin