Aisthetic Review: useful concept, uneven execution (63/100)

Field	Value
Domain	aisthetic.app
Category	AI wardrobe organization and personalized outfit planning
Pricing	Not evidenced
Pages crawled	5
Crawl date	2026-10-08

Aisthetic presents a coherent consumer AI wardrobe assistant, and the homepage makes the core proposition understandable quickly. The strongest public dimensions are first impressions and positioning (72/100), usability (72/100), and technical SEO (72/100). The product story is concrete: digital closet organization, outfit recommendations, planning, and sustainability.

The score is held back by execution. Performance is 48/100: the homepage reached its largest content at 10.2 s in the mobile lab run, while the desktop /home sample recorded CLS 0.27. Design execution scored 58/100, with reported contrast failures, inconsistent mobile typography, small tap targets, and severe desktop layout shift. Writing quality scored 58/100, and editorial QA scored 55/100, including a linked /work 404. Accessibility scored 68/100: basic landmarks and heading structure were sound, but verified Lighthouse failures remain.

Aisthetic communicates a concrete product: an AI wardrobe assistant that organizes a digital closet, suggests outfits, supports planning, and promotes sustainability. The homepage explains photo and barcode ingestion, Gmail receipt scanning, weather-aware recommendations, and feedback-trained personalization. What it does not settle is who should care first: the audience remains implicit rather than anchored to one primary user or recurring wardrobe problem. That matters because Gmail access and personal clothing images create a higher trust burden than a simple styling app. Name one core user and pair the install promise with concise evidence about permissions, privacy, and image handling.

The homepage makes the basic workflow legible: users can add clothing through photos, barcodes, Gmail receipts, or AI-generated images, then receive weather-aware outfit suggestions and schedule looks. The emotional job—reducing decision fatigue—is also clear. The missing layer is decision support for audience and trust. The copy speaks broadly to anyone with a wardrobe, while the Gmail feature asks to scan order receipts without visible detail about scope, retention, or deletion in the supplied evidence. Add a concise “best for” statement and place a permissions-and-privacy explanation beside the install action, including scope, retention, and deletion behavior.

A first-time visitor can identify the product and reach Contact Me, but the decision journey lacks commercial context. The supplied crawl shows Install App and no pricing, plan, or purchase information before the App Store handoff. On mobile, the menu control measures 47×37px, and the primary install action is not in the visible homepage header inventory. The slow first load adds friction before either path begins: mobile LCP is 10.2s and TTI is 10.3s. Add cost or plan context, expose clear learn/install paths, enlarge the menu target to at least 44×44px, and state what happens after contact.

Aisthetic has a reasonable semantic base across the sampled pages: header, navigation, main, and footer landmarks are present, the homepage heading sequence is h1 → h2 → h2 → h2 → h2, and the declared language is en-US. Verified failures remain on the homepage. The audit reports 1 of 5 images missing alt text, failed color contrast, and at least one link without a discernible accessible name. CSS evidence also shows 8 animation declarations and 0 prefers-reduced-motion rules. Locate the failing selectors in Lighthouse or axe details, repair image alternatives, contrast, and link names, then add a reduced-motion path and complete keyboard and screen-reader verification.

The visual direction is distinctive and the sampled pages fit a 390px viewport, but production execution is inconsistent. Desktop CLS reaches 0.658, far above the 0.1 target, and the report flags layout-shift culprits and unsized images. At 390px, the homepage H1 is 109.4px with 33.7px paragraphs, while contact reports an 81.4px H1 and 86.9px paragraphs. Contrast audits fail on mobile and desktop, and the menu control is 47×37px. Reserve image space first, establish a bounded mobile type scale, correct rendered color pairs, and bring controls to at least 44×44px.

Mobile performance is the clearest measured weakness: the homepage reaches its largest content at 10,219.6 ms, while TTI is 10,324.0 ms. The run records 1,819 KiB across 69 requests, 45 blocking requests, an estimated 1,360 ms of render-blocking savings, and 334 KiB of unused JavaScript. Desktop /home is faster but still records CLS 0.2701. Prioritize these fixes in order:nn1. Prioritize the mobile LCP resource.n2. Defer non-critical scripts.n3. Reserve image dimensions.nnPSI supplied no CrUX field data, so these are lab results; re-test against LCP ≤2.5s and CLS ≤0.1.

The homepage has useful building blocks—“Organize,” “Optimize,” “Plan ahead,” and “Sustain”—but the first-screen hierarchy leads with the brand label “aisthetic” rather than the user outcome. N1 extracts the homepage as one 338-word paragraph, which makes the feature story harder to scan. Use a descriptive H1 naming the AI wardrobe assistant and its user benefit, while keeping “aisthetic” as the brand mark. Split the opening and the Organize, Optimize, Plan ahead, and Sustain material into short paragraphs or feature blocks. Replace broad positioning such as “redefines how you interact with your wardrobe” with a concrete morning, trip, or event scenario. Rewrite the sentence as “Optimized not to show the same item too close together.” Also repair homepage links to the sampled /work 404.

The editorial gate should stop on a concrete navigation failure: homepage feature images point to /work, and the crawl reports that URL as HTTP 404. Repair or remove every homepage feature link before publication. Set a descriptive, page-specific title and meta description, and apply the same metadata cleanup to /home and /contact. The copy contains specific operations—capturing clothing images and pre-selecting looks—but delivers them in one 338-word paragraph beside vague positioning. Split the homepage into scannable blocks and replace weak anchors such as “0” and “clicking here” with descriptive destination-specific labels.

The sampled surface is technically crawlable: robots.txt returns valid directives and declares a sitemap, HTTP and non-www roots consolidate in single-hop redirects, and the guaranteed nonexistent URL returns 404. Raw and rendered word counts match across the five sampled pages. The main defect is the internally linked https://www.aisthetic.app/work 404. URL signals also conflict because / and /home both return 200 while /home canonicalizes to / and appears in the sitemap; /contact/ is another 200 trailing-slash duplicate. Choose one homepage and slash convention, align redirects, canonicals, sitemap entries, and links, then add unique titles and meta descriptions.

Aisthetic earns its fair 63/100 on a clear product proposition and a practical feature set. Visitors can understand the wardrobe-assistant concept, reach a human through Contact Me, and follow the App Store handoff.

The fixable weaknesses are concentrated in delivery: the review records a 10.2 s mobile lab result, desktop layout concerns, a reported contrast, typography, and tap-target issues, plus a linked /work 404 and metadata and navigation-label gaps. Resolve these in one release pass. The product addresses outfit decisions, wardrobe organization, sustainability, and event or travel planning. The public site is not yet polished enough to carry the product story without those corrections.

This 13-dimension review uses the supplied crawl evidence for Aisthetic, including 5 pages crawled on 2026-10-08, public-page checks, accessibility and performance observations, writing and editorial QA findings, and technical SEO checks. Scores are shown exactly as provided in the public dimension table; the overall score is 63/100.

Pricing was not evidenced, and market, headquarters, founded year, and connected Search Console data were not evidenced in the supplied inputs. Read How SiteList scores for the full methodology.