easystack.cn website review

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

10 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.4 s faster on a phone.

Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.

About 61 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

3 third-party services load with your homepage (Baidu Analytics, baidu.com and bdstatic.com), adding 41 KiB and 41 ms of main-thread time.

Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need.

About 11 KiB of CSS is downloaded but never applied on this page.

7 KiB could be saved by minifying JavaScript.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 16.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 4.7 MB in 70 requests on a phone: images 4.2 MB (34), scripts 336 KiB (12) and other files 161 KiB (23). Under 2 MB keeps phones on slow connections fast.

3 images (532 KiB) are 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.

5 images further down the page (577 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

6 buttons have no accessible name, so screen readers announce just “button”.

Some lists contain elements other than list items, which screen readers announce wrongly.

<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 40 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No XML sitemap at https://easystack.cn/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 118 pages on easystack.cn and 10 external pages.

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.

There is no /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.

/, /products/cloud-foundation, /products/cloud-native-foundation, /infrastructures/ECP/overview and /infrastructures/ESCL/overview all use the title “EasyStack易捷行云 | 私有云平台,企业云计算产品，新基建云服务厂商”. Search engines can't tell which page to show for a search, so each competes with the others.

/products/cloud-foundation, /products/cloud-native-foundation, /infrastructures/ECP/overview and /infrastructures/ESCL/overview use the same meta description. A description written for each page earns more clicks.

/cloud-products/nova/overview, /cloud-products/alcubierre/overview, /cloud-products/proton/overview, /cloud-products/eks/overview, /cloud-products/eks-managed/overview and /cloud-products/ironic/overview and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

/cloud-products/nova/overview, /cloud-products/alcubierre/overview, /cloud-products/proton/overview, /cloud-products/eks/overview, /products/cloud-native-foundation and /cloud-products/eks-managed/overview and 8 others have 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.

/cloud-products/nova/overview, /cloud-products/eks/overview, /products/cloud-native-foundation, /cloud-products/eks-managed/overview, /cloud-products/ironic/overview and /cloud-products/thor/overview took over 3 s to send their HTML from our server.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 (Unauthorized)”.

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

Large scripts ship without source maps.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

easystack.cn has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage has only about 78 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

DMARC is set to p=none, so mail pretending to be easystack.cn is still delivered. Reports are on, so moving to quarantine is the next step.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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.

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