Skip to content
Audit Complete

Results for https://dedecms.com

Visit site
Netherlands Netherlands · Amsterdam Completed: Apr 22, 2026 22:25 UTC
Download JSON 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)
C74

Site Health

Score: 74 / 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.

Solid SEO basics — a few optimizations could boost rankings.

Good server performance with room for optimization.

Mostly compliant — a few items need attention.

Missing metadata means poor previews on social media and search.

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

Bootstrap · 823 peers
You 74
·
Avg 73
At average
0 50 100
Better than 55% of Bootstrap sites See full Bootstrap benchmark →
Bootstrap Icons · 27 peers
You 74
·
Avg 72
At average
0 50 100
Better than 77% of Bootstrap Icons sites See full Bootstrap Icons 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

HSTS header is missing

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

Security › Security Headers
3

No Content-Security-Policy header found

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

Security › Content Security Policy
4

1 button(s) with no accessible text

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

Accessibility › Link & Button Quality
5

13 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

3

High impact, low effort — start here.

Strategic

2

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%2Fdedecms.com)](https://beavercheck.com/results/46f8a1b2-560d-46dc-a493-7a446817fc02)
<a href="https://beavercheck.com/results/46f8a1b2-560d-46dc-a493-7a446817fc02"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fdedecms.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fdedecms.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.

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

Conversion Barriers

8 warning

8 barrier(s) likely increasing bounce by ~23%.

Speed (1)

Page loads in 3.2s

+5% bounce

Every additional 100ms above 2.5s costs conversions — you're 658ms over

Fix: Target <2.5s LCP: defer non-critical scripts and optimize the hero image

Trust (2)

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 (3)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

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, …)

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Navigation (2)

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

2 broken link(s) on the page

+3% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

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

Return on Investment

¥1,575 investment → ¥4,604/month returns + CNY 50,000,000 risk avoided

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

Investment

¥1,575

4h · 5 findings

Monthly returns

¥4,604 /mo

~¥55,244 / year

  • Conversions recovered ¥4,603
  • Bandwidth savings ¥0.65

Regulatory risk avoided

CNY 50,000,000

if kept compliant

  • PIPL CNY 50,000,000

Payback period

0 12mo 24mo

¥525 — 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,575

4.5 developer hours at ¥350/hr

Based on China rates (¥350/hr)

Quick wins
¥525 3 fixes in ~90 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,667 / month at risk

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

Compliance Risk

¥50,000,000

PIPL
  • No privacy policy link detected
    PIPL: CNY 100,000 – CNY 50,000,000
  • Privacy Policy not detected
    PIPL: CNY 100,000 – CNY 50,000,000

Bandwidth Waste

¥0.65 /mo

1146.2 MB/mo × 0.571 CNY/GB

  • Optimize transfer: save ~115 KB per page load
    Saves ¥0.65/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.

90
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
75
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
83
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.

1.53 s

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

3.16 s

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

23 ms

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

0.004

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

4.63 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.17 s

Detailed Report

Audit breakdown by category with detailed findings.

