Aimag Review: thoughtful platform, clear gaps (70/100)

| Fact | Value |n|---|---|n| Domain | aimag.me |n| Category | AI-powered tarot reading for structured self-reflection |n| Pricing | Unknown; price range unavailable |n| Pages crawled | 38 |n| Crawl date | 2026-09-01 |

Aimag earns 70/100 by combining clear positioning, strong design execution, and useful self-serve learning content with several practical gaps. Its strongest signals are an 85/100 score for first impressions and positioning, an 85/100 score for design execution, and a 76/100 score for docs and self-serve help, including interactive flashcards at /learn, 78 card reference guides, and spread documentation.

The weaker areas affect both conversion clarity and site experience. Decision-support surfaces score 45/100: the three plan tiers are shown in a comparison grid without guidance on which tier fits a user or use case. Performance scores 65/100 because the homepage takes 4.7 seconds to load its main content on mobile. Writing quality scores 62/100 and editorial QA 60/100, while technical SEO is comparatively solid at 73/100.

Aimag presents a distinct proposition: AI-powered tarot reading for structured self-reflection. Its hero, ‘Free AI Tarot Reading — The Cards Await’, makes a falsifiable promise and separates the service from generic tarot sites through AI and psychological depth. The homepage also reports 3,106 readings completed and a 4.6/5 rating, but supplies no source or context for either metric. The audience remains implied rather than named, limiting relevance for specific segments. Consolidate the public brand as aimag.me and update the Organization and WebSite schema name. Add a clear audience cue to the hero, such as ‘for self-reflective individuals’, and link the proof points to their source or explain their timeframe.

Aimag explains its category and offers one free reading daily without sign-up or a credit card, but it does not make the full cost model easy to verify. The pricing page was inaccessible in the supplied crawl, and the homepage does not clarify the free-use limit beyond the daily statement. Trust is also under-explained: the 4.6/5 rating has no review source, and no testimonials or case studies are visible. The copy leans toward ‘We’ and ‘Our’, with a self-orientation ratio above 60%. State the free-tier limit plainly, make pricing accessible, link the rating to its source, and shift key homepage sentences toward ‘you’ and ‘your’.

Aimag’s visual system has clear hierarchy, consistent mobile responsiveness, and considered whitespace. Accessibility limits that polish: body text and interactive elements use #9CA3AF on #FFFFFF at 2.8:1, below the WCAG AA thresholds of 4.5:1 for body text and 3:1 for UI components. Card padding also varies between 24px and 32px, while some H2 headings are 30px and others 28px. Darken the affected color to the evidenced #4B5563 alternative, then standardize card padding and H2 sizing. Recheck the result across the affected sections after the contrast changes.

Aimag’s mobile performance is below the supplied targets: the homepage’s main-content load is reported at 4.7 seconds, and mobile TTFB is 4 seconds against an 800ms threshold. The hero image is 103,780 bytes, served at 576×896px into a 174×104px slot, and loaded lazily; the evidence attributes a 3-second delay to that path. Eight blocking third-party requests also load synchronously in the head. Prioritize the hero with preload and fetchpriority="high", add responsive srcset and sizes, reduce server latency through edge caching or equivalent server rendering, and defer third-party scripts. Add font-display: swap where font-face rules exist.

Aimag has specific material across its tarot tools, guides, and research pages, but the editorial layer needs a structural pass. The homepage extraction places 893 words in one paragraph and the About page 2,080 words in one paragraph, making the content difficult to scan. The Learn page skips from H2 to H4 for quiz activities. The three-card reading page repeats one FAQ question, money-tarot has a 76-character title, and sampled images lack alternatives. Restore paragraph boundaries, repair heading levels, deduplicate the FAQ entity, trim the title, and add descriptive alt text.

The pricing grid shows Free, Seeker, and Mystic, but it does not explain which tier fits a user or use case. The comparison axes include ‘AI Model’ and ‘Interpretation Depth’ without enough decision context, and rows such as ‘All spreads’ and ‘Comprehensive reading’ are checked for every plan. That leaves buyers to reconstruct the tradeoffs themselves. Add concise recommendations for concrete audiences, then compare price per reading, support, and other decision-relevant dimensions. Replace all-checkmark rows with quantities or meaningful differences, such as the number of spreads or depth available in each tier. Treat mobile parity as an open validation item because no mobile pricing screenshot was supplied.

Language roots /pl, /fr, /es, and /pt rely heavily on client-side content, with JS-only shares from 0.925 to 0.995. Separately, /pricing, /tarot-tools, /cards, and /research remain in the sitemap while carrying noindex, nofollow. These conclusions are scoped to the partial crawl.

The most concrete editorial defect is duplicate structured content: the three-card reading page publishes ‘Can I do a 3-card reading for someone else?’ twice in its FAQ schema. The Learn page separately places H4 quiz headings directly beneath the H2 ‘Seven of Pentacles’. The mechanical queue also includes a 76-character money-tarot title and missing alt text on reported images. Deduplicate the FAQ entities, correct the heading hierarchy, complete the listed alt text, and shorten the title before release.

Aimag’s self-serve content is a strength: /learn offers interactive flashcards, the site documents 78 card references and 23 spread layouts, and llms.txt is present at 4,010 bytes. FAQPage and BreadcrumbList schema on /free-3-card-reading also give machine readers structured answers. Findability is weaker. /learn has no internal search box and no persistent sidebar, so users must navigate dense links to reach the reference material. Add a fast search input and a topic index or collapsible sidebar. Keep llms.txt synchronized with product changes, and extend FAQPage markup only to genuine tool-page questions.

Aimag has a sound baseline: HTTPS uses HSTS preload, canonicals are self-referential, redirects are single-hop, and robots.txt permits major search bots. Three issues undermine that foundation. Primary content on /pl, /fr, /es, and /pt is injected through JavaScript, with raw-vs-rendered ratios from 0.925 to 0.995. Four pages also exceed a 390px mobile viewport, reaching 463px scroll width. Server-render H1s and primary content, make public sitemap URLs return 200, reconcile sitemap and noindex directives, and remove the horizontal overflow before validating page experience again.

Aimag works best for people looking for a focused, self-reflective tarot experience with substantial supporting learning content. Its positioning is clear, its design execution is strong at 85/100, and its self-serve help scores 76/100.

The fixable weaknesses are equally clear. Pricing does not answer the cost question in the available evidence, and the three plan tiers lack user- or use-case-based guidance. Mobile lab data reports a 4.7-second main-content/LCP result, while the supplied field-data entry reports 3,064ms for /pl/reading, and the review inputs confirm two contrast failures affecting body text and UI elements. Addressing those issues would make the service easier to choose and easier to use.

This 13-dimension review uses the available crawl and the public dimension score table for 38 pages crawled on 2026-09-01. The review covers the dimensions represented in the supplied evidence.

Google Search Console enrichment was not connected, so no Search Console findings are included. See How SiteList scores for the review method and data notes.