程序设定名字最长字符设定
Jason Grigsby once quipped that “We’ve remade the Internet in our image….obese.” He was right, of course. Average page weight and number of connections has been increasing at a rather alarming rate.
杰森·格里格斯比(Jason Grigsby) 曾打趣说 ：“我们已经按照形象改造了互联网……肥胖。” 他当然是对的。 平均页面权重和连接数一直以惊人的速度增长。
This is why I’ve been so happy to see the recent rash of posts discussing performance as a fundamental component of design. The latest comes from Mr. Brad Frost. He makes the case that performance is not just something developers need to worry about, but that it is an “essential design feature.”
这就是为什么我如此高兴地看到最近有大量文章讨论将性能作为设计的基本组成部分的原因。 最新消息来自Brad Frost先生 。 他认为性能不仅是开发人员需要担心的，而且是“必要的设计功能”。
One of the things he suggests doing is mentioning performance in project documents.
他建议做的一件事是在项目文档中提及绩效。
Statements of work, project proposals and design briefs should explicitly and repeatedly call out performance as a primary goal. “The goal of this project is to create a stunning, flexible, lightning-fast experience…”
工作说明，项目建议书和设计简介应明确并反复地将性能作为主要目标。 “该项目的目标是创造令人惊叹，灵活，闪电般的体验……”
It’s an excellent point. Performance should be brought up early and often to emphasize its importance. Not considering it from the earliest stages of a project is a surefire way to end up with slow and bloated sites. A decision made early on about the visual appearance of a site can have a serious impact on how the site itself will end up performing.
这是一个很好的观点。 应尽早提高绩效，并经常强调其重要性。 从项目的最初阶段就不考虑它是确保缓慢而膨胀的站点的必然选择。 早期就站点的外观做出的决定可能会对站点本身的最终运行方式产生严重影响。
Early in the project, saying things like “lightning-fast experience” is probably sufficient. At some point you need to get a little more direct though.
在项目的早期，说些“闪电般的体验”就足够了。 在某些时候，您需要更直接一点。
Enter the performance budget. I’ve mentioned this before, but it’s worth discussing in a bit more detail.
输入绩效预算。 我之前已经提到了这一点 ，但是值得进行更详细的讨论。
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.
英国广播公司通过其响应式移动网站做到了这一点。 他们确定希望每个页面在GPRS连接上都能在10秒内可用，然后基于页面权重和请求计数的目标。
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:
一旦设定了这些目标，您便会坚持下去。 每当您想在页面中添加内容时，都需要确保其在预算之内。 史蒂夫·苏德斯(Steve Souders)讨论了如果预算不适合您的三种选择：
- Optimize an existing feature or asset on the page. 优化页面上的现有功能或资产。
- Remove an existing feature or asset from the page. 从页面中删除现有功能或资产。
- Don’t add the new feature or asset. 不要添加新功能或资产。
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.
只要确保尽早定义预算即可。 在网站外观最终确定之后定义性能预算会限制其有效性。 它仍然可能有助于指导有关插件等的决策，但是当包含三个旋转木马和全屏高分辨率背景图像的模型已经被批准时，决定页面不能超过500kB是不会做的你好极了。
Clearleft recently wrote an excellent post about their experience with using a performance budget and how it impacted their project:
Clearleft最近写了一篇很棒的文章，介绍了他们使用绩效预算的经验及其对项目的影响：
The important point is to look at every decision, right through the design/build process, as something that has consequence. Having a pre-defined ‘budget’ is a clear, tangible way to frame decisions about what can and can’t be be included, and at a suitably early stage in the project. It can also potentially provide some justification to the client about why certain things have been omitted (or rather, swapped out for something else).
重要的一点是要在整个设计/构建过程中仔细考虑每一项决定，以确保产生决定性的结果。 拥有预定义的“预算”是一种清晰，切实的方法，可以在项目的适当早期阶段就可以包括和不可以包括哪些内容制定决策。 它也可能为客户提供某些理由，说明为何省略了某些内容(或者换成其他内容)。
That’s the value of a performance budget: it provides a framework for discussions as you move forward. It serves as a point of reference as you decide what components should, and shouldn’t, get added to a page.
这就是绩效预算的价值：它为您前进的讨论提供了一个框架。 在您决定应该或不应该将哪些组件添加到页面时，它可以作为参考。
It’s worth noting that I’m assuming you have already determined what content needs to be on the page to begin with. A performance budget doesn’t guide your decisions about what content should be displayed. Rather, it’s about how you choose to display that content. Removing important content altogether to decrease the weight of a page is not a performance strategy.
值得注意的是，我假设您已经确定了开始时页面上需要包含哪些内容。 效果预算不会指导您决定应显示哪些内容。 而是关于您如何选择显示该内容。 完全删除重要内容以减少页面的重量不是性能策略。
As Brad stated, it’s time to give performance the attention it deserves and setting a budget is an excellent place to start.
正如Brad所说，是时候让性能得到应有的关注了，制定预算是一个很好的起点。
翻译自: https://timkadlec.com/2013/01/setting-a-performance-budget/
程序设定名字最长字符设定