Exploding page loadtime as of version 5.8.2 and up

Hello @hanswitteprins

please let us more investigate it and of course, when we can improve the loading time we will try to improve a better performance with the coming updates.

Best regards
Andreas

Closed because of inactivity.

@aweissinpsyde ,

What activity where you expecting, when you just say you will investigate? There is no question there for me to answer to.

Without any solution / change in the plugin, I cannot update to the latest version on this site, since my pages basically stop loading. As I understand it the activity was needed on your end.

I understand this issue is not occurring on all sites, I have another one that does fine with the latest version, but there is a problem when I activate the versions I mentioned, that isn’t happening in earlier versions.

Sinply stating there is no activity, when you didn’t ask for a response and marking it as solved, isn’t enough. This isn’t resolved. Should I enter it again?

If you need anything on our end, you can ask for what you need. Uptil now I didn’t receive any request like that, as far as I know.

regards,
Hans

Hallo @hanswitteprins

unsere Entwickler wusste diesbzgl. Bescheid. Es wurde hier keine Aktivit?t deinerseits erwartet. Wir schliessen Tickets nach 7 Tagen, um hier ein bessere übersicht behalten zu k?nnen. Wir ich sehen, scheint sich die Ladezeit mit dem letzten Update verbessert zu haben.

Wir arbeiten st?ndig weiter daran das Plugin performanter zu machen.

Mit besten Grüssen
Andreas

PS: QueryMonitor als Referenz ist keine verl?ssliche Quelle, das dieses Plugin oftmals false/positive Ergebnisse auswirft.

Hello @aweissinpsyde ,

It seems solved now, and I know what was the problem and how to rule it out now. I understand how closing due to time works, but this problem made the plugin unusable, what is a BIG problem when it is your shops gateway.

I don’t depend on QueryMonitor to test my loadtime, finding out that the page needed 4 times the pageload time was clear enough without it. We were getting user-responses that said the page didn’t work at all, something you don’t want to have happen in the checkout especially.

13-20 seconds or more for a add to cart with version 5.8.2 is crazy long and basically blocks the checkout entirely.

If I was the developer I now would take a good long look at my testing environment and why that quadrupling of the response-time wasn’t noticed before issuing this release. You cannot say performance is important and at the same time let such a thing go through to production.

Perhaps you need a testing setup that also simulates servers that run far from where the server mollie is run and need more time to receive data from mollie.com. Or something that shouts problem when you again add something like this, adding a second to the users response time per icon for something more or less trivial as an icon.

QM has been a very useful source in finding out what was causing the problem and in finding out if the solution worked.

Thanks for solving it in the current version. It has been a long wait.

Hans