no, I don’t think so… checked all the tests, the pinterest js is called only once.
I’ll note that in past, I used to see the page render at around request #11 of the page… now it’s at request number #29 .
I’ve disabled the pinterest calls… and I still see the same .
So it must be one of the css or js files blocking render?
[hr]
hmm. might have caught it.
disabled the pinterest links.
disabled the google analytics code (funny, it’s set to be async)…
Get this result 1.629s to render
re-enable google analytics get this. 1.848 secs to render
even though the ga .js file takes only 64 ms to load… it seems to create a lag before next request.
reinstalled the pinterest links, and sure enough, the culprit is the google analytics.
with pinterest back on, and ga off, I get render at 1.629s
therefore pinterest does not seem to be creating the slowdown, google is.
sure enough, re-enable the google analytics code and the render time is back up to 2.059s
disable it, and it’s back to 1.74s
funny that google analytics would cost me from .3 to .5 seconds, must be a conflict with other stuff.
I loaded your page in my chrome browser and looked at the source. Look at the bottom, you will see that http://assets.pinterest.com/js/pinit.js is loading twice.
you should put your css files call above all JS calls in the
for now, simply putting the google analytics at the bottom seems to help with overall render.
I’ll get your other points done… and let you know.
I found the duplicate pinit.js thanks.
due to some optimizers, I don’t have complete control of locations of css js files, but most are in best locations.
I tried the blog post asynchronous mode for pinterest… works great. pushes the pinterest calls further down the page, after point of render.
Thanks, I think that’s as good as it gets
cheers.
Vince
thanks muchly.
Vincee. [hr]
thanks, Patrick… yes been running a lot … and thanks for the great tool… helped me catch these minor faults today, as other days.
I never fail to be amazed at your tool here :idea: