Error: Website is taking too long to load or does not contain Target Libraries


Sometimes, after putting the URL while creating an Activity you receive the following error: 

"The selected website is taking too long to load or does not contain Target Libraries".



There could be multiple factors causing this. Let's look at a few of them:

  1. Target file is hosted on the page.

    Make sure the target libraries file is hosted on each and every page of your website. Missing libraries at times cause such errors to arise. If you are referencing the target.js file from any other FTP location or any other server, make sure that your website is not blocing it in any way.

  2. Secure Pages, Pages behind logins or pages which need certain information to filled in order to view them.

    If there are any pages which need certain information to be filled in order to reach them or pages which need users to be logged might not load. Target does not save the navigations a user makes inside the Visual Experience Composer, except for the final page on which changes are done all other navigation are not saved.

    Secure Pages: 

    This can be resolved by whitelisting the following IP addresses. These IP addresses are for Adobe's server used for the Enhanced Experience Composer proxy. They are only required for activity editing. Visitors to your site do not need these IP addresses whitelisted.

  3. Enhanced Experience Composer is enabled.

    Several issues can affect page performance in the Target experience composers. Some common issues include:

    • You do not have an mbox on the page.
    • Your site uses proxy blocking, which does not allow the page to be opened in either experience composer.
    • Your site doesn't allow itself to be opened in an iFrame.

If issues occur in the Enhanced Experience Composer, try turning off the Enhanced Experience Composer and use the Visual Experience Composer instead.

To disable the Enhanced Experience Composer, go to Setup > Preferences and turn off the Enable Enhanced Experience Composer option.

If neither the Visual Experience Composer nor the Enhanced Experience Composer works, use a browser extension like Requestly (Chrome) or (Modify Response Headers (Firefox) that can overwrite the X-Frames header options for your site and allow them to be loaded in iFrames, enabling the VEC. If you are unable to use browser extensions, use the Form Composer.

To use the Requestly extension on Chrome:

  1. Turn off the Enhanced Experienced Composer.

  2. Install the Requestly browser extension on Chrome.

  3. Open the extension and configure it using the following:

  4. Select Modify headers.

  5. Enter the following:

  • Rule name
  • Modification rules
  • Toggle Add to Remove.
  • Toggle Request to Response.
  • Enter "X-Frame-Options" as the header name.
  • Change Equals to Contains as the condition for the source URL and enter the URL of the activity that you are trying to load in the VEC.
  • Click Save.
  • You should now be able to load the page quickly with the Visual Experience Composer.

To use the Modify Response Headers extension on Firefox:

  1. Install the Modify Response Headers on Firefox and restart the browser.

  2. From your Firefox extensions, select the Modify Response Headers extension.

  3. Click Preferences.

  4. Select Filter from the Action drop down.

  5. In the Header Name field, enter: X-Frame-Options

  6. Click Add.

  7. Click Start.

After setting up an extension, open Target. Your pages should now load in the Visual Experience Composer, even if the Enhanced Experience Composer is disabled.