# Give me comprehensive website feedback for https://sedayagroup.id

[Open the live Fudge conversation](https://design.withfudge.com/share/3h75uu8cjx/give_me_comprehensive_website_feedback_for_https_sedayagroup_id/)

Last updated: 2026-08-13

```fudge_website_review
{"schemaVersion":1,"reviewKind":"initial","state":"incomplete","target":{"submittedUrl":"https://sedayagroup.id","finalUrl":"https://sedayagroup.id/","canonicalOrigin":"https://sedayagroup.id"},"score":5,"scoreTitle":"Soft hierarchy","explanation":"Sedaya has a credible property-discovery foundation: clear project inventory, strong local proposition, and a restrained red/cream palette. The experience loses force through a low-contrast hero, dense repeated cards, cramped mobile edges, and generic visual treatment. The homepage desktop capture was incomplete, so lower-page desktop judgments are limited.","categories":[{"id":"purpose_clarity","score":6,"summary":"The housing proposition and local service area are clear, but the hero asks visitors to process too many proof points before choosing a path.","findingIds":["f1","f2"]},{"id":"visual_hierarchy","score":5,"summary":"The hero has a strong headline and CTA, but repetitive project cards and similar section treatments flatten the journey.","findingIds":["f2","f3"]},{"id":"readability_accessibility","score":4,"summary":"The structured inspection reports severe hero contrast issues and several low-contrast status/button treatments.","findingIds":["f1","f4"]},{"id":"consistency_polish","score":5,"summary":"The red, cream, and dark-brown system is coherent, but glow shadows, repeated labels, and an occluded card indicate unfinished craft.","findingIds":["f3","f4","f5"]},{"id":"mobile_experience","score":4,"summary":"Mobile content reaches the viewport edge, cards are cramped, and the truncated full-page capture prevents confidence in the complete mobile journey.","findingIds":["f2","f5"]}],"strongest":{"title":"Local housing inventory is easy to understand","summary":"The homepage quickly establishes Sedaya as a Medan-area housing developer and exposes a useful portfolio of named projects with practical attributes such as bedrooms, bathrooms, and availability.","evidenceIds":["f2"]},"findings":[{"id":"f1","number":1,"priority":"high","title":"Repair the hero contrast before polishing anything else","preview":"The hero renders white headline, body copy, proof chips, and CTAs against a backdrop the structured check resolves as near-background, producing reported contrast ratios around 1.04–1.05:1.","detailAccess":"included","evidenceMappingIds":["map-7f7ee60688dfd9befc67425787504127"],"referencePinIds":["454"]},{"id":"f2","number":2,"priority":"high","title":"Turn the homepage into a guided buyer path","preview":"The page presents a proposition, stats, company story, and a large project inventory, but the hierarchy does not clearly separate browse, compare, and contact actions.","detailAccess":"included","evidenceMappingIds":[],"referencePinIds":["454","5597","5588"]},{"id":"f3","number":3,"priority":"medium","title":"Make project cards carry more decision value with less repetition","preview":"The portfolio repeats the same label, room-count string, WhatsApp action, and detail action across cards; the repeated structure makes the inventory feel like a template grid rather than a useful comparison tool.","detailAccess":"included","evidenceMappingIds":[],"referencePinIds":["454","5597"]},{"id":"f4","number":4,"priority":"medium","title":"Remove decorative glow and fix status treatments","preview":"Red and green chromatic shadows are applied to hero and WhatsApp buttons, while the detector reports white text on WhatsApp green at 1.98:1 and a sold-out label at 3.19:1.","detailAccess":"included","evidenceMappingIds":[],"referencePinIds":["5602"]},{"id":"f5","number":5,"priority":"medium","title":"Give mobile content breathing room and prevent text occlusion","preview":"The mobile inspection reports text sitting within 12px of the viewport edge, cramped card padding, clipped overflow, and a project label with 100% text occlusion.","detailAccess":"included","evidenceMappingIds":[],"referencePinIds":["5588"]}],"foundation":{"decision":"page_changes_first","title":"Fix the homepage conversion path first","explanation":"The main problems are concentrated in the homepage hero, project inventory, and mobile card treatment rather than requiring a site-wide design-guide reset. Establish a readable hero and clearer browse-to-contact path first; then propagate the card and status rules across project pages.","findingIds":["f1","f2","f3","f5"],"affectedAreas":["typography","color","spacing_layout","components","responsive_behavior","accessibility_interaction"]}}
```

```fudge_review_map
{"schemaVersion":1,"frames":[{"frameId":"frame-mobile-home","inspectionId":"8e95a836-7e82-4bc8-8fcb-9b0ef975acee","pageUrl":"https://sedayagroup.id/","pageTitle":"Sedaya Property | Rumah Subsidi Terbaik di Medan & Sekitarnya","viewport":"mobile","screenshotUrl":"https://api.withfudge.com/v1/shares/47a034b9-f7c9-45ec-b348-d16af3539317/attachments/f28a0fa8af248b20616e3634/1.jpg","screenshotWidth":390,"screenshotHeight":6000,"completeness":"truncated","markers":[{"findingId":"f1","findingNumber":1,"findingTitle":"Repair the hero contrast before polishing anything else","mappingId":"map-7f7ee60688dfd9befc67425787504127","region":{"x":615,"y":353,"width":8770,"height":199,"scale":10000}}]},{"frameId":"frame-desktop-about","inspectionId":"78de11c7-56e3-4e70-89e6-2a822a43f82d","pageUrl":"https://sedayagroup.id/tentang-kami/","pageTitle":"sedayagroup.id","viewport":"desktop","screenshotUrl":"https://api.withfudge.com/v1/shares/47a034b9-f7c9-45ec-b348-d16af3539317/attachments/f28a0fa8af248b20616e3634/2.jpg","screenshotWidth":1440,"screenshotHeight":3725,"completeness":"complete","markers":[]}]}
```

```fudge_finding_evidence
{"schemaVersion":1,"findingId":"f1","findingNumber":1,"crops":[{"mappingId":"map-7f7ee60688dfd9befc67425787504127","screenshotUrl":"https://api.withfudge.com/v1/shares/47a034b9-f7c9-45ec-b348-d16af3539317/attachments/f28a0fa8af248b20616e3634/1.jpg","sourceWidth":390,"sourceHeight":6000,"crop":{"x":0,"y":273,"width":10000,"height":359,"scale":10000},"alt":"Sedaya mobile hero showing the headline, proof points, and primary actions","caption":"The mobile hero concentrates white copy and calls to action over a backdrop that needs a deterministic dark treatment."}]}
```

Score context: 5/10, with the homepage desktop full-page capture incomplete. The mobile homepage and a complete desktop “Tentang Kami” page provide enough coverage for a useful initial review, but not for confident whole-homepage desktop scoring.

What works:
- The visitor mode is clear: this is a persuade-and-browse experience for people looking for subsidized housing around Medan, Deli Serdang, and Binjai.
- The local proposition is concrete rather than abstract: the hero names the region, financing direction, and housing category.
- The project inventory is the strongest product feature. Named developments, availability labels, room counts, and detail/WhatsApp actions give visitors a practical starting point.
- The rendered details show a coherent visual base: Inter, dark brown #1a1412, warm cream #fdf9f8, red #a03033, and muted brown-gray #6b5f5b.

What to fix, in priority order:

1. Hero contrast — high
   - What you see: the hero uses white copy and white controls over a backdrop that is not reliably dark in the retained style context.
   - Why it hurts: the first decision point becomes visually fragile; the proposition and CTA can disappear into the background.
   - Change: establish a deterministic dark copy surface or stronger overlay, simplify the proof chips, and make “Lihat Proyek” the dominant action.

2. Buyer path — high
   - What you see: proposition, metrics, company story, and portfolio appear as a long sequence without a sharply stated browse/compare/contact progression.
   - Why it hurts: visitors must infer whether to inspect projects, learn about Sedaya, or contact sales.
   - Change: label the journey explicitly: Browse projects → Compare key facts → Ask about availability. Put the project CTA immediately after the hero and repeat a compact contact action after the inventory.

3. Project inventory density — medium
   - What you see: repeated “Rumah Subsidi”, “Tersedia”, room-count, WhatsApp, and detail patterns appear across cards.
   - Why it hurts: the cards consume attention without creating strong comparison signals.
   - Change: prioritize price/cicilan, location, availability, and one differentiator; move repeated secondary metadata into a consistent compact spec row.

4. Decorative treatment and status contrast — medium
   - What you see: red/green chromatic glows are attached to action buttons, and WhatsApp green carries white text.
   - Why it hurts: the glow adds generic polish without helping the housing decision, while status/button treatments need clearer separation and exact contrast validation.
   - Change: remove glow shadows, use flat semantic states, and darken or restyle green actions before release.

5. Mobile card craft — medium
   - What you see: mobile content approaches the viewport edge, card padding is repeatedly flagged as cramped, and one project label is reported as fully occluded.
   - Why it hurts: browsing a long project list becomes tiring and one state can become unreadable.
   - Change: enforce a mobile page gutter, increase card padding, prevent positioned overlays from covering labels, and test long project names plus sold-out cards.

Vibe-coded appearance check

Craft: mixed
Originality: generic kit

| What you see | Kit or distinctive | Why it hurts |
|---|---|---|
| Inter used across the body, hero, headings, cards, and controls | Generic/default | It is clean but gives the property brand no typographic point of view; the detector flags it as overused. |
| Small tracked labels such as “Tentang Kami” and “Portofolio Kami” above headings | Generic/default | The repeated kicker pattern adds a familiar marketing scaffold rather than clarifying a unique housing story. |
| Red chromatic glow on the main hero button and green glow on repeated WhatsApp buttons | Generic/default | The effect is decorative, not informative, and makes actions feel like a template treatment. |
| Repeated rounded project cards with thin borders and wide diffuse red shadows | Generic/default | The cards look assembled from one UI recipe and the shadows compete with the actual property imagery and facts. |
| Auto-scrolling/animated top content and clipped overflow | Generic/default / unfinished craft | Motion and clipping introduce distraction and can make the page feel less controlled on mobile. |
| Repeated property-status pills and identical card metadata | Generic/default | The inventory reads as a repeated component system without enough project-specific differentiation. |
| The local housing proposition and named project inventory | Distinctive/product-specific content | These are the parts that make the site belong to Sedaya; they should carry more of the visual hierarchy.

Contrast attempts

| Element | Foreground | Background | Size / weight | WCAG | AA | AAA | APCA |
|---|---|---|---|---|---|---|---|
| Body pair | #1a1412 | #fdf9f8 | 16px / 400 | Unresolved | Unresolved | Unresolved | Unresolved |
| Hero headline and copy | #ffffff | #fdf9f8 | 36px / 800; 18px / 400 | 1.05:1 reported | Fail | Fail | Unresolved |
| Hero proof chips | #ffffff | #fdfaf9 | 13px / 600 | 1.04:1 reported | Fail | Fail | Unresolved |
| WhatsApp buttons | #ffffff | #25d366 | 13px / 600 | 1.98:1 reported | Fail | Fail | Unresolved |
| Sold-out label | #1a1412 | #6a6664 | 11px / 600 | 3.19:1 reported | Fail | Fail | Unresolved |

The supplied saved references were used as directional comparisons: Zillow for browse-first real-estate hierarchy, Royal for disciplined project presentation, Finding Dreamhouse for property browsing, and Eonna for restrained visual treatment. They are not claims about Sedaya’s implementation.

## First change

Replace the homepage hero treatment: add a reliable dark image overlay or solid dark panel behind the white copy, reduce the proof chips to three high-value claims, and make “Lihat Proyek” the dominant action with “Konsultasi Gratis” as the secondary action. Verify the mobile hero at 390px before touching the project-card grid.

## Implementation prompt

```text
Update the Sedaya homepage only, starting with the hero and preserving the existing red/cream/dark-brown identity.

Goal:
- Make the first screen immediately readable and guide housing buyers into either browsing projects or contacting Sedaya.

Evidence to address:
- The hero’s white headline, paragraph, proof chips, and CTAs are reported at roughly 1.04–1.05:1 against the retained backdrop context.
- The hero uses a red chromatic glow on the primary button.
- Mobile inspection reports content within 12px of the viewport edge.

Implement:
1. Place the hero copy on a deterministic dark surface: either a solid #1a1412 panel or a tested image overlay that keeps white text readable across the full copy region. Do not rely on the current pale backdrop context.
2. Keep the headline concise and make the first CTA “Lihat Proyek” visually primary. Keep “Konsultasi Gratis” secondary and adjacent.
3. Retain only three proof points; use short, concrete claims and avoid a row of small pills competing with the headline.
4. Remove the decorative red glow from the primary button. Use a clear filled red button with a restrained hover state.
5. Add at least 20–24px horizontal padding at the 390px mobile viewport and ensure no copy or card content reaches the viewport edge.
6. Preserve the existing brand colors, logo, Indonesian copy direction, project links, header behavior, and overall section order.

Reference direction:
- Use Zillow’s clearer browse-first real-estate hierarchy as a reference for separating discovery from contact.
- Use the Royal real-estate reference for a more disciplined project presentation; do not copy its visual style.

Checks:
- Desktop: confirm the hero headline, paragraph, proof points, and both CTAs form one clear reading order with no text over a light image area.
- Mobile at 390px: confirm the hero fits naturally, the primary CTA remains obvious, no horizontal overflow exists, and all text stays comfortably inset.
- Verify the hero text/backdrop and both button text/background pairs with an exact contrast check before release.
```

---

## Homepage fonts

The homepage primarily uses **Inter** throughout the header, hero, sections, project cards, buttons, and footer.

| Usage | Font | Size / weight | Line height |
|---|---|---:|---:|
| Body text | Inter | 16px / 400 | 25.6px |
| Hero heading | Inter | 36px / 800 | 39.6px |
| Section headings | Inter | 28px / 700 | 33.6px |
| Hero paragraph | Inter | 18px / 400 | 28.8px |
| Primary buttons | Inter | 16px / 600 | 16px |
| Card labels and controls | Inter | 13px / 600 | 13px |
| Small metadata | Inter | 11–13px / 400–600 | 17.6–20.8px |

`Times New Roman` is also present on the root HTML element as a browser-default fallback, but the visible homepage UI is rendered with Inter. The live inspection did not retain a previewable font source, so I can show the font usage but not an embedded font specimen.

![Sedaya homepage mobile view showing the hero and project content](https://api.withfudge.com/v1/shares/47a034b9-f7c9-45ec-b348-d16af3539317/attachments/f28a0fa8af248b20616e3634/1.jpg)

## Homepage contrast

| Element | Foreground | Background | Size / weight | WCAG | AA | AAA | APCA |
|---|---|---|---|---:|---|---|---:|
| Hero heading | `#ffffff` | Complex backdrop | 36px / 800 | Unresolved | Unresolved | Unresolved | Unresolved |
| Hero paragraph | `#ffffff` at 95% opacity | Complex backdrop | 18px / 400 | Unresolved — foreground transparency | Unresolved | Unresolved | Unresolved |
| Hero emphasized text | `#ffffff` at 95% opacity | Complex backdrop | 18px / 700 | Unresolved — foreground transparency | Unresolved | Unresolved | Unresolved |
| “Konsultasi Gratis” button | `#ffffff` | Complex backdrop | 16px / 600 | Unresolved | Unresolved | Unresolved | Unresolved |
| Primary red button | `#ffffff` | `#a03033` | 16px / 600 | **7.08:1** | Pass | **Pass** | **-88.51 Lc** |
| Hero proof chip | `#ffffff` | Complex backdrop | 13px / 600 | Unresolved | Unresolved | Unresolved | Unresolved |
| Hero proof chip | `#ffffff` | Complex backdrop | 13px / 600 | Unresolved | Unresolved | Unresolved | Unresolved |

The solid red primary button is the strongest confirmed pair: it passes both WCAG AA and AAA. The hero text cannot be given a reliable ratio because its backdrop is composited over a complex image/overlay; the WhatsApp and sold-out treatments also need a resolvable opaque backdrop before their contrast can be calculated. The main improvement is to place the hero copy on a deterministic dark surface, then recheck every hero text and CTA pair.

---

# Recommended direction: Inter + DM Serif Display

I would keep **Inter for body copy, navigation, buttons, project facts, and UI**, but use **DM Serif Display** for the hero headline and major section headings. It gives Sedaya a warmer, more property-oriented identity without forcing the whole interface into a decorative style.

![Sedaya homepage mobile hero and project content](https://api.withfudge.com/v1/shares/47a034b9-f7c9-45ec-b348-d16af3539317/attachments/f28a0fa8af248b20616e3634/1.jpg)

## Captured pages

[![Royal - Realestate Framer Website Template](https://pin.fontofweb.com/5597?format=jpg)](https://design.withfudge.com/share/pin-5597)

[Royal - Realestate Framer Website Template](https://design.withfudge.com/share/pin-5597)

[![Realator](https://pin.fontofweb.com/5587?format=jpg)](https://design.withfudge.com/share/pin-5587)

[Realator](https://design.withfudge.com/share/pin-5587)

[![Interior Design Studio in Bilbao - Andrea Diego](https://pin.fontofweb.com/1881?format=jpg)](https://design.withfudge.com/share/pin-1881)

[Interior Design Studio in Bilbao - Andrea Diego](https://design.withfudge.com/share/pin-1881)

These references support the **editorial property-brand direction** only; they do not establish the exact fonts used on those pages.

## Comparison

| Area | Current Inter | Proposed DM Serif Display |
|---|---|---|
| Personality | Neutral, practical, familiar | Warm, editorial, more memorable |
| Brand signal | Feels like a modern web interface | Feels more like a considered property brand |
| Best use | Body, navigation, buttons, prices, specifications | Hero headline and short section headings |
| Long text | Excellent | Not recommended |
| Project-card metadata | Clear and efficient | Too decorative at small sizes |
| Emotional tone | Functional and trustworthy | Aspirational and residential |
| Main risk | The site feels generic because Inter is used everywhere | It could feel too luxurious if used on every heading or card |

## How I would apply it

### Hero

Replace the current Inter hero heading with **DM Serif Display**:

- Desktop: proposed `56–64px`
- Mobile: proposed `40–44px`
- Weight: regular
- Line height: approximately `1.05–1.1`
- Maximum width: keep the headline to roughly two or three lines
- Use sentence case, not all caps

Example direction:

> Rumah subsidi yang terasa seperti rumah sendiri

Keep the supporting copy in Inter. This creates a clear split between the emotional promise and the practical information.

### Section headings

Use DM Serif Display for:

- “Membangun Lebih dari Sekadar Rumah”
- “Portofolio Kami”
- Short project-page headings
- The closing contact statement

Keep the small labels such as “Tentang Kami” and “Portofolio Kami” in Inter. This prevents the serif from becoming another repeated decorative costume.

### Project cards

Keep card titles in Inter, probably at `18–20px / 700`. Project cards contain practical information, so clarity should win over atmosphere. Reserve the distinctive heading font for the moments where Sedaya is telling its larger brand story.

```fudge-values
{"title":"Proposed homepage typography direction","values":[{"category":"Display type","label":"Hero heading","value":"DM Serif Display, 56–64px / regular / 1.05–1.1 line height"},{"category":"Display type","label":"Mobile hero heading","value":"DM Serif Display, 40–44px / regular / 1.05–1.1 line height"},{"category":"Display type","label":"Section headings","value":"DM Serif Display, 40–48px / regular"},{"category":"UI type","label":"Body and navigation","value":"Inter, 16px / 400"},{"category":"UI type","label":"Buttons and project facts","value":"Inter, 13–16px / 600"}]}
```

## Verdict

**Inter alone is clean but too generic for the homepage hero.**  
**Inter plus DM Serif Display is the stronger combination:** Inter preserves clarity for housing facts and actions, while DM Serif Display gives the brand a more distinctive residential character.

Do not apply the new heading font until the hero has a reliable dark overlay or solid dark copy panel. A more expressive typeface will not solve the existing hero backdrop problem by itself.