Should I preload the large image above the layer?

Question

I am delighted with the property rel="preload"because it looks like this can help speed up the page rendering time.

A use case is a web page with a large image above the fold. Now Chrome does not start loading the image until it receives jQuery (a rather heavy file). When preloading is enabled, they are loaded in parallel.

But I read conflicting messages about whether to use preloadfor things that are in visible HTML elements elsewhere (as opposed to things that are visible when interacting with a user, such as a drop-down menu).

This post seems to recommend not preloading:

If you do not use preloading:

• When an asset is transferred somewhere else on the same page.
• When you are not sure that the user will really require this asset. As on the page, visitors visit only 3% of the time.

Although this one seems to indicate that it is really useful for a similar situation on the Financial Times website:

When the Financial Times submitted the Preload header to link to their site, they shaved off for 1 second from the moment they displayed the mast image ...

So what is this? Should I provide an early “tip” to display the image always shown above? Or should I just let the browser reach it in the usual way?

Answer 1

, A/B, , . , .

, Lean Enterprise, A/B, HIPPO ( ). , , . - , .

, , - Code Complete 2nd Ed. McConnell , , , (. 25 26). , . , "" . , , .

A/B . Amazon SEO, A/B . , , -. - - , , .

, -, , preloading, , , . .. , , . A/B , , , , . , , , , , , - .

, .

Answer 2

rel= "preload" , css, javascript, , - - .

, , , . , A/B , .

Answer 3

. , , . "". , , , , .

, , , , .

Google

preload - , .