{"action":"created","issue":{"url":"https://api.github.com/repos/gatsbyjs/gatsby/issues/2425","repository_url":"https://api.github.com/repos/gatsbyjs/gatsby","labels_url":"https://api.github.com/repos/gatsbyjs/gatsby/issues/2425/labels{/name}","comments_url":"https://api.github.com/repos/gatsbyjs/gatsby/issues/2425/comments","events_url":"https://api.github.com/repos/gatsbyjs/gatsby/issues/2425/events","html_url":"https://github.com/gatsbyjs/gatsby/issues/2425","id":264842493,"number":2425,"title":"pre-caching images across site or sub-section of site","user":{"login":"migs540","id":25975622,"avatar_url":"https://avatars3.githubusercontent.com/u/25975622?v=4","gravatar_id":"","url":"https://api.github.com/users/migs540","html_url":"https://github.com/migs540","followers_url":"https://api.github.com/users/migs540/followers","following_url":"https://api.github.com/users/migs540/following{/other_user}","gists_url":"https://api.github.com/users/migs540/gists{/gist_id}","starred_url":"https://api.github.com/users/migs540/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/migs540/subscriptions","organizations_url":"https://api.github.com/users/migs540/orgs","repos_url":"https://api.github.com/users/migs540/repos","events_url":"https://api.github.com/users/migs540/events{/privacy}","received_events_url":"https://api.github.com/users/migs540/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2017-10-12T07:39:28Z","updated_at":"2017-10-13T11:53:52Z","closed_at":null,"author_association":"NONE","body":"What if we could pre-load images across a site (sub-pages) just as we do for sub-pages? \r\n\r\nAt the moment gatsby is (awesomely):\r\n\r\n1. loading html\r\n2. then js (including subpage data)\r\n3. Only loading images when you navigate to that page\r\n \r\nbut we kind of lose that customer experience of speed with images. We can do things like progressive reveals as noted in this:\r\n\r\nhttps://github.com/gatsbyjs/gatsby/issues/431\r\n\r\nbut that seems to be a bit of a workaround because if I have a small site I can make the assumption (perhaps incorrectly!) that people will want to navigate throughout the site, not just the main page. If so it would make sense to:\r\n\r\nload html\r\nthen js (including subpage data)\r\nthen images on sub pages (perhaps defining a sequence order)\r\n\r\nYes, it increases the overall data size downloaded to devices but if it's a small site or you are enabled to specify how much of (how deep in) the sitemap you wanted to go (or determine form factor and download images for that form-factor size only, sitewide) ... well it seems like we can skip some of the progressive reveal (blurred, skeleton, placeholder photos) and extend the benefits of gatsby's speed to photos themselves. Same could go for animations (lottie) or any content. \r\n\r\nprecache=yes. \r\n\r\nOr have i missed something basic? webpagespeedtest and chrome developer tools (network, img) seem to show the behaviour I mention above for a webpage i built using gatsby build (and copying the public directory contents to my web server). \r\n\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/gatsbyjs/gatsby/issues/comments/336430926","html_url":"https://github.com/gatsbyjs/gatsby/issues/2425#issuecomment-336430926","issue_url":"https://api.github.com/repos/gatsbyjs/gatsby/issues/2425","id":336430926,"user":{"login":"migs540","id":25975622,"avatar_url":"https://avatars3.githubusercontent.com/u/25975622?v=4","gravatar_id":"","url":"https://api.github.com/users/migs540","html_url":"https://github.com/migs540","followers_url":"https://api.github.com/users/migs540/followers","following_url":"https://api.github.com/users/migs540/following{/other_user}","gists_url":"https://api.github.com/users/migs540/gists{/gist_id}","starred_url":"https://api.github.com/users/migs540/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/migs540/subscriptions","organizations_url":"https://api.github.com/users/migs540/orgs","repos_url":"https://api.github.com/users/migs540/repos","events_url":"https://api.github.com/users/migs540/events{/privacy}","received_events_url":"https://api.github.com/users/migs540/received_events","type":"User","site_admin":false},"created_at":"2017-10-13T11:53:52Z","updated_at":"2017-10-13T11:53:52Z","author_association":"NONE","body":"@KyleAMathews I'll give gatsby-image a go. Overall I think it's a step towards what is needed but falls short. Blur-up (or skeleton) just isn't the same as revealing a legible image immediately on page display. When images have legibility we grasp their meaning very quickly, in ms.  "}}
{"actor":{"display_login":"migs540"}}