Public audit / not a customer
Discover What the Audit Engine Found on cloudcostwise.io
Nebula ran its evidence-backed audit on cloudcostwise.io on August 3, 2026. CloudWise is not a Nebula customer. This page shows the raw output of the same engine every free scan uses - 3 findings, evidence included.
Score
7.1/10
Grade
B
Findings
3
Audited
August 3, 2026
Same engine, public URL
Page snapshot · August 3, 2026

Three Findings
Ranked by observable priority. Each finding includes the evidence Nebula used - no opinion, no estimation. Priority scores are rule-based heuristics for fix order, not predicted conversion loss.
Finding 1
Ad Tracking Not Observed in Static Source
No recognized ad-tracking artifact was observed in the fetched source HTML. That does not prove runtime or server-side tracking is absent, but it means the public source does not provide evidence that paid conversion events are configured.
Evidence
Fetched source artifacts present: none. Not observed: Facebook Pixel initializer, GA4 measurement ID, UTM-bearing link, or explicit conversion call. Snapshot timestamp: 2026-08-03T07:38:25Z.
Recommended Fix
Run consent-aware browser and network validation. Confirm the actual ad click, landing, signup, and connected-account events before changing the page or spend.
Finding 2
Meta Description Runs Long
The meta description is 180 characters. Search snippets commonly show roughly 155 characters, so the final part of the message may be truncated.
Evidence
title: "CloudWise – Safe AWS Cost Remediation | CloudWise" (49 chars); meta description: 180 chars; one H1 detected. Snapshot timestamp: 2026-08-03T07:38:25Z.
Recommended Fix
Trim the description to a complete 120–155 character statement while preserving the strongest differentiator: safe, approval-based AWS remediation.
Finding 3
Above-Fold Source Proxy Needs Rendered Validation
The early HTML proxy contains a headline but no clickable control. This is a source-order warning, not proof that the rendered hero lacks a CTA.
Evidence
Early source proxy did not show a headline, primary CTA, or price/offer signal together in the first 3,000 characters. Rendered viewport position remains unverified. Snapshot timestamp: 2026-08-03T07:38:25Z.
Recommended Fix
Inspect the 375px and desktop rendered hero. Only change the page if the primary action is genuinely unclear or below the first viewport.
What This Demonstrates
CloudWise founder Rick described an explicit distribution problem in an IndieHackers feedback post: 0 paid customers after 8 months, approximately $2,700 in ad spend, around 6 trial signups, and 0 conversions. Source: https://www.indiehackers.com/post/looking-for-feedback-afec975212. This teardown does not claim the page caused those outcomes. The current snapshot shows a page with strong headline, CTA, proof, mobile, and AI-readiness signals; the remaining findings are static-source observations that require rendered or runtime validation before being treated as defects.
Work at CloudWise? Verify ownership to manage this teardown in your workspace.
Claim this teardownSee what it finds on your page
Same engine, your URL. Free, no signup. Results in under two minutes.
Find the Leak →Already know your page has issues? Skip the audit.
Fix one leak now, $97 →One finding. 48h delivery. No call, no retainer.