68% mobileesp-for-wordpress

Code Review | MobileESP for WordPress

WordPress plugin MobileESP for WordPress scored68%from 54 tests.

About plugin

  • Plugin page: mobileesp-for-wor...
  • Plugin version: 1.6
  • PHP version: 7.4.16
  • WordPress compatibility: 2.8.3-5.3.1
  • WordPress version: 6.3.1
  • First release: Jan 10, 2011
  • Latest release: Dec 14, 2019
  • Number of updates: 45
  • Update frequency: every 72.4 days
  • Top authors: BandonRandon (100%)

Code review

54 tests

User reviews

5 reviews

Install metrics

50+ active /12,895 total downloads

Benchmarks

Plugin footprint 65% 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.96MB] [CPU: ▼36.79ms] Passed 4 tests

An overview of server-side resources used by MobileESP for WordPress
Server-side resource usage in normal parameters
PageMemory (MB)CPU Time (ms)
Home /3.34 ▼0.1223.13 ▼16.36
Dashboard /wp-admin2.99 ▼0.3522.10 ▼39.42
Posts /wp-admin/edit.php2.99 ▼0.3624.89 ▼17.97
Add New Post /wp-admin/post-new.php2.99 ▼2.8923.54 ▼73.40
Media Library /wp-admin/upload.php2.99 ▼0.2321.09 ▼11.23
MobileESP for WP /wp-admin/options-general.php?page=mobileesp-for-wordpress/mobileesp_wp.php2.9922.09

Server storage [IO: ▲0.09MB] [DB: ▲0.07MB] Passed 3 tests

Filesystem and database footprint
There were no storage issued detected upon installing this plugin
Filesystem: 4 new files
Database: no new tables, 6 new options
New WordPress options
can_compress_scripts
widget_recent-posts
widget_recent-comments
widget_theysaidso_widget
theysaidso_admin_options
db_upgraded

Browser metrics Passed 4 tests

An overview of browser requirements for MobileESP for WordPress
Normal browser usage
PageNodesMemory (MB)Script (ms)Layout (ms)
Home /2,804 ▲5813.26 ▼1.121.57 ▼0.1642.50 ▼3.44
Dashboard /wp-admin2,204 ▲165.86 ▲0.78103.67 ▼1.2237.60 ▲0.17
Posts /wp-admin/edit.php2,096 ▲102.00 ▼0.0238.26 ▲3.2335.31 ▼1.43
Add New Post /wp-admin/post-new.php1,539 ▲623.33 ▼0.06648.61 ▼11.5358.00 ▲7.07
Media Library /wp-admin/upload.php1,392 ▲74.24 ▲0.0795.56 ▼1.1741.58 ▼2.15
MobileESP for WP /wp-admin/options-general.php?page=mobileesp-for-wordpress/mobileesp_wp.php7892.0324.7129.74

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

🔸 Tests weight: 35 | All plugins must uninstall correctly, removing their source code and extra database tables they might have created
The following items require your attention
  • This plugin cannot be uninstalled
    • > User deprecated in wp-includes/functions.php+5737
    Function has_cap was called with an argument that is deprecated since version 2.0.0! Usage of user levels is deprecated. Use capabilities instead.
  • This plugin does not fully uninstall, leaving 6 options in the database
    • widget_theysaidso_widget
    • theysaidso_admin_options
    • can_compress_scripts
    • widget_recent-comments
    • db_upgraded
    • widget_recent-posts

Smoke tests 50% from 4 tests

Server-side errors 0% from 1 test

🔹 Test weight: 20 | Just a short smoke test targeting errors on the server (in the Apache logs)
Please fix the following server-side errors
  • 2 occurences, only the last one shown
    • > GET request to /wp-admin/options-general.php?page=mobileesp-for-wordpress/mobileesp_wp.php
    • > User deprecated in wp-includes/functions.php+5737
    Function has_cap was called with an argument that is deprecated since version 2.0.0! Usage of user levels is deprecated. Use capabilities instead.

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 fix the following
  • 1× PHP files trigger server-side errors or warnings when accessed directly:
    • > PHP Fatal error
      Uncaught Error: Call to undefined function trailingslashit() in wp-content/plugins/mobileesp-for-wordpress/mobileesp_wp.php:32

User-side errors Passed 1 test

🔹 Test weight: 20 | A shallow check that no browser errors were triggered
No browser errors were detected

Optimizations

Plugin configuration 93% from 29 tests

readme.txt Passed 16 tests

Perhaps the most important file in your plugin readme.txt gets parsed in order to generate the public listing of your plugin
4 plugin tags: mobileesp, redirect, browser, mobile

mobileesp-for-wordpress/mobileesp_wp.php 85% from 13 tests

The main file in "MobileESP for WordPress" v. 1.6 serves as a complement to information provided in readme.txt and as the entry point to the plugin
It is important to fix the following:
  • Main file name: Name the main plugin file the same as the plugin slug ("mobileesp-for-wordpress.php" instead of "mobileesp_wp.php")
  • Description: Keep the plugin description shorter than 140 characters (currently 302 characters long)

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
No dangerous file extensions were detected865 lines of code in 2 files:
LanguageFilesBlank linesComment linesLines of code
PHP2177361865

PHP code Passed 2 tests

Cyclomatic complexity and code structure are the fingerprint of this plugin
Great job! No cyclomatic complexity issues were detected in this plugin
Cyclomatic complexity
Average complexity per logical line of code0.74
Average class complexity223.00
▷ Minimum class complexity223.00
▷ Maximum class complexity223.00
Average method complexity4.17
▷ Minimum method complexity1.00
▷ Maximum method complexity17.00
Code structure
Namespaces0
Interfaces0
Traits0
Classes1
▷ Abstract classes00.00%
▷ Concrete classes1100.00%
▷ Final classes00.00%
Methods70
▷ Static methods00.00%
▷ Public methods70100.00%
▷ Protected methods00.00%
▷ Private methods00.00%
Functions3
▷ Named functions3100.00%
▷ Anonymous functions00.00%
Constants1
▷ Global constants1100.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
There were not PNG files found in your plugin