Checked the Our Results page on desktop against several site pages.
Finding: this is not a full Intaker outage. Intaker loads after interaction, but WP Rocket delays the Intaker script with type="text/rocketlazyloadscript". On idle desktop load it does not populate. On the Our Results page specifically, mouse movement and scrolling did not reveal it in one rendered run; pressing Tab triggered it and the Intaker network/API calls completed successfully.
Artifacts: C:UsersSAguiarDocumentsCodexsite-qaintaker-desktop-2026-05-14
Key technical signal: after interaction, the browser requested https://intaker.azureedge.net/widget/chat.min.js and chat-api.intaker.com endpoints with 200 responses.
The issue is broader than one page if expected behavior is immediate desktop population on page load. The Results page is the most obvious failure because it may not trigger on mouse/scroll alone, but the root cause appears to be desktop delayed-JS behavior, not an Intaker service outage.
Exclude the Intaker chat snippet and https://intaker.azureedge.net/widget/chat.min.js from WP Rocket delayed JavaScript, then retest desktop idle load on Results, homepage, About, and one practice page.