This topic describes how to:
- Figure out why pages might not load in the editor
- Get rid of the "Compatibility Mode" dialog that appears in the editor
- Troubleshoot mixed-content issues
When you load a page in the Optimizely Web Experimentation editor, you may see a warning at the top of the editor that reads: "We have loaded your site using compatibility mode—you can still edit your page, but some site functionality might be missing" or "You're in Compatibility Mode." This compatibility mode message means you may be encountering an issue with mixed content.
You can use the Optimizely Web Experimentation desktop app instead of the browser app to avoid the compatibility mode issue (and take advantage of additional features like device emulation). Please note, if you are attempting to load gated content, site that requires a login, see Troubleshoot: Cannot load a password-protected, gated, or session-specific page in the editor.
Compatibility mode is triggered when your browser's security settings block mixed content or keep insecure (HTTP) content from being loaded into the Optimizely Web Experimentation editor's secure (HTTPS) page. As a result, there are two ways you can avoid compatibility mode and prevent the Optimizely Web Experimentation editor from blocking insecure content:
Load your page securely via HTTPS
What's compatibility mode?
Resolving compatibility mode in Google Chrome browsers
Compatibility mode can be usually be resolved in a Google Chrome browser by clicking the red shield icon at the end of the URL address bar and loading "unsafe scripts" and reloading the page.
If the shield icon is not present or if allowing "unsafe scripts" does not resolve compatibility mode, download the Optimizely Experimentation editor Assistant Chrome extension. When the extension is successfully enabled on your Chrome browser, click the extension and enable Strip X-Frame-Options Header and reload the page.
Disable browser security settings
One way to avoid compatibility mode is to disable your browser's security settings.
Google Chrome for Mac or Linux
- Quit Chrome (if you have it open).
- Open Terminal.
- Enter the following command into Terminal to open a Chrome incognito window:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --user-data-dir=/tmp/tempchrome --allow-running-insecure-content --incognito &
Google Chrome for Windows
- Right-click the Chrome icon that you want to modify.
- Select Properties.
- In the Target field, add the command line flag after ‘chrome.exe’ as follows:
- Click OK to save.
How insecure content triggers compatibility mode
If an insecure (HTTP) site that you load into the Optimizely Web Experimentation editor is compromised, it can compromise your Optimizely Web Experimentation account. Optimizely’s editor is always loaded securely via HTTPS to protect your experiments and data.
If you try to load an insecure site into the Optimizely Web Experimentation editor (for example, http://www.example.com instead of https://www.example.com), your browser may trigger a mixed content warning and block the insecure site from loading. This is because the Optimizely Web Experimentation editor’s protocol is HTTPS, and the page you’re trying to load is HTTP.
The Optimizely Web Experimentation editor loads your site in compatibility mode when mixed content is blocked and the editor cannot load all of the content on your page. This is when you see the warning "We have loaded your site using compatibility mode."
The compatibility mode warning advises you that an insecure site (your page) is being loaded inside a secure site (the editor). Optimizely Web Experimentation displays the warning in the main canvas of the editor if it detects that mixed content is being blocked, although it may not always be able to detect this.
How compatibility mode affects your site
Compatibility mode means the Optimizely Web Experimentation editor will not display blocked mixed content. When the Optimizely Web Experimentation editor loads your site in compatibility mode, some styling and content may not display correctly in the editor. Content in iFrames may not render in the editor.
The compatibility mode warning only affects the content displayed in the Optimizely Web Experimentation editor, not your live site.
Troubleshoot other page-loading issues
If your page is not loading correctly in Optimizely Web Experimentation for another reason, see Troubleshoot: Pages not loading in the Editor.
See how Optimizely Web Experimentation loads pages in the editor, which might help you target your troubleshooting
Troubleshoot page-loading in the editor, see Troubleshoot: Cannot load a password-protected, gated, or session-specific page in the editor, for pages that require session-specific information (like a shopping cart, intranet page, or other logged-in-only content)
If you try to load content that is in an iframe, see Troubleshoot: Cannot edit iframes in the editor.
If you use an X-Frame-Options header, see Update your site's Content Security Policies (CSP).