High CPU load from Extractor.php
I'm currently working on the optimisation of my website using Code Profiler Pro (CPP). As I already knew from PageSpeed, Brizy is slow. CPP confirms this now and I want to show you some screenshots.


As you can see the majority of slow processes are coming from Brizy and specifically one: extractor.php. It looks like it lexes and tokenises the entire page content with heavy regular expressions on every uncached request, converts the token stream into a full in‑memory array, and then walks that array multiple times (including recursively for nested placeholders) while also doing fairly expensive attribute parsing. This design means that on complex Brizy pages the placeholder extraction step ends up consuming a lot of CPU time.
Is the development team aware of this and is this on the roadmap for improvement?
-
Hi Patrick,
Thank you for reaching out.
To help isolate the issue, could you please temporarily disable all other plugins except Brizy and Brizy Pro, then test again to see whether extractor time scales with page? Additionally, please ensure you're running PHP 8.1+ and, if available, that object caching (Redis/Memcached) is enabled.
Please try this and let me know how it goes.
Best regards,
Ariel H.0 -
Sure. Below you can see the screenshots from a test with everything but Brizy off.I've included "page3" which shows also the specific methods and functions that are causing this. And yes, I'm on PHP 8.3.30.


0 -
Hi Patrick,
Thank you for the update.
To help us investigate this properly, would it be possible for you to provide temporary access to your WordPress admin area? We don’t have access to Code Profiler Pro on our end, so we’ll need to review and check the issue directly on your site. Apologies for the inconvenience, and please feel free to create a temporary admin account that you can remove once we’re done.
Kindly send the following details to communitysupport@brizy.io:
Community post link: https://support.brizy.io/hc/en-us/community/posts/33230910438418
WordPress Admin URL:
Username:
Password:Best regards,
Ariel H.0 -
Hi Patrick,
Thank you for your cooperation.
For comparison, I installed Code Profiler Pro on my staging site and imported your homepage. On our end, Brizy’s execution time is around 0.151279 seconds, which is considerably lower than what you’re seeing.

Given this difference, the slowdown may be related to server resource limits. I recommend checking your hosting resource usage. It would also be helpful to reach out to your hosting provider so they can review the issue from their side and check the server logs directly, as those would provide more accurate insight.
Please try this and let me know how it goes.
Kind regards,
Ariel H.0
Please sign in to leave a comment.
Comments
4 comments