90

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.

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
dedecms.com/assets/img/jpg/common/footer/qiyeweixin.jpg0.0 ms131.1 KiB
dedecms.com/assets/img/jpg/common/index_bannerbg.jpg0.0 ms101.2 KiB
dedecms.com/assets/pkg/jquery/jquery.min.js?v=17290609350.0 ms30.9 KiB
dedecms.com/assets/pkg/bootstrap-5.2.3-dist/css/bootstrap.min.css?v=17290627790.0 ms27.3 KiB
/assets/pkg/bootstrap-5.2.3-dist/js/bootstrap.bundle.min....0.0 ms23.4 KiB
dedecms.com/assets/pkg/bootstrap-icons/font/bootstrap-icons.css?v=17290627790.0 ms13.6 KiB
dedecms.com/assets/img/jpg/common/footer/gongzhonghao.jpg0.0 ms7.3 KiB
dedecms.com/assets/img/png/common/header/logo@2x.png0.0 ms7.1 KiB
dedecms.com/assets/pkg/toast/toast.js?v=17290609350.0 ms2.7 KiB
dedecms.com/assets/img/png/index/icon_product07.png0.0 ms2.3 KiB
dedecms.com/assets/img/png/index/icon_product06.png0.0 ms2.3 KiB
dedecms.com/assets/img/png/index/icon_product03.png0.0 ms2.1 KiB
dedecms.com/assets/img/png/index/icon_product08.png0.0 ms2.1 KiB
dedecms.com/assets/img/png/index/icon_product02.png0.0 ms2.1 KiB
dedecms.com/assets/img/png/index/icon_product05.png0.0 ms2.0 KiB
dedecms.com/assets/img/png/index/icon_product04.png0.0 ms1.9 KiB
dedecms.com/assets/img/png/index/icon_product01.png0.0 ms1.9 KiB
dedecms.com/assets/pkg/jquery-cookie/jquery.cookie.js?v=17290609350.0 ms1.8 KiB
dedecms.com/assets/beian.png0.0 ms1.8 KiB
dedecms.com/assets/js/dedecms.common.min.js?v=17290609350.0 ms1.2 KiB
dedecms.com/assets/css/common.css?v=17290627790.0 ms1.0 KiB
dedecms.com/assets/css/index.css?v=17290627790.0 ms697 B

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:1268.655 label:Time to first byte subpart:timeToFirstByte] map[duration:729.705 label:Resource load delay subpart:resourceLoadDelay] map[duration:1197.385 label:Resource load duration subpart:resourceLoadDuration] map[duration:48.237 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-SECTION
nodeLabel: DedeCMS V5.7.118 正式版下载 Nginx/IIS/Apache PHP5.6+ MySQL5.7+ 更新于 2025-07-30 购买授…
path: 1,HTML,1,BODY,1,SECTION
selector: body > section.container-fluid
snippet: <section class="container-fluid dede-banner" style="background: url(/assets/img/jpg/common/index_bannerbg.jpg);">

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-SECTION
nodeLabel: DedeCMS V5.7.118 正式版下载 Nginx/IIS/Apache PHP5.6+ MySQL5.7+ 更新于 2025-07-30 购买授…
path: 1,HTML,1,BODY,1,SECTION
selector: body > section.container-fluid
snippet: <section class="container-fluid dede-banner" style="background: url(/assets/img/jpg/common/index_bannerbg.jpg);">

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

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.

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.col-12 > div.d-flex > div.ms-3 > img div.col-12 > div.d-flex > div.ms-3 > img
dedecms.com/assets/img/jpg/common/footer/qiyeweixin.jpg130.6 KiB124.7 KiB
div.col-12 > div.d-flex > div.text-center > img div.col-12 > div.d-flex > div.text-center > img
dedecms.com/assets/img/jpg/common/footer/gongzhonghao.jpg6.8 KiB4.5 KiB

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

Diagnostics

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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: 150 ms 21.7 KiB
URLTransfer SizeEst Savings
dedecms.com/assets/pkg/jquery/jquery.min.js?v=172906093530.4 KiB21.7 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
div.col-12 > div.d-flex > div.ms-3 > img div.col-12 > div.d-flex > div.ms-3 > img
dedecms.com/assets/img/jpg/common/footer/qiyeweixin.jpg
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
dedecms.com/assets/img/png/index/icon_product02.png
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
dedecms.com/assets/img/png/index/icon_product03.png
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
dedecms.com/assets/img/png/index/icon_product06.png
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
dedecms.com/assets/img/png/index/icon_product07.png
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
dedecms.com/assets/img/png/index/icon_product01.png
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
dedecms.com/assets/img/png/index/icon_product04.png
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
dedecms.com/assets/img/png/index/icon_product05.png
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
dedecms.com/assets/img/png/index/icon_product08.png
div.col-12 > div.d-flex > div.text-center > img div.col-12 > div.d-flex > div.text-center > img
dedecms.com/assets/img/jpg/common/footer/gongzhonghao.jpg

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

Time to Interactive 3.2 s
Max Potential First Input Delay 70 ms
Layout shift culprits
Document request latency
Optimize DOM size
Font display
Forced reflow
Optimize viewport for mobile
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 373 KiB
JavaScript execution time 0.1 s
Minimizes main-thread work 1.0 s
Avoid long main-thread tasks 3 long tasks found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 220 ms
Server Backend Latencies 90 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 310 ms
Avoid large layout shifts 1 layout shift found
INP breakdown
User Timing marks and measures
Avoid non-composited animations
75

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header.bg-light > nav.navbar > div.container > button.navbar-toggler header.bg-light > nav.navbar > div.container > button.navbar-toggler

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
nav.navbar > div.container > a.navbar-brand > img nav.navbar > div.container > a.navbar-brand > img
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.col-12 > div.d-flex > div.text-center > img div.col-12 > div.d-flex > div.text-center > img
div.col-12 > div.d-flex > div.ms-3 > img div.col-12 > div.d-flex > div.ms-3 > img
div.container > div.text-center > a > img div.container > div.text-center > a > 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
header.bg-light > nav.navbar > div.container > a.navbar-brand header.bg-light > nav.navbar > div.container > a.navbar-brand

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.

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
购买授权 section.container-fluid > div.py-5 > div.mt-4 > a.btn
产品下载 section.container-fluid > div.py-5 > div.mt-4 > a.btn
© 2023 DesDev Inc. All rights reserved Powered by DedeCMS 沪ICP备17008595号 沪公网安备… footer.mt-5 > div.dede-copyright > div.container > div.text-center
DesDev Inc div.dede-copyright > div.container > div.text-center > a
DedeCMS div.dede-copyright > div.container > div.text-center > a
沪ICP备17008595号 div.dede-copyright > div.container > div.text-center > a
沪公网安备31011802005130号 div.dede-copyright > div.container > div.text-center > a
蓝队云 div.dede-copyright > div.container > div.text-center > a

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
用户口碑 div.col-6 > div.card > div.card-body > h5.card-title

These are opportunities to improve keyboard navigation in your application.

Best practices

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-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
Elements use only permitted ARIA attributes
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
Touch targets have sufficient size and spacing.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Deprecated ARIA roles were not used
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
`[role]`s have all required `[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
`[role]` values are valid
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
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
Form elements have associated labels
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
`<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.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
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.
96

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
div.container > div.text-center > a > img div.container > div.text-center > a > img
dedecms.com/assets/beian.png20 x 20 (1.00)36 x 40 (0.90)
Uses HTTPS
Avoids deprecated APIs
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
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
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
83

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

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #ContentError
1<!DOCTYPE html>Syntax not understood
2<html lang="zh-CN">Syntax not understood
4<head>Syntax not understood
5 <title>织梦 (DedeCMS) 官方网站 - 内容管理系统 - 上海卓卓网络科技有限公司</title>Syntax not understood
7 <meta charset="utf-8">Syntax not understood
8<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">Syntax not understood
9<meta name="description" content="织梦 (DedeCMS) 官方网站 - 内容管理系统 - 上海卓卓网络科技有限公司">Syntax not understood
10<meta name="keywords" content="织梦,dedecms">Syntax not understood
12 <link rel="shortcut icon" type="image/x-icon" href="/assets/favicon.ico">Syntax not understood
13<link rel="stylesheet" type="text/css" href="/assets/pkg/bootstrap-5.2.3-dist/css/bootstrap.min.css?v=1729062779">Syntax not understood
14<link rel="stylesheet" type="text/css" href="/assets/pkg/bootstrap-icons/font/bootstrap-icons.css?v=1729062779">Syntax not understood
15<link rel="stylesheet" type="text/css" href="/assets/css/common.css?v=1729062779">Syntax not understood
16 <link rel="stylesheet" type="text/css" href="/assets/css/index.css?v=1729062779">Syntax not understood
17</head>Syntax not understood
19<body>Syntax not understood
20 <header class="bg-light">Syntax not understood
21 <div class="container">Syntax not understood
22 <div class="row text-secondary pt-1">Syntax not understood
23 <div class="col-12 col-lg-9 d-none d-lg-block">Syntax not understood
24 <span class="fs-6 fw-light">织梦 (DedeCMS) 官方网站 - 内容管理系统 - 上海卓卓网络科技有限公司</span>Syntax not understood
25 </div>Syntax not understood
27 <div class="col-12 col-lg-3 text-end d-none d-lg-block">Syntax not understood
28 <span class="fs-6 fw-light"><i class="bi bi-telephone-fill"></i> 021-37788569</span>Syntax not understood
29 </div>Syntax not understood
30 </div>Syntax not understood
31 </div>Syntax not understood
33 <nav class="navbar navbar-expand-xl" aria-label="Offcanvas navbar large">Syntax not understood
34 <div class="container">Syntax not understood
35 <a class="navbar-brand" href="/">Syntax not understood
36 <img src="/assets/img/png/common/header/logo@2x.png" width="227px" height="40px">Syntax not understood
37 </a>Syntax not understood
39 <button class="navbar-toggler" type="button" data-bs-toggle="offcanvas" data-bs-target="#offcanvasNavbar2"Syntax not understood
40 aria-controls="offcanvasNavbar2">Syntax not understood
41 <span class="navbar-toggler-icon"></span>Syntax not understood
42 </button>Syntax not understood
44 <div class="offcanvas offcanvas-start" tabindex="-1" id="offcanvasNavbar2"Syntax not understood
45 aria-labelledby="offcanvasNavbar2Label">Syntax not understood
46 <div class="offcanvas-header">Syntax not understood
47 <h5 class="offcanvas-title" id="offcanvasNavbar2Label">Syntax not understood
48 <a class="navbar-brand" href="/">Syntax not understood
49 <img src="/assets/img/png/common/header/logo@2x.png" width="227px" height="40px">Syntax not understood
50 </a>Syntax not understood
51 </h5>Syntax not understood
53 <button type="button" class="btn-close" data-bs-dismiss="offcanvas" aria-label="Close"></button>Syntax not understood
54 </div>Syntax not understood
56 <div class="offcanvas-body">Syntax not understood
57 <ul class="navbar-nav justify-content-start flex-grow-1 ms-xl-5">Syntax not understood
58 <li class="nav-item border-bottom">Syntax not understood
59 <a class="nav-link px-2 px-xxl-3 active"Syntax not understood
60 href="/">Syntax not understood
61 首页Syntax not understood
62 </a>Syntax not understood
63 </li>Syntax not understood
64 <li class="nav-item border-bottom">Syntax not understood
65 <a class="nav-link px-2 px-xxl-3" href="/download">Syntax not understood
66 产品下载Syntax not understood
67 </a>Syntax not understood
68 </li>Syntax not understood
69 <li class="nav-item border-bottom">Syntax not understood
70 <a class="nav-link px-2 px-xxl-3" href="/license">Syntax not understood
71 开源协议Syntax not understood
72 </a>Syntax not understood
73 </li>Syntax not understood
74 <li class="nav-item border-bottom">Syntax not understood
75 <a class="nav-link px-2 px-xxl-3" href="/authorization/search">Syntax not understood
76 授权查询Syntax not understood
77 </a>Syntax not understood
78 </li>Syntax not understood
79 <li class="nav-item border-bottom">Syntax not understood
80 <a class="nav-link px-2 px-xxl-3" href="/authorization">Syntax not understood
81 正版授权Syntax not understood
82 </a>Syntax not understood
83 </li>Syntax not understood
84 <li class="nav-item border-bottom">Syntax not understood
85 <a class="nav-link px-2 px-xxl-3" href="https://site.dedecms.com/">Unknown directive
86 网站定制Syntax not understood
87 </a>Syntax not understood
88 </li>Syntax not understood
89 <li class="nav-item dropdown border-bottom">Syntax not understood
90 <a class="nav-link dropdown-toggle px-2 px-xxl-3" href="#"Syntax not understood
91 role="button" data-bs-toggle="dropdown" aria-expanded="false">Syntax not understood
92 增值服务Syntax not understood
93 </a>Syntax not understood
94 <ul class="dropdown-menu">Syntax not understood
95 <li><a class="dropdown-item" href="/support#package">套餐服务</a></li>Syntax not understood
96 <li><a class="dropdown-item" href="/support#price">单项服务</a></li>Syntax not understood
97 <li>Syntax not understood
98 </ul>Syntax not understood
99 </li>Syntax not understood
100 <li class="nav-item border-bottom">Syntax not understood
101 <a class="nav-link px-2 px-xxl-3" href="/hosts">Syntax not understood
102 推荐主机Syntax not understood
103 </a>Syntax not understood
104 </li>Syntax not understood
105 <li class="nav-item border-bottom">Syntax not understood
106 <a class="nav-link px-2 px-xxl-3" href="https://help.dedecms.com/">Unknown directive
107 帮助中心Syntax not understood
108 </a>Syntax not understood
109 </li>Syntax not understood
110 </ul>Syntax not understood
113 <div class="text-start mt-3 mt-xl-0 text-xl-end">Syntax not understood
114 <a href="/register" class="btn btn-success px-4 px-xl-3 me-1">注册</a>Syntax not understood
115 <a href="/login" class="btn btn-outline-secondary px-4 px-xl-3">登录</a>Syntax not understood
116 </div>Syntax not understood
118 </div>Syntax not understood
119 </div>Syntax not understood
120 </div>Syntax not understood
121 </nav>Syntax not understood
122</header>Syntax not understood
124 <section class="container-fluid dede-banner" style="background: url(/assets/img/jpg/common/index_bannerbg.jpg);">Unknown directive
125 <div class="py-5 px-4 text-center">Syntax not understood
126 <h1 class="mt-4 display-6 fw-semibold text-white">DedeCMS V5.7.118 正式版下载</h1>Syntax not understood
128 <p class="mt-4 fs-5 text-light">Nginx/IIS/Apache PHP5.6+ MySQL5.7+</p>Syntax not understood
130 <p class="mt-4 fs-4 text-light">更新于 2025-07-30</p>Syntax not understood
132 <div class="mt-4 d-grid gap-2 d-sm-flex justify-content-sm-center">Syntax not understood
133 <a href="/user/authorization/license" class="btn btn-lg btn-primary px-5 me-sm-3"Syntax not understood
134 style="background-color: #FF6700; border-color: #FF6700;">购买授权</a>Unknown directive
135 <a href="/download" class="btn btn-lg btn-primary px-5"Syntax not understood
136 style="background-color: #FF6700; border-color: #FF6700;">产品下载</a>Unknown directive
137 </div>Syntax not understood
139 <div class="mt-4 mb-4">Syntax not understood
140 <p class="mb-1">Syntax not understood
141 <a target="_blank" href="/post/20211026.html" class="text-light text-decoration-none">Syntax not understood
142 关于侵权网站清单及存证数据移交维权团队的通告Syntax not understood
143 </a>Syntax not understood
144 <span class="badge text-bg-danger">New</span>Syntax not understood
145 </p>Syntax not understood
146 <p class="mb-0">Syntax not understood
147 <a target="_blank" href="/post/20210930.html" class="text-light text-decoration-none">Syntax not understood
148 致广大DedeCMS用户的一封公开信Syntax not understood
149 </a>Syntax not understood
150 </p>Syntax not understood
151 </div>Syntax not understood
152 </div>Syntax not understood
153 </section>Syntax not understood
155 <section class="container mt-5 dede-feature">Syntax not understood
156 <div class="row text-center">Syntax not understood
157 <div class="col-12">Syntax not understood
158 <h2>产品特性</h2>Syntax not understood
159 <span class="text-muted">了解更多产品功能特性</span>Syntax not understood
160 <div class="position-relative">Syntax not understood
161 <span class="dede-title-points"></span>Syntax not understood
162 </div>Syntax not understood
163 </div>Syntax not understood
164 </div>Syntax not understood
166 <div class="row text-center">Syntax not understood
167 <div class="col-6 col-lg-3 mt-3 mt-lg-4">Syntax not understood
168 <div class="card py-3 py-lg-4">Syntax not understood
169 <img src="/assets/img/png/index/icon_product01.png" class="card-img-top w-50 align-self-center">Syntax not understood
170 <div class="card-body">Syntax not understood
171 <h5 class="card-title">用户口碑</h5>Syntax not understood
172 <p class="card-text">Syntax not understood
173 丰富的开源经验赢得<br>良好的口碑Syntax not understood
174 </p>Syntax not understood
175 </div>Syntax not understood
176 </div>Syntax not understood
177 </div>Syntax not understood
179 <div class="col-6 col-lg-3 mt-3 mt-lg-4">Syntax not understood
180 <div class="card py-3 py-lg-4">Syntax not understood
181 <img src="/assets/img/png/index/icon_product02.png" class="card-img-top w-50 align-self-center">Syntax not understood
182 <div class="card-body">Syntax not understood
183 <h5 class="card-title">模块组合</h5>Syntax not understood
184 <p class="card-text">Syntax not understood
185 让网站丰富方便<br>网站扩展Syntax not understood
186 </p>Syntax not understood
187 </div>Syntax not understood
188 </div>Syntax not understood
189 </div>Syntax not understood
191 <div class="col-6 col-lg-3 mt-3 mt-lg-4">Syntax not understood
192 <div class="card py-3 py-lg-4">Syntax not understood
193 <img src="/assets/img/png/index/icon_product03.png" class="card-img-top w-50 align-self-center">Syntax not understood
194 <div class="card-body">Syntax not understood
195 <h5 class="card-title">模板引擎</h5>Syntax not understood
196 <p class="card-text">Syntax not understood
197 简单易用<br>界面随时可更换Syntax not understood
198 </p>Syntax not understood
199 </div>Syntax not understood
200 </div>Syntax not understood
201 </div>Syntax not understood
203 <div class="col-6 col-lg-3 mt-3 mt-lg-4">Syntax not understood
204 <div class="card py-3 py-lg-4">Syntax not understood
205 <img src="/assets/img/png/index/icon_product04.png" class="card-img-top w-50 align-self-center">Syntax not understood
206 <div class="card-body">Syntax not understood
207 <h5 class="card-title">自定义模型</h5>Syntax not understood
208 <p class="card-text">Syntax not understood
209 自己扩展网站后续功能<br>省去诸多烦恼Syntax not understood
210 </p>Syntax not understood
211 </div>Syntax not understood
212 </div>Syntax not understood
213 </div>Syntax not understood
215 <div class="col-6 col-lg-3 mt-3 mt-lg-4">Syntax not understood
216 <div class="card py-3 py-lg-4">Syntax not understood
217 <img src="/assets/img/png/index/icon_product05.png" class="card-img-top w-50 align-self-center">Syntax not understood
218 <div class="card-body">Syntax not understood
219 <h5 class="card-title">动静态部署</h5>Syntax not understood
220 <p class="card-text">Syntax not understood
221 高效的页面部署<br>提高网站收录量Syntax not understood
222 </p>Syntax not understood
223 </div>Syntax not understood
224 </div>Syntax not understood
225 </div>Syntax not understood
227 <div class="col-6 col-lg-3 mt-3 mt-lg-4">Syntax not understood
228 <div class="card py-3 py-lg-4">Syntax not understood
229 <img src="/assets/img/png/index/icon_product06.png" class="card-img-top w-50 align-self-center">Syntax not understood
230 <div class="card-body">Syntax not understood
231 <h5 class="card-title">升级无忧</h5>Syntax not understood
232 <p class="card-text">Syntax not understood
233 及时和官方程序同步<br>安全无忧Syntax not understood
234 </p>Syntax not understood
235 </div>Syntax not understood
236 </div>Syntax not understood
237 </div>Syntax not understood
239 <div class="col-6 col-lg-3 mt-3 mt-lg-4">Syntax not understood
240 <div class="card py-3 py-lg-4">Syntax not understood
241 <img src="/assets/img/png/index/icon_product07.png" class="card-img-top w-50 align-self-center">Syntax not understood
242 <div class="card-body">Syntax not understood
243 <h5 class="card-title">强大的SEO</h5>Syntax not understood
244 <p class="card-text">Syntax not understood
245 灵活调整<br>提升关键词排名Syntax not understood
246 </p>Syntax not understood
247 </div>Syntax not understood
248 </div>Syntax not understood
249 </div>Syntax not understood
251 <div class="col-6 col-lg-3 mt-3 mt-lg-4">Syntax not understood
252 <div class="card py-3 py-lg-4">Syntax not understood
253 <img src="/assets/img/png/index/icon_product08.png" class="card-img-top w-50 align-self-center">Syntax not understood
254 <div class="card-body">Syntax not understood
255 <h5 class="card-title">安全可靠</h5>Syntax not understood
256 <p class="card-text">Syntax not understood
257 十六年持续迭代<br>十万加用户共同见证Syntax not understood
258 </p>Syntax not understood
259 </div>Syntax not understood
260 </div>Syntax not understood
261 </div>Syntax not understood
262 </div>Syntax not understood
263 </section>Syntax not understood
265 <footer class="mt-5" >Syntax not understood
266 <div class="dede-footer">Syntax not understood
267 <div class="container">Syntax not understood
268 <div class="row py-5">Syntax not understood
269 <div class="col-12 col-lg-7 text-white-50">Syntax not understood
270 <div class="row">Syntax not understood
271 <div class="col-12 col-md-auto">Syntax not understood
272 <divSyntax not understood
273 class="d-flex flex-row flex-wrap align-content-start justify-content-start align-items-start">Syntax not understood
274 <div class="text-center">Syntax not understood
275 <img src="/assets/img/jpg/common/footer/gongzhonghao.jpg" width="120px"><br>Syntax not understood
276 <span class="d-block mt-2">微信公众号</span>Syntax not understood
277 </div>Syntax not understood
279 <div class=" ms-3 text-center">Syntax not understood
280 <img src="/assets/img/jpg/common/footer/qiyeweixin.jpg" width="120px"><br>Syntax not understood
281 <span class="d-block mt-2">微信客服</span>Syntax not understood
282 </div>Syntax not understood
283 </div>Syntax not understood
285 </div>Syntax not understood
287 <div class="col-12 col-md mt-3 mt-sm-4 mt-md-0">Syntax not understood
288 <h5 class="fs-5 text-white">Syntax not understood
289 <a class="text-white text-decoration-none" href="tel:021-37788569"Unknown directive
290 target="_blank">021-37788569</a>Syntax not understood
291 </h5>Syntax not understood
292 <span class="text-white-50 fs-6 fw-light">商务咨询电话</span>Syntax not understood
294 <table class="text-white-50 fs-6 fw-light">Syntax not understood
295 <tr>Syntax not understood
296 <td>工作时间:</td>Syntax not understood
297 <td>周一至周五</td>Syntax not understood
298 </tr>Syntax not understood
299 <tr>Syntax not understood
300 <td></td>Syntax not understood
301 <td>8:30~11:30至13:30~18:00</td>Unknown directive
302 </tr>Syntax not understood
303 </table>Syntax not understood
304 </div>Syntax not understood
305 </div>Syntax not understood
306 </div>Syntax not understood
309 <div class="col-12 col-lg-5 mt-3 mt-sm-4 mt-md-4 mt-lg-0">Syntax not understood
310 <div class="row row-cols-3">Syntax not understood
311 <div>Syntax not understood
312 <h5 class="text-white">技术支持</h5>Syntax not understood
313 <ul class="nav flex-column">Syntax not understood
314 <li class="nav-item mb-2"><a href="https://help.dedecms.com/" class="nav-link p-0 text-white-50">帮助中心</a>Unknown directive
315 </li>Syntax not understood
316 <li class="nav-item mb-2"><a href="https://help.dedecms.com/changjianwenti/" class="nav-link p-0 text-white-50">常见问题</a>Unknown directive
317 </li>Syntax not understood
318 <li class="nav-item mb-2"><a href="https://help.dedecms.com/chujie/" class="nav-link p-0 text-white-50">使用手册</a>Unknown directive
319 </li>Syntax not understood
320 <li class="nav-item mb-2"><a href="https://help.dedecms.com/mubanshouce/" class="nav-link p-0 text-white-50">模板手册</a>Unknown directive
321 </li>Syntax not understood
322 </ul>Syntax not understood
323 </div>Syntax not understood
325 <div>Syntax not understood
326 <h5 class="text-white">服务支持</h5>Syntax not understood
327 <ul class="nav flex-column">Syntax not understood
328 <li class="nav-item mb-2"><a href="/license" class="nav-link p-0 text-white-50">授权协议</a>Syntax not understood
329 </li>Syntax not understood
330 <li class="nav-item mb-2"><a href="/authorization/search"Syntax not understood
331 class="nav-link p-0 text-white-50">授权查询</a>Syntax not understood
332 </li>Syntax not understood
333 <li class="nav-item mb-2"><a href="/authorization"Syntax not understood
334 class="nav-link p-0 text-white-50">购买流程</a>Syntax not understood
335 </li>Syntax not understood
336 <li class="nav-item mb-2"><a href="/authorization"Syntax not understood
337 class="nav-link p-0 text-white-50">授权说明</a>Syntax not understood
338 </li>Syntax not understood
339 </ul>Syntax not understood
340 </div>Syntax not understood
342 <div>Syntax not understood
343 <h5 class="text-white">关于我们</h5>Syntax not understood
344 <ul class="nav flex-column">Syntax not understood
345 <li class="nav-item mb-2"><a href="#" class="nav-link p-0 text-white-50">公司简介</a>Syntax not understood
346 </li>Syntax not understood
347 <li class="nav-item mb-2"><a href="#" class="nav-link p-0 text-white-50">招贤纳士</a>Syntax not understood
348 </li>Syntax not understood
349 <li class="nav-item mb-2"><a href="#" class="nav-link p-0 text-white-50">联系我们</a>Syntax not understood
350 </li>Syntax not understood
351 <li class="nav-item mb-2"><a href="https://site.dedecms.com/youqingzhanshi/" class="nav-link p-0 text-white-50">友情展示</a>Unknown directive
352 </li>Syntax not understood
353 </ul>Syntax not understood
354 </div>Syntax not understood
355 </div>Syntax not understood
356 </div>Syntax not understood
357 </div>Syntax not understood
358 </div>Syntax not understood
359 </div>Syntax not understood
361 <div class="dede-copyright">Syntax not understood
362 <div class="container">Syntax not understood
363 <div class="text-center py-4" style="font-size: 14px !important;">Unknown directive
364 © 2023 <a href="http://www.desdev.cn">DesDev Inc</a>.Unknown directive
365 All rights reserved Powered bySyntax not understood
366 <a href="http://www.dedecms.com">DedeCMS</a><br>Unknown directive
367 <a href="http://beian.miit.gov.cn/" title="沪ICP备17008595号" rel="noopener noreferrer"Unknown directive
368 target="_blank">沪ICP备17008595号</a>Syntax not understood
369 <a href="https://www.beian.gov.cn/portal/registerSystemInfo?recordcode=31011802005130" title="沪公网安备31011802005130号" rel="noopener noreferrer"Unknown directive
370 target="_blank">Syntax not understood
371 <img src="/assets/beian.png" width="20px" height="20px">Syntax not understood
372 沪公网安备31011802005130号Syntax not understood
373 </a><br>Syntax not understood
375 云主机支持:Unknown directive
376 <a href="https://www.landui.com/" title="蓝队云" rel="noopener noreferrer" target="_blank">蓝队云</a>Unknown directive
377 </div>Syntax not understood
378 </div>Syntax not understood
379 </div>Syntax not understood
380</footer>Syntax not understood
382 <script type="text/javascript" src="/assets/pkg/jquery/jquery.min.js?v=1729060935"></script>Syntax not understood
383<script type="text/javascript" src="/assets/pkg/jquery-cookie/jquery.cookie.js?v=1729060935"></script>Syntax not understood
384<script type="text/javascript" src="/assets/pkg/bootstrap-5.2.3-dist/js/bootstrap.bundle.min.js?v=1729060935"></script>Syntax not understood
385<script type="text/javascript" src="/assets/pkg/toast/toast.js?v=1729060935"></script>Syntax not understood
386<script type="text/javascript" src="/assets/js/dedecms.common.min.js?v=1729060935"></script>Syntax not understood
387</body>Syntax not understood
389</html>Syntax not understood

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
nav.navbar > div.container > a.navbar-brand > img nav.navbar > div.container > a.navbar-brand > img
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.col-12 > div.d-flex > div.text-center > img div.col-12 > div.d-flex > div.text-center > img
div.col-12 > div.d-flex > div.ms-3 > img div.col-12 > div.d-flex > div.ms-3 > img
div.container > div.text-center > a > img div.container > div.text-center > a > 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
Links are crawlable
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

96
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
83
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
96
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
83
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.

548 ms

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

976 ms

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.017

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

1.65 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.

976 ms

Detailed Report

Audit breakdown by category with detailed findings.

96

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.

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
dedecms.com/assets/img/jpg/common/footer/qiyeweixin.jpg0.0 ms131.1 KiB
/assets/pkg/bootstrap-icons/font/fonts/bootstrap-icons.wo...0.0 ms118.9 KiB
dedecms.com/assets/img/jpg/common/index_bannerbg.jpg0.0 ms101.2 KiB
dedecms.com/assets/pkg/jquery/jquery.min.js?v=17290609350.0 ms30.9 KiB
dedecms.com/assets/pkg/bootstrap-5.2.3-dist/css/bootstrap.min.css?v=17290627790.0 ms27.3 KiB
/assets/pkg/bootstrap-5.2.3-dist/js/bootstrap.bundle.min....0.0 ms23.4 KiB
dedecms.com/assets/pkg/bootstrap-icons/font/bootstrap-icons.css?v=17290627790.0 ms13.6 KiB
dedecms.com/assets/img/jpg/common/footer/gongzhonghao.jpg0.0 ms7.3 KiB
dedecms.com/assets/img/png/common/header/logo@2x.png0.0 ms7.1 KiB
dedecms.com/assets/pkg/toast/toast.js?v=17290609350.0 ms2.7 KiB
dedecms.com/assets/img/png/index/icon_product07.png0.0 ms2.3 KiB
dedecms.com/assets/img/png/index/icon_product06.png0.0 ms2.3 KiB
dedecms.com/assets/img/png/index/icon_product03.png0.0 ms2.1 KiB
dedecms.com/assets/img/png/index/icon_product08.png0.0 ms2.1 KiB
dedecms.com/assets/img/png/index/icon_product02.png0.0 ms2.1 KiB
dedecms.com/assets/img/png/index/icon_product05.png0.0 ms2.0 KiB
dedecms.com/assets/img/png/index/icon_product04.png0.0 ms1.9 KiB
dedecms.com/assets/img/png/index/icon_product01.png0.0 ms1.9 KiB
dedecms.com/assets/pkg/jquery-cookie/jquery.cookie.js?v=17290609350.0 ms1.8 KiB
dedecms.com/assets/beian.png0.0 ms1.8 KiB
dedecms.com/assets/js/dedecms.common.min.js?v=17290609350.0 ms1.2 KiB
dedecms.com/assets/css/common.css?v=17290627790.0 ms1.0 KiB
dedecms.com/assets/css/index.css?v=17290627790.0 ms697 B

Consider setting 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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.col-12 > div.d-flex > div.ms-3 > img div.col-12 > div.d-flex > div.ms-3 > img
dedecms.com/assets/img/jpg/common/footer/qiyeweixin.jpg130.6 KiB128.7 KiB
nav.navbar > div.container > a.navbar-brand > img nav.navbar > div.container > a.navbar-brand > img
dedecms.com/assets/img/png/common/header/logo@2x.png6.7 KiB5.5 KiB
div.col-12 > div.d-flex > div.text-center > img div.col-12 > div.d-flex > div.text-center > img
dedecms.com/assets/img/jpg/common/footer/gongzhonghao.jpg6.8 KiB4.5 KiB

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:1054.765 label:Time to first byte subpart:timeToFirstByte] map[duration:724.524 label:Resource load delay subpart:resourceLoadDelay] map[duration:750.487 label:Resource load duration subpart:resourceLoadDuration] map[duration:78.024 label:Element render delay subpart:elementRenderDelay]]
lhId: page-3-SECTION
nodeLabel: DedeCMS V5.7.118 正式版下载 Nginx/IIS/Apache PHP5.6+ MySQL5.7+ 更新于 2025-07-30 购买授…
path: 1,HTML,1,BODY,1,SECTION
selector: body > section.container-fluid
snippet: <section class="container-fluid dede-banner" style="background: url(/assets/img/jpg/common/index_bannerbg.jpg);">

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-3-SECTION
nodeLabel: DedeCMS V5.7.118 正式版下载 Nginx/IIS/Apache PHP5.6+ MySQL5.7+ 更新于 2025-07-30 购买授…
path: 1,HTML,1,BODY,1,SECTION
selector: body > section.container-fluid
snippet: <section class="container-fluid dede-banner" style="background: url(/assets/img/jpg/common/index_bannerbg.jpg);">

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

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.

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

