You may have perceived that when a Kentico site is sent on to a server, when we scan the site pages surprisingly, it takes much time to load the pages. When it is stored at server side, then the execution of pages progresses.
The answer for evade the above issue would be; on the off chance that we can visit all the pages with-in the site then server side store will be produced and execution of the pages will progress. If we have a couple of number of pages we can do it effectively. At the same time, in the event that we have huge number of pages then going to all the pages may turn into a troublesome errand for the customer. With a specific end goal to evade this sort of issues we have to computerize the meeting of all pages utilizing a project/device.
We have made a Cmsutility project/instrument to visit all the pages with-in the site utilizing casperjs.
Characterizing & requesting searching route steps
Filling & submitting structures
Clicking & taking after connections
Catching screenshots of a page (or piece of it)
Testing remote DOM
Downloading assets, including double ones
Composing practical test suites, sparing results as Junit XML
Scratching Web substance
Use casperjs to peruse the sitemap.xml of the site. casperjs runs on the Phantomjs environment.
For each one page recorded in the sitemap.xml, do a GET demand for the page.
This will make the server reserve the page for speedier reaction for ensuing appeals.
The instrument will keep up a log for all the pages with-in the site.
The instrument would keep up a log of the pages went to and its status including reponse time, in the nearby catalog where the device is run from. Illustration: www.raybiztech.com/blog
Surprisingly it took 10.54s to load the page.
We’ve scanned the site and it stored at server side. After server side reserving it took 4.31s to load the page.
After program storing it took 1.26s to load the page to load the page.
In the wake of Running Utility instrument/program it took 4.32s.
After program storing it took 824ms to load the site.