Title: Bug
Last modified: September 26, 2026

---

# Bug

 *  [Anders Madsen](https://wordpress.org/support/users/itmesteren/)
 * (@itmesteren)
 * [4 days, 14 hours ago](https://wordpress.org/support/topic/bug-459/)
 * There is a bug when you have lazy load turned on
 * you need elementor and griffinforms as well, it will stop griffinforms from working

Viewing 1 replies (of 1 total)

 *  [griffinforms](https://wordpress.org/support/users/griffinforms/)
 * (@griffinforms)
 * [18 hours, 13 minutes ago](https://wordpress.org/support/topic/bug-459/#post-19033281)
 * 
   Hi [@itmesteren](https://wordpress.org/support/users/itmesteren/) ,
 * Thanks for reporting this compatibility issue. We reproduced it with Speed Booster
   Pack 4.5.9.1 when **Lazy load** media is enabled.
 * The problem was caused by an interaction between the two plugins. GriffinForms
   was placing a literal `<img>` element inside an inline JavaScript string. Speed
   Booster Pack’s lazy-load response rewrite scans the complete HTML response, including
   inline script text, and changed that string by inserting `loading="lazy"`. The
   inserted quotes broke the JavaScript parser, which then produced the `missing)
   after argument list` error and the related SVG placeholder error.
 * Elementor was only the place where the problem was visible—the same failure occurred
   with a normal GriffinForms shortcode when the same lazy-load setting was enabled.
 * GriffinForms 3.4.0.0 should fix this issue. We changed the affected renderers
   to create the image nodes through JavaScript instead of embedding literal image
   markup inside the inline script. We tested the fix with Speed Booster Pack inactive,
   active with Lazy load media disabled, and active with Lazy load media enabled,
   in both Elementor and normal shortcode contexts.
 * Please update GriffinForms to 3.4.0.0 and clear any page/cache output before 
   testing again. The existing Speed Booster Pack configuration should no longer
   break the GriffinForms script.
 * For future compatibility, it may also be worth considering excluding `<script
   >` contents from the lazy-load HTML rewrite, since changing markup-looking text
   inside JavaScript can produce similar parser failures for other plugins.
 * Thanks again for the report and for helping us identify the interaction.

Viewing 1 replies (of 1 total)

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fbug-459%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/speed-booster-pack/assets/icon.svg?rev=2342732)
 * [Speed Booster Pack ⚡ PageSpeed Optimization Suite](https://wordpress.org/plugins/speed-booster-pack/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/speed-booster-pack/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/speed-booster-pack/)
 * [Active Topics](https://wordpress.org/support/plugin/speed-booster-pack/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/speed-booster-pack/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/speed-booster-pack/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [griffinforms](https://wordpress.org/support/users/griffinforms/)
 * Last activity: [18 hours, 13 minutes ago](https://wordpress.org/support/topic/bug-459/#post-19033281)
 * Status: not resolved