Diagnostics

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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 21.7 KiB
URLTransfer SizeEst Savings
dedecms.com/assets/pkg/jquery/jquery.min.js?v=172906093530.4 KiB21.7 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
div.col-12 > div.d-flex > div.ms-3 > img div.col-12 > div.d-flex > div.ms-3 > img
dedecms.com/assets/img/jpg/common/footer/qiyeweixin.jpg
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
dedecms.com/assets/img/png/index/icon_product02.png
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
dedecms.com/assets/img/png/index/icon_product03.png
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
dedecms.com/assets/img/png/index/icon_product06.png
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
dedecms.com/assets/img/png/index/icon_product07.png
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
dedecms.com/assets/img/png/index/icon_product01.png
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
dedecms.com/assets/img/png/index/icon_product04.png
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
dedecms.com/assets/img/png/index/icon_product05.png
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
dedecms.com/assets/img/png/index/icon_product08.png
div.col-12 > div.d-flex > div.text-center > img div.col-12 > div.d-flex > div.text-center > img
dedecms.com/assets/img/jpg/common/footer/gongzhonghao.jpg

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

Layout shift culprits
Document request latency
Optimize DOM size
Forced reflow
Optimize viewport for mobile
Time to Interactive 1.0 s
Max Potential First Input Delay 20 ms
Minify CSS
Minify JavaScript
Avoids enormous network payloads Total size was 492 KiB
JavaScript execution time 0.0 s
Minimizes main-thread work 0.3 s
Avoid long main-thread tasks 1 long task found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 220 ms
Server Backend Latencies 90 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Initial server response time was short Root document took 300 ms
Avoid large layout shifts 5 layout shifts found
INP breakdown
User Timing marks and measures
Avoid non-composited animations
83

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
织梦 (DedeCMS) 官方网站 - 内容管理系统 - 上海卓卓网络科技有限公司 div.container > div.row > div.col-12 > span.fs-6
021-37788569 div.container > div.row > div.col-12 > span.fs-6
登录 div#offcanvasNavbar2 > div.offcanvas-body > div.text-start > a.btn
购买授权 section.container-fluid > div.py-5 > div.mt-4 > a.btn
产品下载 section.container-fluid > div.py-5 > div.mt-4 > a.btn
© 2023 DesDev Inc. All rights reserved Powered by DedeCMS 沪ICP备17008595号 沪公网安备… footer.mt-5 > div.dede-copyright > div.container > div.text-center
DesDev Inc div.dede-copyright > div.container > div.text-center > a
DedeCMS div.dede-copyright > div.container > div.text-center > a
沪ICP备17008595号 div.dede-copyright > div.container > div.text-center > a
沪公网安备31011802005130号 div.dede-copyright > div.container > div.text-center > a
蓝队云 div.dede-copyright > div.container > div.text-center > a

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
用户口碑 div.col-6 > div.card > div.card-body > h5.card-title

