性能权衡 - CSS效率，CSS文件大小，HTML文件大小
From my interpretation, google recommends targeting HTML elements via id performs better than targeting purely by hierachy, but when filesize is added into this equation, how do the priorities end up?
根据我的解释,谷歌建议通过id定位HTML元素比仅仅通过层次结构定位更好,但是当将文件大小添加到此等式中时,优先级如何最终?
Just to be clear, there are three factors here which I wish to discuss the trade-offs between.
需要明确的是,这里有三个因素我想讨论它们之间的权衡。
- CSS efficiency
- CSS filesize
- HTML filesize
1 个解决方案
#1
2
In general it is probably better to keep HTML filesize smaller, since HTML is mostly dynamic and difficult to cache.
通常,最好保持较小的HTML文件大小,因为HTML主要是动态的并且难以缓存。
CSS is often static and easily cacheable, so filesize is not so important, if you set your cache headers right. CSS selectors are probably most efficient if the selector expressions are not too complex. I believe id selectors are optimized in many browsers.
CSS通常是静态的并且可以轻松缓存,因此如果您正确设置缓存标头,则文件大小并不重要。如果选择器表达式不是太复杂,CSS选择器可能是最有效的。我相信id选择器在许多浏览器中都得到了优化。
If you want to keep your CSS efficient then use a simple visual layout, a few simple CSS selectors and use newer CSS effects minimally.
如果你想保持你的CSS效率,那么使用一个简单的可视化布局,一些简单的CSS选择器,并最低限度地使用较新的CSS效果。
Here is a good set of general best practices for HTML performance : http://developer.yahoo.com/performance/rules.html
以下是HTML性能的一组常用最佳实践:http://developer.yahoo.com/performance/rules.html
更多相关文章
- html文件上传到vss上面后文件大小改变
- Apache服务器压缩和利用浏览缓存问题
- PHPExcel导入导出及大量数据导入缓存方式的修改
- 解决Apache2+PHP上传文件大小限制的问题技术集锦
- 求助，Xdebug的配置，缓存问题。
- php 缓存output_buffering和ob_start
- Laravel尝试在根文件夹中存储缓存文件
- mysql如何修改导入数据库文件大小限制
- 获取项目列表的更好方法：缓存序列化数据与数据库查询或其他？