By continuing to use this site, you agree to the storing of first- and third-party cookies on your device to enhance site navigation; analyze site, product, and service usage; and assist in our marketing and promotional efforts. Cookie Policy

Skip to Content


If there has been an Omni CMS update and you are experiencing strange behavior, or not seeing the update, clear your cache. Should the strange behavior persist, contact our helpdesk.

Is Omni CMS being slow? There are several steps you can take to narrow down the source of the problem.

Internet ServiceLink to this section

First, verify your internet speed to determine if network traffic is a factor. The following are pages where you can check the speed of your internet:

Also, check your ISP to see if there are there any outages in your area. If you are having difficulty loading pages other than Omni CMS, then that points to an ISP issue, not an Omni CMS one.

Omni CMSLink to this section

  1. Open a new browser window (Chrome or Firefox recommended).
  2. Clear your cache in case older JavaScript files from Omni CMS are in the browser.
  3. Connect to[yoursite] or open up your direct link and log in into Omni CMS.
  4. If you can log in to Omni CMS in less than five seconds, Omni CMS is functioning as expected.
  5. How many Omni CMS tabs do you have open? Having Omni CMS open in four or more tabs at the same time can cause significant slowness.

Site DesignLink to this section

Your website is involved in a large number of complex interactions that, depending on server configuration, may span multiple states or even the country and back again.

Omni CMS keeps the content of your web pages in .pcf files and stylesheets for your pages' layout in .xsl files. The rest of the content comes from your production server (images, media, RSS, scripts, server side includes and programming pages) and some other third-party servers on the internet. Therefore, Omni CMS servers must make multiple connections with these other servers to load pages, one for each item. With Omni CMS servers in California, if your production server is on the East Coast, that's multiple cross-country trips the information must take before finally reaching your computer.

  1. Please check that your production server is up and running and Omni CMS has access to it. Navigate to Setup > Sites > the site in question > Production Server FTP settings.
  2. Make and publish a basic test page. If this runs smoothly, then the publish process is functioning as it should.
  3. Check the third-party content on the page that you are rendering. For example, make sure the page is not displaying a 100 GB movie, or other extremely large files which could take a long time to render.
  4. PDF Course Catalogs can take up to twenty minutes to be rendered due to complexity of XSL-FO transformation.
  5. A complete site publish can take a long time, depending on the number of files that are being transferred from staging to production servers.
  6. If all else fails, submit a ticket to our helpdesk.