Benchmarks

Plugin footprint 65% from 16 tests

Installer Passed 1 test

🔺 Critical test (weight: 50) | All plugins must install correctly, without throwing any errors, warnings, or notices

This plugin's installer ran successfully

Server metrics [RAM: ▲0.04MB] [CPU: ▼4.33ms] Passed 4 tests

Server-side resources used by Naver Blog

Server-side resource usage in normal parameters

Page	Memory (MB)	CPU Time (ms)
Home /	3.50 ▲0.03	40.07 ▼8.13
Dashboard /wp-admin	3.35 ▲0.05	50.03 ▼2.36
Posts /wp-admin/edit.php	3.47 ▲0.11	50.32 ▲0.76
Add New Post /wp-admin/post-new.php	5.94 ▲0.04	93.98 ▼7.60
Media Library /wp-admin/upload.php	3.28 ▲0.04	42.69 ▲1.99

Server storage [IO: ▲0.25MB] [DB: ▲0.00MB] Passed 3 tests

Input-output and database impact of this plugin

This plugin was installed successfully

Filesystem: 6 new files

Database: no new tables, 7 new options

New WordPress options
widget_recent-posts
theysaidso_admin_options
db_upgraded
HintsNaverBlogAPI
widget_theysaidso_widget
widget_recent-comments
can_compress_scripts

Browser metrics Passed 4 tests

Checking browser requirements for Naver Blog

There were no issues detected in relation to browser resource usage

Page	Nodes	Memory (MB)	Script (ms)	Layout (ms)
Home /	2,818 ▲57	14.35 ▲0.00	1.83 ▼0.59	41.57 ▼5.62
Dashboard /wp-admin	2,202 ▲31	5.62 ▲0.03	90.56 ▼12.83	44.07 ▲0.58
Posts /wp-admin/edit.php	2,104 ▲7	2.03 ▲0.05	37.99 ▲0.90	36.07 ▲2.26
Add New Post /wp-admin/post-new.php	1,539 ▲13	23.17 ▲0.00	694.74 ▼30.28	53.67 ▼4.78
Media Library /wp-admin/upload.php	1,404 ▲4	4.23 ▲0.03	114.25 ▼1.59	48.12 ▼2.21
Naver Blog API /wp-admin/naverblogapi.php	26	0.42	0.15	14.35

Uninstaller [IO: ▲0.25MB] [DB: ▲0.00MB] 50% from 4 tests

🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces

Please fix the following items

Incomplete uninstall procedure, leaving 6 files (0.25MB) in the plugin directory
- (new file) screenshot-1.png
- (new file) lib/xmlrpc.inc
- (new file) readme.txt
- (new file) naverblogapi.php
- (new file) naverblogapi_admin_settings.php
- (new file) screenshot-2.png
The uninstall procedure has failed, leaving 7 options in the database
- theysaidso_admin_options
- widget_recent-comments
- widget_theysaidso_widget
- can_compress_scripts
- db_upgraded
- HintsNaverBlogAPI
- widget_recent-posts

Smoke tests 50% from 4 tests

Server-side errors Passed 1 test

🔹 Test weight: 20 | This is a shallow check for server-side errors

Even though no errors were found, this is by no means an exhaustive test

SRP 50% from 2 tests

🔹 Tests weight: 20 | The single-responsibility principle: PHP files have to remain inert when accessed directly, throwing no errors and performing no actions

Please take a closer look at the following

1× GET requests to PHP files trigger server-side errors or Error 500 responses:
- > PHP Fatal error
  Uncaught Error: Using $this when not in object context in wp-content/plugins/naver-blog-api/naverblogapi_admin_settings.php:8

User-side errors 0% from 1 test

🔹 Test weight: 20 | This is a shallow check for browser errors

Please fix the following user-side errors

- > GET request to /wp-admin/naverblogapi.php
- > Network (severe)
wp-admin/naverblogapi.php - Failed to load resource: the server responded with a status of 404 (Not Found)

Optimizations

Plugin configuration 93% from 29 tests

readme.txt 94% from 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

Attributes that require attention:

Screenshots: These screenshots do not have images: #1 (관리자 모드로 최소한의 기능만 제작되었습니다.), #2 (포스팅시 Naver Blog Options 에서 세부 설정을 해주시면 됩니다.)

The official readme.txt is a good inspiration

naver-blog-api/naverblogapi.php 92% from 13 tests

This is the main PHP file of "Naver Blog" version 1.0, providing information about the plugin in the header fields and serving as the principal entry point to the plugin's functions

Please take the time to fix the following:

Main file name: Name the main plugin file the same as the plugin slug ("naver-blog-api.php" instead of "naverblogapi.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

Good job! No executable or dangerous file extensions detected2,810 lines of code in 3 files:

Language	Files	Blank lines	Comment lines	Lines of code
PHP	3	254	1,072	2,810

PHP code Passed 2 tests

A short review of cyclomatic complexity and code structure

Great job! No cyclomatic complexity issues were detected in this plugin

Cyclomatic complexity
Average complexity per logical line of code	0.24
Average class complexity	17.00
▷ Minimum class complexity	17.00
▷ Maximum class complexity	17.00
Average method complexity	2.23
▷ Minimum method complexity	1.00
▷ Maximum method complexity	4.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	13
▷ Static methods	2	15.38%
▷ Public methods	13	100.00%
▷ Protected methods	0	0.00%
▷ Private methods	0	0.00%
Functions	0
▷ Named functions	0	0.00%
▷ Anonymous functions	0	0.00%
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

All PNG images should be compressed to minimize bandwidth usage for end users

2 PNG files occupy 0.12MB with 0.05MB in potential savings

Potential savings

Compression of 2 random PNG files using pngquant
File	Size - original	Size - compressed	Savings
screenshot-1.png	33.05KB	26.55KB	▼ 19.68%
screenshot-2.png	92.92KB	30.43KB	▼ 67.25%

Code Review | Naver Blog

About plugin

Code review

User reviews

Install metrics