Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
litespeed_wiki:cache:litemage:troubleshooting:slow-when-litemage-hit [2017/11/30 17:20]
Jackson Zhang
litespeed_wiki:cache:litemage:troubleshooting:slow-when-litemage-hit [2017/11/30 19:21]
Jackson Zhang
Line 4: Line 4:
  
 Let's look at an example of using Chrome developer tools. Let's look at an example of using Chrome developer tools.
 +
 +{{ :​litespeed_wiki:​cache:​litemage:​troubleshooting:​litemage-slow-waterfall-1.png?​800 |}}
 +
 +{{ :​litespeed_wiki:​cache:​litemage:​troubleshooting:​litemage-slow-waterfall-2.png?​800 |}}
 +
 +{{ :​litespeed_wiki:​cache:​litemage:​troubleshooting:​litemage-slow-waterfall-3.png?​800 |}}
  
    
 +You should be able to see the LiteMage cache page only took ''​159ms''​ to load. It was very fast and you can feel immediately. However when you look at the waterfall elements and overall loading time. It took around ''​4s''​ in total, which is normally the figure you will probably get from online speed checking tools as ''​page load time''​.
 +
 +The html page is the main page which will give a general feeling to end user about fast or slow.  LiteMage reduce the load time of the pages from a couple of seconds to a couple of hundred milliseconds.  ​
 +
 +You may notice there are a lot of static files such as css/jpg/js etc. LiteSpeed doesn'​t cache static file at all. If you have heavy static css/image files, They will take longer to load. Try switching to the lightweight template if you can. Enabling file compression,​ enabling browser cache or enabling CDN cache for static files should also help.
 +
 +If you scrolling down to time-consuming loading items, most of the time are Ajax call from either Magento code or some themes/​extensions installed to you store. ​ Some was calling youtube.com,​ some was calling google api, some was calling facebook, some was calling external website hosted on a remote site with poor response time. All such Ajax calls are non-cachable and will make your store take longer time to load.  Reducing such Ajax calls from php code or changing to liteweight themes/​extentions should help the overall page load time.
 +
 +Overall, with LiteMage'​s help, as far as the user sees the homepage within a couple of milliseconds instead of a couple of seconds, user should feel it very fast since they may not care if every piece on the homepage loaded or not. When the user scrolls down to browse, ​ the Ajax calls may have finish loading already. ​
 +
 +The following are a few example elements which took longer time to load:
 +
 +{{ :​litespeed_wiki:​cache:​litemage:​troubleshooting:​litemage-slow-waterfall-4.png?​800 |}}
 +
 +{{ :​litespeed_wiki:​cache:​litemage:​troubleshooting:​litemage-slow-waterfall-5.png?​800 |}}
  
-Do you have heavy static css/image filesThese take longer to load. Try switching to the lightweight template.+{{ :​litespeed_wiki:​cache:​litemage:​troubleshooting:​litemage-slow-waterfall-6.png?800 |}}
  • Admin
  • Last modified: 2017/11/30 20:30
  • by Lisa Clarke