Website review, no card needed

alibabacloud.com logo

alibabacloud.com website review

Visit site (opens in a new tab)Reviewed 19 October 202657 issues · 91 checks

This review found 57 issues worth fixing on alibabacloud.com, 23 of them high impact, across 91 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
5.5 s4.9 sApr 25Oct 105.2 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20265.1 s
May 2, 20265.1 s
May 9, 20265.0 s
May 16, 20265.1 s
May 23, 20265.0 s
May 30, 20265.0 s
Jun 6, 20265.1 s
Jun 13, 20265.1 s
Jun 20, 20265.1 s
Jun 27, 20265.2 s
Jul 4, 20265.1 s
Jul 11, 20265.1 s
Jul 18, 20265.3 s
Jul 25, 20265.3 s
Aug 1, 20265.3 s
Aug 8, 20265.4 s
Aug 15, 20265.4 s
Aug 22, 20265.4 s
Aug 29, 20265.4 s
Sep 5, 20265.4 s
Sep 12, 20265.4 s
Sep 19, 20265.3 s
Sep 26, 20265.2 s
Oct 3, 20265.2 s
Oct 10, 20265.2 s
Real-visitor tap response (INP)75th percentile, phones
374 ms311 msApr 25Oct 10365 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 2026318 ms
May 2, 2026318 ms
May 9, 2026319 ms
May 16, 2026325 ms
May 23, 2026328 ms
May 30, 2026333 ms
Jun 6, 2026342 ms
Jun 13, 2026345 ms
Jun 20, 2026346 ms
Jun 27, 2026352 ms
Jul 4, 2026346 ms
Jul 11, 2026350 ms
Jul 18, 2026351 ms
Jul 25, 2026338 ms
Aug 1, 2026339 ms
Aug 8, 2026344 ms
Aug 15, 2026348 ms
Aug 22, 2026354 ms
Aug 29, 2026360 ms
Sep 5, 2026361 ms
Sep 12, 2026362 ms
Sep 19, 2026367 ms
Sep 26, 2026363 ms
Oct 3, 2026363 ms
Oct 10, 2026365 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

Full-page screenshot of alibabacloud.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alibabacloud.com at 1.6 s1.6 s
  2. alibabacloud.com at 3.2 s3.2 s
  3. alibabacloud.com at 4.8 s4.8 s
  4. alibabacloud.com at 6.4 s6.4 s
  5. alibabacloud.com at 8.0 s8.0 s
  6. alibabacloud.com at 9.6 s9.6 s
  7. alibabacloud.com at 11.2 s11.2 s
  8. alibabacloud.com at 12.8 s12.8 s

Speed

14 to fix28
  • Reduce unused JavaScript

    5.1 s · 2.1 MB

    About 2.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.1 s faster on a phone.

  • alicdn.com adds 2.2 s

    2.2 s

    alicdn.com costs a phone 2.2 s of main-thread work and 13.1 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Render-blocking requests

    3.3 s

    9 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.3 s.

  • Mobile performance score: 28

    28/100

    Your mobile performance score is 28 (desktop: 39). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 6,002 HTML elements

    The page has 6,002 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Main-thread work: 6.0 s

    A phone's processor spends 6.0 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Improve image delivery

    150 ms · 5.8 MB

    11 images could be 5.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Use efficient cache lifetimes

    900 ms · 4.0 MB

    42 files are served with short cache lifetimes, so returning visitors download them again (4.0 MB).

  • 8 third-party services on the page

    8 third-party services load with your homepage (alicdn.com, Google Tag Manager and alcasset.com and others), adding 14.4 MB and 3.1 s of main-thread time.

  • Reduce unused CSS

    600 ms · 214 KiB

    About 214 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • 15 long tasks on the main thread

    15 long tasks block the main thread while loading, the longest for 623 ms. During a long task the page ignores taps.

  • Google Tag Manager adds 547 ms

    547 ms

    Google Tag Manager costs a phone 547 ms of main-thread work and 686 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.

  • Font display

    500 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 500 ms).

  • alcasset.com adds 271 ms

    271 ms

    alcasset.com costs a phone 271 ms of main-thread work and 333 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.

  • Legacy JavaScript

    150 ms · 79 KiB

    Polyfills for old browsers add 79 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

1 checks passed
  • Server response: 58 ms

    58 ms

    Your server sent the HTML in 58 ms, well inside Google's 600 ms guideline.

Core Web Vitals

12 to fix0
  • 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.8 s

    5.8 s

    Real visitors wait 5.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user CLS: 0.39

    0.39

    For real visitors the layout shifts by 0.39 (75th percentile). Good is under 0.1.

  • Real-user FCP: 4.4 s

    4.4 s

    Real visitors see the first content after 4.4 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 2.9 s

    2.9 s

    Real visitors wait 2.9 s for your server to start answering (75th percentile). Good is under 800 ms.

  • First Contentful Paint: 12.4 s

    12.4 s

    The first text or image appears after 12.4 s on a phone. Good is under 1.8 s.

  • Largest Contentful Paint: 12.5 s

    12.5 s

    Your largest element takes 12.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “$200 instant credits no minimum spend. Unlock up to $150K E…”.

  • Time to Interactive: 40.2 s

    40.2 s

    The page becomes fully interactive after 40.2 s. Good is under 3.8 s.

  • Speed Index: 12.7 s

    12.7 s

    Visually, the page fills in at 12.7 s (Speed Index). Good is under 3.4 s.

  • Total Blocking Time: 1.6 s

    1.6 s

    Scripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.

  • Real-user INP: 396 ms

    396 ms

    Real visitors wait 396 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • 53 images without width and height

    53 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) got 14% slower for real visitors

    +14%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 318 ms to 365 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +2%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 5.1 s to 5.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

