Third-Party Script Governance
Third-party scripts (analytics, review widgets, consent managers, sign-in clients) are among the largest contributors to poor Lighthouse performance scores. ProRank's governance controls let you delay these scripts until user interaction without removing them.
How It Works
When a governance category is enabled, ProRank reduces the startup impact of matching third-party scripts. Depending on the script type, scripts may be delayed until user interaction (with a fallback timer), kept non-blocking, or shifted to load later in the page lifecycle.
This reduces Total Blocking Time (TBT) and improves First Contentful Paint (FCP) and Largest Contentful Paint (LCP) without losing functionality.
Categories
Google Services
Delays Google Tag Manager, gtag.js, Google Analytics, Google Ads conversion tracking, and related measurement scripts.
- Matched patterns:
googletagmanager.com,google-analytics.com,gtag/js,googlesyndication.com - Trade-off: The very first pageview may not be tracked if the visitor leaves before interacting. For most sites this is an acceptable trade-off for better Core Web Vitals.
Review Widgets
Delays review widget loaders such as Trustindex and similar review widget embeds.
- Matched patterns:
cdn.trustindex.io - Effect: The review widget area may appear empty until interaction, then renders normally.
Consent Scripts
Applies non-blocking handling to consent management platforms such as CookieYes and Cookiebot. The consent banner still appears, but the loader script does not block rendering.
- Matched patterns:
cdn-cookieyes.com,consent.cookiebot.com - Caveat: Some consent managers use synchronous blocking intentionally to prevent other scripts from firing before consent. Test thoroughly if your consent setup depends on this behaviour.
Identity Widgets
Delays sign-in client scripts such as Google Sign-In.
- Matched patterns:
accounts.google.com/gsi/client - Effect: The sign-in button appears after interaction.
Configuration
Access these controls from ProRank SEO → Support & Account → Advanced Settings, under the Third-Party Governance section.
Each category is an independent toggle. All are enabled by default in new installations.
Interaction with performance modules
Cache Keep-Warm
When page caching and cache preload are both enabled, ProRank schedules a recurring keep-warm job that re-requests core URLs so they stay in cache. This prevents cold-cache Lighthouse score swings caused by the first uncached request pulling in all render-blocking resources.
- Cadence: Fixed at 15 minutes
- URLs warmed: Homepage (
/) and the WordPress posts page (if a static front page is set) - Gated by: Page cache and cache preload must both be active
Keep-warm pairs well with third-party governance because even the warmed pages benefit from delayed third-party scripts on the initial paint.