What powers gekkeikan.co.jp?
Last seen Jun 2026 · 12 technologies across 9 categories
Analytics
CDN
JavaScript libraries
Miscellaneous
PaaS
Programming languages
Tag managers
Web servers
Widgets
Top search keywords
| Keyword | Position | Est. monthly visits |
|---|---|---|
| fushimi inari | #21 | 62 |
| momoyama castle | #7 | 49 |
| fushimi inari shrine | #40 | 38 |
| fushimi castle kyoto | #12 | 14 |
| fushimi castle | #13 | 11 |
| who built the momoyama castle | #3 | 4 |
| inari meaning | #45 | 3 |
| fushimi-inari station | #87 | 2 |
| fushimi inari station | #87 | 2 |
| inari temple kyoto | #41 | 2 |
| kumataka shrine | #15 | 1 |
| kyoto 1000 gates | #90 | 1 |
| fushimi-ku | #61 | 1 |
| fushimi ku | #28 | 1 |
| fushimi inari temple | #27 | 1 |
| fox fushimi inari | #15 | 1 |
| 1000 torii gates | #96 | 1 |
| who is inari | #52 | 0 |
| christian daimyo | #75 | 0 |
| christian daimyo | #41 | 0 |
| thousand red gates | #89 | 0 |
| thousand gates japan | #79 | 0 |
| what is fushimi inari taisha | #62 | 0 |
| what is fushimi inari | #40 | 0 |
| shusse inari shrine of america | #77 | 0 |
The site's top keywords in Google (US), with the visits each one is estimated to bring per month.
Top backlinks
Top links pointing at the site, one per source domain, strongest first. The anchor text opens the page carrying the link.
Audience
- 70% phone
- 28% desktop
- 1% tablet
Japan
Taiwan
Countries where the site has Chrome traffic, strongest markets first.
Open Page Rank
6.43 / 10 · ranked #80,394 of all domains
345 referring domains · OpenPageRank
Search traffic
190 est. monthly organic visits (US)
62 keywords in Google's top 30
Core Web Vitals
| LCP | 1.4 s |
| INP | 75 ms |
| CLS | 0 |
| TTFB | 300 ms |
Real user p75, Chrome UX Report, Jun 2026.
Page
- Language: Japanese
- Weight: 41.7 MB · 89 requests
- Structured data: OpenGraph, Twitter Cards
Homepage as crawled by the HTTP Archive, Jul 2026.
Subdomains
| Host | Techs |
|---|---|
| washulabo.gekkeikan.co.jp | 9 |
| www.gekkeikan.co.jp | 6 |
Full technology history →
Report an incorrect detection
Recent changes
- detected Nginx Mar 2026