Technology

Every site Umi Group builds — including this one and the 14-site content network we run ourselves — is built on the same platform. This page describes what that platform does and the standards it holds itself to.

Performance

Every page is measured against Google PageSpeed Insights — Google's own performance and quality tool, which drives the Core Web Vitals signals used in search ranking.

Our sites consistently score in the green range (90–100) across all four metrics PageSpeed measures:

  • Performance — how quickly pages load and become interactive on real mobile hardware and slow connections.
  • Accessibility — how usable pages are for readers relying on screen readers, keyboard navigation, or other assistive technology.
  • Best Practices — adherence to current web standards for security, HTTPS, console hygiene, and image handling.
  • SEO — technical correctness as measured against Google's own published guidelines.

This is not a trivial benchmark. Green across all four metrics on mobile is rare for content sites — most rely on heavy JavaScript frameworks and accumulated plugin bloat that make consistent green scores difficult. Our platform uses a lightweight server-rendered architecture specifically to keep performance in that range without compromise.

SEO standards

On-page SEO is designed around Google's published guidelines, not third-party plugin scoring. We validate using PageSpeed and Google Search Console — the same tools Google uses to assess sites itself.

Every article includes correct heading hierarchy, semantic HTML, meta descriptions, canonical URLs, structured data where appropriate, and fast-loading images served in modern formats. Internal linking, category taxonomy, and XML sitemaps are generated automatically to match how Google actually crawls and indexes content.

How topics are chosen

For content-driven sites, topics are sourced from real editorial signals — not from AI inventing things to write about.

The platform monitors RSS feeds from relevant publications and news sources in each site's subject area. A custom pipeline reads those feeds continuously, analyzes what topics are gaining traction across sources, and selects both the article topic and the best-fit keyword before any draft is written.

Result: articles are, by construction, on topics that real editors at real publications are covering — not topics an AI guessed might be interesting. That's a significant part of why the content produced on this platform aims to be useful rather than filler.

Multi-media content, organized by topic

Articles are only one of the content types our platform supports. Each category also hosts:

  • Curated video — relevant video content from publishers and creators in the same subject area, with the option to include original video hosted on the site itself.
  • Podcasts — audio content tied to the same topic categories as written articles.
  • Reels — short-form video appropriate to the niche.
  • Supporting resources — tools, products, and external references related to the category.

All of these are linked to the same category structure as articles, so readers exploring a topic get access to the full range of media covering it. This is closer to how modern professional publications work than to how traditional blogs work — and it's a deliberate choice about how readers actually want to consume information.

Content production

Articles and images on content-driven sites are produced with the help of AI and reviewed before publication. The AI handles drafting; editorial direction, topic scope, and publishing decisions remain human-controlled. Full details on the Editorial Policy page.

The production pipeline is designed for consistency: images use a curated prompt library tuned to the site's subject matter, written content follows style conventions defined for the niche, and quality signals are tracked over time so outputs improve rather than drift.

Accessibility and mobile

Mobile-first is the design default — sites are built and tested on mobile hardware first, with desktop layouts adapted from the mobile baseline. This is why mobile PageSpeed scores match the desktop ones rather than lagging behind them, which is common on sites retrofitted for mobile after the fact.

Accessibility is treated as a technical requirement, not an optional layer. Heading structure, color contrast, focus management, image alternative text, and keyboard navigation all meet the standards measured by PageSpeed's accessibility audit.

Why it matters for clients

When you work with Umi Group, your site inherits all of these standards by default. There is no "premium tier" that gets performance optimization while the base tier ships slow. The platform only builds one way.

That also means we can afford to charge honest, predictable prices — the performance work is already done, embedded in the platform, and doesn't need to be quoted per-project.

See it in practice

The easiest way to evaluate the platform is to look at sites already running on it. Visit the Portfolio page for the full list, or run PageSpeed against any of the sites in our network and see the results yourself.