Website review, no card needed
huaweicloud.com website review
Visit site (opens in a new tab)Reviewed 18 November 202637 issues · 73 checks
This review found 37 issues worth fixing on huaweicloud.com, 16 of them high impact, across 73 checks. The most urgent: use efficient cache lifetimes. 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
62DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 5.2 s |
| Jun 6, 2026 | 5.0 s |
| Jun 13, 2026 | 4.9 s |
| Jun 20, 2026 | 4.9 s |
| Jun 27, 2026 | 5.2 s |
| Jul 4, 2026 | 5.2 s |
| Jul 11, 2026 | 5.1 s |
| Jul 18, 2026 | 5.0 s |
| Jul 25, 2026 | 4.5 s |
| Aug 1, 2026 | 4.4 s |
| Aug 8, 2026 | 4.6 s |
| Aug 15, 2026 | 4.7 s |
| Aug 22, 2026 | 4.9 s |
| Aug 29, 2026 | 5.3 s |
| Sep 5, 2026 | 5.3 s |
| Sep 12, 2026 | 5.4 s |
| Sep 19, 2026 | 5.5 s |
| Sep 26, 2026 | 5.6 s |
| Oct 3, 2026 | 5.9 s |
| Oct 10, 2026 | 5.9 s |
| Oct 17, 2026 | 5.8 s |
| Oct 24, 2026 | 5.5 s |
| Oct 31, 2026 | 5.1 s |
| Nov 7, 2026 | 5.2 s |
| Nov 14, 2026 | 5.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 185 ms |
| Jun 6, 2026 | 176 ms |
| Jun 13, 2026 | 165 ms |
| Jun 20, 2026 | 159 ms |
| Jun 27, 2026 | 163 ms |
| Jul 4, 2026 | 166 ms |
| Jul 11, 2026 | 170 ms |
| Jul 18, 2026 | 169 ms |
| Jul 25, 2026 | 163 ms |
| Aug 1, 2026 | 160 ms |
| Aug 8, 2026 | 164 ms |
| Aug 15, 2026 | 172 ms |
| Aug 22, 2026 | 192 ms |
| Aug 29, 2026 | 194 ms |
| Sep 5, 2026 | 194 ms |
| Sep 12, 2026 | 194 ms |
| Sep 19, 2026 | 182 ms |
| Sep 26, 2026 | 177 ms |
| Oct 3, 2026 | 173 ms |
| Oct 10, 2026 | 174 ms |
| Oct 17, 2026 | 186 ms |
| Oct 24, 2026 | 194 ms |
| Oct 31, 2026 | 191 ms |
| Nov 7, 2026 | 186 ms |
| Nov 14, 2026 | 192 ms |
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.7 s
3.4 s
5.1 s
6.8 s
8.5 s
10.3 s
12.0 s
13.7 s
Speed
Use efficient cache lifetimes
7.3 s · 2.2 MB55 files are served with short cache lifetimes, so returning visitors download them again (2.2 MB).
Avoid multiple page redirects
9.0 sThe page goes through 2 redirects before it starts loading, costing about 9.0 s. Link and advertise the final URL directly.
Reduce unused JavaScript
5.3 s · 720 KiBAbout 720 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.3 s faster on a phone.
Render-blocking requests
2.3 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Reduce unused CSS
1.5 s · 614 KiBAbout 614 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s 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.
3 third-party services on the page
3 third-party services load with your homepage (hc-cdn.com, hc-cdn.cn and myhuaweicloud.com), adding 2.2 MB and 631 ms of main-thread time.
hc-cdn.com adds 554 ms
554 mshc-cdn.com costs a phone 554 ms of main-thread work and 1.5 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.
Document request latency
350 msThe HTML itself could arrive about 350 ms sooner: redirects, a slow server response or missing compression delay everything after it.
1,793 HTML elements
The page has 1,793 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
hc-cdn.cn adds 77 ms
77 mshc-cdn.cn costs a phone 77 ms of main-thread work and 782 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.
Improve image delivery
250 ms · 123 KiB5 images could be 123 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 116 ms. During a long task the page ignores taps.
Legacy JavaScript
33 KiBPolyfills for old browsers add 33 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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
Minify JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 728 ms of it running JavaScript. That is comfortably low.
Server response: 22 ms
22 msYour server sent the HTML in 22 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: 6.2 s
6.2 sReal visitors wait 6.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.0 s
4.0 sReal visitors see the first content after 4.0 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 15.7 s
15.7 sYour largest element takes 15.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “CodeArts Agent Multi-Agent Collaboration | Custom Models | …”.
First Contentful Paint: 5.9 s
5.9 sThe first text or image appears after 5.9 s on a phone. Good is under 1.8 s.
Time to Interactive: 16.9 s
16.9 sThe page becomes fully interactive after 16.9 s. Good is under 3.8 s.
Speed Index: 10.0 s
10.0 sVisually, the page fills in at 10.0 s (Speed Index). Good is under 3.4 s.
Real-user INP: 221 ms
221 msReal visitors wait 221 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 185 ms to 192 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 5.2 s to 5.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Total Blocking Time: 77 ms
77 msScripts block the page for only 77 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
Page weight: 2.9 MB in 94 requests
2.9 MBYour homepage downloads 2.9 MB in 94 requests on a phone: scripts 1.3 MB (30), images 775 KiB (26) and stylesheets 406 KiB (10). Under 2 MB keeps phones on slow connections fast.
About 0.8 g of CO₂ per visit
0.83 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.83 g of CO₂e: 99.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
25 images without alt text
25 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.
9 links without text
9 links have no text or label, so screen readers cannot say where they go.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Headings skip levels
Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
88 links with vague text
88 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Title is short (16 characters)
Your title is only 16 characters: “华为云,用AI解行业难题-华为云”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
28 links crawlers can't follow
28 links have no real href, so search engines can't follow them.
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
237 internal links, 65 external
The homepage links to 237 pages on huaweicloud.com and 65 external pages.
4 checks passed
Meta description: 105 characters
Your meta description is 105 characters: “华为云提供稳定可靠、安全可信、可持续发展的云服务,致力于让云无处不在,让智能无所不及,共建智能世界云底座。助力企业降本增效,全球300万客户的共同选择。7x24小时专业服务支持,5天内无理由退订,免费快速备案。”.
Canonical URL set
The canonical URL is https://www.huaweicloud.com/.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.huaweicloud.com/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.huaweicloud.com/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.
Other pages
2 pages share a title
/ and https://www.huaweicloud.com/intl/zh-cn all use the title “华为云,用AI解行业难题-华为云”. Search engines can't tell which page to show for a search, so each competes with the others.
14 pages without an H1
https://www.huaweicloud.com/intl/zh-cn, https://www.huaweicloud.com/intl/en-us, https://www.huaweicloud.com/intl/id-id, https://www.huaweicloud.com/intl/es-us, https://www.huaweicloud.com/intl/pt-br and https://www.huaweicloud.com/intl/tr-tr and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.huaweicloud.com/mobile_app/hwapp.html has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 101 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
Thin social proof
Social proof on the homepage: 5 customer or partner logos. 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 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,196 words of copy
The homepage carries about 1,196 words of visible text.
2 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 2 phone links and 4 email links.
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 huaweicloud.com, 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
- Huawei Cloud Service data center
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on huaweicloud.com, including 20 speed issues, 6 SEO issues and 3 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.