Mobiri scores 51/100: its website-building and AI-assisted creation offer is clear, but accessibility, performance, and repetitive landing-page content hold the public experience back. The strongest evidence is content available in the initial HTML across 40 crawled pages; the most material weakness is the 16.2-second mobile LCP alongside a 7.9 MiB transfer.
Reviewed by SiteList Engine · 12 of 13 dimensions · published Reviewed on October 11, 2026
Is this your site?
Claim itThe crawl covered 40 pages on 2026-10-09.
| Fact | Value |
|---|---|
| Domain | mobiri.se |
| Category | Website design and AI website builder software |
| Pricing | Free claim visible; paid pricing not established in the supplied evidence. |
| Pages crawled | 40 |
| Crawl date | 2026-10-09 |
| Overall score | 51/100 |
Mobiri is clearly a website-building and AI-assisted creation product, but its public surface spreads attention across too many adjacent intents. The score table shows a mixed experience: usability and audience messaging are fair, while writing quality, editorial QA, review-content integrity, and self-serve help are critical weaknesses.
Performance is the most consequential practical issue; the Performance section provides the detailed lab-versus-field comparison. Accessibility evidence also shows foundational form-label problems, while the 390px render overflows by 16px.
Sibling landing pages repeat more than 80% of their main content and heading structure, weakening editorial distinction and indexation hygiene. A more task-oriented entry point, clearer self-serve help, lighter pages, and distinct content would make the product easier to evaluate and use.
Mobiri is clearly website-building software, but its first impression spreads across too many adjacent intents. The homepage leads with "Website design software" and the promise "Generate stunning websites with AI, no-code, free!" before extending into AI generation, no-code creation, HTML tools, templates, and vertical pages. Choose one primary audience and one concrete job, then move the remaining AI, editor, and template paths into supporting navigation. This would make the visible advantage—AI assistance, no-code editing, and HTML tools—easier to understand.
Mobiri names a recognizable website-building task, but visitors must sort through repeated labels before choosing how to begin. The homepage exposes AI business website generation, free AI generation, AI HTML generation, web-design software, landing-page software, and related pages; overlapping labels include "AI website maker", "AI website builder", "website generator", and "web page maker". The result is fair messaging with a high choice cost. Nominate one default creation flow, group secondary paths by user goal, and add a chooser that explains when each workflow applies. Keep keyword variants in contextual content rather than presenting them as competing primary destinations.
Mobiri is understandable as an AI-assisted website tool, but it does not offer one clearly dominant starting path. Descriptive links such as "Ai Business Website Generator", "Free Ai Website Generator", and "Ai Website Editor" provide useful information scent, while near-synonyms such as "Ai Website Maker", "Ai Website Builder", and "Website Generator" increase choice cost. Mobile PSI adds a concrete delay: LCP is 16.2 seconds, and the payload is 7,921 KiB. Choose one primary homepage action, group routes by goal, and reduce the mobile critical-path payload. Then address the reported link-name, landmark, language, and contrast issues.
Mobiri’s sampled pages have foundational accessibility barriers in the repeated AI-generation form. The homepage textarea relies on placeholder text, and DOM facts report three inputs without a label or ARIA name across the homepage and five representative landing pages. The same sample reports lang:null and landmarks containing nav and section but no main; PSI fails html-has-lang and landmark-one-main. PSI also reports color-contrast and discernible-link failures, while one rendered sequence skips from h2 to h4 and h5. Add visible programmatic labels, the correct language declaration, one main landmark, named links, passing contrast, and a repaired heading hierarchy. Focus and dynamic error behavior still need manual testing.
Mobiri has a credible marketing hierarchy, but mobile correctness and delivery weight weaken the visual result. The responsive system includes 83 media queries and body text measures 16px, yet the 390px render reaches a 406px scroll width, overflowing by 16px. Mobile Lighthouse reports 7,921 KiB, 16.2-second LCP, 9.0-second Speed Index, and 17.3-second Time to Interactive. Five small tap targets were detected, including a 31x20px button; images also lack consistent sizing protection, with estimated delivery savings of 397 KiB mobile and 1,470 KiB desktop. Remove the overflow, enlarge controls to at least 44x44px, size images, and fix the reported contrast and link-name failures.
Mobiri’s field signal is near healthy, but the supplied mobile lab experience is poor because the pages are heavy. CrUX reports mobile p75 LCP at 2.443 seconds, INP at 192 ms, and CLS at 0; the lab homepage reaches LCP in 16.2 seconds and transfers 7,921 KiB. The homepage network summary is 8,177 KiB over 72 requests, while the representative AI generator page reaches 13,722 KiB over 108 requests. On that page, my.mobirise.com contributes 4,293 KiB across 32 requests and YouTube/video origins add roughly 2.7 MiB. Defer gallery and video assets, serve the 228,211-byte in-viewport image responsively, and validate against LCP ≤2,500 ms, INP ≤200 ms, and CLS ≤0.1.
Mobiri’s landing-page writing is dominated by keyword-swapped templates rather than page-specific explanation. The pages /ai-website-maker.html, /ai-business-website-generator.html, and /landing-page-builder.html repeat the same structure, the subhead "Create websites on PC or Mac. Publish anywhere.", and identical FAQ blocks. The meta description pattern also repeats: "AI website maker. Get awesome AI website in seconds. Export and publish anywhere." The copy does not explain distinct mechanisms, audiences, or workflow differences between specialized tools. Replace boilerplate with topic-specific details, state each page’s target user and export options, and write individualized meta descriptions that summarize the actual page function.
Mobiri’s landing-page network stamps the same AggregateRating data across pages without matching visible review provenance. More than 20 crawled pages, including /ai-business-website-generator.html and /free-ai-website-generator.html, claim a 4.8 score from 193 entries in JSON-LD, while the sampled pages do not render individual review records, testimonials, or source attribution for that aggregate. This creates a schema-integrity risk. Remove static AggregateRating markup from template headers unless the page visibly presents itemized, verifiable reviews with traceable provenance. The structured data should describe evidence available on that page, not a value repeated across keyword variants.
Mobiri renders content without JavaScript, but its indexation surface has several stability risks. A guaranteed missing URL was redirected by 301 to https://mobiri.se/ and ended at 200 OK, creating soft-404 behavior with a broad crawl impact. The /robots.txt path serves a full HTML document instead of plain-text directives, and trailing-slash variants such as /ai-business-website-generator.html/ return 200 rather than consolidating to the clean path. These changes would preserve the supplied crawl finding of no JavaScript-rendering dependency across 40 pages while reducing indexation ambiguity.
Mobiri’s programmatic publishing system does not meet a strong editorial QA standard because sibling pages repeat structure, filler, and shallow answers. More than 80% of the main content and heading structures on /ai-website-editor.html match /ai-website-software.html and /ai-website-maker.html. The video introduction "Watch the video below to gain insights on creating an appealing website with the application..." is repeated filler, while FAQ headings follow the same "What is [Keyword]?" and "How to use [Keyword]?" pattern. Consolidate near-identical pages into pillar guides or add substantial unique editorial content, replace generic video introductions with specific descriptions and timestamps, and write FAQs that explain real workflow differences.
The /llms.txt request redirects to the homepage instead of returning product guidance. Publish a getting-started tutorial and user guide, link them from the main navigation and footer, and add a focused onboarding FAQ. A structured FAQPage implementation on relevant pages and a product-information llms.txt could also improve machine-readable guidance, provided the content reflects the actual product.
Mobiri’s HTML is immediately available to crawlers, but core indexation controls are incomplete. Across 40 pages, raw and rendered text lengths match, indicating 0% JavaScript-rendering dependency; titles, canonicals, and structured text are available in the initial response. A trailing-slash HTML variant also returns 200 without consolidation. Deploy a valid text/plain robots file with sitemap declaration, return 404 or 410 for missing paths, generate an XML sitemap, and normalize trailing-slash variants.
Mobiri earns its clearest marks for making the website-building task recognizable and serving fully rendered HTML across the 40-page crawl. Visitors can find descriptive routes into the product, and CrUX field metrics are healthier than the supplied mobile lab result.
The priority weaknesses are specific: reduce the 16.2-second mobile LCP and 7.9 MiB transfer, repair unlabeled AI-generation controls and contrast issues, and replace repeated keyword-led pages with more useful, differentiated content. Public documentation is another material gap for a product that asks users to evaluate and learn a website-building workflow.
Mobiri is aimed at visitors seeking no-code or AI-assisted website creation. It is less convincing for visitors who need a focused starting point, strong self-serve guidance, or a consistently polished mobile experience.
This review uses a 13-dimension framework and is based on a crawl of 40 pages on 2026-10-09. Twelve applicable dimensions were assessed; decision-support surfaces was excluded as not applicable. The review distinguishes lab measurements from field data where both are available.
Owner-only findings and roadmap material are not included.
Read How SiteList scores for the review method and dimension definitions.
Mobiri is aimed at visitors seeking no-code or AI-assisted website creation, but the public surface does not choose one sharply defined audience.
Performance is the clearest practical weakness in the sampled lab data: the homepage reached largest content in 16.2 seconds on mobile and transferred 7.9 MiB. Accessibility also needs focused work.
The sampled evidence shows foundational accessibility issues. Three repeated AI-generation form controls lacked a label or ARIA name, and the primary textarea was identified only by its placeholder.
SiteList crawled 40 pages on 2026-10-09 and assessed 12 applicable dimensions in a 13-dimension framework. Decision-support surfaces was excluded as not applicable.