Benchmarks
Plugin footprint 83% from 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.03MB] [CPU: ▼10.55ms] Passed 4 tests
This is a short check of server-side resources used by WP Naver Map in Post
Server-side resource usage in normal parameters
| Page | Memory (MB) | CPU Time (ms) |
|---|---|---|
| Home / | 3.49 ▲0.03 | 42.60 ▼2.77 |
| Dashboard /wp-admin | 3.34 ▼0.00 | 48.97 ▼13.44 |
| Posts /wp-admin/edit.php | 3.39 ▲0.04 | 57.02 ▲8.01 |
| Add New Post /wp-admin/post-new.php | 5.92 ▲0.04 | 86.67 ▼23.17 |
| Media Library /wp-admin/upload.php | 3.27 ▲0.04 | 35.51 ▼2.81 |
Server storage [IO: ▲0.91MB] [DB: ▲0.00MB] Passed 3 tests
Filesystem and database footprint
This plugin was installed successfully
Filesystem: 32 new files
Database: no new tables, 6 new options
| New WordPress options |
|---|
| db_upgraded |
| widget_theysaidso_widget |
| can_compress_scripts |
| theysaidso_admin_options |
| widget_recent-posts |
| widget_recent-comments |
Browser metrics Passed 4 tests
An overview of browser requirements for WP Naver Map in Post
Normal browser usage
| Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
|---|---|---|---|---|
| Home / | 2,805 ▲44 | 14.14 ▼0.13 | 1.75 ▼0.13 | 43.46 ▲1.49 |
| Dashboard /wp-admin | 2,211 ▲37 | 5.64 ▲0.04 | 90.88 ▼1.26 | 44.07 ▲0.96 |
| Posts /wp-admin/edit.php | 2,123 ▲23 | 2.06 ▲0.03 | 40.37 ▲4.72 | 35.75 ▼1.23 |
| Add New Post /wp-admin/post-new.php | 1,558 ▲18 | 23.36 ▲0.09 | 666.40 ▲20.39 | 52.06 ▼0.13 |
| Media Library /wp-admin/upload.php | 1,416 ▲16 | 4.31 ▲0.06 | 97.98 ▼9.91 | 42.36 ▼6.86 |
Uninstaller [IO: ▲0.00MB] [DB: ▲0.00MB] 75% from 4 tests
🔸 Tests weight: 35 | The uninstall procedure must remove all plugin files and extra database tables
These items require your attention
- This plugin does not fully uninstall, leaving 6 options in the database
- widget_recent-posts
- widget_recent-comments
- theysaidso_admin_options
- can_compress_scripts
- db_upgraded
- widget_theysaidso_widget
Smoke tests 75% from 4 tests
Server-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for server-side errors
Even though everything seems fine, this is not 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
- 1× PHP files trigger server errors when accessed directly:
- > PHP Fatal error
Uncaught Error: Call to undefined function add_action() in wp-content/plugins/wp-naver-map-in-post/alghost_navermap.php:27
- > PHP Fatal error
User-side errors Passed 1 test
🔹 Test weight: 20 | This is a shallow check for browser errors
No browser issues were found
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
These attributes need to be fixed:
- Plugin Name: Please specify the plugin name on the first line (
=== wp-naver-map-in-post ===)
wp-naver-map-in-post/alghost_navermap.php 92% from 13 tests
This is the main PHP file of "WP Naver Map in Post" version 1.2, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions
Please make the necessary changes and fix the following:
- Main file name: Even though not officially enforced, the main plugin file should be the same as the plugin slug ("wp-naver-map-in-post.php" instead of "alghost_navermap.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
There were no executable files found in this plugin1,086 lines of code in 21 files:
| Language | Files | Blank lines | Comment lines | Lines of code |
|---|---|---|---|---|
| JavaScript | 16 | 124 | 217 | 634 |
| HTML | 3 | 37 | 56 | 299 |
| PHP | 1 | 23 | 22 | 137 |
| diff | 1 | 3 | 17 | 16 |
PHP code Passed 2 tests
An short overview of logical lines of code, cyclomatic complexity, and other code metrics
This plugin has no cyclomatic complexity problems
| Cyclomatic complexity | |
|---|---|
| Average complexity per logical line of code | 0.04 |
| Average class complexity | 0.00 |
| ▷ Minimum class complexity | 0.00 |
| ▷ Maximum class complexity | 0.00 |
| Average method complexity | 0.00 |
| ▷ Minimum method complexity | 0.00 |
| ▷ Maximum method complexity | 0.00 |
| Code structure | ||
|---|---|---|
| Namespaces | 0 | |
| Interfaces | 0 | |
| Traits | 0 | |
| Classes | 0 | |
| ▷ Abstract classes | 0 | 0.00% |
| ▷ Concrete classes | 0 | 0.00% |
| ▷ Final classes | 0 | 0.00% |
| Methods | 0 | |
| ▷ Static methods | 0 | 0.00% |
| ▷ Public methods | 0 | 0.00% |
| ▷ Protected methods | 0 | 0.00% |
| ▷ Private methods | 0 | 0.00% |
| Functions | 9 | |
| ▷ Named functions | 9 | 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 50% from 2 tests
Image compression 50% from 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
7 PNG files occupy 0.82MB with 0.47MB in potential savings
Potential savings
| Compression of 5 random PNG files using pngquant | |||
|---|---|---|---|
| File | Size - original | Size - compressed | Savings |
| assets/screenshot-2.png | 108.91KB | 28.41KB | ▼ 73.91% |
| icon/pin_spot2.png | 1.55KB | 1.61KB | 0.00% |
| assets/screenshot-1.png | 68.09KB | 18.73KB | ▼ 72.50% |
| assets/screenshot-4.png | 119.19KB | 34.09KB | ▼ 71.40% |
| assets/screenshot-3.png | 287.03KB | 90.95KB | ▼ 68.31% |