Testing and Validation
Verify the Coframe SDK is installed and measure its impact
Copy this guide and your current settings as a prompt for your AI agent.
Preview agent promptSee the guide, code and settings included when you copy.
This page is the standard verification checklist for a Coframe integration. Use it after the initial installation and again whenever you deploy a change that could affect how the SDK loads. It covers four things: confirming the SDK initialized, inspecting debug logs, measuring LCP impact, and checking for page-load flicker.
On this page
01Check Initialization Status
Open the browser console on any page where Coframe is installed. If the SDK loaded successfully, there should be no errors related to the Coframe script. A clean console — no blocked-resource errors, no script-load failures — is the first confirmation that the SDK is on the page and ran without interruption.
If you see errors, the most common causes are a script tag pointing to the wrong URL, a Content Security Policy that blocks the script host, or a missing project ID in the configuration.
02Check for Errors and Debug Logs
Filter the browser console by [Coframe] to see all log output from the SDK.
This filter surfaces initialization messages, configuration details, and any
warnings the SDK emits at runtime. Scanning these entries is the fastest way to
confirm that the SDK recognized its configuration and completed its setup
sequence.
While the console is open, also open the Network tab and look for the cf.js
request. Confirm that the request returned a successful response. If the request
is missing or failed, check whether an ad blocker or a Content Security Policy
is preventing the script from loading. A blocked cf.js request means the SDK
never ran, regardless of what is in the page HTML.
03Measure LCP Impact
To compare page performance with and without Coframe, append ?cf_disabled to
any URL on your site. For example:
https://yoursite.com?cf_disabledLoading the page with this parameter temporarily disables Coframe for that
request. You can use this to take a Largest Contentful Paint measurement in the
browser’s Performance panel or Lighthouse with Coframe active, then take the
same measurement with ?cf_disabled appended, and compare the two results.
This is the recommended method for isolating Coframe’s contribution to LCP before and after rollout.
04Check for Page-Load Flicker
Watch for a flash of original content when the page loads. Flicker means the page rendered its original content briefly before Coframe applied its changes, which is a sign that the antiflicker script either was not installed or did not run synchronously before the rest of the page painted.
If you observe flicker, confirm that the antiflicker snippet is placed
synchronously in the <head> of the document, before any other scripts. See
Anti-Flicker for the correct installation
pattern and how the snippet suppresses the flash of original content.
# Testing and Validation Verify the Coframe SDK is installed and measure its impact This page is the standard verification checklist for a Coframe integration. Use it after the initial installation and again whenever you deploy a change that could affect how the SDK loads. It covers four things: confirming the SDK initialized, inspecting debug logs, measuring LCP impact, and checking for page-load flicker. ## Check Initialization Status Open the browser console on any page where Coframe is installed. If the SDK loaded successfully, there should be no errors related to the Coframe script. A clean console — no blocked-resource errors, no script-load failures — is the first confirmation that the SDK is on the page and ran without interruption. If you see errors, the most common causes are a script tag pointing to the wrong URL, a Content Security Policy that blocks the script host, or a missing project ID in the configuration. ## Check for Errors and Debug Logs Filter the browser console by `[Coframe]` to see all log output from the SDK. This filter surfaces initialization messages, configuration details, and any warnings the SDK emits at runtime. Scanning these entries is the fastest way to confirm that the SDK recognized its configuration and completed its setup sequence. While the console is open, also open the Network tab and look for the `cf.js` request. Confirm that the request returned a successful response. If the request is missing or failed, check whether an ad blocker or a Content Security Policy is preventing the script from loading. A blocked `cf.js` request means the SDK never ran, regardless of what is in the page HTML. ## Measure LCP Impact To compare page performance with and without Coframe, append `?cf_disabled` to any URL on your site. For example: TEXT ``` https://yoursite.com?cf_disabled ``` Loading the page with this parameter temporarily disables Coframe for that request. You can use this to take a Largest Contentful Paint measurement in the browser’s Performance panel or Lighthouse with Coframe active, then take the same measurement with `?cf_disabled` appended, and compare the two results. This is the recommended method for isolating Coframe’s contribution to LCP before and after rollout. ## Check for Page-Load Flicker Watch for a flash of original content when the page loads. Flicker means the page rendered its original content briefly before Coframe applied its changes, which is a sign that the antiflicker script either was not installed or did not run synchronously before the rest of the page painted. If you observe flicker, confirm that the antiflicker snippet is placed synchronously in the `<head>` of the document, before any other scripts. See [Anti-Flicker](../docs/anti-flicker.html) for the correct installation pattern and how the snippet suppresses the flash of original content.