Refresh Comments
Anonymous comments allowed.
12 comments displayed.
#81
-
anon (01/07/2016) [-]
would it hurt to use an animate() or fadeIn() in your 'success' call in ajax?i mean it would look smoother. You could also make browsing seem a bit faster by preloading the next 1-2 content/comment pages after the user finished loading this page (unless you prefer it like this because of traffic/bandwidth costs). Also saving the last 2 content/comment pages inside a hidden div would help you with less traffic and load times.
#88 to #85
-
kapios ONLINE (01/07/2016) [-] you're re-requesting a page's content (actual content & comments) through ajax, i know images are probably cached, but the rest of it is not,as far as i know. but you might be right, its not that important.
depending on the browser, it can be faster. youre basically loading a div with whatever inside, but there are no frames for the client's browser to actually show. it also starts loading only after the user has finished loading the original page they requested. then when they click next, its instantaneous. I can make some tests and show you the results if you want.
depending on the browser, it can be faster. youre basically loading a div with whatever inside, but there are no frames for the client's browser to actually show. it also starts loading only after the user has finished loading the original page they requested. then when they click next, its instantaneous. I can make some tests and show you the results if you want.
#96 to #93
-
kapios ONLINE (01/08/2016) [-] yeah i thought display: none would just put the node in the DOM tree and wouldnt render it until you wanted it to be displayed. but nope.
that was my next recommendation but i havent tested a client's power before. Ive only played with the bandwidth/ping etc. Its a good idea actually.
My first guess is you test it by waiting for the user to load the whole page (or not - maybe a specific div) and then make him send you the time it took them for some specific js/ajax executions or css transforms, etc. (there's probably a plugin already on github)
that was my next recommendation but i havent tested a client's power before. Ive only played with the bandwidth/ping etc. Its a good idea actually.
My first guess is you test it by waiting for the user to load the whole page (or not - maybe a specific div) and then make him send you the time it took them for some specific js/ajax executions or css transforms, etc. (there's probably a plugin already on github)
