{"action":"closed","issue":{"url":"https://api.github.com/repos/GoogleChrome/lighthouse/issues/490","repository_url":"https://api.github.com/repos/GoogleChrome/lighthouse","labels_url":"https://api.github.com/repos/GoogleChrome/lighthouse/issues/490/labels{/name}","comments_url":"https://api.github.com/repos/GoogleChrome/lighthouse/issues/490/comments","events_url":"https://api.github.com/repos/GoogleChrome/lighthouse/issues/490/events","html_url":"https://github.com/GoogleChrome/lighthouse/issues/490","id":163161817,"number":490,"title":"Audits for contexts with connectivity, data cost, device, power and browser constraints","user":{"login":"samdutton","id":205226,"avatar_url":"https://avatars.githubusercontent.com/u/205226?v=3","gravatar_id":"","url":"https://api.github.com/users/samdutton","html_url":"https://github.com/samdutton","followers_url":"https://api.github.com/users/samdutton/followers","following_url":"https://api.github.com/users/samdutton/following{/other_user}","gists_url":"https://api.github.com/users/samdutton/gists{/gist_id}","starred_url":"https://api.github.com/users/samdutton/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/samdutton/subscriptions","organizations_url":"https://api.github.com/users/samdutton/orgs","repos_url":"https://api.github.com/users/samdutton/repos","events_url":"https://api.github.com/users/samdutton/events{/privacy}","received_events_url":"https://api.github.com/users/samdutton/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":5,"created_at":"2016-06-30T13:11:46Z","updated_at":"2016-11-08T19:23:04Z","closed_at":"2016-11-08T19:23:04Z","body":"A bug to gauge what Lighthouse could/should test for in contexts with any of the following constraints:\n\n• Low bandwidth (poor 3G or worse) and high latency (RTT times).\n• High data cost (such as data-roaming scenarios or contexts where data is expensive relative to median income).\n• Low-spec devices (limited CPU, memory and storage).\n• Small, low-spec screens (small viewports, low display quality, increased proportion interaction failures).\n• Limited access to power (devices with limited battery life, contexts without access to a reliable, affordable power supply).\n• 'Non-evergreen' browsers such as UC and IE8.\n\nMore detail about these concerns here: [developers.google.com/web/billions](https://developers.google.com/web/billions). \n\nData, information and tools [here](https://docs.google.com/document/d/1LV55gzhvvfIvCTrn9yx6kvRrtXgjxIrzbQT-hSLcHZ0).\n\nThe audits I'm proposing are:\n• Works well on browsers such as UC Browser and IE 8: fallbacks or alternatives for CSS calc(), semantic elements, etc.\n• Page weight: warning for >xxMB total, with data for data (money) cost.\n• Number of requests: warning for >xx requests total, with data for potential RTT time.\n• Effective content design for small, low-spec screens (not just viewport size — see example [here](https://developers.google.com/web/fundamentals/design-and-ui/content/viewport)).\n• Works well with limited CPU, memory and storage.\n• Power (battery) consumption.\n\nHard to work out how to test for some of these — and not sure how best to prioritise.\n"}}
{"actor":{"display_login":"paulirish"}}