• 0
Sign in to follow this  
Followers 0

Background Coming in Late

Question

Posted · Report post

I am trying to migrate to PageLines and one issue I'm having is that pages load and then there is a perceptable delay and then the background comes in. I could live with this if it were a one time hit and then the image was cached but it appears to happen every time. Am I doing something wrong?

Share this post


Link to post
Share on other sites

6 answers to this question

  • 0

Posted · Report post

Maybe, maybe not. Could we see the site? Delays could be caused by large background files that take time to load. Because of the order in which things happen, a large background file will result in a delay. On the other hand, a plugin could also cause delays and the only way we'll tell is by seeing it. Thanks. We look forward to seeing the site and helping you resolve this.

Share this post


Link to post
Share on other sites
  • 0

Posted · Report post

Ok. I'll work on getting it onto a public URL. Until then I can say that the filesize is an 81k JPG image. Even if it [i]were[/i] large though it should get cached and the size of the image would only be a factor the first time you went there. Right? I suspect that because I've clicked the "super size me" configuration option that there is something dynamic being done at runtime but haven't tried to reverse engineer how this fullscreen effect is being implemented.

Share this post


Link to post
Share on other sites
  • 0

Posted · Report post

Yes and the super size me (I'm getting hungry) basically just takes the image and stretches it to the dimensions of the browser.

Share this post


Link to post
Share on other sites
  • 0

Posted · Report post

So why aren't we seeing caching taking place? It is a substantial delay and that's running off a locally hosted (localhost) environment so it'll likely be far worse when the latency of Internet wields its final judgement. If the dynamic behavior is just stretching then wouldn't I at least see a not completely fullscreen initially which is then replaced by a fully resized version at some point?

Share this post


Link to post
Share on other sites
  • 0

Posted · Report post

It isnt the caching, the image probably is cached locally. Its just the nature of the supersize javascript plugin. The authors website is here: http://buildinternet.com/2011/07/supersized-3-2-fullscreen-jquery-slideshow/

Share this post


Link to post
Share on other sites
  • 0

Posted · Report post

I think the main thing that Author is focusing on is rotating full-sized images and he has some really nice examples on his site. For this reason the transition-in effect if appropriate for the 2nd image onward but the 1st image should be loaded immediately on PageLines shouldn't it? Anyway my "delay" seems to be (on surface inspection) that jQuery is executing once the full DOM has loaded (that's probably unavoidable with this kind of implementation) and then it transitions in the background. I don't think PageLines is using this plugin in a very effective manner. I think some coordination between client and server might result in much faster load times. This plugin, however, works very well for the 2nd image onward. The Febru site is amazing.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0