https://kiroaas.hnew.city/

Page structure & technical metrics

Words

939

Action candidates

9

Images

10

HTML

64 KB

Copy

Title chars
66
Meta chars
116
H1
1
H2
8

Action

Primary

立即开始

Forms
0
On-site links
18
Off-site links
13

Security & metadata

HTTPS
yes
HSTS
yes
CSP
no
nosniff
yes
viewport
yes
Icon
yes
JSON-LD
yes
Analytics
no

Page

Vite / React / Tailwind

Scripts
1 ext / 5 inline
Lang
en
Third-party hosts
no

Lighthouse

Simulated mobile · Performance

No measurement available

View details

No Lighthouse measurement available; no scores assigned. Attempted 2026-09-05T05:01:27.836Z · timeout

01 / WHAT WORKS

What makes it work

Immediate protocol clarity and ecosystem compatibility

The page directly addresses developer workflow requirements by confirming OpenAI direct replacement, Anthropic protocol parity, streaming SSE, and tool calling alongside client integrations like Cursor and Claude Code.

Disciplined terminal aesthetic and color rhythm

Using JetBrains Mono for code comments like '// Kiro 即服务' against a 0a0a0a backdrop creates an authentic command-line feel without visual clutter.

02 / NEXT STEPS

Where to go next

  1. 01

    Establish a single primary hero CTA with client OS detection

    Both macOS and Windows x64 render as identical high-saturation lime pill buttons. On mobile and narrow viewports, these stack vertically and compete for user attention instead of offering one decisive next step.

    Detect navigator.userAgent on mount. Render the matching OS as the solitary lime filled CTA, and render alternative platforms as a subtle secondary link or dropdown below. Verify at 1440px and 390px that only one filled lime button leads the viewport.

  2. 02

    Consolidate double announcement pills above the headline

    The KiroaaS Cloud notice and the v1.2.1 release pill sit on top of each other right above the H1. On mobile this pushes the core value proposition below the fold.

    Merge release status and cloud availability into a single unified pill badge or relocate the changelog link into the top navigation bar. Verify at 390px that H1 begins within the top 240px of the screen.

03 / DESIGN LANGUAGE

A design system you can reuse

Colors

Background

#0a0a0a

Text

#ffffff

Accent

#ffffff

Typography

Display font
Inter
Body font
Inter
Heading / body
96px / 16px

Spacing & shape

Section gap
0px
Component inset
Card radius
Button radius
3.35544e+07px

CLEARER WORDS

Copy Revision Diff

Now

全新 KiroaaS Cloud — 绕开限制,找回 Claude

SUGGESTED COPY

全新 KiroaaS Cloud:网络中转直连,即刻恢复 Claude 访问

Removes loose spacing around punctuation and sharpens the feature description into a clear technical capability.
Now

绕开限制, 找回你的 Claude。

SUGGESTED COPY

突破网络阻断,无缝恢复 Claude 编码体验。

Fixes irregular whitespace after the comma and tightens the headline for developer clarity.

04 / EVIDENCE

The detail behind the report

Explore each observation, recommendation and captured record.

Taste1 observations

Gradient-clipped headline

Gradient text on the H1 is a generator flourish. It rarely helps the claim.

Set the headline in a solid ink color with weight, not a rainbow fill.

bg-clip-text text-transparent
Conversion3 observations

The page overflows on a phone

High

Horizontal overflow is a bounce on mobile. Most vibe traffic is a phone, and a sideways page never converts.

Fix the overflowing element. Check 390px width. No min-width on full-bleed rows.

overflow-x on 390px viewport

No human or proof on the page

Medium

A stranger landing on an AI-looking site with no maker, no customer, and no contact will not give you an email.

Add a real name, a real face, a real contact method, or one real customer line.

no about, no first-person, no quote

No analytics on the live page

Medium

If you cannot see who bounced, you cannot tell if the next fix worked. Shipping without a counter is flying blind.

Put Plausible, PostHog, or GA4 on the public pages. One snippet is enough.

no gtag / plausible / posthog / umami
Launch1 observations

No Content-Security-Policy

A CSP is the standard way to limit script sources. Vibe-coded pages often load anything, including injected scripts.

Start with a report-only CSP, then default-src 'self' and an explicit script-src.

content-security-policy missing
Link preview

05 / MAKE IT HAPPEN

Give your AI a clear next step

Use the improvement prompt for this page, or the design prompt to borrow its visual language. “Recreate” includes references and implementation steps. Paste either into your coding assistant.

Preview full instructions
Refactor the hero section of the landing page in src/components/Hero.tsx (or corresponding route): 1. Inspect client userAgent to determine current operating system (macOS vs Windows). Render the detected platform as the single primary button using lime-400 background (#84.1% lightness in oklch), and show other platforms ('Other builds: macOS / Windows') as a neutral text link underneath. 2. Consolidate the two badges above the H1 ('全新 KiroaaS Cloud' and 'v1.2.1 已发布') into one horizontal badge: display the version tag with a green indicator, followed by a separator and the cloud announcement link. 3. Clean up typography spaces in Chinese copy strings to avoid stray spaces after commas. 4. Retain all existing design tokens: bg #0a0a0a, text #ffffff, Inter body font, JetBrains Mono for code comments, rounded-full pills, and existing navigation links.