78% wp-keywords-report

Code Review | WP Keywords Report

WordPress plugin WP Keywords Report scored78%from 54 tests.

About plugin

  • Plugin page: wp-keywords-report
  • Plugin version: 1.0
  • PHP version: 7.4.16
  • WordPress compatibility: 2.8-3.8
  • WordPress version: 6.3.1
  • First release: Dec 26, 2013
  • Latest release: Sep 2, 2014
  • Number of updates: 8
  • Update frequency: every 31.2 days
  • Top authors: sunnyverma1984 (100%)

Code review

54 tests

User reviews

2 reviews

Install metrics

30+ active /5,269 total downloads

Benchmarks

Plugin footprint 83% from 16 tests

Installer Passed 1 test

🔺 Critical test (weight: 50) | Verifying that this plugin installs correctly without errors
The plugin installed successfully, without throwing any errors or notices

Server metrics [RAM: ▲0.00MB] [CPU: ▼2.26ms] Passed 4 tests

An overview of server-side resources used by WP Keywords Report
This plugin has minimal impact on server resources
PageMemory (MB)CPU Time (ms)
Home /3.48 ▲0.0238.91 ▼1.83
Dashboard /wp-admin3.31 ▼0.04260.89 ▲199.38
Posts /wp-admin/edit.php3.37 ▲0.0242.32 ▼3.03
Add New Post /wp-admin/post-new.php5.90 ▲0.0282.23 ▼5.64
Media Library /wp-admin/upload.php3.24 ▲0.0235.18 ▲1.46
Full Keywords Report /wp-admin/admin.php?page=full-keywords-report3.20249.16

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

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

Browser metrics Passed 4 tests

A check of browser resources used by WP Keywords Report
There were no issues detected in relation to browser resource usage
PageNodesMemory (MB)Script (ms)Layout (ms)
Home /2,151 ▼58412.29 ▼1.992.07 ▲0.3242.66 ▼3.71
Dashboard /wp-admin1,560 ▼6281.38 ▼3.5313.13 ▼103.3333.93 ▼9.78
Posts /wp-admin/edit.php2,094 ▲52.01 ▲0.0038.95 ▲3.2641.72 ▲6.28
Add New Post /wp-admin/post-new.php1,669 ▲15621.76 ▲4.08678.45 ▲79.3440.47 ▼2.98
Media Library /wp-admin/upload.php1,387 ▲24.21 ▲0.04100.50 ▼0.4840.19 ▼4.02
Full Keywords Report /wp-admin/admin.php?page=full-keywords-report6751.536.3015.55

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

🔸 Tests weight: 35 | Checking the uninstaller removed all traces of the plugin
The following items require your attention
  • This plugin did not uninstall successfully, leaving 7 options in the database
    • theysaidso_admin_options
    • widget_recent-posts
    • db_upgraded
    • recovery_mode_email_last_sent
    • can_compress_scripts
    • widget_recent-comments
    • widget_theysaidso_widget

Smoke tests 50% from 4 tests

Server-side errors 0% from 1 test

🔹 Test weight: 20 | This is a shallow check for server-side errors
These errors were triggered by the plugin
    • > GET request to /wp-admin/admin.php?page=full-keywords-report
    • > Error in wp-content/plugins/wp-keywords-report/wp-keywords-report.php+43
    Uncaught Error: Cannot use object of type WP_Error as array in wp-content/plugins/wp-keywords-report/wp-keywords-report.php:43
    Stack trace:
    #0 wp-includes/class-wp-hook.php(310): gkr_full_report()
    #1 wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters()
    #2 wp-includes/plugin.php(517): WP_Hook->do_action()
    #3 wp-admin/admin.php(259): do_action()
    #4 {main}
    thrown

SRP 50% from 2 tests

🔹 Tests weight: 20 | It is important to ensure that your PHP files perform no action when accessed directly, respecting the single-responsibility principle
Please fix the following items
  • 1× PHP files trigger errors when accessed directly with GET requests:
    • > PHP Fatal error
      Uncaught Error: Call to undefined function site_url() in wp-content/plugins/wp-keywords-report/wp-keywords-report.php:12

User-side errors Passed 1 test

🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
There were no browser issues found

Optimizations

Plugin configuration 90% from 29 tests

readme.txt 88% from 16 tests

The readme.txt file is important because it is parsed by WordPress.org for the public listing of your plugin
Attributes that require attention:
  • Screenshots: Add images for these screenshots: #1 (Dashboard widget demo), #2 (Full report page demo)
  • Tags: There are too many tags (17 tag instead of maximum 10)
Please take inspiration from this readme.txt

wp-keywords-report/wp-keywords-report.php 92% from 13 tests

The entry point to "WP Keywords Report" version 1.0 is a PHP file that has certain tags in its header comment area
Please make the necessary changes and fix the following:
  • Description: Please keep the plugin description shorter than 140 characters (currently 177 characters long)

Code Analysis Passed 3 tests

File types Passed 1 test

🔸 Test weight: 35 | Executable files are not allowed as they can serve as attack vectors
Good job! No executable or dangerous file extensions detected56 lines of code in 1 file:
LanguageFilesBlank linesComment linesLines of code
PHP101356

PHP code Passed 2 tests

An short overview of logical lines of code, cyclomatic complexity, and other code metrics
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity
Average complexity per logical line of code0.26
Average class complexity0.00
▷ Minimum class complexity0.00
▷ Maximum class complexity0.00
Average method complexity0.00
▷ Minimum method complexity0.00
▷ Maximum method complexity0.00
Code structure
Namespaces0
Interfaces0
Traits0
Classes0
▷ Abstract classes00.00%
▷ Concrete classes00.00%
▷ Final classes00.00%
Methods0
▷ Static methods00.00%
▷ Public methods00.00%
▷ Protected methods00.00%
▷ Private methods00.00%
Functions5
▷ Named functions5100.00%
▷ Anonymous functions00.00%
Constants0
▷ Global constants00.00%
▷ Class constants00.00%
▷ Public constants00.00%

Plugin size Passed 2 tests

Image compression Passed 2 tests

Often times overlooked, PNG files can occupy unnecessary space in your plugin
2 PNG files occupy 0.32MB with 0.21MB in potential savings
Potential savings
Compression of 2 random PNG files using pngquant
FileSize - originalSize - compressedSavings
screenshot-2.png184.16KB59.75KB▼ 67.55%
screenshot-1.png145.43KB50.49KB▼ 65.28%