🚀

PageSpeed Insights Report

https://page.xmhai.cn
📱 手机端
📅 2026-06-28 11:08:59 UTC
🏆 Lighthouse 分数
🚀
Performance
73
性能
Accessibility
0
无障碍
Best Practices
0
最佳实践
🔍
Seo
0
SEO
📊 分数总览
🚀 Performance
73
♿ Accessibility
0
✅ Best Practices
0
🔍 SEO
0
⚡ Core Web Vitals & 性能指标
FCP - 首次内容绘制
3.5 s
❌ Poor
LCP - 最大内容绘制
3.8 s
⚠️ Needs Improvement
CLS - 累积布局偏移
0.013
✅ Good
TBT - 总阻塞时间
0 ms
✅ Good
Speed Index - 速度指数
17.9 s
❌ Poor
TTFB - 服务器响应
Root document took 0 ms
✅ Good
📦 资源加载概况
📊
Total size was 432 KiB
总页面大小
🌳
N/A
DOM 节点数
🔧 需要优化的项目 (11 项)
⚠️
Reduce unused CSS
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. [Learn how to reduce unused CSS](https://developer.chrome.com/docs/lighthouse/performance/unused-css-rules/).
0/100
⚠️
Speed Index
Speed Index shows how quickly the contents of a page are visibly populated. [Learn more about the Speed Index metric](https://developer.chrome.com/docs/lighthouse/performance/speed-index/).
0/100
⚠️
Network dependency tree
[Avoid chaining critical requests](https://developer.chrome.com/docs/performance/insights/network-dependency-tree) by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
0/100
⚠️
Forced reflow
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about [forced reflows](https://developer.chrome.com/docs/performance/insights/forced-reflow) and
0/100
⚠️
Render-blocking requests
Requests are blocking the page's initial render, which may delay LCP. [Deferring or inlining](https://developer.chrome.com/docs/performance/insights/render-blocking) can move these network requests out of the critical path.
0/100
⚠️
Font display
Consider setting [font-display](https://developer.chrome.com/docs/performance/insights/font-display) to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with [font metric overrides](https://developer.chrome.com/blog/font-fallbacks).
0/100
⚠️
First Contentful Paint
First Contentful Paint marks the time at which the first text or image is painted. [Learn more about the First Contentful Paint metric](https://developer.chrome.com/docs/lighthouse/performance/first-contentful-paint/).
36/100
⚠️
Minimize main-thread work
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. [Learn how to minimize main-thread work](https://developer.chrome.com/docs/lighthouse/performance/mainthread-work-breakdown/)
50/100
⚠️
Improve image delivery
Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size](https://developer.chrome.com/docs/performance/insights/image-delivery)
50/100
⚠️
Use efficient cache lifetimes
A long cache lifetime can speed up repeat visits to your page. [Learn more about caching](https://developer.chrome.com/docs/performance/insights/cache).
50/100
⚠️
Largest Contentful Paint
Largest Contentful Paint marks the time at which the largest text or image is painted. [Learn more about the Largest Contentful Paint metric](https://developer.chrome.com/docs/lighthouse/performance/lighthouse-largest-contentful-paint/)
56/100