Overall AI readiness score
A combined result across all audit signals.
Average
AI readiness audit: 7/21/2026Public technical data
Overall AI readiness assessment
How ready xjodoin.github.io is for AI systems
Nodemailer MJML i18next Compiler was independently audited by llmsmap. xjodoin.github.io currently scores 61/100 for AI readiness. The result combines AI-specific files, crawler policy, sitemap discovery, structured homepage data, and—when available—the mobile Google Lighthouse technical profile.
Audit context
llms.txt is accessible and contains 1,086 tokens. An expanded llms-full.txt is also available with 2,766 tokens, giving agents more direct context. No separate ai.txt policy was detected; it is optional, but can clarify training, retrieval, and attribution preferences.
robots.txt was not found, so explicit crawler policy could not be confirmed. No Schema.org type was detected on the homepage. 0 OpenGraph tags were found and markup completeness is 0%, leaving more entity interpretation to crawlers.
The mobile Lighthouse profile adds Performance 100/100, Accessibility 55/100, Best Practices 92/100, SEO 82/100, and experimental Agentic Browsing 50/100. These signals have a limited weight: they complement rather than replace llms.txt, robots.txt, and structured-data checks.
Confirmed strengths
- Accessible llms.txt
- Expanded llms-full.txt
Priority improvements
- 1Publish robots.txt with explicit search and AI crawler rules.
- 2Declare the current sitemap.xml in robots.txt.
- 3Add JSON-LD for the organisation, website, and core entities.
- 4Complete OpenGraph and canonical homepage metadata.
llms.txt tokens1,086
llms-full.txt tokens2,766
ai.txt
sitemap.xml
Google Lighthouse technical profile
A mobile Lighthouse measurement. Google’s experimental Agentic Browsing category is explained separately and does not replace the broader llmsmap AI-readiness score.
100
Performance
55
Accessibility
92
Best Practices
82
Technical SEO
50
Agentic Browsing
What these results mean
The mobile page renders efficiently; its largest visible content block appeared in 0.8 s.
Accessibility scored 55/100, Best Practices 92/100, and technical SEO 82/100. The experimental Agentic Browsing category scored 50/100. It measures signals Google currently tests for software agents and is shown separately from the llmsmap AI-readiness score.
1
Make controls unambiguous
Give buttons and links accessible names, associate labels with fields, and use ordered headings and semantic regions. The same structure helps screen readers and software agents understand actions.
2
Improve interface contrast and readability
Increase contrast for text, states, and interactive controls so both people and visual agents can distinguish content from actions and supporting labels.
3
Clarify search and canonical signals
Verify unique titles and descriptions, crawlability, canonicals, descriptive link text, and language relationships. This reduces ambiguity for search engines and AI systems selecting a page.
FCP0.8 s
First content
LCP0.8 s
Main content
CLS0
Layout stability
TBT0 ms
Blocking time
SI0.8 s
Visual speed
Metric glossary
- FCP · First content
- When the first text or image appeared on screen.
- LCP · Main content
- When the largest visible element in the first viewport rendered.
- CLS · Layout stability
- How much content shifted unexpectedly while loading; lower is better.
- TBT · Blocking time
- How long the browser main thread could not respond quickly to input.
- SI · Visual speed
- How quickly the visible viewport filled with content.
7/21/2026Lighthouse 13.4.0Mobile profile
AI readiness checks
Machine-readable files, crawler policy, discovery, and homepage markup.
llms.txt
File found and accessible
https://xjodoin.github.io/nodemailer-mjml-i18next-compiler/latest/llms.txtllms-full.txt
Full version is available
https://xjodoin.github.io/nodemailer-mjml-i18next-compiler/latest/llms-full.txtai.txt
ai.txt file was not found
robots.txt
robots.txt file was not found
Sitemap in robots.txt
Sitemap is not declared in robots.txt
Schema.org (JSON-LD)
Schema.org markup was not found on the homepage
OpenGraph
OpenGraph tags were not found on the homepage
AI bot access
Based on robots.txt analysis
GPTBotNot mentioned
OAI-SearchBotNot mentioned
ChatGPT-UserNot mentioned
Google-ExtendedNot mentioned
ClaudeBotNot mentioned
Claude-SearchBotNot mentioned
Claude-UserNot mentioned
BytespiderNot mentioned
CCBotNot mentioned
PerplexityBotNot mentioned
Perplexity-UserNot mentioned
# Nodemailer MJML i18next Compiler
> Nodemailer compile plugin that renders MJML templates with Handlebars and i18next translations to produce responsive HTML emails from MJML.
This file points LLMs to concise, high-signal references for using the library. Core flow: Handlebars renders data and translations into MJML; MJML compiles to responsive HTML; the Nodemailer compile plugin assigns the result to `mail.data.html` and resolves a translated subject when configured. Templates are resolved by trying `<name>.mjml.hbs`, `.hbs.mjml`, `.mjml`, then `.hbs`. i18n defaults to filesystem-backed `i18next` loading from `locales/<lng>/<ns>.json`. Use `{{t "ns:key"}}` or `{{__ "ns:key"}}` in templates; locale comes from `mail.data.locale`.
Important notes:
- The plugin runs in Nodemailer’s compile phase (`transporter.use('compile', ...)`).
- `strict` throws on MJML errors; otherwise errors are exposed at `mail.data.mjmlErrors`.
- Subjects: set `mail.data.subject`, or use `mail.data.subjectKey`, or enable `autoSubject` (default) to use `<subjectNamespace>:<template>.subject`.
- Security: avoid untrusted helpers/partials; pin `templatesDir`, `partialsDir`, and `localesDir` paths.
## Docs
- [Overview](https://github.com/xjodoin/nodemailer-mjml-i18next-compiler/blob/main/docs/index.md): What the plugin does and a quick start.
- [Usage](https://github.com/xjodoin/nodemailer-mjml-i18next-compiler/blob/main/docs/usage.md): Templates, helpers, i18n, and mail data fields.
- [Options](https://github.com/xjodoin/nodemailer-mjml-i18next-compiler/blob/main/docs/options.md): Full `mjmlI18nextCompiler` configuration.
- [Changelog (docs)](https://github.com/xjodoin/nodemailer-mjml-i18next-compiler/blob/main/docs/changelog.md): Release notes on the docs site.
## API & Source
- [Runtime entry (`src/index.js`)](https://github.com/xjodoin/nodemailer-mjml-i18next-compiler/blob/main/src/index.js): Compiler implementation, template resolution, helpers, and subject logic.
- [Types (`src/index.d.ts`)](https://github.com/xjodoin/nodemailer-mjml-i18next-compiler/blob/main/src/index.d.ts): TypeScript declarations including `MjmlI18nextOptions`.
## Getting Started
- [README](https://github.com/xjodoin/nodemailer-mjml-i18next-compiler/blob/main/README.md): Install, usage example, template format, and notes.
- [Example sender (`example/send.js`)](https://github.com/xjodoin/nodemailer-mjml-i18next-compiler/blob/main/example/send.js): Minimal demo using the plugin.
## Example Assets
- [Template: `welcome.mjml.hbs`](https://github.com/xjodoin/nodemailer-mjml-i18next-compiler/blob/main/example/templates/welcome.mjml.hbs): Example MJML + Handlebars template.
- [Partial: `partials/footer.mjml.hbs`](https://github.com/xjodoin/nodemailer-mjml-i18next-compiler/blob/main/example/templates/partials/footer.mjml.hbs): Example Handlebars partial.
- [Locales: `en/emails.json`](https://github.com/xjodoin/nodemailer-mjml-i18next-compiler/blob/main/example/locales/en/emails.json): Subject/title strings.
- [Locales: `en/common.json`](https://github.com/xjodoin/nodemailer-mjml-i18next-compiler/blob/main/example/locales/en/common.json): Shared strings.
## Scripts
- [Smoke test (`scripts/smoke.js`)](https://github.com/xjodoin/nodemailer-mjml-i18next-compiler/blob/main/scripts/smoke.js): Basic compile + subject validation against the example.
## Project Metadata
- [CHANGELOG.md](https://github.com/xjodoin/nodemailer-mjml-i18next-compiler/blob/main/CHANGELOG.md): Versioned changes.
- [LICENSE](https://github.com/xjodoin/nodemailer-mjml-i18next-compiler/blob/main/LICENSE): MIT license.
- [AUTHORS](https://github.com/xjodoin/nodemailer-mjml-i18next-compiler/blob/main/AUTHORS): Project authors.
- [mkdocs.yml](https://github.com/xjodoin/nodemailer-mjml-i18next-compiler/blob/main/mkdocs.yml): Docs site configuration.
## Optional
- [Nodemailer plugin docs](https://nodemailer.com/usage/plugins/): How compile plugins integrate in Nodemailer.
- [MJML documentation](https://documentation.mjml.io/): MJML components and options.
- [Handlebars guide](https://handlebarsjs.com/guide/): Templates, helpers, and partials.
- [i18next core](https://www.i18next.com/): i18n concepts and usage.
- [i18next-fs-backend](https://github.com/i18next/i18next-fs-backend): Filesystem backend used when no custom i18next instance is provided.
Share or continue the analysis
Share this audit
Discuss with AI
Added 7/19/2026