What can I do if I'm having performance issues?

There can be many reasons why you experience performance issues or slowness in any content management system (CMS). Here are a few examples of how to optimize performance in Core Publisher.

In the back end of any CMS, you can expect standard response times to fluctuate between several seconds in between actions (8-30 seconds). If you find that you are frequently seeing error messages or time outs there may be something more happening than standard response time.  

1. Check your audio/image assets
Core Publisher has image and audio asset recommendations, please follow these when creating your files.

2. Save As You Go & Save Often
It’s common when you’re working on a post that you are also working on other things. f you have multiple tabs open in your browser and are working on a post you may leave the page idol for a while and come back to it later. Saving as you go can save you from experiencing an error message when you come back to your post in Core Publisher.

This is also very important if you are creating a long post that has many different assets in various formats. The more assets you add to one post as you’re creating it, the longer it will take to load. Saving as you go can help.

We would also recommend adding text first then saving, images next then saving, adding audio next then saving, and finally adding any interactives last. If a post doesn’t save after adding a specific asset, this will help you narrow down which asset is incompatible with the post page.

3. Do Not Copy/Paste From Word
Word and many other programs have tons of HTML in the back end to create formatting while in their product. 

Posts travel to other locations, like NPR One & the NPR API. In order for it to make it possible for the content to move to these locations outside of Core Publisher in one piece, posts have restrictions on what can be added to them. Most HTML and non-Javascript based code is not allowed on post pages. In order to protect itself if it detects HTML, Core Publisher will try to strip it out or will not allow the post to be saved/published.

Strip your copy first before copy/pasting into CP – There are several ways to strip code out:
  • Plain Text Editors - Copy/Paste from Word into a plain text editor (Notepad or TextEdit) then copy/paste from there into Core Publisher
  • Browser Edit Options – Open Core Publisher in Safari/Chrome, copy your text, click Source in Core Publisher, use the browser edit options to “Paste & Match Style”
  • Source Code – Copy your text, Click Source in Core Publisher, Paste your text, click Source again

If you are still experiencing issues after trying these best practices the load issues may be caused by the following:

1. Available Bandwidth
Internet bandwidth in your office can greatly impact your load time while building content in a CMS. For example, if you don’t have enough internet bandwidth and you are sharing that limited bandwidth with someone in your office streaming a video while you are creating a post in Core Publisher and uploading a large audio file, your bandwidth will make your audio upload slow. And if it takes too long, it may time out.

We recommend using this formula as a rule of thumb for internet bandwidth:

number_of_people_in_office + 10

For example, if you have a 20 person station, then you’d want at least 30 Mbps internet bandwidth. This is just an estimate. But, it will provide some buffer if someone else in the office starts a large download during your work.

If you want to test your local bandwidth you can use these two speed tests:

2. Firewalls
Contact your IT department and ask if there are any firewalls or proxy servers set up at your site. We have found that it is common for stations located on a university to experience issue with performance due to firewalls. Proxy-based firewalls can be particularly troublesome. A discussion with your IT department is a great place to start.

If you are still experiencing issues with load time and bandwidth, please contact the Station Relations team and we will be happy to troubleshoot these issues with you further.

Questions? Having Trouble? Contact Station Relations

Did you find this article helpful?