Website review, no card needed
lenovo.com.cn website review
Visit site (opens in a new tab)Reviewed 17 November 202639 issues · 67 checks
This review found 39 issues worth fixing on lenovo.com.cn, 15 of them high impact, across 67 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
63DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.1 s |
| Jun 6, 2026 | 3.3 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.1 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 2.2 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 2.4 s |
| Oct 3, 2026 | 3.0 s |
| Oct 10, 2026 | 3.5 s |
| Oct 17, 2026 | 4.0 s |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.8 s
3.6 s
5.4 s
7.2 s
9.0 s
10.8 s
12.6 s
14.4 s
Speed
Reduce unused JavaScript
1.4 s · 438 KiBAbout 438 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Render-blocking requests
1.6 s13 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Use efficient cache lifetimes
600 ms · 1.4 MB50 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).
Improve image delivery
650 ms · 829 KiB10 images could be 829 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.
Mobile performance score: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
4 third-party services on the page
4 third-party services load with your homepage (lefile.cn, portal101.cn and fengkongcloud.cn and others), adding 3.6 MB and 477 ms of main-thread time.
Document request latency
800 msThe HTML itself could arrive about 800 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Avoid multiple page redirects
751 msThe page goes through 1 redirect before it starts loading, costing about 751 ms. Link and advertise the final URL directly.
lefile.cn adds 270 ms
270 mslefile.cn costs a phone 270 ms of main-thread work and 3.1 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
fengkongcloud.cn adds 89 ms
89 msfengkongcloud.cn costs a phone 89 ms of main-thread work and 325 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Minify JavaScript
150 ms · 14 KiB14 KiB could be saved by minifying JavaScript.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 101 ms. During a long task the page ignores taps.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
2 checks passed
Main-thread work: 1.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 607 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 5.2 s
5.2 sReal visitors wait 5.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.9 s
3.9 sReal visitors see the first content after 3.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.0 s
2.0 sReal visitors wait 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 10.9 s
10.9 sYour largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is element render delay (7.9 s).
Speed Index: 23.2 s
23.2 sVisually, the page fills in at 23.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 15.4 s
15.4 sThe page becomes fully interactive after 15.4 s. Good is under 3.8 s.
First Contentful Paint: 5.1 s
5.1 sThe first text or image appears after 5.1 s on a phone. Good is under 1.8 s.
10 images without width and height
10 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.1 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 83 ms
83 msReal visitors wait 83 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 33 ms
33 msScripts block the page for only 33 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.6 MB in 109 requests
3.6 MBYour homepage downloads 3.6 MB in 109 requests on a phone: images 2.6 MB (50), scripts 952 KiB (31) and stylesheets 40 KiB (8). Under 2 MB keeps phones on slow connections fast.
About 1.0 g of CO₂ per visit
1.01 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.01 g of CO₂e: 121.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
13 images without alt text
13 images have no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (40 characters)
Your meta description is only 40 characters: “联想_lenovo笔记本电脑_平板电脑_手机_台式机_服务器_外设数码_联想官网”. 70 to 160 characters is enough to sell the click.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
4 checks passed
Title: 41 characters
Your title is a healthy 41 characters: “联想_lenovo笔记本电脑_平板电脑_手机_台式机_服务器_外设数码_联想官网A”.
Canonical URL set
The canonical URL is https://www.lenovo.com.cn/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.lenovo.com.cn/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://www.lenovo.com.cn/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
1 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Best practices
No mobile viewport
No viewport meta tag, so phones render the desktop layout zoomed out.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “$ is not defined”.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Thin social proof
Social proof on the homepage: 19 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 1,307 words of copy
The homepage carries about 1,307 words of visible text.
1 checks passed
1 call to action
The homepage has 1 call to action, for example “YOGA Book 尊享双屏”.
Privacy and tracking
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
8 other companies contacted
Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at lenovo.com.cn, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Hosting
- CHINA UNICOM China169 Backbone
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on lenovo.com.cn, including 19 speed issues, 7 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.