Public audit / not a customer

Discover What the Audit Engine Found on www.folioverse.app

Nebula ran its evidence-backed audit on www.folioverse.app on August 3, 2026. Folioverse is not a Nebula customer. This page shows the raw output of the same engine every free scan uses - 5 findings, evidence included.

Score

5.6/10

Grade

C

Findings

5

Audited

August 3, 2026

Same engine, public URL

Disclosure: Folioverse did not request this audit and is not affiliated with Nebula Components. This teardown is published to demonstrate what the audit engine produces on a real, well-known page - not to imply any commercial relationship. All findings are evidence-backed; source, selector, and confidence are included per finding. Folioverse may update their page at any time; this reflects a snapshot taken August 3, 2026.

Page snapshot · August 3, 2026

www.folioverse.app
Folioverse landing page snapshot - August 3, 2026

Five 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

No Static H1 Detected

Priority 4/10Quick Win

No <h1> tag was found in the fetched document. If the primary promise is rendered only through client-side code, some readers and extraction systems receive no primary heading.

Evidence

Fetched source: h1 count = 0. Page title: "Folioverse - AI Portfolio Mentor for UX Designers". Snapshot timestamp: 2026-08-03T07:48:48Z.

Recommended Fix

Render one descriptive H1 in the initial HTML and align it with the UX-designer portfolio outcome.

Finding 2

No Source-Level CTA Candidate

Priority 4/10Quick Win

No button or link text was found in fetched source HTML. Client-rendered controls may exist, so browser validation is required before treating this as a visible CTA failure.

Evidence

Fetched source: no button or link text candidate. Rendered primary journey remains unverified. Snapshot timestamp: 2026-08-03T07:48:48Z.

Recommended Fix

Inspect the rendered hero on mobile and desktop. Make the first action explicit without adding unsupported performance claims.

Finding 3

Above-Fold Source Proxy Needs Rendered Validation

Priority 4/10Quick Win

The early HTML proxy lacks a headline, clickable control, or offer term in its first 3,000 characters. This is a source-order warning, not proof of the rendered layout.

Evidence

Early source proxy missing: H1, primary CTA, and price/offer signal together in the first 3,000 source characters. Snapshot timestamp: 2026-08-03T07:48:48Z.

Recommended Fix

Inspect the first viewport at 375px and desktop widths. Change the page only if the rendered value proposition or action is actually unclear.

Finding 4

Ad Tracking Not Observed in Static Source

Priority 4/10Major Project

No recognized ad-tracking artifact was observed in fetched source HTML. Runtime or server-side tracking remains unknown, so the public source alone cannot explain the reported zero-signup result.

Evidence

Not observed: Facebook Pixel initializer, GA4 measurement ID, UTM-bearing link, or explicit conversion call. Snapshot timestamp: 2026-08-03T07:48:48Z.

Recommended Fix

Validate the Google Ads click, landing, CTA, portfolio input, and signup events with consent-aware browser/network inspection.

Finding 5

SEO Foundations: Missing H1

Priority 2.5/10Quick Win

The title and meta description are present, but the static document has no H1. This is a structural issue, not proof of poor rankings or poor AI visibility.

Evidence

title: "Folioverse - AI Portfolio Mentor for UX Designers" (49 chars); meta description: 135 chars; h1 count: 0. Snapshot timestamp: 2026-08-03T07:48:48Z.

Recommended Fix

Add exactly one descriptive H1 that states the portfolio outcome and intended UX-designer audience.

What This Demonstrates

Folioverse founder Ömer Arı identified himself as a product design lead building Folioverse and reported the following in an IndieHackers post: 91 Google Ads clicks, 5.58% CTR, €100 total spend, zero signups, and paid visitors spending an average of 10 seconds on the landing page. Source: https://www.indiehackers.com/post/i-spent-100-on-google-ads-for-my-design-saas-here-is-the-report-that-explained-the-0-signups-16f38e1e19. This teardown does not claim the page caused those outcomes. It identifies source-level gaps that should be confirmed in a rendered browser and in the actual ad-to-signup event path.

Work at Folioverse? Verify ownership to manage this teardown in your workspace.

Claim this teardown

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