Source evidence

Performance

Melapress Login Security · support · 2023-09-27T13:29:00+00:00

Melapress Login Security plugin evidence original source source API

mixedsentiment

highseverity

0.95relevance

2replies

Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

8 / 34 rows with source links

23.5% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

26 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support

jonte98 resolved

This can be further optimized to eat atleast 2x less memory. Here is a test demonstrating the memory usage: https://plugintests.com/plugins/wporg/melapress-login-security/latest Most code is not even required to be loaded sitewide. EDIT: In addition, the remembered old password list and plugin settings can be using a custom database table for even better performance. This topic was modified 2 years, 8 months ago by jonte98 . This topic was modified 2 years, 8 months ago by jonte98 . This topic was modified 2 years, 8 months ago by jonte98 . Hello Jonte98. Sorry for not getting back to you earlier on this one. I had not subscribed yet to this plugin’s support tickets (mistake) so I was not notified of this. Thank you for the tips. We will look into this and we will update the plugin accordingly. Please let me know if there is anything else we can assist you with. Hello jonte98. We are working on the next update of the plugin and we will be definitely looking into ways and means on how to improve the plugin’s performance. However, I have a question about the database; the plugin settings are saved in the wp_options table, and old password etc are used in the wp_usermeta table, as recommended. So as such we are saving the data where it is recommended. Do you have any documentation / links that explain why it would be better to store such data in a custom table? Looking forward to hearing from you.

Commercial Context

Opportunity

trust and abuse-prevention operations

Buyer: site owners, agencies, and maintenance teams

Wedge: test login lockouts, bot/spam defenses, risky access changes, and incident alerts

Proof Blocked card complete market

Analysis

heuristic-v1

Summary: Performance: users show security, performance, missing feature pain that may indicate a product gap.

Evidence quote: Performance This can be further optimized to eat atleast 2x less memory.

Affected feature: form

security performance missing feature support

Plugin

API

Melapress Login Security

2.0K active installs · 27.0K downloads · rating 96.0

brute force limit login attempts limit logins login login security

Comments

2 shown

robertabela 2024-02-29T19:58:00+00:00

Hello Jonte98. Sorry for not getting back to you earlier on this one. I had not subscribed yet to this plugin’s support tickets (mistake) so I was not notified of this. Thank you for the tips. We will look into this and we will update the plugin accordingly. Please let me know if there is anything else we can assist you with.

robertabela 2024-03-22T10:14:00+00:00

Hello jonte98. We are working on the next update of the plugin and we will be definitely looking into ways and means on how to improve the plugin’s performance. However, I have a question about the database; the plugin settings are saved in the wp_options table, and old password etc are used in the wp_usermeta table, as recommended. So as such we are saving the data where it is recommended. Do you have any documentation / links that explain why it would be better to store such data in a custom table? Looking forward to hearing from you.