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
Previous revision
litespeed_wiki:cache:litemage:troubleshooting:slow-when-litemage-hit [2017/11/30 19:21]
Jackson Zhang
litespeed_wiki:cache:litemage:troubleshooting:slow-when-litemage-hit [2017/11/30 20:30]
Lisa Clarke
Line 1: Line 1:
 ===== Site is Slow, Even With Cache Hit ===== ===== Site is Slow, Even With Cache Hit =====
  
-Is your site still slow after enabling LiteMage? ​ How did you mention ​the slowness? ​ Through online testing tools or Chrome/​Firefox Developer Tools?+Is your site still slow, even after enabling LiteMage? ​ How did you measure ​the slowness? ​ Through online testing tools or Chrome/​Firefox Developer Tools?
  
-Let's look at an example of using Chrome developer tools.+Let's look at an example of using Chrome developer tools.(If you need some help using such tools, please refer to [[https://​developers.google.com/​web/​tools/​chrome-devtools/​network-performance/​reference#​timing-explanation| google'​s documentation]])
  
 {{ :​litespeed_wiki:​cache:​litemage:​troubleshooting:​litemage-slow-waterfall-1.png?​800 |}} {{ :​litespeed_wiki:​cache:​litemage:​troubleshooting:​litemage-slow-waterfall-1.png?​800 |}}
Line 12: Line 12:
  
    
-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''​.+You should be able to see the LiteMage ​cached ​page only took ''​159ms''​ to load. It was very fast and you can feel that immediately. Howeverwhen you look at the waterfall elements and overall loading time, you see that it took around ''​4s''​ in total. This overal loading time is usually ​the one that is reported by 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.  ​+The HTML page is the main page. It's the loading of this page that will give a general feeling ​of "fast" ​or "slow" to the end user.  LiteMage ​reduces ​the load time of the main HTML page from a few seconds to a //few 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.+You may notice there are a lot of static files, including CSS, JPG, and JS among others. LiteSpeed doesn'​t cache static ​files at all. If you have heavy static ​CSS or 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.comsome was calling google apisome 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.+If you scroll ​down to see the more slow-loading items, ​you'll notice that most of these are Ajax calls from Magento code or from some themes ​or extensions installed ​in your store. ​There may be calls to YouTubecalls to the Google APIcalls to Facebookor calls to some other 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 to load.  Reducing Ajax calls from php code wherever possible, ​or changing to lightweight ​themes ​and 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:
- +
-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-4.png?​800 |}}
Line 29: Line 27:
  
 {{ :​litespeed_wiki:​cache:​litemage:​troubleshooting:​litemage-slow-waterfall-6.png?​800 |}} {{ :​litespeed_wiki:​cache:​litemage:​troubleshooting:​litemage-slow-waterfall-6.png?​800 |}}
 +
 +With LiteMage'​s help, as far as the user is concerned, the homepage loads within a few milliseconds. It //feels// very fast, since it often doesn'​t matter if every piece of the homepage is loaded at the beginning. By the time the user scrolls down to browse, the Ajax calls may have finished loading. ​
 +
  • Admin
  • Last modified: 2017/11/30 20:30
  • by Lisa Clarke