Mobile app version of vmapp.org
Login or Join
Samaraweera270

: Lightspeed webstore runs very slow I am currently working on a website that was built by another developer. It is a Joomla website on the front-end, and the back-end is being managed through

@Samaraweera270

Posted in: #Iframe #Joomla

I am currently working on a website that was built by another developer. It is a Joomla website on the front-end, and the back-end is being managed through Lightspeed. Lightspeed builds out a webstore that stays in sync with the back-end as far as inventory, pricing, etc. is concerned, which is great.

The problem is that the original developer essentially embedded the Lightspeed webstore within the Joomla site via an IFrame, and now the site is running very slow. If a user tries to click on a product or use the back button the site will often times just freeze up for 30+ seconds. I know that IFrames can definitely affect performance, but I was just wondering if anyone else has had any experience with Lightspeed webstores and if they are maybe just inherently slow?

10.01% popularity Vote Up Vote Down


Login to follow query

More posts by @Samaraweera270

1 Comments

Sorted by latest first Latest Oldest Best

 

@Harper822

Using Iframes can contribute to slow speeds because an extra request is made to a server.

Also, check all website links (including the most important pages) for any internal redirects (pages that return a 301 status or that display "the document has been moved here" type of messages). Google Page-speed Insights is excellent at finding these. Also, redirect chains are even worse because that's a redirect followed by a redirect, etc.

Having said all that, all these additional requests including requests for external javascript and stylesheet files and all the individual image files that make up the page will make the whole site slower as a whole.

There is a website that measures how long it takes for a page to process in the background before the first byte is received from the server. Go to:
bytecheck.com

Place in any URL that you claim is slow and submit it a few times. If the http code returned is anything but 200, then you're in trouble. If after a few checks, your byte speed is at least 0.200 seconds, then its slow and you'll definitely need to look into the entire back end to see if the server as a whole is functioning properly.

Once you get an average number, you can then calculate the waiting time for your webpage.

Let's say for example you have a product page listing 100 products and you have an external stylesheet as well as five external javascript files along with another external file required to load the page.

If the average load time for any item is 0.2 seconds, then on a poorly designed product page, you'll have to wait at least 21.2 seconds for everything to be ready to begin displaying. This excludes the time it takes for the individual elements to finish displaying.

So my advice is this:

Consolidate the small images into a CSS sprite so that you only need to load 1 image file instead of dozens of images.

Combine all scripts together and if they're small enough, include them directly into the HTML instead of calling them externally.

Eliminate IFrames. If you are trying to make a function where a click causes something to load in the middle of the screen instead of the whole page loading, then use AJAX (advanced javascript).

Once that is done, then tune litespeed for optimal settings and make sure nothing else on the server (such as email programs, etc) is slowing the delivery of the webpages.

Unfortunately, one thing you won't be able to control is the number of visitors that visit the site, but if you really want to limit that (just to try to pick up speed somewhat for the moment), you can use a robots text file to instruct various robots on the internet (such as search engine spiders) not to index your pages.

10% popularity Vote Up Vote Down


Back to top | Use Dark Theme