This guide is a list of simple steps you can take to improve website performance. If you are experiencing performance problems, please look through this guide before contacting Dynamicweb service desk.
Generally, if you have problems with performance or your site is unavailable you should contact your hosting provider. For most Dynamicweb solutions the hosting provider will be Hostnordic A/S who can be contacted at email@example.com or by phone at +45 70 22 90 28. They are responsible for the hosting environment and are much better equipped to pinpoint hardware related performance issues. If they determine that the Dynamicweb Software causes the issue, Hostnordic will forward the problem to us.
Before contacting Hostnordic please check the following common issues.
Performance problems in the backend are often caused by:
- Excessive statistics tables
If the Dynamicweb backend is slow immediately after logging in you should try removing statistics from “My Page”. Go to Management Center > Solution Settings > My Page > Hide statistics. If you have access to the database you can also choose to simply delete some or all of the statistics.
- Suggesting Metadata
Suggesting Metadata on every selected page decreases backend performance as the suggestion code has to analyze the entire content including tags. When your website is up and running with Metadata we recommend disabling the suggestion. Go to management center > editing >metadata.
- A full trash bin
Always try to keep your trash bin empty and be aware that all solutions on Access databases eventually grow too big - especially with a lot of traffic. Is your site on an appropriate hosting platform?
- A high number of pages
If the solution has a lot of pages, make sure that it is running on an SQL database. See our recommendations for Access-databases in our System Requirements document.
- Old version
Dynamicweb is continually optimized for performance. Is your solution running the latest version? If not please check out the guide to upgrade your solution on Developer.
Performance problems in the frontend are often caused by:
- Custom modules
Try adding:”?dbstat=true” to your URL for information about database connections.
You can also add”&Debug=True” to your URL, to check connection-speeds in a detailed overview.
Try setting up your solution with our standard templates. If it helps perhaps your frontend developers need to take another look at your templates. Default templates can always be downloaded as part of our default files and database package.
Checking the page with a good resource monitor like Chrome Inspector or Firebug can give an indication if you are causing the slowness yourself by piling on heavy images and scripts.
- Non-existent pages/items
Often slow loading pages are waiting for non-existing items to time out before continuing. We recommend opening the page with fiddler http://www.fiddler2.com/fiddler2/ or similar. It will show you if items time out with 404 during loading after which you can check if they were deliberately deleted.
- Excessive use of GetImage.aspx
Images generated by GetImage.aspx are cached serverside in this folder: /Files/Cache.Net/Images. If they are heavily compressed it increases workload considerably. Consider removing the compression parameter from your GetImage call – it can potentially increase performance to a great extent. For an overview of the possibilities with GetImage.aspx call it without any parameters to bring up a configuration interface. E.g.: yoursolution.dk/admin/public/getimage.aspx.