Benchmarks
Plugin footprint 83% from 16 tests
Installer Passed 1 test
🔺 Critical test (weight: 50) | Checking the installer triggered no errors
The plugin installed successfully, without throwing any errors or notices
Server metrics [RAM: ▲0.01MB] [CPU: ▼4.04ms] Passed 4 tests
Server-side resources used by Advanced Custom Fields: Markdown Field
This plugin has minimal impact on server resources
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.47 ▲0.01 | 36.21 ▼5.79 |
Dashboard /wp-admin | 3.31 ▲0.01 | 44.60 ▼6.75 |
Posts /wp-admin/edit.php | 3.36 ▲0.00 | 44.27 ▼0.62 |
Add New Post /wp-admin/post-new.php | 5.89 ▲0.00 | 92.99 ▼2.98 |
Media Library /wp-admin/upload.php | 3.24 ▲0.00 | 36.13 ▲2.12 |
Server storage [IO: ▲0.59MB] [DB: ▲0.00MB] Passed 3 tests
How much does this plugin use your filesystem and database?
This plugin installed successfully
Filesystem: 78 new files
Database: no new tables, 6 new options
New WordPress options |
---|
widget_recent-comments |
db_upgraded |
widget_theysaidso_widget |
can_compress_scripts |
widget_recent-posts |
theysaidso_admin_options |
Browser metrics Passed 4 tests
A check of browser resources used by Advanced Custom Fields: Markdown Field
This plugin renders optimally with no browser resource issues detected
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,825 ▲90 | 13.16 ▼1.49 | 1.93 ▼0.46 | 38.34 ▼10.24 |
Dashboard /wp-admin | 2,209 ▲21 | 4.86 ▼0.95 | 110.58 ▲8.99 | 41.24 ▼2.55 |
Posts /wp-admin/edit.php | 2,089 ▼0 | 2.04 ▲0.01 | 38.88 ▲3.05 | 34.64 ▼0.71 |
Add New Post /wp-admin/post-new.php | 1,533 ▲14 | 23.49 ▲0.26 | 666.78 ▼49.15 | 58.30 ▲0.53 |
Media Library /wp-admin/upload.php | 1,388 ▲3 | 4.21 ▲0.04 | 123.89 ▲15.41 | 51.38 ▲4.25 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
You still need to fix the following
- This plugin did not uninstall successfully, leaving 6 options in the database
- widget_theysaidso_widget
- widget_recent-posts
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-comments
- db_upgraded
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | A shallow check that no server-side errors were triggered
Everything seems fine, however this is by no means 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 take a closer look at the following
- 3× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
Uncaught Error: Class 'acf_field' not found in wp-content/plugins/advanced-custom-fields-markdown/acf-markdown-v4.php:3
- > PHP Fatal error
Uncaught Error: Class 'acf_field' not found in wp-content/plugins/advanced-custom-fields-markdown/acf-markdown-v5.php:3
- > PHP Fatal error
Uncaught Error: Call to undefined function load_plugin_textdomain() in wp-content/plugins/advanced-custom-fields-markdown/acf-markdown.php:19
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine on the user side
Optimizations
Plugin configuration 93% from 29 tests
readme.txt 94% from 16 tests
Often overlooked, readme.txt is one of the most important files in your plugin
Please fix the following attributes:
- Tags: Too many tags (12 tag instead of maximum 10); only the first 5 tags are used in your directory listing
advanced-custom-fields-markdown/acf-markdown.php 92% from 13 tests
This is the main PHP file of "Advanced Custom Fields: Markdown Field" version 1.1.4, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
You should first fix the following items:
- Main file name: Name the main plugin file the same as the plugin slug ("advanced-custom-fields-markdown.php" instead of "acf-markdown.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
No dangerous file extensions were detected8,552 lines of code in 72 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 56 | 749 | 438 | 5,170 |
JavaScript | 4 | 423 | 600 | 2,009 |
Markdown | 8 | 363 | 0 | 885 |
PHP | 3 | 267 | 587 | 480 |
Stylus | 1 | 0 | 0 | 8 |
PHP code Passed 2 tests
A short review of cyclomatic complexity and code structure
Although this was not an exhaustive test, there were no cyclomatic complexity issues detected
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.05 |
Average class complexity | 3.50 |
▷ Minimum class complexity | 3.00 |
▷ Maximum class complexity | 4.00 |
Average method complexity | 1.29 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 4.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 | 17 | |
▷ Static methods | 0 | 0.00% |
▷ Public methods | 17 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 2 | |
▷ Named functions | 2 | 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
It is recommended to compress PNG files in your plugin to minimize bandwidth usage
2 PNG files occupy 0.02MB with 0.01MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
js/lib/highlight/styles/brown_papersq.png | 17.77KB | 9.92KB | ▼ 44.16% |
js/lib/highlight/styles/school_book.png | 0.47KB | 0.34KB | ▼ 27.37% |