The https://www.ucas.com core non-functional requirements v2.1 states:
When creating web pages, the only part of a page that you can rely upon working is the HTML. Even that can fail, but without HTML there is no web page and everything else becomes moot. The attitude towards building for the web with this in mind is called progressive enhancement.
Source https://www.gov.uk/service-manual/making-software/progressive-enhancement.html
The page goes on to give guidelines under the following headers:
We have a small library of resources which we refer to for guidance on design priciples, regarding responsive website creation:
A performance budget is just what it sounds like: you set a “budget” on your page and do not allow the page to exceed that. This may be a specific load time, but it is usually an easier conversation to have when you break the budget down into the number of requests or size of the page.
The BBC did this with their responsive mobile site. They determined that they wanted each page to be usable within 10 seconds on a GPRS connection and then based their goals for page weight and request count on that.
Once those goals are set, you stick to them. Anytime you want to add something to a page, you need to ensure it stays within budget. Steve Souders talked about the three options you have if something does not fit within the budget:
Just be sure to define the budget early on. Defining a performance budget after you’ve already finalized the appearance of a site limits its effectiveness. It may still help to guide decisions about plugins and so on, but deciding a page can’t exceed 500kB when a mock-up containing three carousels and a full-screen high-resolution background image has already been approved isn’t going to do you much good.
Srouce http://www.timkadlec.com/2013/01/setting-a-performance-budget
Security has many tenets, but from a frontend developer point of view, we will pay particular attention to the following areas: