[{"data":1,"prerenderedAt":417},["ShallowReactive",2],{"tool-site-audit-yellow-lab-tools":3,"footer-total":389,"related-site-audit-yellow-lab-tools":390},{"id":4,"title":5,"author":6,"bestFor":7,"body":8,"category":348,"cons":349,"cover":355,"date":356,"description":357,"draft":358,"extension":359,"meta":360,"navigation":361,"notFor":362,"path":363,"pricing":364,"pros":366,"region":372,"score":373,"scoreBreakdown":374,"seo":380,"stem":381,"tags":382,"toolName":216,"updated":356,"url":387,"vendor":216,"__hash__":388},"tools\u002Ftools\u002Fsite-audit\u002Fyellow-lab-tools.md","Yellow Lab Tools 评测","元析评测","前端工程师在自己机器上快速定位 JS 与 DOM 层面的性能问题,尤其是老站点或 jQuery 遗留项目",{"type":9,"value":10,"toc":320},"minimark",[11,15,23,26,29,45,48,53,56,59,63,66,69,73,76,79,83,86,89,92,95,99,102,106,109,113,116,120,123,127,130,133,199,202,205,277,283,287,291,294,298,301,305,308,311,314],[12,13,14],"h2",{"id":14},"结论先行",[16,17,18,22],"p",{},[19,20,21],"strong",{},"推荐,总分 7.4,完全免费且开源,适合前端工程师自查 JS 执行与 DOM 结构层面的瓶颈——特别是接手 jQuery 老项目的时候。"," 它会把耗时最长的函数按调用栈列出来,省掉自己开 Performance 面板录一遍再找火焰图的步骤。",[16,24,25],{},"它不是给管理层看的工具。没有真实用户数据,没有历史趋势,测点也只有一台机器,你无法用它证明\"我们的 Core Web Vitals 达标了\"。把它放在工程师的日常工具箱里,价值才成立。",[12,27,28],{"id":28},"这篇评测基于什么数据",[30,31,32,36,39,42],"ul",{},[33,34,35],"li",{},"工具本体:2026-11 在 yellowlab.tools 网页版上对几个不同类型站点跑过测试,记录指标分组与报告结构。",[33,37,38],{},"开源仓库:查阅项目在 GitHub 的说明与部署文档,确认可用 Docker 自托管,以及可配置的测点与超时参数。",[33,40,41],{},"横向参照:与 Lighthouse、Sitespeed.io 的公开能力表比对,重点看指标口径与可扩展性。",[33,43,44],{},"实测边界:未做多轮统计与跨工具并跑,关于测点单一与更新放缓的判断来自公开仓库动态与工具页面说明。",[12,46,47],{"id":47},"核心功能",[49,50,52],"h3",{"id":51},"函数级-javascript-耗时","函数级 JavaScript 耗时",[16,54,55],{},"报告里最有用的一块是 JS 执行分析:通过采 CPU 采样,把耗时最长的函数按累计时间排序,并标出它所在的文件与行号。一个页面总脚本耗时 2.3 秒时,通常前三个函数就占了七成。",[16,57,58],{},"对第三方脚本多的站点,先按域名过滤,确认是自己的代码问题还是外部标签问题,再决定找谁改。这块能直接指出是埋点 SDK、广告脚本还是自家的组件库在拖时间。看完基本能决定\"删掉、延后加载还是改写\"。",[49,60,62],{"id":61},"jquery-与坏做法检查","jQuery 与坏做法检查",[16,64,65],{},"它会检测页面是否引入 jQuery、版本是多少、用了多少选择器,并对低效写法给出提示。很多老项目一次加载整个 jQuery 只为用几个 DOM 方法,这项检查能让团队下决心换掉。",[16,67,68],{},"坏做法一栏列的是硬伤:document.write、同步 XMLHttpRequest、重复加载同一库、内联脚本阻塞解析。每一条都指向具体文件,改起来不需要猜。",[49,70,72],{"id":71},"dom-与-css-复杂度","DOM 与 CSS 复杂度",[16,74,75],{},"DOM 栏统计节点总数、最大深度、以及节点最多的标签。节点数过万、深度超过二十层时,样式重算和布局的代价会明显上升,移动端尤其明显。",[16,77,78],{},"CSS 栏统计选择器数量与平均复杂度,并标出过长的选择器链。这一项常被忽略,改版时也最容易带进新问题,但老站点里\"三层后代选择器加属性选择器\"的写法很常见,累积起来会拖慢首屏渲染。",[49,80,82],{"id":81},"图片字体与服务器配置","图片、字体与服务器配置",[16,84,85],{},"图片栏列出体积最大与尺寸不匹配的资源,标出可以压缩或换格式的项。字体栏检查是否加载了过多字重与字符集。",[16,87,88],{},"报告底部还有一个总览,适合先扫一眼再决定细看哪一块:页面请求数、总传输量、首屏时间与 DOM 就绪时间。这四项能把到底慢在哪一层先归个类,省掉反复试错——请求数多说明资源碎,传输量大说明没压缩或图片没处理,首屏时间远早于 DOM 就绪说明脚本在拖。",[16,90,91],{},"服务器配置栏看的是压缩是否开启、缓存头是否合理、有没有多余的重定向跳转。这几项改起来成本最低,收益往往也最直接。",[12,93,94],{"id":94},"评分明细",[49,96,98],{"id":97},"功能完整度7210","功能完整度:7.2\u002F10",[16,100,101],{},"前端层面的检查做得很细,函数级耗时是差异化能力。扣分在没有字段数据、没有瀑布图、没有批量与历史,站点级与技术 SEO 层面的问题一概不覆盖。",[49,103,105],{"id":104},"易用性8410","易用性:8.4\u002F10",[16,107,108],{},"输入网址点运行,等二十秒左右出报告,指标分组清楚。要自托管的话,一条 Docker 命令就能起服务,配置项不多。",[49,110,112],{"id":111},"数据质量8010","数据质量:8.0\u002F10",[16,114,115],{},"函数耗时与 DOM 统计的数据可信,重复跑结果接近。短板在测点单一,网络耗时不代表目标市场;采样精度也受页面脚本量影响,超大页面可能截断。",[49,117,119],{"id":118},"性价比9410","性价比:9.4\u002F10",[16,121,122],{},"开源免费,不限次数,能自托管,这几项加起来几乎无可挑剔。扣分只在于免费也意味着没有服务承诺与更新保障。",[49,124,126],{"id":125},"客户支持5410","客户支持:5.4\u002F10",[16,128,129],{},"没有商业支持,只能提 Issue 或看文档。仓库的 Issue 响应看维护者时间,前沿框架的兼容问题可能长期没人处理。",[12,131,132],{"id":132},"定价说明",[134,135,136,152],"table",{},[137,138,139],"thead",{},[140,141,142,146,149],"tr",{},[143,144,145],"th",{},"项目",[143,147,148],{},"价格",[143,150,151],{},"说明",[153,154,155,167,177,188],"tbody",{},[140,156,157,161,164],{},[158,159,160],"td",{},"网页版",[158,162,163],{},"免费",[158,165,166],{},"无需注册,无次数限制",[140,168,169,172,174],{},[158,170,171],{},"自托管",[158,173,163],{},[158,175,176],{},"Docker 部署,需自备服务器",[140,178,179,182,185],{},[158,180,181],{},"商用授权",[158,183,184],{},"开源许可",[158,186,187],{},"按项目许可证使用,无付费档",[140,189,190,193,196],{},[158,191,192],{},"技术支持",[158,194,195],{},"无",[158,197,198],{},"社区 Issue,无 SLA",[16,200,201],{},"没有付费入口,也没有额度概念。代价是项目由个人维护,更新频率取决于维护者的时间。作为内部工具链的一环,建议把关键报告截图存档,不要指望它长期提供历史数据。",[12,203,204],{"id":204},"和竞品对比",[134,206,207,223],{},[137,208,209],{},[140,210,211,214,217,220],{},[143,212,213],{},"维度",[143,215,216],{},"Yellow Lab Tools",[143,218,219],{},"Lighthouse",[143,221,222],{},"Sitespeed.io",[153,224,225,236,250,263],{},[140,226,227,229,231,233],{},[158,228,148],{},[158,230,163],{},[158,232,163],{},[158,234,235],{},"开源免费,云服务付费",[140,237,238,241,244,247],{},[158,239,240],{},"函数级耗时",[158,242,243],{},"有,按调用栈排序",[158,245,246],{},"无,只看总分与建议",[158,248,249],{},"有,可自定义指标",[140,251,252,255,257,260],{},[158,253,254],{},"批量与历史",[158,256,195],{},[158,258,259],{},"可脚本化但无存储",[158,261,262],{},"有,可写 Graphite 等时序库",[140,264,265,268,271,274],{},[158,266,267],{},"短板",[158,269,270],{},"单页、更新放缓",[158,272,273],{},"无 DOM 与 jQuery 细节",[158,275,276],{},"部署与配置偏重",[16,278,279,282],{},[19,280,281],{},"怎么选",":手头有个老站点想快速找出 JS 拖累点,选 Yellow Lab Tools;要接进 CI 做发布门禁,选 Lighthouse;要长期采集几百个页面的指标并画趋势图,选 Sitespeed.io。",[12,284,286],{"id":285},"faq","FAQ",[49,288,290],{"id":289},"q-这个项目还在维护吗能放心用","Q: 这个项目还在维护吗,能放心用?",[16,292,293],{},"A: 仓库仍在,但提交频率明显低于几年前,对新框架的适配不算及时。作为一次性排查工具可以放心用;要放进长期流程,建议同时准备 Lighthouse 作为替代,避免哪天网页版打不开。",[49,295,297],{"id":296},"q-报告里函数耗时-800-毫秒具体指哪个函数","Q: 报告里\"函数耗时 800 毫秒\"具体指哪个函数?",[16,299,300],{},"A: 指 CPU 采样里累计占用时间最长的那个函数,报告会给出文件名、行号和调用栈。它统计的是自身执行加子调用,所以越靠栈底的函数数字越大,看的时候要结合层级。",[49,302,304],{"id":303},"q-能部署到公司内网测内部系统吗","Q: 能部署到公司内网测内部系统吗?",[16,306,307],{},"A: 能,用 Docker 起一个实例,配置目标地址与回调即可。注意内网系统如果依赖登录,需要在配置里带上 cookie,否则测到的是登录页。",[12,309,310],{"id":310},"评测方法说明",[16,312,313],{},"元析评测围绕功能完整度、易用性、数据质量、性价比、客户支持五个维度打分,每项满分 10 分,五项均值折算总分。文中功能与部署方式于 2026-11 对照工具网页与开源仓库文档核实;未做多轮统计实测,测点与更新节奏的判断来自公开信息。开源项目的功能可能随版本变化,以仓库说明为准。",[16,315,316,319],{},[19,317,318],{},"最后更新",":2026-11-16",{"title":321,"searchDepth":322,"depth":322,"links":323},"",2,[324,325,326,333,340,341,342,347],{"id":14,"depth":322,"text":14},{"id":28,"depth":322,"text":28},{"id":47,"depth":322,"text":47,"children":327},[328,330,331,332],{"id":51,"depth":329,"text":52},3,{"id":61,"depth":329,"text":62},{"id":71,"depth":329,"text":72},{"id":81,"depth":329,"text":82},{"id":94,"depth":322,"text":94,"children":334},[335,336,337,338,339],{"id":97,"depth":329,"text":98},{"id":104,"depth":329,"text":105},{"id":111,"depth":329,"text":112},{"id":118,"depth":329,"text":119},{"id":125,"depth":329,"text":126},{"id":132,"depth":322,"text":132},{"id":204,"depth":322,"text":204},{"id":285,"depth":322,"text":286,"children":343},[344,345,346],{"id":289,"depth":329,"text":290},{"id":296,"depth":329,"text":297},{"id":303,"depth":329,"text":304},{"id":310,"depth":322,"text":310},"site-audit",[350,351,352,353,354],"只有实验室数据,没有真实用户指标,也没有 Core Web Vitals 字段数据可对照","一次测一个 URL,没有批量与历史,报告不留档,关掉就没了","测点只有一台机器,国内站点测出来的网络耗时参考价值有限","项目更新节奏明显放缓,对最新框架与新版 Chrome 的适配不如商业工具及时","界面英文与法文混排,部分指标说明只有一句话,没有客服可问",null,"2026-11-16","Yellow Lab Tools 评测:开源免费,除加载时间还给出函数级 JS 耗时、jQuery 用量和 DOM 复杂度,前端自查瓶颈很快;没有真实用户数据,项目更新节奏已放缓。",false,"md",{},true,"需要向老板汇报 Core Web Vitals 达标率、或需要持续监控几十个页面的团队","\u002Ftools\u002Fsite-audit\u002Fyellow-lab-tools",{"free":361,"startingPrice":321,"currency":163,"billingPeriod":163,"notes":365},"开源项目,网页版免费使用且无需注册,无查询次数限制;也可用 Docker 自行部署到内网。官网未列出任何付费档位,2026-11 核对。",[367,368,369,370,371],"把 JavaScript 执行时间拆到函数级,直接列出最耗时的调用栈,不必自己录 Performance 面板","指标分组围绕前端问题组织:jQuery 用量、DOM 节点数与深度、CSS 选择器复杂度、图片体积","能识别 document.write、同步 XHR、内联大段脚本这类坏做法,并指出具体出现在哪个文件","开源可自托管,用 Docker 一条命令起服务,内网系统也能出同样报告","免费且不限次数,做改版前后对比可以反复跑,不用算额度","global",7.4,{"features":375,"ease":376,"data":377,"price":378,"support":379},7.2,8.4,8,9.4,5.4,{"title":5,"description":357},"tools\u002Fsite-audit\u002Fyellow-lab-tools",[383,384,385,386],"站点审计工具","开源工具","YellowLabTools","前端性能","https:\u002F\u002Fyellowlab.tools\u002F","Lz_Mc5jq-5awNgVhyd7X5bFVkzRC-4bEGZkZqjooPJQ",1016,[391,402,409],{"path":392,"toolName":393,"description":394,"score":395,"pricing":396,"vendor":401,"date":356,"category":348},"\u002Ftools\u002Fsite-audit\u002Fahrefs-site-audit","Ahrefs Site Audit","Ahrefs Site Audit 评测:Lite 套餐 $129\u002F月起,每周自动复爬并按影响排序问题,适合长期盯站的外贸与 SaaS 站;它只读 HTML 源码,前端渲染出的内容和字段级瀑布要另配工具。",8.6,{"free":358,"startingPrice":397,"currency":398,"billingPeriod":399,"notes":400},"129","USD","月","Site Audit 不单独售卖,含在 Ahrefs 订阅中:Lite $129\u002F月、Standard $249\u002F月、Advanced $449\u002F月,年付比月付便宜约两个月;Enterprise 需联系销售。新账号提供 7 天 $7 试用。价格于 2026-11 核对官网定价页。","Ahrefs",{"path":403,"toolName":404,"description":405,"score":376,"pricing":406,"vendor":408,"date":356,"category":348},"\u002Ftools\u002Fsite-audit\u002Fpagespeed-insights","PageSpeed Insights","PageSpeed Insights 评测:Google 官方、完全免费,一次给出实验室 Lighthouse 分和 28 天真实用户 CrUX 数据,适合对照 Core Web Vitals 排序整改;流量小的站没有字段数据。",{"free":361,"startingPrice":321,"currency":163,"billingPeriod":163,"notes":407},"网页版完全免费、无需登录、无查询次数限制。API v5 免费,官方配额为每天 25,000 次、每分钟 240 次,超出返回配额错误。官网未提供任何付费档位,2026-11 核对。","Google",{"path":410,"toolName":411,"description":412,"score":376,"pricing":413,"vendor":416,"date":356,"category":348},"\u002Ftools\u002Fsite-audit\u002Fsemrush-site-audit","Semrush Site Audit","Semrush Site Audit 评测:SEO 套餐 $139\u002F月起(年付约 $117),把 140 多项检查压成一个健康分,和关键词排名共用一个后台;月抓取页数按档位限额,大站容易顶到上限。",{"free":361,"startingPrice":414,"currency":398,"billingPeriod":399,"notes":415},"139","Site Audit 含在 SEO 套餐内:SEO $139\u002F月(年付折合 $117.33\u002F月),Starter $199\u002F月(年付 $165.17\u002F月),更高档位到 $549\u002F月;2026 年 5 月改过套餐结构,老版 Pro $139.95、Guru $249.95、Business $499.95 仍可在部分入口续订。免费账号可跑 100 页试点。价格于 2026-11 核对官网定价页。","Semrush",1794788243184]