Audit Speed

作者 calm-northc1f633bea512無授權條款21 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫7 個月前更新

Deep Core Web Vitals and page speed audit. Use when the user asks about page speed, Core Web Vitals, LCP, CLS, INP, FCP, TTFB, Lighthouse scores, why a page is slow, performance optimization, or resource size analysis. For broader technical SEO issues, see diagnose-seo.

AI 產生的概覽

稽核 Core Web Vitals 與頁面速度,診斷根本原因並提出資源最佳化建議。

功能
提供針對 Core Web Vitals(LCP、CLS、INP、FCP、TTFB)的結構化稽核流程,包含門檻表與根因決策樹。它引導診斷伺服器、圖片、字型、阻擋渲染、版面位移與主執行緒問題,並包含附基準值的資源大小拆解。最終產出格式化稽核報告,含指標評級、根本原因、優先修正項目與快速見效項目。
適用情境
適用於使用者詢問頁面速度、Core Web Vitals、LCP、CLS、INP、FCP、TTFB 或 Lighthouse 分數,或想了解頁面為何緩慢時。也適合資源大小分析與效能最佳化規劃。
執行需求
僅為說明文件,不附帶指令碼。最好已有 Lighthouse 或 PageSpeed Insights 資料,以及目標頁面、技術堆疊與限制條件等背景資訊;若無資料,它會建議執行 Google PageSpeed Insights。

Audit Speed

Deep Core Web Vitals audit with root-cause analysis trees and resource optimization recommendations.

Core Web Vitals Thresholds

MetricGoodNeeds ImprovementPoor
LCP (Largest Contentful Paint)< 2.5s2.5s - 4.0s> 4.0s
CLS (Cumulative Layout Shift)< 0.10.1 - 0.25> 0.25
INP (Interaction to Next Paint)< 200ms200ms - 500ms> 500ms
FCP (First Contentful Paint)< 1.8s1.8s - 3.0s> 3.0s
TTFB (Time to First Byte)< 800ms800ms - 1800ms> 1800ms

Before You Start

Gather this context:

  1. Which pages? Homepage, key landing pages, or specific slow pages.
  2. Current scores. If the user has Lighthouse or PageSpeed Insights data, start there.
  3. Tech stack. CMS, framework, hosting — this determines which optimizations are available.
  4. Known constraints. Third-party scripts they can't remove, design requirements that limit optimization.

If no data is available, suggest running Google PageSpeed Insights on the key URLs.

LCP Root-Cause Tree

LCP measures when the largest visible element finishes rendering. Diagnose:

Is TTFB slow (> 800ms)?

  • → Server response time issue
  • Check: hosting quality, CDN configuration, database queries, server-side rendering time
  • Fix: upgrade hosting, add CDN, optimize server-side code, enable caching

Is the LCP element an image?

  • → Image optimization issue
  • Check: image format (use WebP/AVIF), image size (serve responsive sizes), lazy loading on LCP image (should NOT be lazy loaded)
  • Fix: convert to modern formats, add width/height attributes, use fetchpriority="high" on LCP image, preload the LCP image

Is the LCP element text?

  • → Font loading issue
  • Check: custom fonts blocking render, font file size, font-display strategy
  • Fix: use font-display: swap or optional, preload critical fonts, subset fonts to used characters

Is render-blocking CSS/JS delaying the LCP?

  • Check: large CSS files in <head>, synchronous JS before content
  • Fix: inline critical CSS, defer non-critical CSS, async/defer JS

CLS Root-Cause Tree

CLS measures unexpected layout shifts. Diagnose:

Do images/videos lack dimensions?

  • → Browser can't reserve space before loading
  • Fix: add width and height attributes to all <img> and <video> elements, use CSS aspect-ratio

Do ads or embeds inject content?

  • → Dynamic content pushing existing content down
  • Fix: reserve space for ad slots with min-height, use contain-intrinsic-size for lazy content

Do fonts cause text reflow?

  • → FOUT (Flash of Unstyled Text) causes layout shift when custom font loads
  • Fix: use font-display: optional (no swap = no shift), or match fallback font metrics

Does dynamic content insert above the fold?

  • → Banners, cookie notices, notifications pushing content
  • Fix: use overlays instead of inline insertions, or reserve space with fixed-height containers

