Arablyzer vs Lighthouse
Lighthouse is a tool you run yourself, in Chrome DevTools, from the command line or through PageSpeed Insights, and it reports on the page you point it at. Its audits are general to every language; we add checks for Arabic text and how it renders in more than one engine. The two tools complement each other.
On this page
Line by line
| Feature | Arablyzer | Lighthouse |
|---|---|---|
| Checks made for Arabic | Yes. Rules for broken letters (letter-spacing), fonts missing letters, tatweel, mixed digits, RTL direction, and the new riyal sign | Not stated. Its documentation lists no checks made for Arabic text; its audits are general, hreflang among them |
| Page drawn in real browsers | Yes. Chromium, Firefox and WebKit, with the results compared | Partly. Runs in Chrome; its documentation requires Google Chrome installed to run it from the command line or as a Node module |
| Platform detection | Yes. Salla, Zid and YouCan (ExpandCart at low confidence) beside WordPress and others, from the page’s fingerprints | Not stated. Its documentation does not state store-platform detection |
| Sign-up before the first check | Yes. Not needed for the single-page tools | Yes. Its documentation states no account; it runs inside Chrome DevTools or from the command line |
| Free limits | Partly. Free within a rate limit that keeps sites from being flooded; paid plans are not set yet | Yes. Open source under Apache-2.0, and you run it yourself |
| Arabic and English interface | Yes. Every page in Arabic first, and in English | Partly. Its documentation is offered in Arabic, English and other languages per the language list on its site; its report language is not stated |
| Code and method | Partly. The methodology and the rule library are published on this site and explain how each rule decides; the code itself is not public | Yes. Open source under Apache-2.0 on GitHub, and each audit has a documentation page explaining why it matters and how to fix it |
| AI readiness | Yes. AI crawler access, how machines read Arabic text, and robots.txt blocks | Not stated. Its documentation does not state a check for AI crawler access |
| Core Web Vitals data | Partly. We read CrUX field data (LCP, INP, CLS) and compare it by country; we do not run Lighthouse | Partly. Lab data from running the audit itself, not real-user data |
| Whole-site crawl and daily monitoring | No. Not available yet; they are the paid plans to come, with no prices so far | Partly. Audits the address you give it in each run; its documentation mentions Lighthouse CI to prevent regressions on sites |
When to pick Lighthouse
- You want the performance, accessibility, best-practices, SEO and Agentic Browsing report for one page in Chrome DevTools, or you want to wire it into your continuous integration.
- You want to audit pages that require sign-in: its documentation says it runs on any page, public or requiring authentication.
When to pick Arablyzer
- You want checks for Arabic text that we did not find among the audits in Lighthouse’s documentation: letter joining, fonts, digits and direction.
- You want to see the page in Firefox and WebKit beside Chromium.
- Your store is on Salla, Zid or YouCan and you want advice that fits your platform.
How we compared
The rows are what Arablyzer really does, read from its own code. The other tool's cell says what its public pages state on the day we read them, and nothing else: where a page says nothing, the cell reads “Not stated”, not “No”. We did not sign up to any of them or try their paid plans. Prices and limits change, so check their pages before you decide, and if you spot a mistake, tell us and we will fix it.
The public pages this tool’s cells rest on, as we read them on the date above:
- Introduction to Lighthouse, Chrome for Developers
- Lighthouse hreflang audit
- Lighthouse repository on GitHub (license)
- web.dev: Why lab and field data can be different
Every single-page tool is free with no sign-up. Paste your address and compare the result with what you know. Try it yourself