karrikas

<p>Lazy image load. Firts html block images then load by user demand.</p>
<h3>1.0</h3>
<ul>
<li>new version</li>
</ul>
<h4>0.2</h4>
<ul>
<li>Add js with wordpress method</li>
</ul>
<h4>0.1</h4>
<ul>
<li>Put code on head</li>
</ul>
<h4>0.0</h4>
<ul>
<li>First release</li>
</ul>


javascript-image-loader

Block images only loading images that user see.

Francisco Torres

<p>¿What is <a href="https://developers.google.com/chrome/whitepapers/prerender" rel="nofollow ugc">Prerender</a> and <a href="http://en.wikipedia.org/wiki/Link_prefetching" rel="nofollow ugc">Prefetch</a>? Nice question. It’s a new-navigators technique (ok i’m a liar, Mozilla do it from 2003!) that loads in background the next page you believe the visitor is going to visit.</p>
<p>This plugin puts the required metatag in your WordPress pages, based on settings you can change, allowing those compatible navigators to do a pre-load of the next page. When the visitor try to visit that page Boom! it just appears without need to wait for it!</p>
<h4>Testing Prerender and Prefetch Support in your navigator</h4>
<p>You can <a href="http://prerender-test.appspot.com/" rel="nofollow ugc">test here Chrome’s prerender</a> with any page.</p>
<h4>Install and after install</h4>
<p>*When installing, remember to set the server’s load limit on settings.<br />
*This is a plugin in development, feel free to ask questions in “Support” section and colaborate with it.</p>


Prerender and Prefetch

Puts Prerender and Prefetch tag in the page. Allowing compatible navigators to do a pre-load of the page you figure the visitor is going to go.

javascript-image-loader vs Prerender and Prefetch