INP Root-Cause Tree

INP measures responsiveness to user interactions. Diagnose:

Is the main thread blocked by long tasks?

  • Check: JavaScript execution time, third-party scripts, large DOM
  • Fix: break long tasks with requestIdleCallback or setTimeout, code-split heavy modules

Do event handlers do heavy synchronous work?

  • Check: click handlers that trigger large DOM updates, form validation on every keystroke
  • Fix: debounce inputs, use requestAnimationFrame for visual updates, offload work to web workers

Are third-party scripts competing for the main thread?

  • Check: analytics, chat widgets, A/B testing tools, social embeds
  • Fix: defer loading until after interaction, use loading="lazy" for embeds, consider removing low-value scripts

Resource Analysis

Break down the total page weight:

Resource TypeSizeAssessmentAction
HTML[x] KB[ok/large]Compress, reduce inline styles/scripts
CSS[x] KB[ok/large]Remove unused CSS, minify, critical CSS extraction
JavaScript[x] KB[ok/large]Code-split, tree-shake, defer non-critical
Images[x] KB[ok/large]Modern formats, responsive sizes, lazy load below fold
Fonts[x] KB[ok/large]Subset, limit families/weights, preload critical
Third-party[x] KB[ok/large]Audit necessity, defer, self-host if possible

Benchmarks:

  • Total page weight under 1.5 MB is good
  • JavaScript under 300 KB (compressed) for most sites
  • CSS under 100 KB (compressed)
  • First-party fonts under 100 KB

Output Format

Speed Audit: [URL or domain]

Core Web Vitals

MetricValueRatingRoot Cause
LCP[value]Good / Needs Improvement / Poor[identified cause]
CLS[value]......
INP[value]......
FCP[value]......
TTFB[value]......

Resource Breakdown [Table from Resource Analysis]

Priority Fixes

For each failing metric, ordered by impact:

  1. [Metric]: [Root cause]

    • Current: [value]
    • Target: [threshold]
    • Fix: [specific action]
    • Estimated impact: [high/medium/low]
  2. ...

Quick Wins List optimizations that require minimal effort:

  • Add width/height to images
  • Set fetchpriority="high" on LCP image
  • Defer non-critical JavaScript
  • ...

Pro Tip: Use the free CWV Impact Calculator to estimate the traffic impact of fixing Core Web Vitals, and the Critical CSS Generator to extract above-the-fold CSS. SEOJuice MCP users can run /seojuice:page-audit [domain] [url] for instant CWV scores, Lighthouse data, and resource breakdowns.

來源與署名

來源:calm-north/seojuice-skills位於skills/audit-speed提交c1f633b

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架

更多來自 calm-north/seojuice-skills 的技能

Target Serp

calm-north

指導 SEO 爭取精選摘要、People Also Ask 和複合式搜尋結果等 SERP 功能。

Marketing & Sales217 個月前更新

Recover Content

calm-north

診斷現有頁面的搜尋流量下滑,並提出內容更新、合併、重新導向或下線的處置建議。

Marketing & Sales217 個月前更新

Rank Local

calm-north

Build a local SEO strategy covering Google Business Profile, local citations, reviews, and NAP consistency. Use when the user asks about local SEO, Google Business Profile, Google Maps ranking, local pack, NAP consistency, local citations, review strategy, or ranking for "[service] near me" searches.

待分類217 個月前更新

Optimize For Ai

calm-north

Optimize content for AI search engines — ChatGPT, Perplexity, Claude, Gemini, Google AI Overviews. Use when the user asks about AI SEO, AISO, getting cited by AI, appearing in AI answers, answer engine optimization, AEO, GEO, LLMO, AI Overviews, zero-click search, or how to appear in ChatGPT/Perplexity results. For traditional SEO, see diagnose-seo.

待分類217 個月前更新

Migrate Site

calm-north

指導網站遷移,提供稽核、重新導向對應、監控與回復標準,以保護搜尋排名。

Marketing & Sales217 個月前更新

Fix Linking

calm-north

Design or audit internal link structure for a website. Use when the user asks about internal linking, link architecture, orphan pages, PageRank flow, anchor text, site structure, silo architecture, or why pages aren't ranking despite good content. For external link building, see build-links.

待分類217 個月前更新