1 checks passed
  • Cumulative Layout Shift: 0.051

    0.051

    The layout barely moves while loading (CLS 0.051, good is under 0.1).

Images and page weight

4 to fix38
  • Page weight: 14.5 MB in 223 requests

    14.5 MB

    Your homepage downloads 14.5 MB in 223 requests on a phone: images 6.4 MB (91), scripts 4.3 MB (60) and media 3.4 MB (2). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    O1CN01gqgwq222p04sSPwnt_!!6000000007168-1-tps-500-410.gif weighs 5.4 MB. On a phone connection a single image that size takes seconds.

  • 7 images below the first screen load straight away

    7 images further down the page (5.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    58 KiB

    1 image is downloaded at several times the size a phone draws it, for example O1CN01OXAz3J1tqWrFDznin_!!6000000005953-2-tps-2160-1086.png at 2,160 px wide, shown at 342 px. Resized copies would save about 58 KiB.

  • 1 image in older formats

    1 image (419 KiB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • About 4.1 g of CO₂ per visit

    4.11 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.11 g of CO₂e: 493.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

6 to fix79
  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

  • 26 text elements with low contrast

    26 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 25 links without text

    25 visible links have no text or label, so screen readers cannot say where they go.

  • 17 tap targets too small

    17 tap targets are too small or too close together to hit reliably with a finger.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

SEO

6 to fixGoogle 7771
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • 86 links crawlers can't follow

    86 links have no real href, so search engines can't follow them.

  • Title is long (84 characters)

    Your title is 84 characters, so Google will cut it off around 60: “Empower Your Business in USA & Canada with Alibaba Cloud's Cloud Products & Services”.

  • 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 long (200 characters)

    Your meta description is 200 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 7 links with vague text

    7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • Open Graph partly set

    Open Graph is missing og:title and og:description, so shared links fall back to guesses.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 51 internal links, 14 external

    The homepage links to 51 pages on alibabacloud.com and 14 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://www.alibabacloud.com/en?_p_lc=5.

  • 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.alibabacloud.com/sitemaps/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    11%

    A phone browser shows 1,747 words, but the HTML your server sends has only 191. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • 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.alibabacloud.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

5 to fix63
  • 6 pages without a title

    https://www.alibabacloud.com/trust-center, https://www.alibabacloud.com/customers, https://www.alibabacloud.com/about/analyst-reports, https://www.alibabacloud.com/pricing-calculator, https://www.alibabacloud.com/product/ecs and https://www.alibabacloud.com/product/swas have no <title>, so Google invents the link text in results.

  • 2 pages share a title

    https://www.alibabacloud.com/en?_p_lc=5 and / all use the title “Empower Your Business in USA & Canada with Alibaba Cloud's Cloud Prod…”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://www.alibabacloud.com/trust-center, https://www.alibabacloud.com/customers, https://www.alibabacloud.com/about/analyst-reports, https://www.alibabacloud.com/pricing-calculator, https://www.alibabacloud.com/product/ecs and https://www.alibabacloud.com/product/swas have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 links to non-canonical URLs

    Your homepage links to 9 pages by a URL that isn't their canonical one, for example /, whose canonical is https://www.alibabacloud.com/en?_p_lc=5. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 15 pages without an H1

    /, https://www.alibabacloud.com/product, https://www.alibabacloud.com/ai-assistant, https://www.alibabacloud.com/contact-sales, https://www.alibabacloud.com/help and https://www.alibabacloud.com/about and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.alibabacloud.com/help 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.

  • 10 pages slow to respond

    https://www.alibabacloud.com/help, https://www.alibabacloud.com/about, https://www.alibabacloud.com/china-gateway, https://www.alibabacloud.com/global-locations, https://www.alibabacloud.com/trust-center and https://www.alibabacloud.com/customers and 4 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 33 found) and read each the way a search engine does.

2 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

Best practices

5 to fixGoogle 6969
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5662674&Ver=2&mid=630e6e0e-973f-4a42-a7f8-5ce3ac88e5c3&bo=1&sid=5dbd5b60cb5011f1b3bca7e9662ca25a&vid=5dbd7dd0cb5011f193562f88ba5f42db&vids=1&msclkid=N&pi=918639831&lg=.

  • 10 small tap targets

    10 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 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.”).

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot assign to read only property 'open' of object '#<Window>'”.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix70
  • Thin social proof

    Social proof on the homepage: 1 customer or partner logo. 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,747 words of copy

    The homepage carries about 1,747 words of visible text.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Start For Free”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Pricing”, “Contact Us” and “Pricing Calculator”.

Privacy and tracking

  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 2 mores (measured from a US location before any click). A consent tool (TrustArc) is installed; check it blocks these until visitors agree where the law requires it.

  • 25 cookies set on arrival

    25

    Opening the homepage sets 25 cookies (measured from a US location before any click).

  • 39 other companies contacted

    Loading the homepage contacts 39 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: TrustArc

    A consent management tool (TrustArc) loads with the page.

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 alibabacloud.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2009.

Stack

Framework
React

Company

Founded
2009

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 57 issues on alibabacloud.com, including 26 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25