74% full-utf-8

Code Review | Full UTF-8

WordPress plugin Full UTF-8 scored74%from 54 tests.

About plugin

  • Plugin page: full-utf-8
  • Plugin version: 2.0.1
  • PHP version: 7.4.16
  • WordPress compatibility: 1.0-4.0
  • WordPress version: 6.3.1
  • First release: Jan 14, 2011
  • Latest release: Oct 6, 2014
  • Number of updates: 31
  • Update frequency: every 43.9 days
  • Top authors: aercolino (100%)

Code review

54 tests

User reviews

6 reviews

Install metrics

600+ active /18,353 total downloads

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
Install script ran successfully

Server metrics [RAM: ▲0.02MB] [CPU: ▼5.41ms] Passed 4 tests

Server-side resources used by Full UTF-8
This plugin does not affect your website's performance
PageMemory (MB)CPU Time (ms)
Home /3.48 ▲0.0243.92 ▲2.18
Dashboard /wp-admin3.32 ▲0.0247.12 ▼5.63
Posts /wp-admin/edit.php3.37 ▲0.0244.97 ▼4.92
Add New Post /wp-admin/post-new.php5.90 ▲0.0283.45 ▼13.15
Media Library /wp-admin/upload.php3.25 ▲0.0238.60 ▲2.06

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

How much does this plugin use your filesystem and database?
The plugin installed successfully
Filesystem: 9 new files
Database: no new tables, 6 new options
New WordPress options
db_upgraded
widget_recent-posts
theysaidso_admin_options
can_compress_scripts
widget_theysaidso_widget
widget_recent-comments

Browser metrics Passed 4 tests

Checking browser requirements for Full UTF-8
Minimal impact on browser resources
PageNodesMemory (MB)Script (ms)Layout (ms)
Home /2,789 ▲2814.75 ▲0.361.74 ▼0.3245.05 ▼5.35
Dashboard /wp-admin2,198 ▲215.63 ▼0.0189.51 ▼8.0339.73 ▼3.31
Posts /wp-admin/edit.php2,100 ▼02.00 ▼0.0034.76 ▼0.8835.62 ▼0.71
Add New Post /wp-admin/post-new.php1,545 ▲1923.25 ▲5.69653.69 ▼1.2159.31 ▲4.46
Media Library /wp-admin/upload.php1,394 ▼64.25 ▲0.02104.43 ▼0.4941.36 ▼5.73

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

🔸 Tests weight: 35 | It is important to correctly uninstall your plugin, without leaving any traces
These items require your attention
  • Uninstall procedure validation failed for this plugin
    • > Warning in wp-content/plugins/full-utf-8/FullUtf8.php+142
    rename(wp-content/db.php,wp-content/db.php---2023-10-14--16-36-56): No such file or directory
  • Zombie WordPress options were found after uninstall: 6 options
    • widget_recent-comments
    • theysaidso_admin_options
    • can_compress_scripts
    • db_upgraded
    • widget_recent-posts
    • widget_theysaidso_widget

Smoke tests 75% from 4 tests

Server-side errors Passed 1 test

🔹 Test weight: 20 | A smoke test targeting 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
  • 5× GET requests to PHP files have triggered server-side errors or warnings:
    • > PHP Fatal error
      Uncaught Error: Class 'wpdb' not found in wp-content/plugins/full-utf-8/FullUtf8_wpdb.php:10
    • > PHP Warning
      require_once(WP_CONTENT_DIR/plugins/full-utf-8/FullUtf8_wpdb.php): failed to open stream: No such file or directory in wp-content/plugins/full-utf-8/db.php on line 7
    • > PHP Fatal error
      require_once(): Failed opening required 'WP_CONTENT_DIR/plugins/full-utf-8/FullUtf8_wpdb.php' (include_path='.:/usr/share/php') in wp-content/plugins/full-utf-8/db.php on line 7
    • > PHP Warning
      Use of undefined constant WP_CONTENT_DIR - assumed 'WP_CONTENT_DIR' (this will throw an Error in a future version of PHP) in wp-content/plugins/full-utf-8/db.php on line 7
    • > PHP Fatal error
      Uncaught Error: Call to undefined function register_activation_hook() in wp-content/plugins/full-utf-8/full-utf-8.php:16

User-side errors Passed 1 test

🔹 Test weight: 20 | This is a smoke test targeting browser errors/issues
Everything seems fine, but this is not an exhaustive test

Optimizations

Plugin configuration 93% from 29 tests

readme.txt 88% from 16 tests

Don't ignore readme.txt as it is the file that instructs WordPress.org on how to present your plugin to the world
These attributes need your attention:
  • Screenshots: Add an image for screenshot #1 (WordPress + Full UTF-8: Nice.
    )
  • Plugin Name: Please replace "Plugin Name" with the name of your plugin on the first line ( === full-utf-8 === )
The official readme.txt might help

full-utf-8/full-utf-8.php Passed 13 tests

"Full UTF-8" version 2.0.1's main PHP file describes plugin functionality and also serves as the entry point to any WordPress functionality
82 characters long description:
Trustfully write anything in your language. Stop worrying about truncated content.

Code Analysis Passed 3 tests

File types Passed 1 test

🔸 Test weight: 35 | An overview of files in this plugin; executable files are not allowed
Good job! No executable or dangerous file extensions detected464 lines of code in 5 files:
LanguageFilesBlank linesComment linesLines of code
PHP579312464

PHP code Passed 2 tests

Analyzing cyclomatic complexity and code structure
Everything seems fine, there were no complexity issues found
Cyclomatic complexity
Average complexity per logical line of code0.38
Average class complexity20.00
▷ Minimum class complexity1.00
▷ Maximum class complexity50.00
Average method complexity4.62
▷ Minimum method complexity1.00
▷ Maximum method complexity14.00
Code structure
Namespaces0
Interfaces0
Traits0
Classes4
▷ Abstract classes00.00%
▷ Concrete classes4100.00%
▷ Final classes00.00%
Methods21
▷ Static methods1990.48%
▷ Public methods1361.90%
▷ Protected methods314.29%
▷ Private methods523.81%
Functions0
▷ Named functions00.00%
▷ Anonymous functions00.00%
Constants0
▷ Global constants00.00%
▷ Class constants00.00%
▷ Public constants00.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.20MB with 0.13MB in potential savings
Potential savings
Compression of 3 random PNG files using pngquant
FileSize - originalSize - compressedSavings
screenshot-3.png79.58KB26.42KB▼ 66.80%
screenshot-2.png51.23KB17.11KB▼ 66.60%
screenshot-1.png69.05KB22.83KB▼ 66.94%