Howdy!
My website (nop 2.5) is hosted on WinHost. I sent an email to them asking about my performance issue on their servers and I got the following message:
******************** BEGIN *********************
Alberto
The latency you experienced are two folds.
NopCommerce application is known to consumes lots of server resources that could triggers application pool recycle event.
We host each website in its unique application pool/process. To ensure server stability we recycle the application if any of the following conditions are met:
1) More than 20 minutes of idle time (no HTTP request in 20 minutes)
2) The application uses more than 100 MB of memory for the Basic plan and 200 MB of memory for the Max and Ultimate plan.
3) The application uses more than 70% of CPU resources for more than 5 minutes
Checking the servers event log, I did find evidence that your application pool was getting recycled due to the 100 MB memory threshold.
What this means is that when ever your application pool is recycled, there is some delay when a browser calls on it again. When it is called, all the objects/data/code must be loaded back unto the process which can cause the delay. Once everything is loaded, your site works much more smoothly until the application pool is recycled once more thus causing it to reload back into the process.
Using a 3rd party web analyzing tool, it also shows that a great deal of objects is being called when you perform the first initial load. This will make it seem that your website is displaying slowly. Here is the link and results of this 3rd party web analyzing test.
External Objects
External Object QTY
Total HTML: 1
Total HTML Images: 3
Total CSS Images: 30
Total Images: 33
Total Scripts: 7
Total CSS imports: 1
Total Frames: 0
Total Iframes: 0
Download Times*
Connection Rate Download Time
14.4K 125.94 seconds
28.8K 67.17 seconds
33.6K 58.78 seconds
56K 38.63 seconds
ISDN 128K 17.66 seconds
T1 1.44Mbps 9.20 seconds
Analysis and Recommendations
TOTAL_HTML - Congratulations, the total number of HTML files on this page (including the main HTML file) is 1 which most browsers can multithread. Minimizing HTTP requests is key for web site optimization. Y
TOTAL_OBJECTS - Warning! The total number of objects on this page is 42 which by their number will dominate web page delay. Consider reducing this to a more reasonable number. Above 20 objects per page the overhead from dealing with the actual objects (description time and wait time) accounts for more than 80% of whole page latency. See Figure II-3: Relative distribution of latency components showing that object overhead dominates web page latency in Website Optimization Secrets for more details on how object overhead dominates web page latency. Combine, refine, and optimize your external objects. Replace graphic rollovers with CSS rollovers to speed display and minimize HTTP requests. Consider using CSS sprites to help consolidate decorative images. Using CSS techniques such as colored backgrounds, borders, or spacing instead of graphic techniques can reduce HTTP requests. Replace graphic text headers with CSS text headers to further reduce HTTP requests. Finally, consider optimizing parallel downloads by using different hostnames or a CDN to reduce object overhead.
TOTAL_IMAGES - Warning! The total number of images on this page is 33 , consider reducing this to a more reasonable number. Recommend combining, replacing, and optimizing your graphics. Replace graphic rollover menus with CSS rollover menus to speed display and minimize HTTP requests. Consider using CSS sprites to help consolidate decorative images. Use CSS techniques such as colored backgrounds, borders, or spacing instead of graphic techniques to reduce HTTP requests. Replace graphic text headers with CSS text headers to further reduce HTTP requests. Finally, consider optimizing parallel downloads by using different hostnames to reduce object overhead.
TOTAL_CSS - Congratulations, the total number of external CSS files on this page is 1 . Because external CSS files must be in the HEAD of your HTML document, they must load first before any BODY content displays. Although they are cached, CSS files slow down the initial display of your page. Remember to place CSS files in the HEAD and JavaScript files at the end of the BODY to enable progressive display.
TOTAL_SIZE - Caution. The total size of this page is 151658 bytes, which will load in over 20 seconds on a 56Kbps modem - or 38.63 seconds on a 56Kbps modem. Consider reducing total page size to less than 100K to achieve sub 20 second response times on 56K connections. Be sure to provide feedback for pages over 100K by layering your design to display useful content within the first two seconds. Consider optimizing your site with Website Optimization Secrets, Speed Up Your Site or contacting us about our optimization services.
TOTAL_SCRIPT - Warning! The total number of external script files on this page is 7 , consider reducing this to a more reasonable number. Combine, refactor, and minify to optimize your JavaScript files. Ideally you should have one (or even embed scripts for high-traffic pages) on your pages. Consider suturing JavaScript files together at the server to minimize HTTP requests. Placing external JavaScript files at the bottom of your BODY, and CSS files in the HEAD enables progressive display in XHTML web pages.
HTML_SIZE - Congratulations, the total size of this HTML file is 5281 bytes, which less than 50K. Assuming that you specify the HEIGHT and WIDTH of your images, this size allows your HTML to display content in under 10 seconds, the average time users are willing to wait for a page to display without feedback.
IMAGES_SIZE - Congratulations, the total size of all your images is 37922 bytes, which is less than 50K. Even with a 50K HTML page this page should load in less than 20 seconds on a 56Kbps connection. Ideally each image should be less than 1160 bytes, to easily fit into one TCP-IP packet.
SCRIPT_SIZE - Warning! The total size of external your scripts is 89482 bytes, which is over 20K. Consider optimizing your JavaScript for size, combining them, and using HTTP compression where appropriate for any scripts placed in the HEAD of your documents. You can substitute CSS menus for JavaScript-based menus to minimize or even eliminate the use of JavaScript.
CSS_SIZE - Caution. The total size of your external CSS is 18973 bytes, which is above 8K and less than 20K. For external files, ideally keep them less than 1160 bytes to fit within one higher-speed TCP-IP packet (or an approximate multiple thereof). Consider optimizing your CSS and eliminating features to reduce this to a more reasonable size.
MULTIM_SIZE - Congratulations, the total size of all your external multimedia files is 0 bytes, which is less than 10K.
What I suggest from this point is to see about coding your website to not consume so much of the servers memory so that it does not get recycled by the system. Additionally, possibly design the website to not load so many objects on it's initial load.
http://analyze.websiteoptimization.com/wso
******************** END *********************
Any Idea of how to improve it?