Skip to content
Audit Complete

Results for https://cnblogs.com

Visit site
Spain Spain · Madrid Completed: Apr 21, 2026 20:43 UTC
Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C72

Site Health

Score: 72 / 100

Based on 8 categories, 0 sections

Fast site — your users get a smooth experience.

Several missing protections leave your users and data exposed.

Major barriers for users with disabilities — up to 15% of your audience.

Well-optimized for search — your content is discoverable.

Good server performance with room for optimization.

Mostly compliant — a few items need attention.

Good content signals with minor gaps.

Lean and efficient — low environmental impact per visit.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Google Search Console · 2306 peers
You 72
·
Avg 73
At average
0 50 100
Better than 33% of Google Search Console sites See full Google Search Console benchmark →
Google Workspace · 1091 peers
You 72
·
Avg 73
At average
0 50 100
Better than 24% of Google Workspace sites See full Google Workspace benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
3

11 image-only link(s) without alt text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Link & Button Quality
4

18 image-in-link without alt text

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Alt Text Quality
5

20 image(s) missing alt attribute

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Alt Text Quality
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

2

High impact, low effort — start here.

Strategic

3

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fcnblogs.com)](https://beavercheck.com/results/2fe59d1f-6aae-40ce-b974-905d07a7dc7c)
<a href="https://beavercheck.com/results/2fe59d1f-6aae-40ce-b974-905d07a7dc7c"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fcnblogs.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fcnblogs.com

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

2 security gaps detected — browsers may warn visitors about your site.
3 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

2 critical 5 warning

7 barrier(s) likely increasing bounce by ~29%.

Speed (1)

Page takes 4.6s to load

+12% bounce

Users abandon at ~3s — you're 2.1s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

Trust (3)

Mixed content on HTTPS page

+8% bounce

Browsers block insecure subresources — broken images, missing scripts, warning badge

Fix: Change http:// URLs inside the page to https:// (or protocol-relative)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Content (1)

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Navigation (2)

8 link(s) with generic text ("click here", "read more")

+1% bounce

Screen-reader users navigating by link list see no context — and search engines can't infer relevance

Fix: Rewrite with descriptive phrases that identify the destination

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

¥1,925 investment → ¥12,846/month returns + CNY 50,000,000 risk avoided

Payback period: < 1 month First-year ROI: +7908%

Investment

¥1,925

6h · 5 findings

Monthly returns

¥12,846 /mo

~¥154,155 / year

  • Conversions recovered ¥12,845
  • Bandwidth savings ¥1.09

Regulatory risk avoided

CNY 50,000,000

if kept compliant

  • PIPL CNY 50,000,000

Payback period

0 12mo 24mo

¥350 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

¥1,925

5.5 developer hours at ¥350/hr

Based on China rates (¥350/hr)

Quick wins
¥350 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
¥ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

¥4,166,668 / month at risk

~¥50,000,013 / year if left unfixed

Compliance Risk

¥50,000,000

PIPL
  • No privacy policy link detected
    PIPL: CNY 100,000 – CNY 50,000,000
  • Trackers detected but no cookie policy found
    PIPL: CNY 100,000 – CNY 50,000,000
  • Trackers detected but no privacy policy found
    PIPL: CNY 100,000 – CNY 50,000,000

+1 more

Bandwidth Waste

¥1.09 /mo

1899.4 MB/mo × 0.571 CNY/GB

  • Optimize transfer: save ~190 KB per page load
    Saves ¥1.09/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

72
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
72
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
73
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
85
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

4.59 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

4.59 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

74 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.002

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

4.69 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

6.64 s

Detailed Report

Audit breakdown by category with detailed findings.

72

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
assets.cnblogs.com/images/ghs.png86400.0 s19.0 KiB

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
div#side_right > div#cnblogs_b4 > a > img div#side_right > div#cnblogs_b4 > a > img
img2024.cnblogs.com/blog/35695/202603/35695-20260305163238916-712956342.jpg76.5 KiB39.1 KiB
div#side_right > div#cnblogs_b2 > a > img div#side_right > div#cnblogs_b2 > a > img
img2024.cnblogs.com/blog/35695/202604/35695-20260415221132085-1775010472.webp70.1 KiB32.8 KiB
div#footer_bottom > div.beian > a.gongan > img div#footer_bottom > div.beian > a.gongan > img
assets.cnblogs.com/images/ghs.png18.8 KiB18.7 KiB
div#side_right > div#cnblogs_b3 > a > img div#side_right > div#cnblogs_b3 > a > img
img2024.cnblogs.com/blog/35695/202512/35695-20251205182619157-1150461542.webp54.6 KiB17.2 KiB
博主头像 div.post-item-text > p.post-item-summary > a > img.avatar
pic.cnblogs.com/face/3784694/20260401160101.png5.9 KiB5.5 KiB
博主头像 div.post-item-text > p.post-item-summary > a > img.avatar
pic.cnblogs.com/face/3708248/20250926144504.png5.6 KiB5.2 KiB
div#side_right > div#cnblogs_b1 > a > img div#side_right > div#cnblogs_b1 > a > img
img2024.cnblogs.com/blog/35695/202512/35695-20251201125434258-461912837.webp19.9 KiB4.7 KiB
博主头像 div.post-item-text > p.post-item-summary > a > img.avatar
pic.cnblogs.com/face/3693259/20260319124404.png5.0 KiB4.6 KiB
博主头像 div.post-item-text > p.post-item-summary > a > img.avatar
pic.cnblogs.com/face/3578564/20241218184338.png4.6 KiB4.2 KiB
博主头像 div.post-item-text > p.post-item-summary > a > img.avatar
pic.cnblogs.com/face/534218/20200616131310.png4.5 KiB4.2 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 1.3 s
URLTime Spent
cnblogs.com/1.3 s
www.cnblogs.com/0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in the main frame.Actionable

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 0.0 ms 64.5 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtag/js?id=G-M95P3TTWJZ157.0 KiB64.5 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
博客园Logo ul.navbar-list > li.navbar-branding > a > img
www.cnblogs.com/images/logo.svg?v=2SMrXdIvlZwVoB1akyXm38WIKuTHVqvGD0CweV-B6cY
ul.navbar-list > li.dropdown > div.dropdown-button > img ul.navbar-list > li.dropdown > div.dropdown-button > img
www.cnblogs.com/images/aggsite/pulldown-bold.svg

More information about the performance of your application. These numbers don't directly affect the Performance score.

Max Potential First Input Delay 120 ms
Layout shift culprits
Optimize DOM size
Font display
Forced reflow
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Reduce unused CSS
Avoids enormous network payloads Total size was 618 KiB
User Timing marks and measures 9 user timings
JavaScript execution time 0.5 s
Minimizes main-thread work 1.9 s
Avoid long main-thread tasks 5 long tasks found
Avoid non-composited animations 1 animated element found
Network Requests
Network Round Trip Times 240 ms
Server Backend Latencies 880 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 230 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
LCP request discovery
72

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
分类 ul.sidenav > li#sidenav_category > a > span
精华 ul.sidenav > li#sidenav_pick > a > span
订阅 ul.sidenav > li#sidenav_subscription > a > span
关注 ul.sidenav > li#sidenav_following > a > span
我评 ul.sidenav > li#sidenav_commented > a > span
我赞 ul.sidenav > li#sidenav_digged > a > span
足迹 ul.sidenav > li#sidenav_history > a > span
··· div#pager_bottom > div#paging_block > div.pager > span.ellipsis
100 div#pager_bottom > div#paging_block > div.pager > a.p_100
48小时阅读排行 div#side_right > div.card > h4.card-title > a
10天推荐排行 div#side_right > div.card > h4.card-title > a
15天热门博文 div#side_right > div.card > h4.card-title > a
编辑推荐 div#side_right > div.card > h4.card-title > a
热门新闻 div#side_right > div.card > h4.card-title > a
推荐新闻 div#side_right > div.card > h4.card-title > a
战略合作:Chat2DB凌霞软件 body > div#wrapper > footer#footer > div.ally-link
Chat2DB div#wrapper > footer#footer > div.ally-link > a
凌霞软件 div#wrapper > footer#footer > div.ally-link > a
Powered by .NET 10.0 on Kubernetes div#wrapper > footer#footer > div#footer_bottom > div.poweredby
关于博客园 footer#footer > div#footer_bottom > div.about > a
联系我们 footer#footer > div#footer_bottom > div.about > a
商务合作 footer#footer > div#footer_bottom > div.about > a
企业博客 footer#footer > div#footer_bottom > div.about > a
企业发布 footer#footer > div#footer_bottom > div.about > a
Copyright © 2004-2026 博客园 版权所有 footer#footer > div#footer_bottom > div.about > span
浙公网安备 33010602011771号 div#footer_bottom > div.beian > a.gongan > span
浙ICP备2021040463号-3 footer#footer > div#footer_bottom > div.beian > a
违法和不良信息举报中心 footer#footer > div#footer_bottom > div.report-contact > a
举报邮箱:contact@cnblogs.com footer#footer > div#footer_bottom > div.report-contact > span
网站举报中心 footer#footer > div#footer_bottom > div.report-contact > a

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul.navbar-list > li.dropdown > div.dropdown-button > img ul.navbar-list > li.dropdown > div.dropdown-button > img
div#side_right > div#cnblogs_b1 > a > img div#side_right > div#cnblogs_b1 > a > img
div#side_right > div#cnblogs_b2 > a > img div#side_right > div#cnblogs_b2 > a > img
div#side_right > div#cnblogs_b3 > a > img div#side_right > div#cnblogs_b3 > a > img
div#side_right > div#cnblogs_b4 > a > img div#side_right > div#cnblogs_b4 > a > img
div#footer_bottom > div.beian > a.gongan > img div#footer_bottom > div.beian > a.gongan > img

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > div#wrapper > a body > div#wrapper > a
div#main > div#side_right > div#cnblogs_b1 > a div#main > div#side_right > div#cnblogs_b1 > a
div#main > div#side_right > div#cnblogs_b2 > a div#main > div#side_right > div#cnblogs_b2 > a
div#main > div#side_right > div#cnblogs_b3 > a div#main > div#side_right > div#cnblogs_b3 > a
div#main > div#side_right > div#cnblogs_b4 > a div#main > div#side_right > div#cnblogs_b4 > a

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul.navbar-list > li > form#zzk_search_mobile > input#zzk_search_input_mobile ul.navbar-list > li > form#zzk_search_mobile > input#zzk_search_input_mobile

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
搜索 ul.navbar-list > li > form#zzk_search_mobile > button#zzk_search_button_mobile
» div.card > ul > li > a.right_more
» div.card > ul > li > a.right_more
» div.card > ul > li > a.right_more

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
Buttons have an accessible name
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Heading elements appear in a sequentially-descending order
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements use only permitted ARIA attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Image elements do not have `[alt]` attributes that are redundant text.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
73

Best Practices

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLDisplayed sizeActual sizeExpected size
博主头像 div.post-item-text > p.post-item-summary > a > img.avatar
pic.cnblogs.com/face/3693259/20260319124404.png48 x 4848 x 4872 x 72
博主头像 div.post-item-text > p.post-item-summary > a > img.avatar
pic.cnblogs.com/face/3784694/20260401160101.png48 x 4848 x 4872 x 72

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Access to script at 'https://cdn-www.cnblogs.com/ng/main-ia2uqgxu.js' from origin 'https://www.cnblogs.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to script at 'https://cdn-www.cnblogs.com/ng/polyfills-jq6heycx.js' from origin 'https://www.cnblogs.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Page has the HTML doctype
Properly defines charset
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
85

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
nav#nav_main > ul#nav_right > li#navbar_login_status > a#navbar_lite_mode_indicator
简洁模式 ... li#navbar_login_status > div#user_info > div#navbar_menu > a#navbar_lite_mode_toggle
退出登录 li#navbar_login_status > div#user_info > div#navbar_menu > a
发现 ul.navbar-list > li.dropdown > div.dropdown-button > a
退出 ul.navbar-list > li#user_info_mobile > div.dropdown-menu > a
更多 ul.sidenav > li#sidenav_more > div.dropdown-button > a
div#side_nav > ul.sidenav > li#dark_switch > a div#side_nav > ul.sidenav > li#dark_switch > a
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19890716
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19904194
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19903757
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19897604
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19903938
1 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19903842
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19903293
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19903270
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19902860
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19902842
3 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19902722
2 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19902693
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19902643
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19902499
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19901906
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19901796
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19901456
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19901328
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19899804
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19899767

To appear in search results, crawlers need access to your app.

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul.navbar-list > li.dropdown > div.dropdown-button > img ul.navbar-list > li.dropdown > div.dropdown-button > img
div#side_right > div#cnblogs_b1 > a > img div#side_right > div#cnblogs_b1 > a > img
div#side_right > div#cnblogs_b2 > a > img div#side_right > div#cnblogs_b2 > a > img
div#side_right > div#cnblogs_b3 > a > img div#side_right > div#cnblogs_b3 > a > img
div#side_right > div#cnblogs_b4 > a > img div#side_right > div#cnblogs_b4 > a > img
div#footer_bottom > div.beian > a.gongan > img div#footer_bottom > div.beian > a.gongan > img

Format your HTML in a way that enables crawlers to better understand your app’s content.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links have descriptive text
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

68
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
72
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
77
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
85
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

2.48 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

3.13 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

0 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.000

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

2.55 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

3.13 s

Detailed Report

Audit breakdown by category with detailed findings.

68

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:1189.168 label:Time to first byte subpart:timeToFirstByte] map[duration:1613.603 label:Resource load delay subpart:resourceLoadDelay] map[duration:200.208 label:Resource load duration subpart:resourceLoadDuration] map[duration:24.916 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: div#side_right > div#cnblogs_b1 > a > img
path: 1,HTML,1,BODY,0,DIV,2,DIV,0,DIV,2,DIV,0,DIV,0,A,0,IMG
selector: div#side_right > div#cnblogs_b1 > a > img
snippet: <img src="https://img2024.cnblogs.com/blog/35695/202512/35695-20251201125434258-4619…" onload="countCreativeImpressions('B1-字节-trae')">

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: div#side_right > div#cnblogs_b1 > a > img
path: 1,HTML,1,BODY,0,DIV,2,DIV,0,DIV,2,DIV,0,DIV,0,A,0,IMG
selector: div#side_right > div#cnblogs_b1 > a > img
snippet: <img src="https://img2024.cnblogs.com/blog/35695/202512/35695-20251201125434258-4619…" onload="countCreativeImpressions('B1-字节-trae')">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

RequestCache TTLTransfer Size
assets.cnblogs.com/images/ghs.png86400.0 s19.1 KiB

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
div#side_right > div#cnblogs_b4 > a > img div#side_right > div#cnblogs_b4 > a > img
img2024.cnblogs.com/blog/35695/202603/35695-20260305163238916-712956342.jpg76.5 KiB64.3 KiB
div#side_right > div#cnblogs_b2 > a > img div#side_right > div#cnblogs_b2 > a > img
img2024.cnblogs.com/blog/35695/202604/35695-20260415221132085-1775010472.webp70.1 KiB57.9 KiB
div#side_right > div#cnblogs_b3 > a > img div#side_right > div#cnblogs_b3 > a > img
img2024.cnblogs.com/blog/35695/202512/35695-20251205182619157-1150461542.webp54.6 KiB42.4 KiB
div#footer_bottom > div.beian > a.gongan > img div#footer_bottom > div.beian > a.gongan > img
assets.cnblogs.com/images/ghs.png18.8 KiB18.7 KiB
div#wrapper > a > div.imagebar > img div#wrapper > a > div.imagebar > img
img2024.cnblogs.com/blog/35695/202604/35695-20260413214144970-407851675.webp21.0 KiB16.3 KiB
div#side_right > div#cnblogs_b1 > a > img div#side_right > div#cnblogs_b1 > a > img
img2024.cnblogs.com/blog/35695/202512/35695-20251201125434258-461912837.webp19.9 KiB14.9 KiB
博主头像 div.post-item-text > p.post-item-summary > a > img.avatar
pic.cnblogs.com/face/3784694/20260401160101.png5.9 KiB5.5 KiB
博主头像 div.post-item-text > p.post-item-summary > a > img.avatar
pic.cnblogs.com/face/3708248/20250926144504.png5.6 KiB5.2 KiB
博主头像 div.post-item-text > p.post-item-summary > a > img.avatar
pic.cnblogs.com/face/3693259/20260319124404.png5.0 KiB4.6 KiB
博主头像 div.post-item-text > p.post-item-summary > a > img.avatar
pic.cnblogs.com/face/3578564/20241218184338.png4.6 KiB4.2 KiB
博主头像 div.post-item-text > p.post-item-summary > a > img.avatar
pic.cnblogs.com/face/534218/20200616131310.png4.5 KiB4.2 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 760 ms
URLTime Spent
cnblogs.com/760 ms
www.cnblogs.com/0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Estimated savings: 140 ms 63.1 KiB
URLTransfer SizeEst Savings
www.googletagmanager.com/gtag/js?id=G-M95P3TTWJZ157.0 KiB63.1 KiB

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in the main frame.Actionable

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
div#wrapper > a > div.imagebar > img div#wrapper > a > div.imagebar > img
img2024.cnblogs.com/blog/35695/202604/35695-20260413214144970-407851675.webp
博客园Logo ul#nav_left > li.navbar-branding > a > img
www.cnblogs.com/images/logo.svg?v=2SMrXdIvlZwVoB1akyXm38WIKuTHVqvGD0CweV-B6cY
ul.sidenav > li#dark_switch > a > img ul.sidenav > li#dark_switch > a > img
www.cnblogs.com/images/aggsite/dark.svg
ul.sidenav > li#sidenav_history > a > img ul.sidenav > li#sidenav_history > a > img
www.cnblogs.com/images/aggsite/history.svg
ul.sidenav > li#sidenav_category > a > img ul.sidenav > li#sidenav_category > a > img
www.cnblogs.com/images/aggsite/category.svg
ul.sidenav > li#sidenav_pick > a > img ul.sidenav > li#sidenav_pick > a > img
www.cnblogs.com/images/aggsite/picked.svg
ul.sidenav > li#sidenav_candidate > a > img ul.sidenav > li#sidenav_candidate > a > img
www.cnblogs.com/images/aggsite/candidate.svg
ul.sidenav > li#sidenav_subscription > a > img ul.sidenav > li#sidenav_subscription > a > img
www.cnblogs.com/images/aggsite/subscription.svg
ul.sidenav > li#sidenav_following > a > img ul.sidenav > li#sidenav_following > a > img
www.cnblogs.com/images/aggsite/following.svg
ul.sidenav > li#sidenav_commented > a > img ul.sidenav > li#sidenav_commented > a > img
www.cnblogs.com/images/aggsite/commented.svg
ul.sidenav > li#sidenav_digged > a > img ul.sidenav > li#sidenav_digged > a > img
www.cnblogs.com/images/aggsite/digged.svg
ul#nav_left > li.dropdown > div.dropdown-button > img ul#nav_left > li.dropdown > div.dropdown-button > img
www.cnblogs.com/images/aggsite/pulldown-light.svg

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Optimize DOM size
Font display
Forced reflow
Modern HTTP
Optimize viewport for mobile
Max Potential First Input Delay 30 ms
Minify CSS
Minify JavaScript
Reduce unused CSS
Avoids enormous network payloads Total size was 619 KiB
User Timing marks and measures 11 user timings
JavaScript execution time 0.1 s
Minimizes main-thread work 0.5 s
Avoid long main-thread tasks 1 long task found
Avoid non-composited animations 2 animated elements found
Network Requests
Network Round Trip Times 220 ms
Server Backend Latencies 790 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 200 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
72

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
反馈 ul.sidenav > li.sidenav-item > a.feedback > span
··· div#pager_bottom > div#paging_block > div.pager > span.ellipsis
100 div#pager_bottom > div#paging_block > div.pager > a.p_100
48小时阅读排行 div#side_right > div.card > h4.card-title > a
10天推荐排行 div#side_right > div.card > h4.card-title > a
15天热门博文 div#side_right > div.card > h4.card-title > a
编辑推荐 div#side_right > div.card > h4.card-title > a
热门新闻 div#side_right > div.card > h4.card-title > a
推荐新闻 div#side_right > div.card > h4.card-title > a
战略合作:Chat2DB凌霞软件 body > div#wrapper > footer#footer > div.ally-link
Chat2DB div#wrapper > footer#footer > div.ally-link > a
凌霞软件 div#wrapper > footer#footer > div.ally-link > a
友情链接: 艾思科蓝 飞致云 阿里云 腾讯云 华为云 天翼云 站长之家 腾讯WeTest IShell body > div#wrapper > footer#footer > div#friend_link
艾思科蓝 div#wrapper > footer#footer > div#friend_link > a
飞致云 div#wrapper > footer#footer > div#friend_link > a
阿里云 div#wrapper > footer#footer > div#friend_link > a
腾讯云 div#wrapper > footer#footer > div#friend_link > a
华为云 div#wrapper > footer#footer > div#friend_link > a
天翼云 div#wrapper > footer#footer > div#friend_link > a
站长之家 div#wrapper > footer#footer > div#friend_link > a
腾讯WeTest div#wrapper > footer#footer > div#friend_link > a
IShell div#wrapper > footer#footer > div#friend_link > a
Powered by .NET 10.0 on Kubernetes div#wrapper > footer#footer > div#footer_bottom > div.poweredby
关于博客园 footer#footer > div#footer_bottom > div.about > a
联系我们 footer#footer > div#footer_bottom > div.about > a
商务合作 footer#footer > div#footer_bottom > div.about > a
企业博客 footer#footer > div#footer_bottom > div.about > a
企业发布 footer#footer > div#footer_bottom > div.about > a
Copyright © 2004-2026 博客园 版权所有 footer#footer > div#footer_bottom > div.about > span
浙公网安备 33010602011771号 div#footer_bottom > div.beian > a.gongan > span
浙ICP备2021040463号-3 footer#footer > div#footer_bottom > div.beian > a
违法和不良信息举报中心 footer#footer > div#footer_bottom > div.report-contact > a
举报邮箱:contact@cnblogs.com footer#footer > div#footer_bottom > div.report-contact > span
网站举报中心 footer#footer > div#footer_bottom > div.report-contact > a

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul#nav_left > li.dropdown > div.dropdown-button > img ul#nav_left > li.dropdown > div.dropdown-button > img
div#wrapper > a > div.imagebar > img div#wrapper > a > div.imagebar > img
ul.sidenav > li#sidenav_category > a > img ul.sidenav > li#sidenav_category > a > img
ul.sidenav > li#sidenav_pick > a > img ul.sidenav > li#sidenav_pick > a > img
ul.sidenav > li#sidenav_candidate > a > img ul.sidenav > li#sidenav_candidate > a > img
ul.sidenav > li#sidenav_subscription > a > img ul.sidenav > li#sidenav_subscription > a > img
ul.sidenav > li#sidenav_following > a > img ul.sidenav > li#sidenav_following > a > img
ul.sidenav > li#sidenav_commented > a > img ul.sidenav > li#sidenav_commented > a > img
ul.sidenav > li#sidenav_digged > a > img ul.sidenav > li#sidenav_digged > a > img
ul.sidenav > li#sidenav_history > a > img ul.sidenav > li#sidenav_history > a > img
li#sidenav_more > div.dropdown-button > a > img li#sidenav_more > div.dropdown-button > a > img
ul.sidenav > li.sidenav-item > a.feedback > img ul.sidenav > li.sidenav-item > a.feedback > img
ul.sidenav > li#dark_switch > a > img ul.sidenav > li#dark_switch > a > img
div#side_right > div#cnblogs_b1 > a > img div#side_right > div#cnblogs_b1 > a > img
div#side_right > div#cnblogs_b2 > a > img div#side_right > div#cnblogs_b2 > a > img
div#side_right > div#cnblogs_b3 > a > img div#side_right > div#cnblogs_b3 > a > img
div#side_right > div#cnblogs_b4 > a > img div#side_right > div#cnblogs_b4 > a > img
div#footer_bottom > div.beian > a.gongan > img div#footer_bottom > div.beian > a.gongan > img

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > div#wrapper > a body > div#wrapper > a
div#side_nav > ul.sidenav > li#dark_switch > a div#side_nav > ul.sidenav > li#dark_switch > a
div#main > div#side_right > div#cnblogs_b1 > a div#main > div#side_right > div#cnblogs_b1 > a
div#main > div#side_right > div#cnblogs_b2 > a div#main > div#side_right > div#cnblogs_b2 > a
div#main > div#side_right > div#cnblogs_b3 > a div#main > div#side_right > div#cnblogs_b3 > a
div#main > div#side_right > div#cnblogs_b4 > a div#main > div#side_right > div#cnblogs_b4 > a

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul#nav_right > li > form#zzk_search > input#zzk_search_input ul#nav_right > li > form#zzk_search > input#zzk_search_input

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
搜索 ul#nav_right > li > form#zzk_search > button#zzk_search_button
» div.card > ul > li > a.right_more
» div.card > ul > li > a.right_more
» div.card > ul > li > a.right_more
» div.card > ul > li > a.right_more

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
Buttons have an accessible name
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Heading elements appear in a sequentially-descending order
Deprecated ARIA roles were not used
Uses ARIA roles only on compatible elements
Identical links have the same purpose.
`[accesskey]` values are unique
`[aria-*]` attributes match their roles
`button`, `link`, and `menuitem` elements have accessible names
ARIA attributes are used as specified for the element's role
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
`[aria-hidden="true"]` elements do not contain focusable descendents
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements use only permitted ARIA attributes
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Image elements do not have `[alt]` attributes that are redundant text.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
77

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
Access to script at 'https://cdn-www.cnblogs.com/ng/main-ia2uqgxu.js' from origin 'https://www.cnblogs.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Access to script at 'https://cdn-www.cnblogs.com/ng/polyfills-jq6heycx.js' from origin 'https://www.cnblogs.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
Failed to load resource: net::ERR_FAILED
Failed to load resource: net::ERR_FAILED
Uses HTTPS
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Use a strong HSTS policy
Ensure proper origin isolation with COOP
Mitigate clickjacking with XFO or CSP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
85

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
nav#nav_main > ul#nav_right > li#navbar_login_status > a#navbar_lite_mode_indicator
简洁模式 ... li#navbar_login_status > div#user_info > div#navbar_menu > a#navbar_lite_mode_toggle
退出登录 li#navbar_login_status > div#user_info > div#navbar_menu > a
发现 ul.navbar-list > li.dropdown > div.dropdown-button > a
退出 ul.navbar-list > li#user_info_mobile > div.dropdown-menu > a
更多 ul.sidenav > li#sidenav_more > div.dropdown-button > a
div#side_nav > ul.sidenav > li#dark_switch > a div#side_nav > ul.sidenav > li#dark_switch > a
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19890716
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19904194
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19903757
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19897604
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19903938
1 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19903842
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19903293
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19903270
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19902860
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19902842
3 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19902722
2 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19902693
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19902643
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19902499
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19901906
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19901796
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19901456
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19901328
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19899804
0 article.post-item > section.post-item-body > footer.post-item-foot > a#digg_control_19899767

To appear in search results, crawlers need access to your app.

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul#nav_left > li.dropdown > div.dropdown-button > img ul#nav_left > li.dropdown > div.dropdown-button > img
div#wrapper > a > div.imagebar > img div#wrapper > a > div.imagebar > img
ul.sidenav > li#sidenav_category > a > img ul.sidenav > li#sidenav_category > a > img
ul.sidenav > li#sidenav_pick > a > img ul.sidenav > li#sidenav_pick > a > img
ul.sidenav > li#sidenav_candidate > a > img ul.sidenav > li#sidenav_candidate > a > img
ul.sidenav > li#sidenav_subscription > a > img ul.sidenav > li#sidenav_subscription > a > img
ul.sidenav > li#sidenav_following > a > img ul.sidenav > li#sidenav_following > a > img
ul.sidenav > li#sidenav_commented > a > img ul.sidenav > li#sidenav_commented > a > img
ul.sidenav > li#sidenav_digged > a > img ul.sidenav > li#sidenav_digged > a > img
ul.sidenav > li#sidenav_history > a > img ul.sidenav > li#sidenav_history > a > img
li#sidenav_more > div.dropdown-button > a > img li#sidenav_more > div.dropdown-button > a > img
ul.sidenav > li.sidenav-item > a.feedback > img ul.sidenav > li.sidenav-item > a.feedback > img
ul.sidenav > li#dark_switch > a > img ul.sidenav > li#dark_switch > a > img
div#side_right > div#cnblogs_b1 > a > img div#side_right > div#cnblogs_b1 > a > img
div#side_right > div#cnblogs_b2 > a > img div#side_right > div#cnblogs_b2 > a > img
div#side_right > div#cnblogs_b3 > a > img div#side_right > div#cnblogs_b3 > a > img
div#side_right > div#cnblogs_b4 > a > img div#side_right > div#cnblogs_b4 > a > img
div#footer_bottom > div.beian > a.gongan > img div#footer_bottom > div.beian > a.gongan > img

Format your HTML in a way that enables crawlers to better understand your app’s content.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links have descriptive text
robots.txt is valid
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback