[{"data":1,"prerenderedAt":410},["ShallowReactive",2],{"tool-technical-seo-lighthouse":3,"footer-total":383,"related-technical-seo-lighthouse":384},{"id":4,"title":5,"author":6,"bestFor":7,"body":8,"category":339,"cons":340,"cover":346,"date":347,"description":348,"draft":349,"extension":350,"meta":351,"navigation":352,"notFor":353,"path":354,"pricing":355,"pros":360,"region":366,"score":367,"scoreBreakdown":368,"seo":374,"stem":375,"tags":376,"toolName":206,"updated":347,"url":380,"vendor":381,"__hash__":382},"tools\u002Ftools\u002Ftechnical-seo\u002Flighthouse.md","Lighthouse 评测","元析评测","有前端开发参与、需要在每次发布前对关键页面做性能与基础 SEO 自查的团队",{"type":9,"value":10,"toc":311},"minimark",[11,15,22,25,28,31,47,50,54,57,60,64,67,70,74,82,85,88,91,94,97,101,104,108,111,115,118,122,125,129,132,135,189,192,195,268,274,278,282,285,289,292,296,299,302,305],[12,13,14],"h2",{"id":14},"结论先行",[16,17,18],"p",{},[19,20,21],"strong",{},"推荐,总分 8.9,完全免费(0 元),适合有前端开发、要在每次发布前给关键页面做性能与基础 SEO 自查的团队。",[16,23,24],{},"Lighthouse 是 Chrome 团队维护的开源审计工具,装在浏览器里、跑在命令行里、也能挂进 CI。它打开一个页面,用固定网络与 CPU 条件加载一遍,输出五个维度的分数和一份逐条可执行的改进清单。对开发来说,它的价值不在分数本身,而在\"哪一行代码让 LCP 多了 800 毫秒\"这种可落地的定位。",[16,26,27],{},"把它当成体检而不是诊断:它告诉你这一页现在的状态,不告诉你全站有多少页有同样的问题,也不代表真实用户看到的体验。SEO 那一项拿到 100 分,和页面能不能被收录是两件事。",[12,29,30],{"id":30},"这篇评测基于什么数据",[32,33,34,38,41,44],"ul",{},[35,36,37],"li",{},"官方文档,2026-11 核对:Lighthouse 以 Apache 2.0 许可开源,提供 DevTools 面板、Node CLI、Node API 与 Lighthouse CI 四种用法,PageSpeed Insights 后台用的也是同一套引擎。",[35,39,40],{},"评分口径:性能分由 FCP、SI、LCP、TBT、CLS 五项加权,权重分别为 10%、10%、25%、30%、25%,其余类别按通过项占比折算。",[35,42,43],{},"SEO 类别检查项:文档标题、meta 描述、可抓取链接、HTTP 状态码、robots.txt 有效性、图片 alt、canonical、hreflang、字体可读性、点击目标尺寸。",[35,45,46],{},"本文在同一台机器上对公开站点做过多次重复运行,确认分数存在波动;未做跨地区、跨设备的对照实验。",[12,48,49],{"id":49},"核心功能",[51,52,53],"h3",{"id":53},"五个类别怎么给分",[16,55,56],{},"报告分五块:性能、可访问性、最佳实践、SEO,以及早期版本里的 PWA 类别(新版本已淡出)。性能是唯一按指标加权计算的类别,其余四类按检查项通过率折算——二十项检查过了十八项,大致就是 90 分。",[16,58,59],{},"这些分数不能横向比较。性能 70 分说明加载体验有明显问题,SEO 70 分可能只是少了一个 meta 描述。看报告时要先看具体是哪几条没过,再决定要不要为它排期。",[51,61,63],{"id":62},"三个核心指标tbtlcpcls","三个核心指标:TBT、LCP、CLS",[16,65,66],{},"TBT 占总分 30%,衡量主线程被长任务阻塞的时间,直接对应\"页面能点但点了没反应\"的体感。LCP 和 CLS 各占 25%,前者是最大内容元素的渲染时间,后者是布局偏移量。",[16,68,69],{},"LCP 差通常是图片没压缩、字体阻塞渲染、首屏依赖接口;CLS 差多半是图片没写宽高、广告位动态插入、字体切换导致重排。TBT 差就要看第三方脚本和长任务拆分。报告会把每个指标拆到具体资源,能直接对应到代码。",[51,71,73],{"id":72},"从-devtools-到-ci让它跑在每次发布前","从 DevTools 到 CI:让它跑在每次发布前",[16,75,76,77,81],{},"最轻的用法是 DevTools 的 Lighthouse 面板,选类别、点分析,几十秒出报告。命令行用 ",[78,79,80],"code",{},"npx lighthouse \u003Curl> --output=json"," 适合批量跑。真正有价值的是 Lighthouse CI:在流水线里对关键页面跑一遍,配置断言,主页面性能低于 85 就让构建失败。",[16,83,84],{},"断言可以按指标设,比如 LCP 不超过 2.5 秒、CLS 不超过 0.1,也可以按预算设 JS 体积上限。这样一来性能从\"上线后再说\"变成\"合并前就卡住\",这是它比手动跑分更有用的地方。",[51,86,87],{"id":87},"实验室数据与真实用户的差距",[16,89,90],{},"Lighthouse 用模拟的慢速 4G 和四倍 CPU 降速跑页面,测的是\"在这种条件下会怎样\"。真实用户的设备、网络、缓存状态千差万别,所以同一页面在 Lighthouse 里 60 分,CrUX 里可能显示 75% 的良好访问占比。",[16,92,93],{},"判断优先级时,两者要一起看:实验室数据用来定位可优化项,字段数据用来判断影响面。只盯分数容易优化到\"对分数友好但对用户无感\"的地方,比如把首屏图片换成极小尺寸,分数上去了,用户看到的却是糊图。",[12,95,96],{"id":96},"评分明细",[51,98,100],{"id":99},"功能完整度8610","功能完整度:8.6\u002F10",[16,102,103],{},"性能、可访问性、最佳实践、SEO 四类的检查项覆盖了前端质量的主要面,报告还带改进建议与预估收益。扣分在于它只做单页审计,没有站点级爬取、没有历史趋势对比,也不校验结构化数据的业务正确性。",[51,105,107],{"id":106},"易用性8810","易用性:8.8\u002F10",[16,109,110],{},"DevTools 里一键运行,报告结构清晰,每条问题都能点开看到受影响的资源与代码位置。命令行与 CI 的接入文档完整,配置断言不需要读源码。对非技术人员的门槛在报告解读,不在操作。",[51,112,114],{"id":113},"数据质量9410","数据质量:9.4\u002F10",[16,116,117],{},"指标计算口径公开,权重透明,网络与 CPU 条件可复现,同一配置下重复运行结果接近。扣分来自波动:第三方脚本加载时快时慢,单次跑分可能差十几分,需要连跑三次取中位数才有参考价值。",[51,119,121],{"id":120},"性价比10010","性价比:10.0\u002F10",[16,123,124],{},"开源免费,没有账号、额度、席位,CI 里跑多少次都不额外收费。同类商业性能监测工具按页面数或监测频次收月费,Lighthouse 把这件事的成本压到了零,给满分没有争议。",[51,126,128],{"id":127},"客户支持7610","客户支持:7.6\u002F10",[16,130,131],{},"Chrome 团队维护,GitHub 上 issue 响应及时,文档随版本更新。但它没有商业支持合同,遇到企业环境特有问题只能在仓库里提问;版本升级偶尔会调整评分口径,历史分数不能直接对比。",[12,133,134],{"id":134},"定价说明",[136,137,138,154],"table",{},[139,140,141],"thead",{},[142,143,144,148,151],"tr",{},[145,146,147],"th",{},"项目",[145,149,150],{},"价格",[145,152,153],{},"说明",[155,156,157,169,179],"tbody",{},[142,158,159,163,166],{},[160,161,162],"td",{},"Lighthouse 本体",[160,164,165],{},"免费",[160,167,168],{},"Apache 2.0 开源,DevTools、CLI、Node API 均不收费",[142,170,171,174,176],{},[160,172,173],{},"Lighthouse CI",[160,175,165],{},[160,177,178],{},"自建运行,成本为 CI 机器时间",[142,180,181,184,186],{},[160,182,183],{},"PageSpeed Insights",[160,185,165],{},[160,187,188],{},"同一引擎,附带 CrUX 字段数据,有调用频率限制",[16,190,191],{},"成本为零不代表没有投入。把它接进流水线需要前端配合,断言阈值要按业务调,误报会让团队逐渐忽略红灯。真正稀缺的是\"有人看报告并排期修改\",工具本身不解决这件事。",[12,193,194],{"id":194},"和竞品对比",[136,196,197,212],{},[139,198,199],{},[142,200,201,204,207,209],{},[145,202,203],{},"维度",[145,205,206],{},"Lighthouse",[145,208,183],{},[145,210,211],{},"WebPageTest",[155,213,214,228,240,254],{},[142,215,216,219,222,225],{},[160,217,218],{},"定位",[160,220,221],{},"本地与 CI 的单页审计",[160,223,224],{},"在线跑分加真实用户数据",[160,226,227],{},"多地点多设备的深度性能测试",[142,229,230,233,235,237],{},[160,231,232],{},"起步价",[160,234,165],{},[160,236,165],{},[160,238,239],{},"公开实例免费,私有实例付费",[142,241,242,245,248,251],{},[160,243,244],{},"强项",[160,246,247],{},"可进 CI、可设断言、报告可落地",[160,249,250],{},"实验室数据与 CrUX 字段数据并列",[160,252,253],{},"瀑布图、视频对比、多地域节点",[142,255,256,259,262,265],{},[160,257,258],{},"短板",[160,260,261],{},"单页、实验室数据、分数波动",[160,263,264],{},"无法批量与断言,依赖网络提交",[160,266,267],{},"配置项多,上手慢,免费额度有限",[16,269,270,273],{},[19,271,272],{},"怎么选",":要在发布前卡住性能回归,用 Lighthouse 加 CI,断言写进流水线;想快速看一个 URL 的实验室分与真实用户分布,用 PageSpeed Insights;要定位跨地域、跨设备的加载差异,或者需要瀑布图和视频回放,用 WebPageTest。",[12,275,277],{"id":276},"faq","FAQ",[51,279,281],{"id":280},"q-lighthouse-的-seo-拿了-100-分是不是技术-seo-就没问题了","Q: Lighthouse 的 SEO 拿了 100 分,是不是技术 SEO 就没问题了?",[16,283,284],{},"A: 不是。它检查的是十几条基础项:标题有没有、描述有没有、链接能不能抓、robots.txt 是否有效、canonical 是否合法。收录与排名还取决于内容质量、内链结构、站点权重、抓取预算,这些它一项都不测。100 分只说明\"没有低级错误\"。",[51,286,288],{"id":287},"q-同一页面-devtools-跑-85-分ci-里只有-62-分差在哪","Q: 同一页面 DevTools 跑 85 分,CI 里只有 62 分,差在哪?",[16,290,291],{},"A: 先对齐三件事:网络与 CPU 限速配置、是否模拟移动端、Chrome 版本。CI 容器里通常没有 GPU 加速,渲染路径不同,分数天然偏低;插件和后台标签页也会影响本地结果。对齐配置后仍有差距,就要看 CI 机器负载,CPU 抢占会直接拉低 TBT。",[51,293,295],{"id":294},"q-手机端-50-分桌面端-90-分以哪个为准","Q: 手机端 50 分、桌面端 90 分,以哪个为准?",[16,297,298],{},"A: 看流量结构。移动端是主要入口就以移动为准,并且把移动端的 LCP 和 TBT 当硬指标;桌面为主就单独设桌面阈值。两个都要看的情况,建议在 CI 里分别跑移动与桌面两套配置,各自设阈值,不要用一套分数覆盖两种场景。",[12,300,301],{"id":301},"评测方法说明",[16,303,304],{},"元析评测围绕功能完整度、易用性、数据质量、性价比、客户支持五个核心维度打分,每项满分 10 分,按固定权重折算总分。Lighthouse 为开源工具,本文的评分口径、检查项与用法于 2026-11 对照官方文档核实;分数波动与实验室数据局限来自重复运行的观察,未做跨地区设备矩阵测试。版本升级可能调整权重,以官方文档为准。",[16,306,307,310],{},[19,308,309],{},"最后更新",":2026-11-16",{"title":312,"searchDepth":313,"depth":313,"links":314},"",2,[315,316,317,324,331,332,333,338],{"id":14,"depth":313,"text":14},{"id":30,"depth":313,"text":30},{"id":49,"depth":313,"text":49,"children":318},[319,321,322,323],{"id":53,"depth":320,"text":53},3,{"id":62,"depth":320,"text":63},{"id":72,"depth":320,"text":73},{"id":87,"depth":320,"text":87},{"id":96,"depth":313,"text":96,"children":325},[326,327,328,329,330],{"id":99,"depth":320,"text":100},{"id":106,"depth":320,"text":107},{"id":113,"depth":320,"text":114},{"id":120,"depth":320,"text":121},{"id":127,"depth":320,"text":128},{"id":134,"depth":313,"text":134},{"id":194,"depth":313,"text":194},{"id":276,"depth":313,"text":277,"children":334},[335,336,337],{"id":280,"depth":320,"text":281},{"id":287,"depth":320,"text":288},{"id":294,"depth":320,"text":295},{"id":301,"depth":313,"text":301},"technical-seo",[341,342,343,344,345],"只审计单个 URL,不爬站,看不到全站有多少页面存在同类问题","给的是实验室模拟数据,和真实用户的 CrUX 字段数据经常对不上","性能分波动明显,同一页面连跑三次可能差十几分,单次结果不能当结论","默认模拟移动端 4G 与四倍 CPU 降速,桌面端表现好的页面分数会显得很难看","SEO 分数只覆盖基础检查,拿满分不代表页面能被收录或拿到排名",null,"2026-11-16","Lighthouse 评测:Chrome 团队开源,完全免费,一条命令给单页打性能、可访问性、最佳实践、SEO 四类分。适合开发在发布前自查指标;它只跑单页、只给实验室数据,不等于真实用户体感与排名。",false,"md",{},true,"没有技术人手、想靠一个分数判断全站 SEO 健康状况的运营团队","\u002Ftools\u002Ftechnical-seo\u002Flighthouse",{"free":352,"startingPrice":356,"currency":357,"billingPeriod":358,"notes":359},"0","USD","月","Apache 2.0 开源,完全免费,无账号与额度限制;DevTools 面板、Node CLI、Lighthouse CI 均不收费,成本只在你自己的 CI 机器时间。2026-11 核对官方文档。",[361,362,363,364,365],"完全免费且开源,DevTools 里点一下就能跑,不需要注册或申请密钥","一条命令可在 CI 里跑,能设置分数阈值与性能预算,低于阈值就让构建失败","性能分由 TBT、LCP、CLS、FCP、SI 五项指标加权得出,权重公开,分数可解释","SEO 类别含约十项检查:标题、描述、可抓取链接、robots.txt、canonical、hreflang、图片 alt","报告给出具体的优化建议与预估节省时间,开发拿着报告就能改,不需要再翻译一层","global",8.9,{"features":369,"ease":370,"data":371,"price":372,"support":373},8.6,8.8,9.4,10,7.6,{"title":5,"description":348},"tools\u002Ftechnical-seo\u002Flighthouse",[377,378,206,379],"技术 SEO","性能审计","开源工具","https:\u002F\u002Fdeveloper.chrome.com\u002Fdocs\u002Flighthouse\u002Foverview\u002F","Google (Chrome)","rU1orSfjZbYu9PG2yMAqVme9NrT7CW3aJmsXeZ8TueA",1016,[385,393,402],{"path":386,"toolName":387,"description":388,"score":369,"pricing":389,"vendor":392,"date":347,"category":339},"\u002Ftools\u002Ftechnical-seo\u002Frich-results-test","Rich Results Test","Rich Results Test 评测:Google 官方免费工具,零成本验证页面能出哪几种富媒体结果,结论比第三方 Schema 校验器更接近真实搜索结果;只测单页,没有批量与历史记录。",{"free":352,"startingPrice":312,"currency":165,"billingPeriod":390,"notes":391},"一次性","Google 官方免费工具,无付费层级、无套餐分级,不登录 Google 账号也能用。官方未公布每日检测次数上限,常规单页验收不会触发拦截。价格与功能于 2026-11 核对官网。","Google",{"path":394,"toolName":395,"description":396,"score":397,"pricing":398,"vendor":395,"date":347,"category":339},"\u002Ftools\u002Ftechnical-seo\u002Fseopress","SEOPress","SEOPress 评测:PRO 单站每年 $49、五站 $59、不限站 $149,续费不涨价,带白标与 Google News 站点地图;界面偏工程师风格,新手需要时间适应。",8.4,{"free":352,"startingPrice":399,"currency":357,"billingPeriod":400,"notes":401},"49","年","免费版在 WordPress 插件库下载;PRO 单站 $49\u002F年、五站 $59\u002F年、不限站 $149\u002F年(均不含税),续费同价,14 天无理由退款。Insights(关键词与反链跟踪)$99\u002F年\u002F站需单独加购,AI 额度另有 $19\u002F29\u002F49 每月的包。价格于 2026-11 核对官网。",{"path":403,"toolName":404,"description":405,"score":406,"pricing":407,"vendor":404,"date":347,"category":339},"\u002Ftools\u002Ftechnical-seo\u002Frank-math","Rank Math","Rank Math 评测:免费版就带重定向、404 监控与二十多种 schema,PRO 首年 $95.88、自建站不限数量;续费涨到 $107.88,客户站要另买授权。",8.3,{"free":352,"startingPrice":408,"currency":357,"billingPeriod":400,"notes":409},"95.88","免费版在 WordPress 插件库下载;PRO 首年 $95.88,续费 $107.88\u002F年,覆盖自己拥有的网站且不限数量,含 500 个关键词跟踪额度与 15 天试用。面向客户站的 Business\u002FAgency 档与 Content AI 额度另计,金额需按站点数在官网选购。价格于 2026-11 核对官网。",1794788243460]