QueueForge – Interaction to Next Paint Fixer

Google’s Core Web Vitals now use Interaction to Next Paint (INP) instead of First Input Delay. Caching plugins make pages load fast, but they do nothing about the bloated JavaScript from other plugins, themes, ads, and analytics that blocks the browser’s main thread and makes mobile interactions feel choppy.

QueueForge INP Fixer attacks INP directly:

• Delays eligible JavaScript until the visitor’s first scroll, tap, key press, or mouse move. The main thread stays free during the critical early window, so the page responds immediately.

• Yields the main thread between scripts when the deferred code finally runs, using the native scheduler.yield() (with a setTimeout fallback) so the queued scripts do not re-block the thread in one long task.

• Fallback timeout loads delayed scripts automatically after N seconds even with no interaction, protecting analytics and ad impressions.

• Live INP overlay for admins shows measured INP and long-task blocking time right on the front end, using PerformanceObserver ( event + longtask ).

Key Features

• Delay all eligible third-party / theme JavaScript until first interaction

• Main-thread yielding between deferred scripts ( scheduler.yield() + fallback)

• Configurable fallback timeout (0 = interaction only)

• Optional jQuery delay (off by default for safety)

• Keyword exclusion list, plus per-tag data-no-optimize opt-out

• Skips logged-in editors so page builders keep working

• Live INP + blocking-time debug overlay (admins only)

queueforge_off URL switch to bypass the delay for one page load

• No database writes on the front end; nothing is cached or stored per visitor

Why INP?

INP measures how quickly the page visually responds to every interaction across the whole visit, not just the first one. The single biggest cause of poor INP is JavaScript executing long tasks on the main thread while the user is trying to interact. Delaying that JavaScript until it is actually needed — and breaking its execution into yield-separated chunks — is the most direct fix.

Developer-Friendly

• qfinp_exclusions filter to programmatically add never-delay keywords.

• Uses an output buffer on template_redirect; no edits to your theme or other plugins.