🆚 i-SITE vs. Oriko Blog
- 📈 Oriko Blog is much more popular than i-SITE.
- 🌍 Oriko Blog is more popular in all countries.
- ⭐ i-SITE is particularly popular in Japan.
Statistics based on 3.8M+ analyzed websites. About this data
i-SITE
Oriko BlogType
Content management system
Content management system
About
i-SITE is a Japanese content management system based on 
ASP.NET and Microsoft SQL Server.
Oriko Blog is a Japanese CMS for creating and managing corporate websites that combines visual page editing with industry-specific templates.
It provides automatic mobile optimization, multilingual site translation, SEO settings, access analytics, digital catalog and brochure creation, and integrations with Google for Jobs and RICOH Kintone plus.
Headquarters
Tottori, Japan
Nagasaki, Japan
Pricing
Free version ❌
Custom
Popularity
Determined by the number of sites using each technology.
The Oriko Blog CMS platform is 34 times more popular than i-SITE.
Total websites
Market share
CMS
Popularity by country
Determined by the number of sites detected from each country.
Oriko Blog is more popular than i-SITE in all countries.
Japan
United States
Popularity by domain category
Determined by the number of sites in each category.
Oriko Blog is more popular among sites focused on business, education and reference, and travel, while i-SITE is more commonly used on government and military sites.
Business
Education/Reference
Travel
Internet Services
Marketing/Merchandising
Online Shopping
Government/Military
Real Estate
Alcohol
Non-Profit/Advocacy/NGO
Top sites
Top-ranked sites that use these technologies.
Compare alternatives
Technologies with similar characteristics.
🗃️ About This Data
- We evaluate the popularity of technologies based on the number of websites where we detect their usage.
- Technologies without a detectable web footprint, and those we do not track, are not reflected in the calculated market share.
- This report is based on the analysis of 3,816,780 websites.
- Statistics were last calculated on .
- For more details, see our methodology and disclaimer.