Thank you for the response! You're correct, I'm Dutch đŗđą, actually, the whole team is đ
I saw that Buttonizer was taking it's time on your webserver, but I am not sure if it's Buttonizer alone as it loads in with the core of WordPress. So the ajax request will use the same loadtime as a regular WordPress page. It may be the webserver itself, a plugin (Buttonizer?) or the core of WordPress itself.
In short: when your website is taking 1 second to load + HTML & all plugins, it will mean Buttonizer will load at least 1 second, as the core needs that time to load. So it's easy to say from a hosting from a waterfall "ÊÊn enkele actie die u ruim 1.72 seconde kost" (one single action that requires 1.72 seconds from the webserver) when the site itself also needs 1 second to load the core. I actually thought that the webhoster checked the webserver logs and said it was Buttonizer, but they took the easy way by just looking at the request đ
As you can see another request on your website, a POST request not from Buttonizer, also takes more then 1 second to load (taking even a longer time to load then Buttonizer). Screenshot below (I use Lightshot for screenshots):
![Lightshot screenshot](https://image.prntscr.com/image/6y9ANLVZRtmCUHdJvVVltw.png)
But, as you're saying it's faster when you've turned off Buttonizer, I'm getting curious! Are you able to turn off Buttonizer for a few minutes? Then I can re-do some performance tests đ
To add a photo to a post, you can use the following Markdown code:
![](http://example-photo-url.com/photo.png)