It is not a network (packets back and forth) or memory issue; it is a cpu issue involved with the rendering of the webpages. I cannot figure how clicking on an excursion takes 100% of my cpu resources and still takes around 30 seconds for the page to render. That it takes 30 seconds for a check mark to show up also doesn't make sense. I am not seeing lots of packets go back and forth just cpu utilization. If this has been around for months, you would think someone would have fixed it, or don't roll out earlier excursion booking until you have it fixed.