{"id":13672328,"url":"https://github.com/JohnsenZhou/Front-End-Performance-Checklist","last_synced_at":"2025-04-27T21:32:47.043Z","repository":{"id":46148204,"uuid":"142171719","full_name":"JohnsenZhou/Front-End-Performance-Checklist","owner":"JohnsenZhou","description":"🎮  前端性能清单，让你的网站跑的更快","archived":false,"fork":true,"pushed_at":"2019-03-28T01:44:24.000Z","size":160,"stargazers_count":539,"open_issues_count":0,"forks_count":59,"subscribers_count":22,"default_branch":"master","last_synced_at":"2024-08-03T09:11:56.671Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"http://lab.johnsenzhou.com/Front-End-Performance-Checklist/","language":null,"has_issues":false,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":"thedaviddias/Front-End-Performance-Checklist","license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/JohnsenZhou.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":".github/CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":"CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2018-07-24T14:40:11.000Z","updated_at":"2024-07-30T13:40:15.000Z","dependencies_parsed_at":null,"dependency_job_id":null,"html_url":"https://github.com/JohnsenZhou/Front-End-Performance-Checklist","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/JohnsenZhou%2FFront-End-Performance-Checklist","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/JohnsenZhou%2FFront-End-Performance-Checklist/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/JohnsenZhou%2FFront-End-Performance-Checklist/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/JohnsenZhou%2FFront-End-Performance-Checklist/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/JohnsenZhou","download_url":"https://codeload.github.com/JohnsenZhou/Front-End-Performance-Checklist/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":224087243,"owners_count":17253522,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-08-02T09:01:32.400Z","updated_at":"2024-11-11T10:30:38.651Z","avatar_url":"https://github.com/JohnsenZhou.png","language":null,"readme":"\u003ch1 align=\"center\"\u003e\n\u003cbr\u003e\n  \u003cimg src=\"https://raw.githubusercontent.com/thedaviddias/Front-End-Performance-Checklist/master/images/logo-front-end-performance-checklist.jpg\" alt=\"Front-End Performance Checklist\" width=\"170\"\u003e\n  \u003cbr\u003e\n    \u003cbr\u003e\n  前端性能清单\n  \u003cbr\u003e\n\u003c/h1\u003e\n\n\u003ch4 align=\"center\"\u003e🎮 前端性能清单，让你的网站跑的更快\u003c/h4\u003e\n\u003cp align=\"center\"\u003e单一原则: \"在设计和编写时考虑到性能\"\u003c/p\u003e\n\n\u003cp align=\"center\"\u003e\n  \u003ca href=\"http://makeapullrequest.com\"\u003e\n    \u003cimg src=\"https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat-square\" alt=\"PRs Welcome\"\u003e\n  \u003c/a\u003e\n  \u003ca href=\"https://spectrum.chat/front-end-checklist\"\u003e\n    \u003cimg src=\"https://img.shields.io/badge/chat-on_spectrum-4837E2.svg?style=flat-square\" alt=\"Spectrum\"\u003e\n  \u003c/a\u003e\n    \u003ca href=\"https://opensource.org/licenses/MIT\"\u003e\n    \u003cimg src=\"https://img.shields.io/badge/license-MIT-blue.svg?style=flat-square\" alt=\"Licence MIT\"\u003e\n  \u003c/a\u003e\n\u003c/p\u003e\n\n\u003cp align=\"center\"\u003e\n  \u003ca href=\"#how-to-use\"\u003eHow To Use\u003c/a\u003e • \u003ca href=\"#contributing\"\u003eContributing\u003c/a\u003e • \u003ca href=\"https://www.producthunt.com/posts/front-end-performance-checklist\"\u003eProduct Hunt\u003c/a\u003e\n\u003c/p\u003e\n\u003cp align=\"center\"\u003e\n    \u003cspan\u003e其他清单：\u003c/span\u003e\n    \u003cbr\u003e\n  🗂 \u003ca href=\"https://github.com/JohnsenZhou/Front-End-Checklist\"\u003eFront-End Checklist\u003c/a\u003e • 💎 \u003ca href=\"https://github.com/JohnsenZhou/Front-End-Design-Checklist\"\u003eFront-End Design Checklist\u003c/a\u003e\n\u003c/p\u003e\n\n## 目录\n\n1. **[HTML](#html)**\n2. **[CSS](#css)**\n3. **[Fonts](#fonts)**\n4. **[Images](#images)**\n5. **[JavaScript](#javascript)**\n6. **[Server](#server) (梳理中)**\n7. **[JS Frameworks](#js-frameworks) (梳理中)**\n\n## 概述\n\n性能是一个很大的主题，但它并不总是一个“后端”或“管理（admin）”所要考虑的主题：它也是一个前端需要考虑的。作为前端开发人员，前端性能清单是你在项目中应该检查或者至少需要注意的性能要点的详尽列表。\n\n### 如何使用?\n\n对于每个规则，将有一个段落解释**为什么**此规则很重要以及**如何**解决它。有关更深入的信息，可相应找到可指向的🛠工具，📖文章或📹媒体的链接，以便梳理。\n\n前端性能清单中的所有项目都是获得最高性能得分的基本要素，但是你可以找到一些指标来帮助你最终确定一些规则的优先顺序。以下有3个级别的优先级：\n\n* ![Low][low] 表示该项目的优先级**较低**，对项目有影响。\n* ![Medium][medium] 表示该项目具有**中等优先级**并对项目产生影响，开发时需要处理这些项目。\n* ![High][high] 表示该项目具有**高优先级**并对项目产生影响，开发时必须要处理这些项目，不然性能将大打折扣。\n\n### 性能测试工具\n\n以下是一些您可以用来测试或监控您的网站或应用程序的工具：\n\n * 🛠 [WebPagetest - Website Performance and Optimization Test](https://www.webpagetest.org/)\n * 🛠 ☆ [Dareboost: Website Speed Test and Website Analysis](https://www.dareboost.com/) (use the coupon WPCDD20 for -20%)\n * 🛠 [GTmetrix | Website Speed and Performance Optimization](https://gtmetrix.com/)\n * 🛠 [PageSpeed Insights](https://developers.google.com/speed/pagespeed/insights/)\n * 🛠 [Web.dev](https://web.dev/measure)\n * 🛠 [Pingdom Website Speed Test](https://tools.pingdom.com)\n * 📖 [Pagespeed - The tool and optimization guide](https://varvy.com/pagespeed/)\n * 📖 [Make the Web Faster | Google Developers](https://developers.google.com/speed/)\n * 🛠 [Sitespeed.io - Welcome to the wonderful world of Web Performance](https://www.sitespeed.io/)\n * 🛠 [Calibre](https://calibreapp.com/)\n * 🛠 [Website Speed Test | Check Web Performance \u0026raquo; Dotcom-Tools](https://www.dotcom-tools.com/website-speed-test.aspx)\n * 🛠 [Website and Server Uptime Monitoring - Pingdom](https://www.pingdom.com/product/uptime-monitoring/) ([Free Signup Link](https://www.pingdom.com/free))\n * 🛠 [Uptime Robot](https://uptimerobot.com)\n * 🛠 [SpeedCurve: Monitor front-end performance](https://speedcurve.com)\n * 🛠 [PWMetrics - CLI tool and lib to gather performance metrics](https://github.com/paulirish/pwmetrics)\n * 🛠 [Varvy - Page speed optimization]( https://varvy.com/pagespeed/)\n * 🛠 [Lighthouse - Google]( https://developers.google.com/web/tools/lighthouse/#devtools)\n * 🛠 [Checkbot browser extension - Checks for web performance best practices](https://www.checkbot.io/)\n * 🛠 [Yellow Lab Tools | Online test to help speeding up heavy web pages](https://yellowlab.tools/)\n * 🛠 [Speedrank - Web Performance Monitoring](https://speedrank.app/)\n * 🛠 [DebugBear - Monitor website performance and Lighthouse scores](https://www.debugbear.com/)\n\n### 参考\n\n * 📖 [The Cost Of JavaScript - YouTube](https://www.youtube.com/watch?v=_bzqF05xsC4)\n * 📖 [AddyOsmani.com - Start Performance Budgeting](https://addyosmani.com/blog/performance-budgets/)\n * 📖 [Get Started With Analyzing Runtime Performance  |  Google Developers](https://developers.google.com/web/tools/chrome-devtools/evaluate-performance/)\n * 📖 [State of the Web | 2018_01_01](https://httparchive.org/reports/state-of-the-web?start=2018_01_01)\n * 📖 [Page Weight Doesn't Matter](https://www.speedshop.co/2015/11/05/page-weight-doesnt-matter.html)\n * 📖 [Front-End Performance Checklist 2018 [PDF, Apple Pages]](https://www.smashingmagazine.com/2018/01/front-end-performance-checklist-2018-pdf-pages/)\n * 📖 [Designing for Performance Weighing Aesthetics and Speed - By Lara Callender Hogan [eBook, Print]](http://designingforperformance.com/index.html)\n * 📖 [Varvy - Web performance glossary](https://varvy.com/performance/)\n * 📖 [fabkrum/web-performance-resources: Up to date collection of valuable web performance resources](https://github.com/fabkrum/web-performance-resources)\n * 📖 [Checkbot - Web Speed Best Practices](https://www.checkbot.io/guide/speed/)\n * 🛠 [Progressive Tooling - A list of community-built, third-party tools that can be used to improve page performance](https://progressivetooling.com/)\n\n---\n\n## HTML\n\n![html]\n\n- [ ] **压缩 HTML:** ![medium] HTML代码压缩，将注释、空格和新行从生产文件中删除。\n\n    *为什么：*\n    \u003e 删除所有不必要的空格、注释和中断行将减少HTML的大小，加快网站的页面加载时间，并显著减少用户的下载时间。\n\n    *怎么做：*\n    \u003e 大多数框架都有插件用来压缩网页的体积。你可以使用一组可以自动完成工作的NPM模块。\n\n    * 🛠 [HTML minifier | Minify Code](http://minifycode.com/html-minifier/)\n    * 📖 [Experimenting with HTML minifier — Perfection Kills](http://perfectionkills.com/experimenting-with-html-minifier/#use_short_doctype)\n\n- [ ] **删除不必要的注释：** ![low] 确保从您的网页中删除注释。\n\n    *为什么：*\n    \u003e 注释对用户来说是没有用的，应该从生产环境文件中删除。可能需要保留注释的一种情况是：保留远端代码库（keep the origin for a library）。\n\n    *怎么做：*\n    \u003e 大多数情况下，可以使用HTML minify插件删除注释。\n\n * 🛠 [remove-html-comments - npm](https://www.npmjs.com/package/remove-html-comments)\n\n- [ ] **删除不必要的属性：** ![low] 像 `type=\"text/javascript\"` or `type=\"text/css\"` 这样的属性应该被移除。\n\n    ```html\n    \u003c!-- Before HTML5 --\u003e\n    \u003cscript type=\"text/javascript\"\u003e\n        // Javascript code\n    \u003c/script\u003e\n\n    \u003c!-- Today --\u003e\n    \u003cscript\u003e\n        // Javascript code\n    \u003c/script\u003e\n    ```\n\n    *为什么*\n    \u003e 类型属性不是必需的，因为HTML5把text/css和text/javascript作为默认值。没用的代码应在网站或应用程序中删除，因为它们会使网页体积增大。\n\n    *怎么做：*\n    \u003e ⁃ 确保所有\u003clink\u003e和\u003cscript\u003e标记都没有任何type属性。\n\n    * 📖 [The Script Tag | CSS-Tricks](https://css-tricks.com/the-script-tag/)\n   \n- [ ] **在JavaScript引用之前引用CSS标记：** ![high] 确保在使用JavaScript代码之前加载CSS。\n\n    ```html\n    \u003c!-- 不推荐 --\u003e\n    \u003cscript src=\"jquery.js\"\u003e\u003c/script\u003e\n    \u003cscript src=\"foo.js\"\u003e\u003c/script\u003e\n    \u003clink rel=\"stylesheet\" href=\"foo.css\"/\u003e\n\n    \u003c!-- 推荐 --\u003e\n    \u003clink rel=\"stylesheet\" href=\"foo.css\"/\u003e\n    \u003cscript src=\"jquery.js\"\u003e\u003c/script\u003e\n    \u003cscript src=\"foo.js\"\u003e\u003c/script\u003e\n    ```\n\n    *为什么：*\n    \u003e 在引用JavaScript之前引用CSS可以实现更好地并行下载，从而加快浏览器的渲染速度。\n\n    *怎么做：*\n    \u003e 确保\u003chead\u003e中的\u003clink\u003e和\u003cstyle\u003e始终位于\u003cscript\u003e之前。\n\n    * 📖 [合理安排styles和scripts来提高网页速度](https://varvy.com/pagespeed/style-script-order.html)\n\n- [ ] **最小化iframe的数量：** ![high] 仅在没有任何其他技术可行性时才使用iframe。尽量避免使用iframe。\n\n- [ ] **DNS预取：** ![high] 一次 DNS 查询时间大概在60-120ms之间或者更长，提前解析网页中可能的网络连接域名\n    ```html\n     \u003clink rel=\"dns-prefetch\" href=\"http://example.com/\"\u003e\n    ```\n\n**[⬆ 返回顶部](#table-of-contents)**\n\n## CSS\n\n![css]\n\n- [ ] **压缩:** ![high] 所有CSS文件都需要被压缩，从生产文件中删除注释，空格和空行。\n\n    *为什么：*\n    \u003e 缩小CSS文件后，内容加载速度更快，并且将更少的数据发送到客户端，所以在生产中缩小CSS文件是非常重要，这对用户是有益的，就像任何企业想要降低带宽成本和降低资源。\n\n    *怎么做：*\n    \u003e 使用工具在构建或部署之前自动压缩文件。\n\n    * 🛠 [cssnano: 基于PostCSS生态系统的模块化压缩工具。](https://cssnano.co/)\n    * 🛠 [@neutrinojs/style-minify - npm](https://www.npmjs.com/package/@neutrinojs/style-minify)\n    * 🛠 [Online CSS Compressor](http://refresh-sf.com)\n\n- [ ] **Concatenation:** ![medium] CSS文件合并（对于HTTP/2效果不是很大）。\n\n    ```html\n\n    \u003c!-- 不推荐 --\u003e\n    \u003clink rel=\"stylesheet\" src=\"foo.css\"/\u003e\n    \u003clink rel=\"stylesheet\" src=\"ajax.css\"/\u003e\n\n    \u003c!-- 推荐 --\u003e\n    \u003clink rel=\"stylesheet\" src=\"combined.css\"/\u003e\n    ```\n\n    *为什么：*\n    \u003e 如果你还在使用HTTP/1，那么你就需要合并你的文件。不过在使用HTTP/2的情况下不用这样（效果待测试）。\n\n    *怎么做：*\n    \u003e 在构建或部署之前使用在线工具或者其他插件来合并文件。\n    \u003e 当然，要确保合并文件后项目可以正常运行。\n\n    * 📖 [HTTP: 优化应用程序交付 - 高性能浏览器网络 (O'Reilly)](https://hpbn.co/optimizing-application-delivery/#optimizing-for-http2)\n    * 📖 [HTTP/2时代的性能最佳实践](https://deliciousbrains.com/performance-best-practices-http2/)\n\n- [ ] **非阻塞：** ![high] CSS文件需要非阻塞引入，以防止DOM花费更多时间才能渲染完成。\n\n    ```html\n    \u003clink rel=\"preload\" href=\"global.min.css\" as=\"style\" onload=\"this.rel='stylesheet'\"\u003e\n    \u003cnoscript\u003e\u003clink rel=\"stylesheet\" href=\"global.min.css\"\u003e\u003c/noscript\u003e\n    ```\n\n    *为什么：*\n    \u003e CSS文件可以阻止页面加载并延迟页面呈现。使用`preload`实际上可以在浏览器开始显示页面内容之前加载CSS文件。\n\n    *怎么做：*\n    \u003e 需要添加`rel`属性并赋值`preload`，并在`\u003clink\u003e`元素上添加`as=“style”`。\n\n    * 📖 [loadCSS by filament group](https://github.com/filamentgroup/loadCSS)\n    * 📖 [使用loadCSS预加载CSS的示例](https://gist.github.com/thedaviddias/c24763b82b9991e53928e66a0bafc9bf)\n    * 📖 [使用rel =“preload”预加载内容](https://developer.mozilla.org/en-US/docs/Web/HTML/Preloading_content)\n    * 📖 [Preload: What Is It Good For? — Smashing Magazine](https://www.smashingmagazine.com/2016/02/preload-what-is-it-good-for/)\n\n- [ ] **CSS类(class)的长度:** ![low] class的长度会对HTML和CSS文件产生（轻微）影响。\n\n    *为什么：*\n    \u003e 甚至性能影响也是有争议的，项目的命名策略会对样式表的可维护性有重大影响。如果使用BEM，在某些情况下可能会写出比所需要的类名更长的字符。重要的是要明智的选择名字和命名空间。\n\n    *怎么做：*\n    \u003e 可能有些人更关注类名的长度，但是网站按组件进行划分的话可以帮助减少类名的数量和长度。\n\n    * 🛠 [long vs short class · jsPerf](https://jsperf.com/long-vs-short-class)\n\n- [ ] **不用的CSS:** ![medium] 删除未使用的CSS选择器。\n\n    *为什么：*\n    \u003e 删除未使用的CSS选择器可以减小文件的大小，提高资源的加载速度。\n\n    *怎么做：*\n    \u003e ⚠️ 检查要使用的CSS框架是否已包含reset/normalize代码，可能不需要用到reset/normalize文件中的内容。\n\n    * 🛠 [UnCSS Online](https://uncss-online.com/)\n    * 🛠 [PurifyCSS](https://github.com/purifycss/purifycss)\n    * 🛠 [PurgeCSS](https://github.com/FullHuman/purgecss)\n    * 🛠 [Chrome DevTools Coverage](https://developers.google.com/web/updates/2017/04/devtools-release-notes#coverage)\n\n* [ ] **关键CSS（Critical）:** ![high] 将页面渲染时必备的CSS通过```\u003cstyle\u003e\u003c/style\u003e```的方式内联到页面中（尽可能压缩后引用）。\n\n    *为什么：*\n    \u003e 内联关键CSS有助于加速网页的呈现，减少对服务器的请求数量。\n\n    *怎么做：*\n    \u003e 使用在线工具或使用Addy Osmani开发的插件生成关键CSS。\n\n    * 📖 [理解关键CSS](https://www.smashingmagazine.com/2015/08/understanding-critical-css/)\n    * 🛠 [Critical by Addy Osmani on GitHub](https://github.com/addyosmani/critical) automates this.\n    * 📖 [Inlining critical CSS for better web performance | Go Make Things](https://gomakethings.com/inlining-critical-css-for-better-web-performance/)\n    * 📖 [Critical Path CSS Generator - Prioritize above the fold content :: SiteLocity](https://www.sitelocity.com/critical-path-css-generator)\n    * 📖 [Reduce the size of the above-the-fold content](https://developers.google.com/speed/docs/insights/PrioritizeVisibleContent)\n\n- [ ] **嵌入或内联CSS：** ![high] 避免在\u003cbody\u003e中使用嵌入或内联CSS*（对HTTP/2无效）*\n\n    *为什么：*\n    \u003e 因为将内容与设计分开是一种很好的做法。它还可以提高代码的可维护性并使站点可访问性更强。对于性能来说，它只是减少了HTML页面的文件大小和加载时间。\n\n    *怎么做：*\n    \u003e 始终使用外部样式表或在\u003chead\u003e中嵌入CSS（并遵循其他CSS性能规则）。\n\n    * 📖 [Observe CSS Best Practices: Avoid CSS Inline Styles](https://www.lifewire.com/avoid-inline-styles-for-css-3466846)\n\n- [ ] **分析样式表的复杂性：** ![high] 分析样式表有助于发现有问题的、冗余和重复的CSS选择器。\n\n    *为什么：*\n    \u003e 有时在CSS中会出现冗余或验证错误，分析CSS文件并删除这些复杂性的代码可以加速CSS文件的读取和加载（因为您的浏览器会更快地读取它们）\n\n    *怎么做：*\n    \u003e CSS需要有编写规范，再通过CSS预处理器处理。下面列出的一些在线工具也可以帮助你分析和更正你的代码。\n    \n    * 🛠 [TestMyCSS | 优化和检查CSS性能](http://www.testmycss.com/)\n    * 📖 [CSS 统计数据（stats）](https://cssstats.com/)\n    * 🛠 [macbre/analyze-css: CSS选择器复杂性和性能分析](https://github.com/macbre/analyze-css)\n    * 🛠 [Project Wallace](https://www.projectwallace.com/) is like CSS Stats but stores stats over time so you can track your changes\n\n**[⬆ 返回顶部](#table-of-contents)**\n\n## 字体\n\n![fonts]\n\n* 📖 [A Book Apart, Webfont Handbook](https://abookapart.com/products/webfont-handbook)\n\n- [ ] **Webfont格式：** ![medium] 在你的网站或者应用使用WOFF2格式字体。\n\n    *为什么：*\n    \u003e 根据Google的说法，WOFF 2.0 Web字体压缩格式平均比WOFF 1.0高30％的增益。一个较好的做法是使用WOFF 2.0作为主要字体，WOFF 1.0和TTF格式字体作为备选。\n\n    *怎么做：*\n    \u003e 在购买新字体之前应先检查提供商是否提供了WOFF2格式。如果使用的是免费字体，则可以始终使用Font Squirrel生成所需格式的字体。\n\n    * 📖 [WOFF 2.0 – 了解有关下一代Web字体格式的更多信息，并将TTF转换为WOFF2](https://gist.github.com/sergejmueller/cf6b4f2133bcb3e2f64a)\n    * 🛠 [创建你自己的@ font-face Kits » Font Squirrel](https://www.fontsquirrel.com/tools/webfont-generator)\n    * 🛠 [IcoMoon App - Icon Font, SVG, PDF \u0026 PNG Generator](https://icomoon.io/app/)\n    * 📖 [Using @font-face | CSS-Tricks](https://css-tricks.com/snippets/css/using-font-face/?ref=frontendchecklist)\n    * 📖 [Can I use... WOFF2](https://caniuse.com/#feat=woff2)\n\n- [ ] **使用`preconnect`可以更快地加载字体：** ![medium]\n\n    ```html\n    \u003clink rel=\"preconnect\" href=\"https://fonts.gstatic.com\" crossorigin\u003e\n    ```\n\n    *为什么：*\n    \u003e 当你浏览网站时，设备需要获取网站所在的位置以及需要连接的服务器。浏览器必须连接DNS服务器并等待查找完成后再获取资源（字体，CSS文件...），`prefetche`和`preconnect`允许浏览器在空闲时进行上面的操作，在真实请求时就不需要再花时间去做一系列动作。这带来了性能的提升，因为当浏览器使用字体信息解析css文件并切从服务器请求字体文件时，它已经预先解析了DNS信息并且在其连接池中准备好与服务器的开放连接。\n\n    *怎么做：*\n    \u003e 在预取您的网络字体之前，请使用网页测试来检测网站.\n    \u003e 查找蓝绿色DNS查找并记下正在请求的主机（Look for teal colored DNS lookups and note the host that are being requested.）\n    \u003e 在\u003chead\u003e中添加预取的webfonts，添加上一步查找到的主机名。\n\n    * 📖 [Faster Google Fonts with Preconnect - CDN Planet](https://www.cdnplanet.com/blog/faster-google-webfonts-preconnect/)\n    * 📖 [Make Your Site Faster with Preconnect Hints | Viget](https://www.viget.com/articles/make-your-site-faster-with-preconnect-hints/)\n    * 📖 [Ultimate Guide to Browser Hints: Preload, Prefetch, and Preconnect - MachMetrics Speed Blog](https://www.machmetrics.com/speed-blog/guide-to-browser-hints-preload-preconnect-prefetch/)\n    * 📖 [A Comprehensive Guide to Font Loading Strategies—zachleat.com](https://www.zachleat.com/web/comprehensive-webfonts/#font-face)\n    * 🛠 [typekit/webfontloader: Web Font Loader gives you added control when using linked fonts via @font-face.](https://github.com/typekit/webfontloader)\n\n- [ ] **Webfont大小：** ![medium] Webfont尺寸不超过300kb（包括所有变体）\n\n * 📖 [Font Bytes - Page Weight](https://httparchive.org/reports/page-weight#bytesFont)\n\n**[⬆ 返回顶部](#table-of-contents)**\n\n## 图片\n\n![images]\n\n * 📖 [Image Bytes in 2018](https://httparchive.org/reports/page-weight#bytesImg)\n\n* [ ] **图像优化:** ![high] 在保证压缩后的图片符合产品要求的情况下将图像进行优化。\n\n    *为什么：*\n    \u003e 优化的图像在浏览器中加载速度更快，消耗的数据更少。\n\n    *怎么做：*\n    \u003e 尽可能尝试使用CSS3效果（而不是用小图像替代）\n    \u003e 尽可能使用字体图片\n    \u003e 使用 SVG\n    \u003e 使用编译工具并指定85以下的级别压缩。\n\n    * 📖 [Image Optimization | Web Fundamentals | Google Developers](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/image-optimization)\n    * 📖 [Essential Image Optimization - An eBook by Addy Osmani](https://images.guide/)\n    * 🛠 [TinyJPG – Compress JPEG images intelligently](https://tinyjpg.com/)\n    * 🛠 [Kraken.io - Online Image Optimizer](https://kraken.io/web-interface)\n    * 🛠 [Compressor.io - optimize and compress JPEG photos and PNG images](https://compressor.io/compress)\n    * 🛠 [Cloudinary - Image Analysis Tool](https://webspeedtest.cloudinary.com)\n    * 🛠 [SVGOMG - Optimize SVG vector graphics files](https://jakearchibald.github.io/svgomg/)\n\n\n* [ ] **图像格式：** ![high] 适当选择图像格式。\n\n    *为什么：*\n    \u003e 确保图片不会减慢网站速度\n        \n    *怎么做：*\n    \u003e 使用[Lighthouse](https://developers.google.com/web/tools/lighthouse/)识别哪些图像可以使用下一代图片格式（如JPEG 2000m JPEG XR或WebP）。\n    \u003e 比较不同的格式，有时使用PNG8比PNG16好，有时候不是。\n\n    * 📖 [Serve Images in Next-Gen Formats  |  Tools for Web Developers  |  Google Developers](https://developers.google.com/web/tools/lighthouse/audits/webp)\n    * 📖 [What Is the Right Image Format for Your Website? — SitePoint](https://www.sitepoint.com/what-is-the-right-image-format-for-your-website/)\n     * 📖 [PNG8 - The Clear Winner — SitePoint](https://www.sitepoint.com/png8-the-clear-winner/)\n     * 📖 [8-bit vs 16-bit - What Color Depth You Should Use And Why It Matters - DIY Photography](https://www.diyphotography.net/8-bit-vs-16-bit-color-depth-use-matters/)\n\n- [ ] **使用矢量图像 VS 栅格/位图：** ![medium] 可以的话，推荐使用矢量图像而不是位图图像。\n\n    *为什么：*\n    \u003e 矢量图像（SVG）往往比图像小，具有响应性和完美缩放功能。而且这些图像可以通过CSS进行动画和修改操作。\n\n* [ ] **图像尺寸：** ![medium] 如果已知最终渲染图像大小，请在\u003cimg\u003e上设置宽度和高度属性。\n\n    *为什么：*\n    \u003e 如果设置了高度和宽度，则在加载页面时会保留图像所需的空间。如果没有这些属性，浏览器就不知道图像的大小，也无法为其保留适当的空间，导致页面布局在加载期间发生变化。\n\n* [ ] **避免使用Base64图像：** ![medium] 你可以将微小图像转换为base64，但实际上并不是最佳实践。\n\n    * 📖 [Base64 Encoding \u0026 Performance, Part 1 and 2 by Harry Roberts](https://csswizardry.com/2017/02/base64-encoding-and-performance/)\n    * 📖 [A closer look at Base64 image performance – The Page Not Found Blog](http://www.andygup.net/a-closer-look-at-base64-image-performance/)\n    * 📖 [When to base64 encode images (and when not to) | David Calhoun](https://www.davidbcalhoun.com/2011/when-to-base64-encode-images-and-when-not-to/)\n   * 📖 [Base64 encoding images for faster pages | Performance and seo factors](https://varvy.com/pagespeed/base64-images.html)\n\n* [ ] **懒加载：** ![medium] 图像懒加载（始终提供noscript作为后备方案）。\n\n    *为什么：*\n    \u003e 它能改善当前页面的响应时间，避免加载一些用户可能不需要或不必要的图像。\n\n    *怎么做：*\n    \u003e 使用[Lighthouse](https://developers.google.com/web/tools/lighthouse/)可以识别当前屏幕外的图像数量。\n    \u003e 要确保图片懒加载时鼠标悬停或其他用户操作时显示的替代图像。\n    \u003e 可以使用以下图像懒加载的JavaScript插件。\n\n    * 🛠 [verlok/lazyload: Github](https://github.com/verlok/lazyload)\n    * 📖 [Lazy Loading Images and Video  |  Web Fundamentals  |  Google Developers](https://developers.google.com/web/fundamentals/performance/lazy-loading-guidance/images-and-video/)\n    * 📖 [5 Brilliant Ways to Lazy Load Images For Faster Page Loads - Dynamic Drive Blog](http://blog.dynamicdrive.com/5-brilliant-ways-to-lazy-load-images-for-faster-page-loads/)\n\n* [ ] **响应式图像：** ![medium] 确保提供接近设备显示尺寸的图像。\n\n    *为什么：*\n    \u003e 小型设备不需要比视口大的图像。建议在不同尺寸上使用一个图像的多个版本。\n\n    *怎么做：*\n    \u003e 为不同的设备设置不同大小的图像。\n    \u003e 使用srcset和picture为每个图像提供多种变体（variants）。\n\n     * 📖 [Responsive images - Learn web development | MDN](https://developer.mozilla.org/en-US/docs/Learn/HTML/Multimedia_and_embedding/Responsive_images)\n\n**[⬆ 返回顶部](#table-of-contents)**\n\n## JavaScript\n\n![javascript]\n\n- [ ] **JS 压缩:** ![high] 所有JavaScript文件都要被压缩，生产环境中删除注释、空格和空行（在HTTP/2仍然有效果）。\n\n    *为什么：*\n    \u003e 删除所有不必要的空格、注释和空行将减少JavaScript文件的大小，并加快网站的页面加载时间，提升用户体验。\n\n    *怎么做：*\n    \u003e 建议使用下面的工具在构建或部署之前自动缩小文件。\n\n    * 📖 [uglify-js - npm](https://www.npmjs.com/package/uglify-js)\n    * 🛠 [Online JavaScript Compressor](http://refresh-sf.com)\n    * 📖 [Short read: How is HTTP/2 different? Should we still minify and concatenate?](https://scaleyourcode.com/blog/article/28)\n\n* [ ] **不内嵌JavaScript:** ![medium] *(仅对网站有效)* 避免在`body`中间嵌入多个JavaScript代码，将JavaScript代码重新集中到外部文件中，放在\u003chead\u003e或页面末尾（\u003c/body\u003e之前）。\n\n    *为什么：*\n    \u003e 将JavaScript嵌入代码直接放在\u003cbody\u003e中可能会降低页面速度，因为它在构建DOM时会加载。最好的选择是使用`async` 或 `defer`的外部文件来避免阻塞DOM渲染。另一种选择是在\u003chead\u003e中放置一些脚本。大多数时候是需要在DOM进入主处理之前加载的分析代码或小脚本。\n\n    *怎么做：*\n    \u003e 确保使用async或defer加载所有script文件，并准确地在\u003chead\u003e中加载代码。\n    \n     * 📖 [优化JavaScript并提高网站加载速度的11个技巧](https://www.upwork.com/hiring/development/11-tips-to-optimize-javascript-and-improve-website-loading-speeds/)\n\n* [ ] **非阻塞JavaScript：** ![high] 使用defer属性或使用async来异步加载JavaScript文件。\n\n    ```html\n    \u003c!-- Defer Attribute --\u003e\n    \u003cscript defer src=\"foo.js\"\u003e\n\n    \u003c!-- Async Attribute --\u003e\n    \u003cscript async src=\"foo.js\"\u003e\n    ```\n\n    *为什么：*\n    \u003e JavaScript阻止HTML文档的正常解析，因此当解析器到达\u003cscript\u003e标记时（特别是在\u003chead\u003e内），它会停止解析并且执行脚本。如果您的脚本位于页面顶部，则强烈建议添加`async`和`defer`，但如果在\u003c/body\u003e标记之前加载，没有太大影响。但是，使用这些属性来避免性能问题是一种很好的做法。\n\n    *怎么做：*\n    \u003e 添加`async`（如果脚本不依赖于其他脚本）或`defer`（如果脚本依赖或依赖于异步脚本）作为script脚本标记的属性。\n    \u003e 如果有小脚本，可以在异步脚本上方使用内联脚本。\n\n    * 📖 [Remove Render-Blocking JavaScript](https://developers.google.com/speed/docs/insights/BlockingJS)\n    * 📖 [Defer loading JavaScript](https://varvy.com/pagespeed/defer-loading-javascript.html)\n\n* [ ] **优化和更新的JS库：** ![medium] 项目中使用的所有JavaScript库都是有用到的 (推荐使用原生JS的简单功能)并更新到最新版本\n\n    *为什么：*\n    \u003e 大多数情况下，新版本都带有优化和安全性修复，所以应该使用最优化的代码来优化项目。确保不存在过时插件。\n\n    *怎么做：*\n    \u003e 如果项目使用NPM管理依赖包，[npm-check](https://www.npmjs.com/package/npm-check)是一个非常有用的库来升级/更新你的库。\n\n    * 📖 [You may not need jQuery](http://youmightnotneedjquery.com/)\n    * 📖 [Vanilla JavaScript for building powerful web applications](https://plainjs.com/)\n\n- [ ] **检查依赖项大小限制：** ![low] 确保使用最优的外部库，大多数情况下，可以使用更轻的库来实现相同的功能。\n\n    *为什么：*\n    \u003e 你可能想使用npm中745 000个包中的一个，但你需要选择最适合项目需求的包。例如，MomentJS是一个很棒的库，但是你可能永远不会使用其中的很多方法，这就是为什么创建Day.js的原因。瞬间大小从16.4kB到2kB。\n\n\n    *怎么做：*\n    \u003e 始终比较并选择最适合您需求的轻型库。您还可以使用[npm trends](http://www.npmtrends.com/)等工具来比较NPM包下载次数或[Bundlephobia](https://bundlephobia.com/)以了解依赖项的大小。\n    \n    * 🛠 [ai/size-limit: Prevent JS libraries bloat. If you accidentally add a massive dependency, Size Limit will throw an error.](https://github.com/ai/size-limit)\n    * 📖 [webpack-bundle-analyzer - npm](https://www.npmjs.com/package/webpack-bundle-analyzer)\n    * 📖 [Size Limit: Make the Web lighter — Martian Chronicles, Evil Martians’ team blog](https://evilmartians.com/chronicles/size-limit-make-the-web-lighter)\n\n- [ ] **JavaScript 分析:** ![medium] 检查JavaScript文件（以及CSS）中的性能问题。\n\n    *为什么：*\n    \u003e JavaScript复杂性可能会降低运行时性能。识别这些可能的问题对提供流畅的用户体验来说至关重要。\n\n    *怎么做：*\n    \u003e 使用Chrome开发者工具中的时间轴工具来评估脚本事件，并找到可能需要花费太多时间的事件。\n\n    * 📖 [Speed Up JavaScript Execution  |  Tools for Web Developers  |  Google Developers](https://developers.google.com/web/tools/chrome-devtools/rendering-tools/js-execution)\n    * 📖 [JavaScript Profiling With The Chrome Developer Tools — Smashing Magazine](https://www.smashingmagazine.com/2012/06/javascript-profiling-chrome-developer-tools/)\n    * 📖 [How to Record Heap Snapshots  |  Tools for Web Developers  |  Google Developers](https://developers.google.com/web/tools/chrome-devtools/memory-problems/heap-snapshots)\n    * 📖 [Chapter 22 - Profiling the Frontend - Blackfire](https://blackfire.io/docs/book/22-frontend-profiling)\n    * 📖 [30 Tips To Improve Javascript Performance](http://www.monitis.com/blog/30-tips-to-improve-javascript-performance/)\n\n\n- [ ] **Use of Service Workers:** ![medium] You are using Service Workers in your PWA to cache datas or execute possible heavy tasks without impacting the user experience of your application. \n    \n    * 📖 [Service Workers: an Introduction  |  Web Fundamentals  |  Google Developers](https://developers.google.com/web/fundamentals/primers/service-workers/)\n    * 📖 [Measuring the Real-world Performance Impact of Service Workers  |  Web  |  Google Developers](https://developers.google.com/web/showcase/2016/service-worker-perf)\n    * 📖 [What Are Service Workers and How They Help Improve Performance](https://www.keycdn.com/blog/service-workers/)\n    * 📖 [How does a service worker work? - YouTube](https://www.youtube.com/watch?v=__xAtWgfzvc)\n\n\n - [ ] **使用 tree shaking 技术减少 js 大小:** ![high] 通过构建工具分析 JavaScript 代码并移除生产环境中用不到的 js 模块或方法\n\n    * 📖 [\nReduce JavaScript Payloads with Tree Shaking](https://developers.google.com/web/fundamentals/performance/optimizing-javascript/tree-shaking/)\n\n- [ ] **使用 code splitting 分包加载 js:** ![high] 通过分包加载，减少首次加载所需时间\n    \n    *怎么做：*\n    \u003e * **Vendor splitting** 根据库文件拆分模块，例如 React 或 lodash 单独打包成一个文件\n    \u003e * **Entry point splitting** 根据入口拆分模块，例如通过多页应用入口或者单页应用路由进行拆分\n    \u003e * **Dynamic splitting** 根据动态加载拆分模块，使用动态加载语法 ```import()``` ，实现模块按需加载\n\n    * 📖 [Reduce JavaScript Payloads with Tree Shaking](https://developers.google.com/web/fundamentals/performance/optimizing-javascript/code-splitting/)   \n\n**[⬆ 返回顶部](#table-of-contents)**\n\n## Server\n\n![server-side]\n\n- [ ] **网站使用HTTPS:** ![high] \n\n    *Why:*\n    \u003e HTTPS不仅适用于电子商务网站，也适用于所有存在数据传递的网站。如今的现代浏览器对于不安全的网站在许多功能上做了些限制。 例如：如果网站未使用HTTPS，则地理定位，推送通知和服务工作程序等功能会不起作用。今天设置和使用SSL证书比以前容易得多([Let's Encrypt](https://letsencrypt.org/)能提供免费的https服务).\n\n    * 📖 [Why Use HTTPS? | Cloudflare](https://www.cloudflare.com/learning/security/why-use-https/)\n    * 📖 [Enabling HTTPS Without Sacrificing Your Web Performance - Moz](https://moz.com/blog/enabling-https-without-sacrificing-web-performance)\n    * 📖 [How HTTPS Affects Website Performance](https://wp-rocket.me/blog/https-affects-website-performance/)\n    * 📖 [HTTP versus HTTPS versus HTTP2 - The real story | Tune The Web](https://www.tunetheweb.com/blog/http-versus-https-versus-http2/)\n    * 📖 [HTTP vs HTTPS — Test them both yourself](https://www.httpvshttps.com/)\n\n- [ ] **页面大小 \u003c 1500 KB(理想 \u003c 500 KB):** ![high] (理想情况 \u003c 500 KB) 尽可能减少页面和资源的大小。\n\n    *为什么：*\n    \u003e 理想情况下，应该尝试让页面大小\u003c500 KB，但Web页面大小中位数大约为1500 KB（即使在移动设备上）。根据你的目标用户、连接速度、设备，尽可能减少页面大小以尽可能获得最佳用户体验非常重要。\n\n    *怎么做：*\n    \u003e 前端性能清单中的所有规则将帮助你尽可能地减少资源和代码。\n\n    * 📖 [Page Weight](https://httparchive.org/reports/page-weight#bytesTotal)\n    * 🛠 [What Does My Site Cost?](https://whatdoesmysitecost.com/)\n\n- [ ] **页面加载时间 \u003c 3秒：** ![high] 尽可能减少页面加载时间，以便快速将内容传递给用户。\n\n    *为什么：*\n    \u003e 网站或应用程序速度越快，反弹增加的可能性越小，换句话说，失去用户或未来客户的机会就越少。Google对该主题的充分研究证明了这一点。\n    \n    *怎么做：*\n    \u003e  使用[Page Speed Insight](https://developers.google.com/speed/pagespeed/insights/)或[WebPageTest](https://www.webpagetest.org/)等在线工具分析可能会降低速度的工具，并使用前端性能清单来缩短加载时间。\n\n    * 🛠 [Compare your mobile site speed](https://www.thinkwithgoogle.com/feature/mobile/)\n    * 🛠 [Test Your Mobile Website Speed and Performance - Think With Google](https://testmysite.thinkwithgoogle.com/?_ga=1.155316027.1489996091.1482187369)\n    * 📖 [Average Page Load Times for 2018 - How does yours compare? - MachMetrics Speed Blog](https://www.machmetrics.com/speed-blog/average-page-load-times-websites-2018/)\n\n- [ ] **TTFB \u003c 1.3 seconds:** ![high] 尽可能减少浏览器在接收数据之前等待的时间。\n\n    * 📖 [什么是DevTools中的TTFB，以及如何处理它](https://scaleyourcode.com/blog/article/27)\n    * 📖 [Monitoring your servers with free tools is easy](https://scaleyourcode.com/blog/article/7)\n    * 📖 [Time to First Byte (TTFB)](https://varvy.com/pagespeed/ttfb.html)\n    * 🛠 [Global latency testing tool](https://latency.apex.sh)\n\n* [ ] **Cookie 大小:** ![medium] 如果您使用cookie，请确保每个cookie不超过4096字节，并且一个域名下不超过20个cookie。\n\n    *为什么：*\n    \u003e cookie存在于HTTP头中，在Web服务器和浏览器之间交换。保持cookie的大小尽可能低是非常重要的，以尽量减少对用户响应时间的影响。\n\n    *怎么做：*\n    \u003e 消除不必要的cookie\n    \n    * 📖 [Cookie specification: RFC 6265](https://tools.ietf.org/html/rfc6265)\n    * 📖 [Cookies](https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies)\n    * 🛠 [Browser Cookie Limits](http://browsercookielimits.squawky.net/)\n    * 📖 [Website Performance: Cookies Don't Taste So Good - Monitis Blog](http://www.monitis.com/blog/website-performance-cookies-dont-taste-so-good/)\n    * 📖 [Google's Web Performance Best Practices #3: Minimize Request Overhead - GlobalDots Blog](https://www.globaldots.com/googles-web-performance-best-practices-3-minimize-request-overhead/)\n\n- [ ] **最小化HTTP请求：** ![high] 始终确保所请求的每个文件对网站或应用程序至关重要，尽可能减少http请求。\n\n * 📖 [Combine external CSS](https://varvy.com/pagespeed/combine-external-css.html)\n * 📖 [Combine external JavaScript](https://varvy.com/pagespeed/combine-external-javascript.html)\n\n- [ ] **使用CDN提供静态文件：** ![medium] 使用CDN可以更快地在全球范围内获取到你的静态文件。\n\n * 📖 [10 Tips to Optimize CDN Performance - CDN Planet](https://www.cdnplanet.com/blog/10-tips-optimize-cdn-performance/)\n * 📖 [HTTP Caching  |  Web Fundamentals  |  Google Developers](https://developers.google.com/web/fundamentals/performance/optimizing-content-efficiency/http-caching)\n\n- [ ] **提供来自相同协议的文件：** ![high] 避免网站使用HTTPS同时使用HTTP来提供相同源地址的文件。\n\n- [ ] **提供可访问的文件：** ![high] 避免请求无法访问的文件（404）。\n\n- [ ] **正确设置HTTP缓存标头：** ![high] 合理设置HTTP缓存标头来减少http请求次数。\n\n- [ ] **启用GZIP压缩** ![high]使用压缩方法（如Gzip或Brotli）来减小JavaScript文件的大小。使用较小尺寸的文件，用户可以更快地下载资源，从而提高性能。\n\n * 📖 [Check GZIP compression](https://checkgzipcompression.com/)\n * 🛠 [Check Brotli Compression](https://tools.keycdn.com/brotli-test)\n * 📖 [Can I use... Brotli](https://caniuse.com/#feat=brotli)\n\n - [ ] **分域存放资源：** ![medium] 由于浏览器同一域名并行下载数有限，利用多域名主机存放静态资源，增加并行下载数，缩短资源加载时间\n\n - [ ] **减少页面重定向** ![high] \n\n**[⬆ 返回顶部](#table-of-contents)**\n\n---\n## 性能与前端框架\n\n### Angular\n * 📖 [Angular Performance Checklist](https://github.com/mgechev/angular-performance-checklist)\n\n### React\n\n * 📖 [Optimizing Performance - React](https://reactjs.org/docs/optimizing-performance.html)\n * 📖 [React image manipulation | Cloudinary](https://cloudinary.com/documentation/react_image_manipulation)\n * 📖 [Debugging React performance with React 16 and Chrome Devtools.](https://building.calibreapp.com/debugging-react-performance-with-react-16-and-chrome-devtools-c90698a522ad)\n\n### Vue\n\n### WordPress\n\n* 🛠 [Test Your Website Speed | WordPress Hosting by @WPEngine](https://wpengine.com/speed-tool/)\n\n#### 文章\n\n * 📖 [19 Tips to Speed Up WordPress Performance (Updated)](https://www.wpbeginner.com/wordpress-performance-speed/)\n * 📖 [Speed Up Your WordPress - How to Save Images Optimized for Web](https://www.wpbeginner.com/beginners-guide/speed-wordpress-save-images-optimized-web/)\n\n#### 插件推荐\n\n* 🛠 [Caching Plugin for WordPress - Speed up your website with WP Rocket](https://wp-rocket.me/)\n* 🛠 [WP-Sweep | WordPress.org](https://wordpress.org/plugins/wp-sweep/)\n* 🛠 [Imagify Image Optimizer | WordPress.org](https://wordpress.org/plugins/imagify/)\n\n---\n\n## Translations\n\nThe Front-End Performance Checklist wants to also be available in other languages! Don't hesitate to submit your contribution!\n\n* 🇵🇹 Portuguese: [fernandofawkes/Front-End-Performance-Checklist](https://github.com/fernandofawkes/Front-End-Performance-Checklist)\n* 🇨🇳 Chinese: [JohnsenZhou/Front-End-Performance-Checklist](https://github.com/JohnsenZhou/Front-End-Performance-Checklist)\n* 🇷🇺 Russian: [lex111/Front-End-Performance-Checklist](https://github.com/lex111/Front-End-Performance-Checklist)\n* 🇫🇷 French: [WilliamDASILVA/Front-End-Performance-Checklist](https://github.com/WilliamDASILVA/Front-End-Performance-Checklist)\n* 🇰🇷 Korean: [ParkSB/Front-End-Performance-Checklist](https://github.com/ParkSB/Front-End-Performance-Checklist)\n* 🇪🇸 Spanish: [dagerzuga/Front-End-Performance-Checklist](https://github.com/dagerzuga/Front-End-Performance-Checklist)\n* 🇻🇮 Vietnamese : [huynhan147/Front-End-Performance-Checklist](https://github.com/huynhan147/FrontEnd-Performance-Checklist)\n\n## Contributing\n\n**Open an issue or a pull request to suggest changes or additions.**\n\n## Support\n如果有什么问题和疑问，请通过以下途径联系:\n\n* [Chat on Gitter](https://gitter.im/Front-End-Checklist/Lobby?utm_source=share-link\u0026utm_medium=link\u0026utm_campaign=share-link)\n* [Facebook](https://www.facebook.com/frontendchecklist/)\n* [Twitter](https://twitter.com/thedaviddias)\n\n## Author\n\n**Build with ❤️ by [David Dias](https://github.com/thedaviddias) at [@influitive](https://influitive.com/) 🇨🇦**\n\n## Contributors\n\n感谢各位参与本项目的人员所作出的贡献。 [[Contribute]](.github/CONTRIBUTING.md).\n\u003ca href=\"https://github.com/thedaviddias/Front-End-Performance-Checklist/graphs/contributors\"\u003e\n    \u003cimg src=\"https://opencollective.com/front-end-checklist/contributors.svg?width=890\" /\u003e\n\u003c/a\u003e\n\n## Backers\n\nThank you to all our backers! 🙏 [[Become a backer](https://opencollective.com/front-end-checklist#backer)]\n\n\u003ca href=\"https://opencollective.com/front-end-checklist#backers\" target=\"_blank\"\u003e\u003cimg src=\"https://opencollective.com/front-end-checklist/backers.svg?width=890\"\u003e\u003c/a\u003e\n\n\n## Sponsors\n\nSupport this project by becoming a sponsor. Your logo will show up here with a link to your website. [[Become a sponsor](https://opencollective.com/front-end-checklist#sponsor)]\n\n\u003ca href=\"https://opencollective.com/front-end-checklist/sponsor/0/website\" target=\"_blank\"\u003e\u003cimg src=\"https://opencollective.com/front-end-checklist/sponsor/0/avatar.svg\"\u003e\u003c/a\u003e\n\u003ca href=\"https://opencollective.com/front-end-checklist/sponsor/1/website\" target=\"_blank\"\u003e\u003cimg src=\"https://opencollective.com/front-end-checklist/sponsor/1/avatar.svg\"\u003e\u003c/a\u003e\n\u003ca href=\"https://opencollective.com/front-end-checklist/sponsor/2/website\" target=\"_blank\"\u003e\u003cimg src=\"https://opencollective.com/front-end-checklist/sponsor/2/avatar.svg\"\u003e\u003c/a\u003e\n\u003ca href=\"https://opencollective.com/front-end-checklist/sponsor/3/website\" target=\"_blank\"\u003e\u003cimg src=\"https://opencollective.com/front-end-checklist/sponsor/3/avatar.svg\"\u003e\u003c/a\u003e\n\u003ca href=\"https://opencollective.com/front-end-checklist/sponsor/4/website\" target=\"_blank\"\u003e\u003cimg src=\"https://opencollective.com/front-end-checklist/sponsor/4/avatar.svg\"\u003e\u003c/a\u003e\n\u003ca href=\"https://opencollective.com/front-end-checklist/sponsor/5/website\" target=\"_blank\"\u003e\u003cimg src=\"https://opencollective.com/front-end-checklist/sponsor/5/avatar.svg\"\u003e\u003c/a\u003e\n\u003ca href=\"https://opencollective.com/front-end-checklist/sponsor/6/website\" target=\"_blank\"\u003e\u003cimg src=\"https://opencollective.com/front-end-checklist/sponsor/6/avatar.svg\"\u003e\u003c/a\u003e\n\u003ca href=\"https://opencollective.com/front-end-checklist/sponsor/7/website\" target=\"_blank\"\u003e\u003cimg src=\"https://opencollective.com/front-end-checklist/sponsor/7/avatar.svg\"\u003e\u003c/a\u003e\n\u003ca href=\"https://opencollective.com/front-end-checklist/sponsor/8/website\" target=\"_blank\"\u003e\u003cimg src=\"https://opencollective.com/front-end-checklist/sponsor/8/avatar.svg\"\u003e\u003c/a\u003e\n\u003ca href=\"https://opencollective.com/front-end-checklist/sponsor/9/website\" target=\"_blank\"\u003e\u003cimg src=\"https://opencollective.com/front-end-checklist/sponsor/9/avatar.svg\"\u003e\u003c/a\u003e\n\n## License\n\n[MIT](LICENCE.md)\n\nAll icons are provided by [Icons8](https://icons8.com/)\n\n**[⬆ 返回顶部](#table-of-contents)**\n\n[logo]: images/logo-front-end-performance-checklist.jpg\n[html]: images/html.png\n[css]: images/css.png\n[fonts]: images/fonts.png\n[images]: images/images.png\n[javascript]: images/javascript.png\n[server-side]: images/server-side.png\n\n[low]: https://front-end-checklist.now.sh/low.svg\n[medium]: https://front-end-checklist.now.sh/medium.svg\n[high]: https://front-end-checklist.now.sh/high.svg\n\n\n","funding_links":["https://opencollective.com/front-end-checklist"],"categories":["Translations","Others"],"sub_categories":["WordPress"],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2FJohnsenZhou%2FFront-End-Performance-Checklist","html_url":"https://awesome.ecosyste.ms/projects/github.com%2FJohnsenZhou%2FFront-End-Performance-Checklist","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2FJohnsenZhou%2FFront-End-Performance-Checklist/lists"}