{"action":"created","issue":{"url":"https://api.github.com/repos/postcss/postcss.org/issues/89","labels_url":"https://api.github.com/repos/postcss/postcss.org/issues/89/labels{/name}","comments_url":"https://api.github.com/repos/postcss/postcss.org/issues/89/comments","events_url":"https://api.github.com/repos/postcss/postcss.org/issues/89/events","html_url":"https://github.com/postcss/postcss.org/issues/89","id":127104886,"number":89,"title":"Load-time optimisations","user":{"login":"jeddy3","id":808227,"avatar_url":"https://avatars.githubusercontent.com/u/808227?v=3","gravatar_id":"","url":"https://api.github.com/users/jeddy3","html_url":"https://github.com/jeddy3","followers_url":"https://api.github.com/users/jeddy3/followers","following_url":"https://api.github.com/users/jeddy3/following{/other_user}","gists_url":"https://api.github.com/users/jeddy3/gists{/gist_id}","starred_url":"https://api.github.com/users/jeddy3/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jeddy3/subscriptions","organizations_url":"https://api.github.com/users/jeddy3/orgs","repos_url":"https://api.github.com/users/jeddy3/repos","events_url":"https://api.github.com/users/jeddy3/events{/privacy}","received_events_url":"https://api.github.com/users/jeddy3/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2016-01-17T16:08:07Z","updated_at":"2016-01-17T19:27:20Z","closed_at":null,"body":"Continuing to break issues into smaller bite-sized chunks... this issue is just about load-time optimisations.\r\n\r\n@ai likes these optimisations and [has said](https://github.com/postcss/postcss.org/issues/74#issuecomment-172246663) he'd tackle it after the first iteration is done :)\r\n\r\nPerhaps to help him out, everyone can jot down things they think could be included in that process. Here's a couple to get started:\r\n\r\n1. Optimise SVG logs with [SVGO](https://github.com/svg/svgo)?\r\n2. Optimise the hero image using the \"[compressive images](https://www.filamentgroup.com/lab/compressive-images.html)\" technique?\r\n4. Optimizing the [critical rendering path](https://developers.google.com/web/fundamentals/performance/critical-rendering-path/?hl=en)?"},"comment":{"url":"https://api.github.com/repos/postcss/postcss.org/issues/comments/172369148","html_url":"https://github.com/postcss/postcss.org/issues/89#issuecomment-172369148","issue_url":"https://api.github.com/repos/postcss/postcss.org/issues/89","id":172369148,"user":{"login":"ai","id":19343,"avatar_url":"https://avatars.githubusercontent.com/u/19343?v=3","gravatar_id":"","url":"https://api.github.com/users/ai","html_url":"https://github.com/ai","followers_url":"https://api.github.com/users/ai/followers","following_url":"https://api.github.com/users/ai/following{/other_user}","gists_url":"https://api.github.com/users/ai/gists{/gist_id}","starred_url":"https://api.github.com/users/ai/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ai/subscriptions","organizations_url":"https://api.github.com/users/ai/orgs","repos_url":"https://api.github.com/users/ai/repos","events_url":"https://api.github.com/users/ai/events{/privacy}","received_events_url":"https://api.github.com/users/ai/received_events","type":"User","site_admin":false},"created_at":"2016-01-17T19:27:20Z","updated_at":"2016-01-17T19:27:20Z","body":"Loading on scroll is good for big sites with long lists.\r\n\r\nIn your case we should just split images to two parts: critical and non-critical. And load all non-critical just afrer `onload` event.\r\n\r\nOn main page non-critical JS will be for REPL, because PostCSS is not big (because of `source-map` package). Alll other JS and CSS can be packed into one `main.js` and `main.css`.\r\n\r\nDocs and other pages can share one `app.js` and `app.css`, I think."}}