Website review, no card needed
nebuacloud.com website review
Visit site (opens in a new tab)Reviewed 10 November 202626 issues · 74 checks
This review found 26 issues worth fixing on nebuacloud.com, 9 of them high impact, across 74 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
75CClosest competitors among SaaS websites
Compare side by sideOne score from every part of this review. How it works
Speed
Reduce unused JavaScript
14.6 s · 2.8 MBAbout 2.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 14.6 s faster on a phone.
Improve image delivery
950 ms · 191 KiB3 images could be 191 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 950 ms faster on a phone.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 166 ms
166 msGoogle Tag Manager costs a phone 166 ms of main-thread work and 308 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.
Document request latency
235 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
2 third-party services on the page
2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 309 KiB and 166 ms of main-thread time.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 140 ms. During a long task the page ignores taps.
Reduce unused CSS
96 KiBAbout 96 KiB of CSS is downloaded but never applied on this page.
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.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 986 ms of it running JavaScript. That is comfortably low.
Server response: 532 ms
532 msYour server sent the HTML in 532 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 27.9 s
27.9 sYour largest element takes 27.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Autonomous Private Cloud Infrastructure Platform”.
Time to Interactive: 27.9 s
27.9 sThe page becomes fully interactive after 27.9 s. Good is under 3.8 s.
Speed Index: 5.8 s
5.8 sVisually, the page fills in at 5.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Total Blocking Time: 341 ms
341 msScripts block taps and scrolling for 341 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image 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.
1 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.0 MB in 48 requests
5.0 MBYour homepage downloads 5.0 MB in 48 requests on a phone: scripts 4.2 MB (21), HTML 351 KiB (1) and images 327 KiB (7). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (26 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.41 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.41 g of CO₂e: 169.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (8 elements)
Interactive controls must not be nested: 8 elements on the page fail this check, rated serious by axe-core.
ARIA progressbar nodes must have an accessible name (1 element)
ARIA progressbar nodes must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (153 elements)
All page content should be contained by landmarks: 153 elements on the page fail this check, rated moderate by axe-core.
3 links without text
3 visible 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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 4 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
14 internal links, 7 external
The homepage links to 14 pages on nebuacloud.com and 7 external pages.
8 checks passed
Meta description: 112 characters
Your meta description is 112 characters: “Discover a private cloud infrastructure automation platform for secure, scalable, and cost-effective operations.”.
One H1 headline
Your main headline reads: “Autonomous Private Cloud Infrastructure Platform”.
Title: 52 characters
Your title is a healthy 52 characters: “NebuaCloud - Private Cloud Infrastructure Automation”.
Canonical URL set
The canonical URL is https://nebuacloud.com/.
Structured data in place
Structured data found: Organization.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://nebuacloud.com/sitemap/sitemap-index.xml.
AI search readiness
No llms.txt
There is no https://nebuacloud.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.
3 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and description; sameAs (social profiles) and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,509 words), so crawlers that don't run JavaScript still read it.
Other pages
8 pages share 2 titles
/, https://nebuacloud.com/legal/terms, https://nebuacloud.com/legal/privacy-policy, https://nebuacloud.com/legal/refund, https://nebuacloud.com/legal/delivery-policy and https://nebuacloud.com/legal/delete-policie all use the title “NebuaCloud - Private Cloud Infrastructure Automation”, and 1 other title repeat too. 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://nebuacloud.com/organization and https://nebuacloud.com/legal/dpa have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages share a meta description
https://nebuacloud.com/legal/terms, https://nebuacloud.com/legal/privacy-policy, https://nebuacloud.com/legal/refund, https://nebuacloud.com/legal/delivery-policy and https://nebuacloud.com/legal/delete-policie use the same meta description. A description written for each page earns more clicks.
9 pages without an H1
https://nebuacloud.com/organization, https://nebuacloud.com/pricing, https://nebuacloud.com/docs, https://nebuacloud.com/legal/terms, https://nebuacloud.com/legal/privacy-policy and https://nebuacloud.com/legal/refund and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.
6 pages with very little text
https://nebuacloud.com/business, https://nebuacloud.com/legal/terms, https://nebuacloud.com/legal/privacy-policy, https://nebuacloud.com/legal/refund, https://nebuacloud.com/legal/delivery-policy and https://nebuacloud.com/legal/delete-policie 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.
12 internal pages checked
We fetched 12 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 12 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 12 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Minified React error #421; visit https://reactjs.org/docs/error-decoder.html?invariant=421 for the full message or use …”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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,351 words of copy
The homepage carries about 1,351 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Schedule a Session”.
8 calls to action
The homepage has 8 calls to action, for example “Contact”, “Get Started Now” and “Start Free”.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
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.
2 cookies set on arrival
2Opening the homepage sets 2 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.
3 other companies contacted
Loading the homepage contacts 3 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 nebuacloud.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Belcloud LTD
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 26 issues on nebuacloud.com, including 10 speed issues and 2 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.