Home › Forums › Product Support Forums › Ajax Search Pro for WordPress Support › results lag making site footer missing
- This topic has 1 reply, 2 voices, and was last updated 1 year, 1 month ago by
Ernest Marcinko.
-
AuthorPosts
-
April 9, 2025 at 2:55 pm #53645
kerry_avxz
ParticipantHi, I have an issue I hope you can help with.
Some searches that can take a while longer than others sometimes stop before finishing and results do not complete and the site footer does not get loaded. As there is no footer there is also no scripts that are in the WP footer, so design and functionality are lost. I have checked docs etc and tried increasing Execution time in config but doesnt seem to work. Unforuately the results are inconsistant, sometimes it happens sometimes not. Happens more in priavte incognito browsers.
I will add screnshots for with and without issue. Heres a link https://archivesdundee.wpenginepowered.com/?s=book&asp_active=1&p_asid=1&p_asp_data=1&termset%5Battachment_category%5D%5B%5D=21&termset%5Battachment_category%5D%5B%5D=22&termset%5Battachment_category%5D%5B%5D=19&termset%5Battachment_category%5D%5B%5D=20&termset%5Battachment_category%5D%5B%5D=24&termset%5Battachment_category%5D%5B%5D=18&termset%5Battachment_category%5D%5B%5D=23&filters_initial=1&filters_changed=0&qtranslate_lang=0&asp_highlight=1¤t_page_id=5437
Scroll to the bottom to see if the footer is loaded.
April 10, 2025 at 9:36 am #53655Ernest Marcinko
KeymasterHi,
It’s because of the amount of text you are printing to the page and probably in combination with the keyword highlighter. I’m looking at the extracted texts, some of those are really really long and it eats up browser memory. It isn’t related to the search process, but the amount of data pushed to the page, it is way too much.
I would suggest turning off the keyword highlighter first, to see if that changes anything. It would explain the lag, as it has to parse through thousands of pages on page load and the browser memory spikes through the roof. If that doesn’t help at all, then it’s a script somewhere in elementor that tries to deal with the data and just fails. Then try to completely remove the extracted text, that should immediately resolve the problem.
The best solution would be to not load the text during page load, but to mitigate it to an asynchronous handler via rest API to load the text when the user clicks on the “view extracted text” icon. Nothing too complicated, only a single rest endpoint and a handler, that should do the trick. Not sure if Elementor has support for loading data asynchronously though, you may have to custom code it.
-
AuthorPosts
- You must be logged in to reply to this topic.