Benchmarks

Plugin footprint 83% from 16 tests

Installer Passed 1 test

🔺 Critical test (weight: 50) | Checking the installer triggered no errors

Install script ran successfully

Server metrics [RAM: ▼0.57MB] [CPU: ▼16.26ms] Passed 4 tests

This is a short check of server-side resources used by PPO Call To Actions

Server-side resource usage in normal parameters

Page	Memory (MB)	CPU Time (ms)
Home /	3.57 ▲0.11	43.24 ▼3.97
Dashboard /wp-admin	3.43 ▲0.12	47.44 ▲0.42
Posts /wp-admin/edit.php	3.48 ▲0.12	51.60 ▲3.85
Add New Post /wp-admin/post-new.php	3.25 ▼2.63	38.21 ▼61.66
Media Library /wp-admin/upload.php	3.35 ▲0.12	34.50 ▲0.18
PPO Call To Actions /wp-admin/options-general.php?page=PPOCTA	3.29	31.32

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

How much does this plugin use your filesystem and database?

There were no storage issued detected upon installing this plugin

Filesystem: 13 new files

Database: no new tables, 6 new options

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

Browser metrics Passed 4 tests

An overview of browser requirements for PPO Call To Actions

This plugin renders optimally with no browser resource issues detected

Page	Nodes	Memory (MB)	Script (ms)	Layout (ms)
Home /	2,808 ▲62	14.48 ▲0.10	1.76 ▼0.20	38.35 ▼3.72
Dashboard /wp-admin	2,210 ▲22	4.85 ▼1.04	108.62 ▼3.05	40.44 ▼3.37
Posts /wp-admin/edit.php	2,093 ▲1	2.06 ▲0.06	41.02 ▼0.86	34.38 ▼3.51
Add New Post /wp-admin/post-new.php	6,721 ▲5,187	20.15 ▼2.88	973.00 ▲323.29	60.43 ▼3.61
Media Library /wp-admin/upload.php	1,392 ▲10	4.29 ▲0.03	97.07 ▼5.32	41.82 ▼1.43
PPO Call To Actions /wp-admin/options-general.php?page=PPOCTA	1,001	2.20	23.40	24.20

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

You still need to fix the following

This plugin did not uninstall successfully, leaving 6 options in the database
- db_upgraded
- widget_recent-comments
- can_compress_scripts
- widget_recent-posts
- widget_theysaidso_widget
- theysaidso_admin_options

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)

These errors were triggered by the plugin

14 occurences, only the last one shown
- > GET request to /wp-admin/options-general.php?page=PPOCTA
- > User deprecated in wp-includes/functions.php+5453
Function get_settings is deprecated since version 2.1.0! Use get_option() instead.

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× GET requests to PHP files have triggered server-side errors or warnings:
- > PHP Fatal error
  Uncaught Error: Call to undefined function is_admin() in wp-content/plugins/ppo-call-to-actions/call2actions.php:23

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)

Everything seems fine on the user side

Optimizations

Plugin configuration 87% 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 need to be fixed:

Tags: There are too many tags (13 tag instead of maximum 10)
Screenshots: These screenshots do not have images: #1 (Settings page), #2 (Call and Register buttons)

The official readme.txt is a good inspiration

ppo-call-to-actions/call2actions.php 85% from 13 tests

The entry point to "PPO Call To Actions" version 0.1.3 is a PHP file that has certain tags in its header comment area

The following require your attention:

Description: Please keep the plugin description shorter than 140 characters (currently 166 characters long)
Main file name: It is recommended to name the main PHP file as the plugin slug ("ppo-call-to-actions.php" instead of "call2actions.php")

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

Success! There were no dangerous files found in this plugin702 lines of code in 1 file:

Language	Files	Blank lines	Comment lines	Lines of code
PHP	1	14	27	702

PHP code Passed 2 tests

Analyzing logical lines of code, cyclomatic complexity, and other code metrics

All good! No complexity issues found

Cyclomatic complexity
Average complexity per logical line of code	0.60
Average class complexity	76.00
▷ Minimum class complexity	76.00
▷ Maximum class complexity	76.00
Average method complexity	10.38
▷ Minimum method complexity	2.00
▷ Maximum method complexity	20.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	8
▷ Static methods	0	0.00%
▷ Public methods	8	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	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

It is recommended to compress PNG files in your plugin to minimize bandwidth usage

11 PNG files occupy 1.23MB with 0.62MB in potential savings

Potential savings

Compression of 5 random PNG files using pngquant
File	Size - original	Size - compressed	Savings
screenshot-1.png	25.72KB	13.28KB	▼ 48.37%
screenshot-6.png	256.97KB	100.63KB	▼ 60.84%
screenshot-2.png	21.24KB	9.92KB	▼ 53.30%
screenshot-3.png	264.92KB	110.97KB	▼ 58.11%
images/messenger.png	2.66KB	1.83KB	▼ 31.11%

Code Review | PPO Call To Actions

About plugin

Code review

User reviews

Install metrics