Benchmarks
Plugin footprint 58% from 16 tests
Installer 0% from 1 test
🔺 Critical test (weight: 50) | It is important to correctly install your plugin, without throwing errors or notices
Please fix the following installer errors
- The plugin cannot be installed
- > Notice in wp-content/plugins/locationews/classes/Plugin.php+126
Trying to access array offset on value of type bool
Server metrics [RAM: ▲0.29MB] [CPU: ▲1.41ms] Passed 4 tests
Server-side resources used by Locationews
No issues were detected with server-side resource usage
Page | Memory (MB) | CPU Time (ms) |
---|---|---|
Home / | 3.58 ▲0.12 | 50.19 ▲6.65 |
Dashboard /wp-admin | 3.68 ▲0.38 | 51.28 ▼0.45 |
Posts /wp-admin/edit.php | 3.73 ▲0.38 | 50.81 ▲1.46 |
Add New Post /wp-admin/post-new.php | 6.23 ▲0.35 | 100.36 ▼2.04 |
Media Library /wp-admin/upload.php | 3.55 ▲0.32 | 40.82 ▲9.07 |
Import Settings /wp-admin/admin.php?page=locationews-json-settings | 3.42 | 27.51 |
Edit Settings /wp-admin/admin.php?page=locationews-settings | 3.43 | 29.84 |
Server storage [IO: ▲0.38MB] [DB: ▲0.00MB] Passed 3 tests
Input-output and database impact of this plugin
The plugin installed successfully
Filesystem: 37 new files
Database: no new tables, 8 new options
New WordPress options |
---|
widget_recent-comments |
locationews_user |
widget_theysaidso_widget |
locationews_options |
can_compress_scripts |
db_upgraded |
theysaidso_admin_options |
widget_recent-posts |
Browser metrics Passed 4 tests
Locationews: an overview of browser usage
This plugin has a minimal impact on browser resources
Page | Nodes | Memory (MB) | Script (ms) | Layout (ms) |
---|---|---|---|---|
Home / | 2,827 ▲81 | 13.65 ▼0.70 | 1.73 ▼0.08 | 41.29 ▼1.47 |
Dashboard /wp-admin | 2,236 ▲48 | 4.87 ▼1.02 | 108.76 ▼4.15 | 40.62 ▼5.39 |
Posts /wp-admin/edit.php | 2,116 ▲24 | 2.00 ▼0.00 | 40.10 ▲0.42 | 38.02 ▲2.31 |
Add New Post /wp-admin/post-new.php | 1,657 ▲129 | 23.29 ▲4.98 | 672.01 ▲25.61 | 79.20 ▲25.47 |
Media Library /wp-admin/upload.php | 1,412 ▲21 | 4.28 ▲0.06 | 96.71 ▼3.29 | 41.84 ▼0.15 |
Import Settings /wp-admin/admin.php?page=locationews-json-settings | 874 | 2.56 | 55.99 | 37.43 |
Edit Settings /wp-admin/admin.php?page=locationews-settings | 1,512 | 6.92 | 131.97 | 118.95 |
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
- widget_theysaidso_widget
- db_upgraded
- widget_recent-comments
- can_compress_scripts
- theysaidso_admin_options
- widget_recent-posts
Smoke tests 25% from 4 tests
Server-side errors 0% from 1 test
🔹 Test weight: 20 | This is a short smoke test looking for server-side errors
Smoke test failed, please fix the following
- 2 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=locationews-settings
- > Notice in wp-content/plugins/locationews/classes/Plugin.php+220
Undefined variable: post_meta
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 take a closer look at the following
- 6× PHP files trigger errors when accessed directly with GET requests:
- > PHP Fatal error
Uncaught Error: Class 'Locationews_AbstractProvider' not found in wp-content/plugins/locationews/classes/Provider/I18n.php:17
- > PHP Fatal error
Uncaught Error: Class 'Locationews_AbstractPlugin' not found in wp-content/plugins/locationews/classes/Plugin.php:17
- > PHP Fatal error
Uncaught Error: Class 'Locationews_AbstractProvider' not found in wp-content/plugins/locationews/classes/Provider/Public.php:17
- > PHP Fatal error
Uncaught Error: Class 'Locationews_AbstractProvider' not found in wp-content/plugins/locationews/classes/Provider/Admin.php:17
- > PHP Fatal error
Uncaught Error: Class 'Locationews_AbstractProvider' not found in wp-content/plugins/locationews/classes/Provider/Metabox.php:17
- > PHP Fatal error
Uncaught Error: Class 'Locationews_AbstractProvider' not found in wp-content/plugins/locationews/classes/Provider/Options.php:17
- > PHP Fatal error
User-side errors 0% from 1 test
🔹 Test weight: 20 | Just a short smoke test targeting errors on the browser (console and network errors and warnings)
Please fix the following user-side errors
- 2 occurences, only the last one shown
- > GET request to /wp-admin/admin.php?page=locationews-settings
- > Console-api (warning) in unknown
https://maps.googleapis.com/maps/api/js?key=AIzaSyDzBoxUanA44A1qpzSRJNQJL_f7CLEyisM&language=en®ion=US&libraries=places&ver=2.0.6 234:51 "Google Maps JavaScript API has been loaded directly without a callback. This is not supported and can lead to race conditions and suboptimal performance. For supported loading patterns please see https://goo.gle/js-api-loading"
- > GET request to /wp-admin/admin.php?page=locationews-json-settings
- > Javascript (severe) in unknown
/wp-admin/load-scripts.php?c=0&load%5Bchunk_0%5D=jquery-core,jquery-migrate,utils&ver=6.3.1 1:28721 Uncaught fca: Map: Expected mapDiv of type HTMLElement but was passed null.
Optimizations
Plugin configuration Passed 29 tests
readme.txt Passed 16 tests
The readme.txt file uses markdown syntax to describe your plugin to the world
6 plugin tags: publishing, local, news, location, journalism...
locationews/locationews.php Passed 13 tests
The main PHP file in "Locationews" ver. 2.0.6 adds more information about the plugin and also serves as the entry point for this plugin
47 characters long description:
Publish location based articles in Locationews.
Code Analysis Passed 3 tests
File types Passed 1 test
🔸 Test weight: 35 | This is a short overview of programming languages used in this plugin, detecting executable files
Everything looks great! No dangerous files found in this plugin5,007 lines of code in 27 files:
Language | Files | Blank lines | Comment lines | Lines of code |
---|---|---|---|---|
CSS | 2 | 0 | 27 | 2,742 |
PHP | 13 | 443 | 975 | 1,737 |
JavaScript | 9 | 54 | 24 | 263 |
PO File | 1 | 68 | 80 | 223 |
Markdown | 1 | 20 | 0 | 41 |
JSON | 1 | 0 | 0 | 1 |
PHP code Passed 2 tests
An overview of cyclomatic complexity and code structure
This plugin has no cyclomatic complexity issues
Cyclomatic complexity | |
---|---|
Average complexity per logical line of code | 0.50 |
Average class complexity | 26.60 |
▷ Minimum class complexity | 1.00 |
▷ Maximum class complexity | 105.00 |
Average method complexity | 3.77 |
▷ Minimum method complexity | 1.00 |
▷ Maximum method complexity | 29.00 |
Code structure | ||
---|---|---|
Namespaces | 0 | |
Interfaces | 0 | |
Traits | 0 | |
Classes | 10 | |
▷ Abstract classes | 2 | 20.00% |
▷ Concrete classes | 8 | 80.00% |
▷ Final classes | 0 | 0.00% |
Methods | 83 | |
▷ Static methods | 7 | 8.43% |
▷ Public methods | 83 | 100.00% |
▷ Protected methods | 0 | 0.00% |
▷ Private methods | 0 | 0.00% |
Functions | 11 | |
▷ Named functions | 5 | 45.45% |
▷ Anonymous functions | 6 | 54.55% |
Constants | 3 | |
▷ Global constants | 3 | 100.00% |
▷ Class constants | 0 | 0.00% |
▷ Public constants | 0 | 0.00% |
Plugin size Passed 2 tests
Image compression Passed 2 tests
Using a strong compression for your PNG files is a great way to speed-up your plugin
6 PNG files occupy 0.03MB with 0.01MB in potential savings
Potential savings
Compression of 5 random PNG files using pngquant | |||
---|---|---|---|
File | Size - original | Size - compressed | Savings |
assets/img/locationewslogo.png | 7.78KB | 4.19KB | ▼ 46.07% |
assets/img/locationewslogoretina.png | 16.29KB | 7.65KB | ▼ 53.01% |
assets/img/icon-small.png | 1.44KB | 1.11KB | ▼ 22.90% |
assets/img/locationewsmerkki.png | 2.71KB | 1.97KB | ▼ 27.25% |
assets/img/locationewsmerkkinormaali.png | 1.44KB | 1.11KB | ▼ 22.90% |