Skip to content
https://1688.com

Lighthouse Desktop

· 0 checks — Desktop Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

56

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

Performance issues directly impact user engagement and conversion rates.

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
g.alicdn.com/trace/trace/1.3.22/??sdk.js,resourceError-plugin.js,perf-plugin.js268.0 s24.3 KiB
g.alicdn.com/AWSC/fireyejs/1.234.20/fireyejs.js651574.0 s170.8 KiB
g.alicdn.com/AWSC/et/1.83.8/et_f.js2293139.0 s89.5 KiB
g.alicdn.com/alilog/??/aplus_plugin_b2bfront/index.js,mlog/aplus_v2.js4949.0 s7.8 KiB
g.alicdn.com/bsop-static/sufei-punish/0.1.122/build/htmltocanvas.min.js972551.0 s46.0 KiB
g.alicdn.com/bsop-static/sufei-punish/0.1.122/build/punishpage.min.js972567.0 s36.4 KiB
g.alicdn.com/AWSC/nc/1.97.0/nc.js1128588.0 s18.2 KiB
g.alicdn.com/mtb/lib-mtop/2.6.3/mtop.js1809657.0 s9.5 KiB
g.alicdn.com/secdev/entry/x/0e473074f301b974.js3496.0 s896 B
g.alicdn.com/sd/punish/0.0.1/qrcode.min.js2381443.0 s7.4 KiB
g.alicdn.com/alilog/mlog/aplus_v2.js1146919.0 s6.5 KiB
g.alicdn.com/bsop-static/sufei-punish/0.1.122/build/main.css972577.0 s5.4 KiB
g.alicdn.com/AWSC/CAPTCHA/0.0.1/awsc.js2332359.0 s3.7 KiB
ftnprj.tdum.alibaba.com/dss.js0.0 ms312 B
/nocaptcha/initialize.jsonp?a=X82Y__3ae6ed0376520147e8c65...0.0 ms276 B
g.alicdn.com/mtb/lib-windvane/3.0.6/windvane.js2274177.0 s2.4 KiB
g.alicdn.com/mtb/lib-flexible/0.3.2/flexible.js2483843.0 s1.5 KiB
/ts?url=&token=gAlkkNGjHObBXu-YHjNWHeqiaxvYN7NQIDCLvWEe3o...0.0 ms139 B
/_____tmd_____/report?x5secdata=xg22772d8a370055f1ja0f305...0.0 ms85 B

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:label label:Subpart valueType:text] map[key:duration label:Duration valueType:ms]]
items: [map[duration:1451.257 label:Time to first byte subpart:timeToFirstByte] map[duration:1458.356 label:Resource load delay subpart:resourceLoadDelay] map[duration:87.889 label:Resource load duration subpart:resourceLoadDuration] map[duration:35.854 label:Element render delay subpart:elementRenderDelay]]
lhId: page-0-IMG
nodeLabel: div.content-inside > div.bannar > div.bg-img-wrap > img#bg-img
path: 1,HTML,1,BODY,5,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,IMG
selector: div.content-inside > div.bannar > div.bg-img-wrap > img#bg-img
snippet: <img id="bg-img" src="https://img.alicdn.com/imgextra/i2/O1CN010VLpQY1VWKHBQuBUQ_!!6000000002660…" onerror="customImageError(this)">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: div.content-inside > div.bannar > div.bg-img-wrap > img#bg-img
path: 1,HTML,1,BODY,5,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,IMG
selector: div.content-inside > div.bannar > div.bg-img-wrap > img#bg-img
snippet: <img id="bg-img" src="https://img.alicdn.com/imgextra/i2/O1CN010VLpQY1VWKHBQuBUQ_!!6000000002660…" onerror="customImageError(this)">

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer SizeDuration
g.alicdn.com/trace/trace/1.3.22/??sdk.js,resourceError-plugin.js,perf-plugin.js24.3 KiB
g.alicdn.com/bsop-static/sufei-punish/0.1.122/build/punishpage.min.js36.4 KiB
g.alicdn.com/mtb/lib-flexible/0.3.2/flexible.js1.5 KiB
g.alicdn.com/AWSC/CAPTCHA/0.0.1/awsc.js3.7 KiB
g.alicdn.com/mtb/lib-mtop/2.6.3/mtop.js9.5 KiB
g.alicdn.com/mtb/lib-windvane/3.0.6/windvane.js2.4 KiB
g.alicdn.com/sd/punish/0.0.1/qrcode.min.js7.4 KiB
g.alicdn.com/bsop-static/sufei-punish/0.1.122/build/main.css5.4 KiB208 ms

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.content-inside > div.bannar > div.bg-img-wrap > img#bg-img div.content-inside > div.bannar > div.bg-img-wrap > img#bg-img
/imgextra/i2/O1CN010VLpQY1VWKHBQuBUQ_!!6000000002660-2-tp...10.1 KiB5.4 KiB

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

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 872 ms
URLTime Spent
1688.com/872 ms
www.1688.com/0.0 ms

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 40 ms 85.9 KiB
URLTransfer SizeEst Savings
g.alicdn.com/AWSC/fireyejs/1.234.20/fireyejs.js170.8 KiB62.8 KiB
g.alicdn.com/bsop-static/sufei-punish/0.1.122/build/htmltocanvas.min.js45.2 KiB23.1 KiB

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in the main frame.Actionable
Pages with cache-control:no-store header cannot enter back/forward cache.Actionable

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
div.content-inside > div.bannar > div.bg-img-wrap > img#bg-img div.content-inside > div.bannar > div.bg-img-wrap > img#bg-img
/imgextra/i2/O1CN010VLpQY1VWKHBQuBUQ_!!6000000002660-2-tp...
div#J_Header > h1#logo > a > img div#J_Header > h1#logo > a > img
img.alicdn.com/tfs/TB17G2dJGmWBuNjy1XaXXXCbXXa-241-41.png
center > div.bx-pu-qrcode-wrap > div.captcha-qrcode > img center > div.bx-pu-qrcode-wrap > div.captcha-qrcode > img

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

