Benchmarks
Plugin footprint Passed 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices
Install script ran successfully
Server metrics [RAM: ▲0.01MB] [CPU: ▼298.49ms] Passed 4 tests
A check of server-side resources used by Advanced Custom Fields: Typography Field
Normal server usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.51 ▼0.01 | 57.90 ▼11.04 |
Dashboard /wp-admin | 3.46 ▲0.05 | 39.86 ▼2.65 |
Posts /wp-admin/edit.php | 3.69 ▲0.05 | 41.70 ▼0.14 |
Add New Post /wp-admin/post-new.php | 6.93 ▼0.05 | 102.66 ▼1,180.12 |
Media Library /wp-admin/upload.php | 3.34 ▲0.04 | 33.76 ▲5.71 |
ACF Typography Settings /wp-admin/options-general.php?page=acf-typography-field | 3.31 | 25.13 |
Server storage [IO: ▲0.24MB] [DB: ▲0.00MB] Passed 3 tests
Analyzing filesystem and database footprints of this plugin
No storage issues were detected
Filesystem: 12 new files
Database: no new tables, no new options
Browser metrics Passed 4 tests
An overview of browser requirements for Advanced Custom Fields: Typography Field
Minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 3,186 ▼536 | 16.07 ▲0.46 | 0.37 ▼5.27 | 32.92 ▲30.63 |
Dashboard /wp-admin | 2,897 ▲39 | 6.12 ▼0.05 | 117.58 ▼16.52 | 151.03 ▼12.06 |
Posts /wp-admin/edit.php | 2,696 ▲2 | 3.24 ▼0.00 | 63.09 ▼2.47 | 144.08 ▲1.79 |
Add New Post /wp-admin/post-new.php | 1,714 ▲53 | 20.41 ▲4.17 | 405.80 ▼4.41 | 168.29 ▲13.91 |
Media Library /wp-admin/upload.php | 1,700 ▲2 | 5.53 ▲0.02 | 149.26 ▲13.73 | 184.38 ▲1.24 |
ACF Typography Settings /wp-admin/options-general.php?page=acf-typography-field | 994 | 2.39 | 53.31 | 113.60 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] Passed 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
Uninstall script ran successfully
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A smoke test targeting server-side errors
Everything seems fine, however this is by no means an exhaustive test
SRP 50% from 2 tests
🔹 Tests weight: 20 | A shallow check of the single-responsibility principle; PHP files should perform no action - including output of placeholder text - and trigger no errors when accessed directly
Almost there! Just fix the following items
- 3× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/acf-typography-field/includes/functions.php:79
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/acf-typography-field/includes/admin_settings.php:9
- > PHP Fatal error
Uncaught Error: Call to undefined function add_shortcode() in wp-content/plugins/acf-typography-field/includes/api-template.php:143
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected
Optimizations
Plugin configuration 90% from 29 tests
readme.txt 88% from 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
These attributes need to be fixed:
- Screenshots: Please add images for these screenshots: #1 (Typography Field Settings), #2 (Typography Field Content Editing), #3 (Google Key Field required for Google Fonts)
- Tags: Too many tags (11 tag instead of maximum 10); only the first 5 tags are used in your directory listing
acf-typography-field/acf-typography.php 92% from 13 tests
"Advanced Custom Fields: Typography Field" version 3.2.2's primary PHP file adds more information about the plugin and serves as the entry point for WordPress
Please make the necessary changes and fix the following:
- Main file name: Please rename the main PHP file in this plugin to the plugin slug ("acf-typography-field.php" instead of "acf-typography.php")
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is an overview of file extensions present in this plugin and a short test that no dangerous files are bundled with this plugin
No dangerous file extensions were detected1,128 lines of code in 7 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
PHP | 6 | 406 | 630 | 1,083 |
JavaScript | 1 | 25 | 0 | 45 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
There are no cyclomatic complexity problems detected for this plugin
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.38 |
Average class complexity | 23.33 |
▷ Minimum class complexity | 2.00 |
▷ Maximum class complexity | 35.00 |
Average method complexity | 3.68 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 29.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 | 25 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 25 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 14 | |
▷ Named functions | 13 | 92.86% |
▷ Anonymous functions | 1 | 7.14% |
Constants | 1 | |
▷ Global constants | 1 | 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
3 PNG files occupy 0.18MB with 0.12MB in potential savings
Potential savings
Compression of 3 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
screenshot-3.png | 9.69KB | 3.79KB | ▼ 60.88% |
screenshot-1.png | 135.36KB | 38.52KB | ▼ 71.54% |
screenshot-2.png | 37.34KB | 9.93KB | ▼ 73.40% |