Jump to content


Photo
- - - - -

Background Coming in Late


  • Please log in to reply
6 replies to this topic

#1 ksnyde

ksnyde

    Super Member

  • Members
  • 177 posts
  • Framework Version:2.3

Posted 27 January 2012 - 06:12 PM

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?

#2 Rob

Rob

    One Smart Egg

  • Members
  • 13575 posts
  • LocationEast Coast, USA
  • Framework Version:The Latest, of course
  • Country: Country Flag

Posted 27 January 2012 - 07:08 PM

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.

#3 ksnyde

ksnyde

    Super Member

  • Members
  • 177 posts
  • Framework Version:2.3

Posted 27 January 2012 - 07:38 PM

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 were 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.

#4 Rob

Rob

    One Smart Egg

  • Members
  • 13575 posts
  • LocationEast Coast, USA
  • Framework Version:The Latest, of course
  • Country: Country Flag

Posted 27 January 2012 - 09:01 PM

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

#5 ksnyde

ksnyde

    Super Member

  • Members
  • 177 posts
  • Framework Version:2.3

Posted 27 January 2012 - 11:14 PM

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?

#6 Simon_P

Simon_P

    Messer

  • Administrators
  • 8388607 posts
  • LocationDevon
  • Framework Version:2.0
  • Country: Country Flag

Posted 27 January 2012 - 11:35 PM

It isnt the caching, the image probably is cached locally. Its just the nature of the supersize javascript plugin. The authors website is here:

Please Login or Register to see this Hidden Content



#7 ksnyde

ksnyde

    Super Member

  • Members
  • 177 posts
  • Framework Version:2.3

Posted 28 January 2012 - 01:55 PM

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.