These are opportunities to improve keyboard navigation in your application.

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
nav.navbar > div.container > a.navbar-brand > img nav.navbar > div.container > a.navbar-brand > img
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.col-12 > div.d-flex > div.text-center > img div.col-12 > div.d-flex > div.text-center > img
div.col-12 > div.d-flex > div.ms-3 > img div.col-12 > div.d-flex > div.ms-3 > img
div.container > div.text-center > a > img div.container > div.text-center > a > 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
header.bg-light > nav.navbar > div.container > a.navbar-brand header.bg-light > nav.navbar > div.container > a.navbar-brand

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.

Best practices

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-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
Elements use only permitted ARIA attributes
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
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Deprecated ARIA roles were not used
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
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 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
Buttons have an accessible name
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
Form elements have associated labels
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
`<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.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Identical links have the same purpose.
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.
96

Best Practices

User Experience

Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLAspect Ratio (Displayed)Aspect Ratio (Actual)
div.container > div.text-center > a > img div.container > div.text-center > a > img
dedecms.com/assets/beian.png20 x 20 (1.00)36 x 40 (0.90)
Uses HTTPS
Avoids deprecated APIs
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
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
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
83

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

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more about robots.txt.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Line #ContentError
1<!DOCTYPE html>Syntax not understood
2<html lang="zh-CN">Syntax not understood
4<head>Syntax not understood
5 <title>织梦 (DedeCMS) 官方网站 - 内容管理系统 - 上海卓卓网络科技有限公司</title>Syntax not understood
7 <meta charset="utf-8">Syntax not understood
8<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">Syntax not understood
9<meta name="description" content="织梦 (DedeCMS) 官方网站 - 内容管理系统 - 上海卓卓网络科技有限公司">Syntax not understood
10<meta name="keywords" content="织梦,dedecms">Syntax not understood
12 <link rel="shortcut icon" type="image/x-icon" href="/assets/favicon.ico">Syntax not understood
13<link rel="stylesheet" type="text/css" href="/assets/pkg/bootstrap-5.2.3-dist/css/bootstrap.min.css?v=1729062779">Syntax not understood
14<link rel="stylesheet" type="text/css" href="/assets/pkg/bootstrap-icons/font/bootstrap-icons.css?v=1729062779">Syntax not understood
15<link rel="stylesheet" type="text/css" href="/assets/css/common.css?v=1729062779">Syntax not understood
16 <link rel="stylesheet" type="text/css" href="/assets/css/index.css?v=1729062779">Syntax not understood
17</head>Syntax not understood
19<body>Syntax not understood
20 <header class="bg-light">Syntax not understood
21 <div class="container">Syntax not understood
22 <div class="row text-secondary pt-1">Syntax not understood
23 <div class="col-12 col-lg-9 d-none d-lg-block">Syntax not understood
24 <span class="fs-6 fw-light">织梦 (DedeCMS) 官方网站 - 内容管理系统 - 上海卓卓网络科技有限公司</span>Syntax not understood
25 </div>Syntax not understood
27 <div class="col-12 col-lg-3 text-end d-none d-lg-block">Syntax not understood
28 <span class="fs-6 fw-light"><i class="bi bi-telephone-fill"></i> 021-37788569</span>Syntax not understood
29 </div>Syntax not understood
30 </div>Syntax not understood
31 </div>Syntax not understood
33 <nav class="navbar navbar-expand-xl" aria-label="Offcanvas navbar large">Syntax not understood
34 <div class="container">Syntax not understood
35 <a class="navbar-brand" href="/">Syntax not understood
36 <img src="/assets/img/png/common/header/logo@2x.png" width="227px" height="40px">Syntax not understood
37 </a>Syntax not understood
39 <button class="navbar-toggler" type="button" data-bs-toggle="offcanvas" data-bs-target="#offcanvasNavbar2"Syntax not understood
40 aria-controls="offcanvasNavbar2">Syntax not understood
41 <span class="navbar-toggler-icon"></span>Syntax not understood
42 </button>Syntax not understood
44 <div class="offcanvas offcanvas-start" tabindex="-1" id="offcanvasNavbar2"Syntax not understood
45 aria-labelledby="offcanvasNavbar2Label">Syntax not understood
46 <div class="offcanvas-header">Syntax not understood
47 <h5 class="offcanvas-title" id="offcanvasNavbar2Label">Syntax not understood
48 <a class="navbar-brand" href="/">Syntax not understood
49 <img src="/assets/img/png/common/header/logo@2x.png" width="227px" height="40px">Syntax not understood
50 </a>Syntax not understood
51 </h5>Syntax not understood
53 <button type="button" class="btn-close" data-bs-dismiss="offcanvas" aria-label="Close"></button>Syntax not understood
54 </div>Syntax not understood
56 <div class="offcanvas-body">Syntax not understood
57 <ul class="navbar-nav justify-content-start flex-grow-1 ms-xl-5">Syntax not understood
58 <li class="nav-item border-bottom">Syntax not understood
59 <a class="nav-link px-2 px-xxl-3 active"Syntax not understood
60 href="/">Syntax not understood
61 首页Syntax not understood
62 </a>Syntax not understood
63 </li>Syntax not understood
64 <li class="nav-item border-bottom">Syntax not understood
65 <a class="nav-link px-2 px-xxl-3" href="/download">Syntax not understood
66 产品下载Syntax not understood
67 </a>Syntax not understood
68 </li>Syntax not understood
69 <li class="nav-item border-bottom">Syntax not understood
70 <a class="nav-link px-2 px-xxl-3" href="/license">Syntax not understood
71 开源协议Syntax not understood
72 </a>Syntax not understood
73 </li>Syntax not understood
74 <li class="nav-item border-bottom">Syntax not understood
75 <a class="nav-link px-2 px-xxl-3" href="/authorization/search">Syntax not understood
76 授权查询Syntax not understood
77 </a>Syntax not understood
78 </li>Syntax not understood
79 <li class="nav-item border-bottom">Syntax not understood
80 <a class="nav-link px-2 px-xxl-3" href="/authorization">Syntax not understood
81 正版授权Syntax not understood
82 </a>Syntax not understood
83 </li>Syntax not understood
84 <li class="nav-item border-bottom">Syntax not understood
85 <a class="nav-link px-2 px-xxl-3" href="https://site.dedecms.com/">Unknown directive
86 网站定制Syntax not understood
87 </a>Syntax not understood
88 </li>Syntax not understood
89 <li class="nav-item dropdown border-bottom">Syntax not understood
90 <a class="nav-link dropdown-toggle px-2 px-xxl-3" href="#"Syntax not understood
91 role="button" data-bs-toggle="dropdown" aria-expanded="false">Syntax not understood
92 增值服务Syntax not understood
93 </a>Syntax not understood
94 <ul class="dropdown-menu">Syntax not understood
95 <li><a class="dropdown-item" href="/support#package">套餐服务</a></li>Syntax not understood
96 <li><a class="dropdown-item" href="/support#price">单项服务</a></li>Syntax not understood
97 <li>Syntax not understood
98 </ul>Syntax not understood
99 </li>Syntax not understood
100 <li class="nav-item border-bottom">Syntax not understood
101 <a class="nav-link px-2 px-xxl-3" href="/hosts">Syntax not understood
102 推荐主机Syntax not understood
103 </a>Syntax not understood
104 </li>Syntax not understood
105 <li class="nav-item border-bottom">Syntax not understood
106 <a class="nav-link px-2 px-xxl-3" href="https://help.dedecms.com/">Unknown directive
107 帮助中心Syntax not understood
108 </a>Syntax not understood
109 </li>Syntax not understood
110 </ul>Syntax not understood
113 <div class="text-start mt-3 mt-xl-0 text-xl-end">Syntax not understood
114 <a href="/register" class="btn btn-success px-4 px-xl-3 me-1">注册</a>Syntax not understood
115 <a href="/login" class="btn btn-outline-secondary px-4 px-xl-3">登录</a>Syntax not understood
116 </div>Syntax not understood
118 </div>Syntax not understood
119 </div>Syntax not understood
120 </div>Syntax not understood
121 </nav>Syntax not understood
122</header>Syntax not understood
124 <section class="container-fluid dede-banner" style="background: url(/assets/img/jpg/common/index_bannerbg.jpg);">Unknown directive
125 <div class="py-5 px-4 text-center">Syntax not understood
126 <h1 class="mt-4 display-6 fw-semibold text-white">DedeCMS V5.7.118 正式版下载</h1>Syntax not understood
128 <p class="mt-4 fs-5 text-light">Nginx/IIS/Apache PHP5.6+ MySQL5.7+</p>Syntax not understood
130 <p class="mt-4 fs-4 text-light">更新于 2025-07-30</p>Syntax not understood
132 <div class="mt-4 d-grid gap-2 d-sm-flex justify-content-sm-center">Syntax not understood
133 <a href="/user/authorization/license" class="btn btn-lg btn-primary px-5 me-sm-3"Syntax not understood
134 style="background-color: #FF6700; border-color: #FF6700;">购买授权</a>Unknown directive
135 <a href="/download" class="btn btn-lg btn-primary px-5"Syntax not understood
136 style="background-color: #FF6700; border-color: #FF6700;">产品下载</a>Unknown directive
137 </div>Syntax not understood
139 <div class="mt-4 mb-4">Syntax not understood
140 <p class="mb-1">Syntax not understood
141 <a target="_blank" href="/post/20211026.html" class="text-light text-decoration-none">Syntax not understood
142 关于侵权网站清单及存证数据移交维权团队的通告Syntax not understood
143 </a>Syntax not understood
144 <span class="badge text-bg-danger">New</span>Syntax not understood
145 </p>Syntax not understood
146 <p class="mb-0">Syntax not understood
147 <a target="_blank" href="/post/20210930.html" class="text-light text-decoration-none">Syntax not understood
148 致广大DedeCMS用户的一封公开信Syntax not understood
149 </a>Syntax not understood
150 </p>Syntax not understood
151 </div>Syntax not understood
152 </div>Syntax not understood
153 </section>Syntax not understood
155 <section class="container mt-5 dede-feature">Syntax not understood
156 <div class="row text-center">Syntax not understood
157 <div class="col-12">Syntax not understood
158 <h2>产品特性</h2>Syntax not understood
159 <span class="text-muted">了解更多产品功能特性</span>Syntax not understood
160 <div class="position-relative">Syntax not understood
161 <span class="dede-title-points"></span>Syntax not understood
162 </div>Syntax not understood
163 </div>Syntax not understood
164 </div>Syntax not understood
166 <div class="row text-center">Syntax not understood
167 <div class="col-6 col-lg-3 mt-3 mt-lg-4">Syntax not understood
168 <div class="card py-3 py-lg-4">Syntax not understood
169 <img src="/assets/img/png/index/icon_product01.png" class="card-img-top w-50 align-self-center">Syntax not understood
170 <div class="card-body">Syntax not understood
171 <h5 class="card-title">用户口碑</h5>Syntax not understood
172 <p class="card-text">Syntax not understood
173 丰富的开源经验赢得<br>良好的口碑Syntax not understood
174 </p>Syntax not understood
175 </div>Syntax not understood
176 </div>Syntax not understood
177 </div>Syntax not understood
179 <div class="col-6 col-lg-3 mt-3 mt-lg-4">Syntax not understood
180 <div class="card py-3 py-lg-4">Syntax not understood
181 <img src="/assets/img/png/index/icon_product02.png" class="card-img-top w-50 align-self-center">Syntax not understood
182 <div class="card-body">Syntax not understood
183 <h5 class="card-title">模块组合</h5>Syntax not understood
184 <p class="card-text">Syntax not understood
185 让网站丰富方便<br>网站扩展Syntax not understood
186 </p>Syntax not understood
187 </div>Syntax not understood
188 </div>Syntax not understood
189 </div>Syntax not understood
191 <div class="col-6 col-lg-3 mt-3 mt-lg-4">Syntax not understood
192 <div class="card py-3 py-lg-4">Syntax not understood
193 <img src="/assets/img/png/index/icon_product03.png" class="card-img-top w-50 align-self-center">Syntax not understood
194 <div class="card-body">Syntax not understood
195 <h5 class="card-title">模板引擎</h5>Syntax not understood
196 <p class="card-text">Syntax not understood
197 简单易用<br>界面随时可更换Syntax not understood
198 </p>Syntax not understood
199 </div>Syntax not understood
200 </div>Syntax not understood
201 </div>Syntax not understood
203 <div class="col-6 col-lg-3 mt-3 mt-lg-4">Syntax not understood
204 <div class="card py-3 py-lg-4">Syntax not understood
205 <img src="/assets/img/png/index/icon_product04.png" class="card-img-top w-50 align-self-center">Syntax not understood
206 <div class="card-body">Syntax not understood
207 <h5 class="card-title">自定义模型</h5>Syntax not understood
208 <p class="card-text">Syntax not understood
209 自己扩展网站后续功能<br>省去诸多烦恼Syntax not understood
210 </p>Syntax not understood
211 </div>Syntax not understood
212 </div>Syntax not understood
213 </div>Syntax not understood
215 <div class="col-6 col-lg-3 mt-3 mt-lg-4">Syntax not understood
216 <div class="card py-3 py-lg-4">Syntax not understood
217 <img src="/assets/img/png/index/icon_product05.png" class="card-img-top w-50 align-self-center">Syntax not understood
218 <div class="card-body">Syntax not understood
219 <h5 class="card-title">动静态部署</h5>Syntax not understood
220 <p class="card-text">Syntax not understood
221 高效的页面部署<br>提高网站收录量Syntax not understood
222 </p>Syntax not understood
223 </div>Syntax not understood
224 </div>Syntax not understood
225 </div>Syntax not understood
227 <div class="col-6 col-lg-3 mt-3 mt-lg-4">Syntax not understood
228 <div class="card py-3 py-lg-4">Syntax not understood
229 <img src="/assets/img/png/index/icon_product06.png" class="card-img-top w-50 align-self-center">Syntax not understood
230 <div class="card-body">Syntax not understood
231 <h5 class="card-title">升级无忧</h5>Syntax not understood
232 <p class="card-text">Syntax not understood
233 及时和官方程序同步<br>安全无忧Syntax not understood
234 </p>Syntax not understood
235 </div>Syntax not understood
236 </div>Syntax not understood
237 </div>Syntax not understood
239 <div class="col-6 col-lg-3 mt-3 mt-lg-4">Syntax not understood
240 <div class="card py-3 py-lg-4">Syntax not understood
241 <img src="/assets/img/png/index/icon_product07.png" class="card-img-top w-50 align-self-center">Syntax not understood
242 <div class="card-body">Syntax not understood
243 <h5 class="card-title">强大的SEO</h5>Syntax not understood
244 <p class="card-text">Syntax not understood
245 灵活调整<br>提升关键词排名Syntax not understood
246 </p>Syntax not understood
247 </div>Syntax not understood
248 </div>Syntax not understood
249 </div>Syntax not understood
251 <div class="col-6 col-lg-3 mt-3 mt-lg-4">Syntax not understood
252 <div class="card py-3 py-lg-4">Syntax not understood
253 <img src="/assets/img/png/index/icon_product08.png" class="card-img-top w-50 align-self-center">Syntax not understood
254 <div class="card-body">Syntax not understood
255 <h5 class="card-title">安全可靠</h5>Syntax not understood
256 <p class="card-text">Syntax not understood
257 十六年持续迭代<br>十万加用户共同见证Syntax not understood
258 </p>Syntax not understood
259 </div>Syntax not understood
260 </div>Syntax not understood
261 </div>Syntax not understood
262 </div>Syntax not understood
263 </section>Syntax not understood
265 <footer class="mt-5" >Syntax not understood
266 <div class="dede-footer">Syntax not understood
267 <div class="container">Syntax not understood
268 <div class="row py-5">Syntax not understood
269 <div class="col-12 col-lg-7 text-white-50">Syntax not understood
270 <div class="row">Syntax not understood
271 <div class="col-12 col-md-auto">Syntax not understood
272 <divSyntax not understood
273 class="d-flex flex-row flex-wrap align-content-start justify-content-start align-items-start">Syntax not understood
274 <div class="text-center">Syntax not understood
275 <img src="/assets/img/jpg/common/footer/gongzhonghao.jpg" width="120px"><br>Syntax not understood
276 <span class="d-block mt-2">微信公众号</span>Syntax not understood
277 </div>Syntax not understood
279 <div class=" ms-3 text-center">Syntax not understood
280 <img src="/assets/img/jpg/common/footer/qiyeweixin.jpg" width="120px"><br>Syntax not understood
281 <span class="d-block mt-2">微信客服</span>Syntax not understood
282 </div>Syntax not understood
283 </div>Syntax not understood
285 </div>Syntax not understood
287 <div class="col-12 col-md mt-3 mt-sm-4 mt-md-0">Syntax not understood
288 <h5 class="fs-5 text-white">Syntax not understood
289 <a class="text-white text-decoration-none" href="tel:021-37788569"Unknown directive
290 target="_blank">021-37788569</a>Syntax not understood
291 </h5>Syntax not understood
292 <span class="text-white-50 fs-6 fw-light">商务咨询电话</span>Syntax not understood
294 <table class="text-white-50 fs-6 fw-light">Syntax not understood
295 <tr>Syntax not understood
296 <td>工作时间:</td>Syntax not understood
297 <td>周一至周五</td>Syntax not understood
298 </tr>Syntax not understood
299 <tr>Syntax not understood
300 <td></td>Syntax not understood
301 <td>8:30~11:30至13:30~18:00</td>Unknown directive
302 </tr>Syntax not understood
303 </table>Syntax not understood
304 </div>Syntax not understood
305 </div>Syntax not understood
306 </div>Syntax not understood
309 <div class="col-12 col-lg-5 mt-3 mt-sm-4 mt-md-4 mt-lg-0">Syntax not understood
310 <div class="row row-cols-3">Syntax not understood
311 <div>Syntax not understood
312 <h5 class="text-white">技术支持</h5>Syntax not understood
313 <ul class="nav flex-column">Syntax not understood
314 <li class="nav-item mb-2"><a href="https://help.dedecms.com/" class="nav-link p-0 text-white-50">帮助中心</a>Unknown directive
315 </li>Syntax not understood
316 <li class="nav-item mb-2"><a href="https://help.dedecms.com/changjianwenti/" class="nav-link p-0 text-white-50">常见问题</a>Unknown directive
317 </li>Syntax not understood
318 <li class="nav-item mb-2"><a href="https://help.dedecms.com/chujie/" class="nav-link p-0 text-white-50">使用手册</a>Unknown directive
319 </li>Syntax not understood
320 <li class="nav-item mb-2"><a href="https://help.dedecms.com/mubanshouce/" class="nav-link p-0 text-white-50">模板手册</a>Unknown directive
321 </li>Syntax not understood
322 </ul>Syntax not understood
323 </div>Syntax not understood
325 <div>Syntax not understood
326 <h5 class="text-white">服务支持</h5>Syntax not understood
327 <ul class="nav flex-column">Syntax not understood
328 <li class="nav-item mb-2"><a href="/license" class="nav-link p-0 text-white-50">授权协议</a>Syntax not understood
329 </li>Syntax not understood
330 <li class="nav-item mb-2"><a href="/authorization/search"Syntax not understood
331 class="nav-link p-0 text-white-50">授权查询</a>Syntax not understood
332 </li>Syntax not understood
333 <li class="nav-item mb-2"><a href="/authorization"Syntax not understood
334 class="nav-link p-0 text-white-50">购买流程</a>Syntax not understood
335 </li>Syntax not understood
336 <li class="nav-item mb-2"><a href="/authorization"Syntax not understood
337 class="nav-link p-0 text-white-50">授权说明</a>Syntax not understood
338 </li>Syntax not understood
339 </ul>Syntax not understood
340 </div>Syntax not understood
342 <div>Syntax not understood
343 <h5 class="text-white">关于我们</h5>Syntax not understood
344 <ul class="nav flex-column">Syntax not understood
345 <li class="nav-item mb-2"><a href="#" class="nav-link p-0 text-white-50">公司简介</a>Syntax not understood
346 </li>Syntax not understood
347 <li class="nav-item mb-2"><a href="#" class="nav-link p-0 text-white-50">招贤纳士</a>Syntax not understood
348 </li>Syntax not understood
349 <li class="nav-item mb-2"><a href="#" class="nav-link p-0 text-white-50">联系我们</a>Syntax not understood
350 </li>Syntax not understood
351 <li class="nav-item mb-2"><a href="https://site.dedecms.com/youqingzhanshi/" class="nav-link p-0 text-white-50">友情展示</a>Unknown directive
352 </li>Syntax not understood
353 </ul>Syntax not understood
354 </div>Syntax not understood
355 </div>Syntax not understood
356 </div>Syntax not understood
357 </div>Syntax not understood
358 </div>Syntax not understood
359 </div>Syntax not understood
361 <div class="dede-copyright">Syntax not understood
362 <div class="container">Syntax not understood
363 <div class="text-center py-4" style="font-size: 14px !important;">Unknown directive
364 © 2023 <a href="http://www.desdev.cn">DesDev Inc</a>.Unknown directive
365 All rights reserved Powered bySyntax not understood
366 <a href="http://www.dedecms.com">DedeCMS</a><br>Unknown directive
367 <a href="http://beian.miit.gov.cn/" title="沪ICP备17008595号" rel="noopener noreferrer"Unknown directive
368 target="_blank">沪ICP备17008595号</a>Syntax not understood
369 <a href="https://www.beian.gov.cn/portal/registerSystemInfo?recordcode=31011802005130" title="沪公网安备31011802005130号" rel="noopener noreferrer"Unknown directive
370 target="_blank">Syntax not understood
371 <img src="/assets/beian.png" width="20px" height="20px">Syntax not understood
372 沪公网安备31011802005130号Syntax not understood
373 </a><br>Syntax not understood
375 云主机支持:Unknown directive
376 <a href="https://www.landui.com/" title="蓝队云" rel="noopener noreferrer" target="_blank">蓝队云</a>Unknown directive
377 </div>Syntax not understood
378 </div>Syntax not understood
379 </div>Syntax not understood
380</footer>Syntax not understood
382 <script type="text/javascript" src="/assets/pkg/jquery/jquery.min.js?v=1729060935"></script>Syntax not understood
383<script type="text/javascript" src="/assets/pkg/jquery-cookie/jquery.cookie.js?v=1729060935"></script>Syntax not understood
384<script type="text/javascript" src="/assets/pkg/bootstrap-5.2.3-dist/js/bootstrap.bundle.min.js?v=1729060935"></script>Syntax not understood
385<script type="text/javascript" src="/assets/pkg/toast/toast.js?v=1729060935"></script>Syntax not understood
386<script type="text/javascript" src="/assets/js/dedecms.common.min.js?v=1729060935"></script>Syntax not understood
387</body>Syntax not understood
389</html>Syntax not understood

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
nav.navbar > div.container > a.navbar-brand > img nav.navbar > div.container > a.navbar-brand > img
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.row > div.col-6 > div.card > img.card-img-top div.row > div.col-6 > div.card > img.card-img-top
div.col-12 > div.d-flex > div.text-center > img div.col-12 > div.d-flex > div.text-center > img
div.col-12 > div.d-flex > div.ms-3 > img div.col-12 > div.d-flex > div.ms-3 > img
div.container > div.text-center > a > img div.container > div.text-center > a > 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
Links are crawlable
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback