Looks like you're in . Want the local site?
CUSTOM WORDPRESS DEV · カスタムWordPress開発
Ignited Nepal builds custom WordPress websites for Japanese businesses and organisations that need genuine flexibility. We build bilingual Japanese and English sites with proper UTF-8 encoding and CJK font loading, custom post types, ACF field groups, and a Gutenberg block library your team can edit without developer support. No poorly translated themes. No page builders. Core Web Vitals optimised and version-controlled with Git from the first commit.
We are proudly featured on
Trusted by businesses we have shipped growth for
/ This is for you if
Your WordPress site was built on an international theme that was never designed for Japanese content. The typography is wrong, character spacing is uncomfortable, CJK fonts load slowly or fall back to system defaults, and the editorial experience was built for Latin text. You need a site designed for Japanese content from the ground up.
You serve both Japanese and international audiences and your site needs to function fully in both languages, not as a patched translation of a Japanese-only or English-only primary site. You need a WordPress build where Japanese and English content have equal structural standing, proper language routing, and consistent design across both versions.
Your site was built several years ago by a development team that is no longer available. It runs on a premium theme from a marketplace, depends on several plugins that conflict with each other, and updating WordPress itself is a risk. You need a clean rebuild with a maintainable codebase and no legacy dependencies.
/ What's broken
Japanese text requires different line height, character spacing, and font rendering than Latin text. A Western WordPress theme applied to Japanese content produces uncomfortable reading experiences: text that is too tightly spaced, headings that overflow their containers, and vertical rhythm that breaks because the theme was designed for ASCII characters. This is not a minor visual issue. It affects whether Japanese readers trust the site.
Japanese, Chinese, and Korean character sets are substantially larger than Latin character sets. Loading a full CJK web font without subsetting or display optimisation adds significant render-blocking weight to every page load. Many Japanese WordPress sites either load fonts too slowly, fall back to unattractive system fonts, or subset incorrectly and display missing characters. CJK font loading strategy is a build decision, not an afterthought.
Sites built with WPML or Polylang on top of a single-language theme often produce bilingual experiences where the English and Japanese versions have different layouts, inconsistent navigation, or translation strings that never got updated. A genuine bilingual WordPress site requires a content architecture where both language versions share a common structural model and receive equal editorial attention.
A WordPress site built on a page builder or a heavily customised theme often requires developer involvement for routine content updates because the editorial interface is too complex or too fragile for non-technical staff. A custom Gutenberg block library, built to match your content model, gives editors a structured, safe way to publish without needing to understand the underlying code.
/ What we engineer
Each workstream is built by the team that audits it, and wired into the rest of your growth system.
We document the full build before development begins. Custom post types, taxonomies, ACF field groups, Gutenberg block list, bilingual routing, URL structure, font loading strategy, and hosting configuration. Both Japanese and English content architecture are specified in full. You review and approve before any code is written.
We build a custom WordPress theme designed for Japanese content from the start. Line height, character spacing, heading sizes, and typographic rhythm are calibrated for Japanese text. CJK web font loading is handled with subsetting and font-display optimisation so fonts load quickly and display correctly without falling back to system defaults. The same theme handles English content equally well when language routing serves an English page.
We configure WordPress for bilingual operation with proper language routing, consistent URL structures for both language versions, and a content model where Japanese and English entries are linked at the post level. Navigation, metadata, and structured data are managed independently for each language. Neither version is a machine translation of the other.
We configure custom post types and ACF field groups for your content model. News articles, project portfolios, staff profiles, product pages, service descriptions, or whatever your organisation publishes. Field labels and editorial instructions are provided in Japanese for editorial staff who work primarily in Japanese.
We build a library of custom Gutenberg blocks that match your design system and content patterns. Each block is built for both Japanese and English content, handles the typographic differences between the two languages, and is editable in the block editor without the ability to break the page layout.
We address Core Web Vitals at the code level with particular attention to CJK font loading, which is a common source of Largest Contentful Paint and Cumulative Layout Shift failures on Japanese sites. Image optimisation, critical CSS, script deferral, and font subsetting are all included in the build, not added later.
We build on staging, manage the codebase in Git, and deploy to your production environment after full QA. Editorial documentation is provided in Japanese, covering every custom post type, field group, and Gutenberg block so your team can publish independently from the first day after launch.
/ What changes
/ How it works
We audit your current WordPress site or your brief. We review your theme, typography, CJK font loading, plugin stack, Core Web Vitals scores, bilingual setup if one exists, and content architecture. We deliver a written diagnostic report in English (with Japanese summaries where your team requires them). This takes one week.
We write the full build specification covering custom post types, ACF field groups, Gutenberg block list, bilingual routing, font loading strategy, and editorial workflow. Field labels and editorial instructions are specified in Japanese for editorial staff. You review and approve before development begins.
We build the custom theme with Japanese typography and CJK font loading, configure bilingual architecture, develop custom post types and ACF field groups, and build the Gutenberg block library. All work happens on staging. Weekly updates are shared with your team.
We test across Japanese and English language versions, check Core Web Vitals on both mobile and desktop, verify CJK font rendering on multiple devices, test all custom blocks in both languages, and confirm that bilingual routing is working correctly. We launch, monitor the first 48 hours, and deliver editorial documentation in Japanese.
/ Common questions
Straight answers on scope, timelines and cost. Anything else, ask us directly.
Ask us directlyWordPress handles bilingual content correctly when the architecture is built for it. UTF-8 encoding is WordPress's default, and custom post types with language-linked entries, combined with a custom theme designed for both Japanese and English typography, produce a bilingual site where neither language version is a compromise. The problems with bilingual Japanese WordPress sites almost always come from applying a plugin-based translation layer to a theme that was built for one language. We build bilingual architecture from the start.
CJK character sets are large, and loading a full web font for Japanese adds significant weight to every page load. We use font subsetting to load only the characters used on each page, combined with font-display: swap to prevent the font from blocking rendering, and preload hints for the fonts used above the fold. The result is correct Japanese typography without the LCP penalty that CJK fonts typically impose on sites where loading strategy has not been addressed.
We evaluate the right multilingual approach for each build. WPML and Polylang are both capable tools when implemented correctly. For some builds, a custom post relationship approach without a multilingual plugin is cleaner and faster. The decision depends on your editorial workflow, your content volume, and whether you need professional translation integration. We make a recommendation in the technical specification based on your specific requirements.
A marketplace theme for Japanese WordPress is a theme built with Japanese content in mind but designed to serve many different businesses and use cases. It ships with layout options, colour schemes, typography settings, and page templates that you will never use. Every unused feature adds weight. A custom theme is built only for your site, loaded only with what your pages need, and calibrated for your specific content model and typographic requirements. The performance difference is significant and the editorial experience is substantially cleaner.
WordPress uses UTF-8 encoding throughout, which supports all Japanese character sets including hiragana, katakana, kanji, and full-width punctuation. We configure the database, theme templates, and any custom post type outputs to handle UTF-8 correctly and consistently. We also test character display across browsers and devices, including older Android browsers still in use in Japan, to confirm there are no encoding or rendering issues before launch.
Start here
A poorly translated theme with slow CJK font loading and a broken bilingual structure is not a Japanese WordPress site. It is an English WordPress site with Japanese text forced into it. Ignited Nepal builds WordPress sites that treat Japanese content as the primary case, not the translation layer. Start with a diagnostic.
Ignited Nepal
Growth engineering · replies within 1 business day
By continuing you agree to our privacy policy.