●Layout shift culprits
●Optimize DOM size
●Font display
●Forced reflow
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●Reduce unused CSS
●Avoids enormous network payloads Total size was 586 KiB
●JavaScript execution time 0.8 s
●Minimizes main-thread work 1.1 s
●Avoid long main-thread tasks 5 long tasks found
●Avoid non-composited animations 1 animated element found
●Network Requests
●Network Round Trip Times 230 ms
●Server Backend Latencies 250 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Initial server response time was short Root document took 270 ms
●Avoid large layout shifts 2 layout shifts found
○INP breakdown
○User Timing marks and measures
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.

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
Click to feedback > div.captcha-tips > center > div.bx-pu-qrcode-wrap > a#bx-feedback-btn

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

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
div.content-inside > div.bannar > div.bg-img-wrap > img#bg-img div.content-inside > div.bannar > div.bg-img-wrap > img#bg-img
center > div.bx-pu-qrcode-wrap > div.captcha-qrcode > img center > div.bx-pu-qrcode-wrap > div.captcha-qrcode > img

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

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta head > meta

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
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●Links have a discernible name
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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 a valid value for its `[lang]` attribute
○`<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
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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.
81

Best Practices

General

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / WarningSource
Unload event listeners are deprecated and will be removed.
g.alicdn.com/AWSC/et/1.83.8/et_f.js
●Uses HTTPS
●Avoids third-party cookies
●Allows users to paste into input fields
●Avoids requesting the geolocation permission on page load
●Avoids requesting the notification permission on page load
●Displays images with correct aspect ratio
●Serves images with appropriate resolution
●Page has the HTML doctype
●Properly defines charset
●No 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
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Detected JavaScript libraries
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.

Content Best Practices

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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
div.content-inside > div.bannar > div.bg-img-wrap > img#bg-img div.content-inside > div.bannar > div.bg-img-wrap > img#bg-img
center > div.bx-pu-qrcode-wrap > div.captcha-qrcode > img center > div.bx-pu-qrcode-wrap > div.captcha-qrcode > 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
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●robots.txt is valid
●Document has a valid `hreflang`
○Document has a valid `rel=canonical`

Send Feedback