Website review, no card needed
asiacloudserver.com website review
Visit site (opens in a new tab)Reviewed 7 November 202643 issues · 87 checks
This review found 43 issues worth fixing on asiacloudserver.com, 20 of them high impact, across 87 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
68DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.9 s
1.9 s
2.8 s
3.7 s
4.7 s
5.6 s
6.5 s
7.5 s
Speed
Use efficient cache lifetimes
20.6 s · 11.0 MB48 files are served with short cache lifetimes, so returning visitors download them again (11.0 MB).
Improve image delivery
15.6 s · 9.0 MB6 images could be 9.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 15.6 s faster on a phone.
Render-blocking requests
1.6 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Font display
1.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
480 ms · 175 KiBAbout 175 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 480 ms faster on a phone.
Reduce unused CSS
160 ms · 65 KiBAbout 65 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 160 ms faster on a phone.
Minify CSS
160 ms · 5 KiB5 KiB could be saved by minifying CSS.
3 third-party services on the page
3 third-party services load with your homepage (Google Tag Manager, Google Fonts and Google Analytics), adding 178 KiB and 95 ms of main-thread time.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 55 ms. During a long task the page ignores taps.
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.
2 checks passed
Main-thread work: 0.7 s
A phone's processor spends 0.7 s on main-thread work while loading, 332 ms of it running JavaScript. That is comfortably low.
Server response: 228 ms
228 msYour server sent the HTML in 228 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 26.9 s
26.9 sYour largest element takes 26.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “CREATE A VIBRANT ONLINE IDENTITY WordPress Hosting: SMEs, s…”.
Time to Interactive: 27.1 s
27.1 sThe page becomes fully interactive after 27.1 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.322
0.322The layout shifts by 0.322 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 6.6 s
6.6 sVisually, the page fills in at 6.6 s (Speed Index). Good is under 3.4 s.
22 images without width and height
22 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
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.
2 checks passed
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 13 ms
13 msScripts block the page for only 13 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 11.7 MB in 61 requests
11.7 MBYour homepage downloads 11.7 MB in 61 requests on a phone: images 10.7 MB (32), fonts 539 KiB (11) and scripts 399 KiB (9). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (47 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.
3 images below the first screen load straight away
3 images further down the page (91 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.3 g of CO₂ per visit
3.32 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.32 g of CO₂e: 398.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Invalid ARIA attributes
2 elements use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (2 elements)
Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.
ARIA attributes must conform to valid values (2 elements)
ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.
Hidden but focusable
11 elements hidden from screen readers can still receive keyboard focus.
ARIA input fields must have an accessible name (2 elements)
ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
13 links without text
13 visible links have no text or label, so screen readers cannot say where they go.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Elements marked as presentational should be consistently ignored (2 elements)
Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 31 images in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 15 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
17 links with vague text
17 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Invalid hreflang
Your hreflang tags are invalid, so Google may show the wrong language version.
63 internal links, 12 external
The homepage links to 63 pages on asiacloudserver.com and 12 external pages.
6 checks passed
Meta description: 125 characters
Your meta description is 125 characters: “领先的香港虚拟主机,云端管理主机,WordPress 主机,独立主机,弹性云计算,VPShosting 为香港及中国企业提供最优的商业主机解决方案,提供大容量与高可用性的香港虚拟主机,并设有不同的香港虚拟主机计划,务必让你可以更加即时地发…”.
Title: 38 characters
Your title is a healthy 38 characters: “香港虚拟主机,WordPress 主机,Linux&Windows 云端主机”.
Canonical URL set
The canonical URL is https://www.vpshosting.com.hk/zh/.
Structured data in place
Structured data found: BreadcrumbList, WebPage and WebSite.
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.vpshosting.com.hk/sitemap_index.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.vpshosting.com.hk/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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (928 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages share a title
/, https://www.vpshosting.com.hk/en and https://www.vpshosting.com.hk/zh all use the title “香港虚拟主机,WordPress 主机,Linux&Windows 云端主机”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://www.vpshosting.com.hk/blog/how-should-sme-choose-their-vps-hosting and https://www.vpshosting.com.hk/blog/%E9%81%B8%E6%93%87-vps-%E8%99%9B%E6%93%AC%E4%BC%BA%E6%9C%8D%E5%99%A8%E7%9A%84-4-%E5%A4%A7%E5%8E%9F%E5%9B%A0 have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.vpshosting.com.hk/en and https://www.vpshosting.com.hk/zh use the same meta description. A description written for each page earns more clicks.
10 links to non-canonical URLs
Your homepage links to 10 pages by a URL that isn't their canonical one, for example https://www.vpshosting.com.hk/en, whose canonical is https://www.vpshosting.com.hk/zh. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
10 pages without an H1
https://www.vpshosting.com.hk/en, https://www.vpshosting.com.hk/zh, https://www.vpshosting.com.hk/linux-vps-hosting, https://www.vpshosting.com.hk/window-vps-hosting, https://www.vpshosting.com.hk/linux-cloud-hosting-servers and https://www.vpshosting.com.hk/windows-cloud-hosting-servers and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.vpshosting.com.hk/zh 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.
5 pages slow to respond
https://www.vpshosting.com.hk/zh, https://www.vpshosting.com.hk/window-vps-hosting, https://www.vpshosting.com.hk/linux-cloud-hosting-servers, https://www.vpshosting.com.hk/windows-cloud-hosting-servers and https://www.vpshosting.com.hk/managed-dedicated-servers took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 36 found) and read each the way a search engine does.
3 checks passed
Linked pages load
13 pages of 15 loaded without an error (the rest turned automated requests away).
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
4 small tap targets
4 of 16 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.”).
1 JavaScript error while loading
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 404 ()”.
7 low-resolution images
7 images are 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
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.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
About 931 words of copy
The homepage carries about 931 words of visible text.
5 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact Us”.
Social proof on the page
Social proof on the homepage: 9 testimonial or review blocks and 8 customer or partner logos.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
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.
4 other companies contacted
Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 asiacloudserver.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- Asia Web Service Ltd
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on asiacloudserver.com, including 11 speed issues, 4 SEO issues and 1 conversion gap. 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.