fujisan.ne.jp favicon

fujisan.ne.jp

https://fujisan.ne.jp· First analyzed 10 May 2026· Updated 10 May 2026
Export
fujisan.ne.jp
Desktop screenshot of fujisan.ne.jp
Mobile screenshot of fujisan.ne.jp
Mobile

Sponsored

Hosting Provider

IP Address

219.94.155.236

Site Location

🇯🇵 Japanvia tld

Server Location

🇯🇵 Osaka, Japan

ASN

AS9371

Organization

SAKURA

Server

Nginx

Nameservers

ns1.dns.ne.jp.ns2.dns.ne.jp.

Performance

73

Core Web Vitals

Weight

First Contentful Paint
7.7 s10%
Speed Index
10.0 s10%
Largest Contentful Paint
25%
Total Blocking Time
0.0 ms30%
Cumulative Layout Shift
0.00025%
8.8 MB
81 requests

Image Optimization

Lazy LoadWebPResponsive
0–49
50–89
90–100

Architecture Stack

Monolithic
⚙️ SSR
WordPressv6.1.5
cms
fujikawaguchikoCustom

Technology Stack

11 Technologies Detected

SEO Analysis

D57/100
16
8
2
Meta Tags7/15
Content8/12
Headings3/8
Technical19/25
E-E-A-T0/7
Images2/7
Links2/5
URL5/5
Social4/5
Freshness0/4
Mobile4/4
Indexability3/3
F
fujisan.ne.jpfujisan.ne.jp

富士河口湖町観光情報サイト│FUJIKAWAGUCHIKO

富士河口湖町の公式観光情報サイト。富士山と湖が織りなす絶景スポット、四季の自然、グルメや体験、モデルコースまで幅広く紹介。静かな観光や地域の魅力を深く楽しむ旅の情報が見つかります。

Title Length29 chars

Recommended: 50-60 chars (~183px / 580px)

Description Length90 chars

Recommended: 120-160 chars

Issues (2)

  • Missing H1 tag — every page should have exactly one H1
  • Most images missing alt text (59/98) — critical for accessibility and SEO

Crawlability

Sitemap

Type: index

8 URLs

8 sub-sitemaps

robots.txt

4 rules

Sitemap reference found

Local SEO

Local Search Readiness

6/100
Poor
2 13 2

This site doesn't appear to be a local business. Local SEO signals are optional for non-local websites.

Sponsored

AI & LLM Readiness

F35/100
Bot Access
20/25
Machine Read.
7/25
Schema Data
0/25
Citation
8/25

AI Bot Access

14/14 accessible
AI Search
OAI-SearchBot
PerplexityBot
Claude-SearchBot
Gemini-Deep-Research
DuckAssistBot
Training
GPTBot
ClaudeBot
Google-Extended
Meta-ExternalAgent
Bytespiderinfo
Amazonbot
Applebot-Extended
CCBotinfo
Fetch
ChatGPT-User

Machine Readability

llms.txt
llms-full.txt
Semantic HTML
Heading Hierarchy
nav
Text ratio:2%
Words:178
Token eff.:Too Short
Sections/1K:84.3
Depth:1/5

Structured Data

No Schema

Citation Readiness

Opening Summary
Descriptive Headingsavg 1.2w
Canonical URL
Open Graph3/3
Twitter Card1/3
Language Tag
Publish Date
Author Info
Lists
Tables
TL;DR / Summary
About Page Link
Recommendations (10)
AI readiness recommendation preview...

Sponsored

Accessibility

WCAG 2.1 Compliance

Evaluates how accessible your website is for users with disabilities, based on WCAG 2.1 guidelines. Checks images, forms, keyboard navigation, ARIA roles, and color contrast.
A
80/100
14
Passed
1
Critical
3
Warnings
Images & Alt Text
20/20
Checks if images have descriptive alt text for screen readers and visually impaired users.
Semantic Structure
20/20
Evaluates proper use of HTML5 semantic elements (header, nav, main, footer) and heading hierarchy.
Forms & Inputs
7/15
Verifies form fields have labels, error messages are clear, and inputs are properly associated.
Color & Contrast
15/15
Tests text-to-background color contrast ratios against WCAG AA/AAA minimum requirements.
Keyboard & Focus
11/15
Ensures all interactive elements are reachable and operable via keyboard (tab, enter, escape).
ARIA & Roles
7/15
Checks correct use of WAI-ARIA attributes (roles, states, properties) for assistive technologies.
3 recommendations
  • Accessibility recommendation preview...

Carbon Footprint

SWDM v4 · Eco-Score

Carbon emissions estimated using the Sustainable Web Design Model v4 (SWDM v4). Factors in data center, network, and device energy across new and returning visitors. Grade thresholds based on HTTP Archive percentiles.
16/100
F
1.12 g
CO₂e / view
8.8 MB
Page Weight
5%
Cleaner Than
New Visitor
1.27 g
vs
Returning (cached)
637 mg
Annual (10K/mo)
133.8 kg
Emission Segments
Data Center
249 mg
Network
268 mg
Device
599 mg
Resource Breakdown
JavaScript
293.9 KB
Images
7.7 MB
CSS
636.3 KB
Fonts
88.4 KB
HTML
105.8 KB
Green Hosting Not Verified
SAKURA
9 recommendations
  • Carbon footprint recommendation preview...
F

Security Score

21%Critical
Interactive

HTTPS

No WAF

315d

Certificate Details

Type

Domain Validated (DV)

Certificate Authority

GlobalSign nv-sa

Key Algorithm

RSA (2048 bit)

Signature

SHA-256 with RSA

TLS Version

TLSv1.2

HTTP Protocol

HTTP/2

Valid From

18.02.2026

Valid Until

22.03.2027

OCSP Stapling

Enabled

Subject Alternative Names (2)

www.fujisan.ne.jpfujisan.ne.jp

SHA-256 Fingerprint

37:3D:D2:3C:EA:10:72:06:32:8D:39:F9:76:50:15:ED:D4:11:1E:12...

Top Recommendations

Security recommendation preview

HTTP Headers

Developer Console

content-type
text/html; charset=UTF-8
date
Sun, 10 May 2026 16:34:29 GMT
link
<https://fujisan.ne.jp/wp-json/>; rel="https://api.w.org/", ...
server
nginx
vary
Accept-Encoding
Good Warning Issue

Email Infrastructure

Custom Mail Server

Score

65

SPF
DKIM
DMARC

DMARC Policy

None (Monitor Only)

MX Records (1)

mail.fujisan.ne.jp

Domain Information

fujisan.ne.jp

DNSSEC
Not Enabled

Privacy & Compliance

Cookie Consent Banner
Privacy Policy
Terms of Service

GDPR Indicators

Privacy policy page linked

Mobile Compatibility

Viewport & Responsive Test

Tests how well your website works on mobile devices. Checks viewport configuration, responsive layout, touch targets, font readability, and simulates rendering across different screen sizes.
B
72/100
Mobile Friendly1 breakpoint
Viewport Meta
The viewport meta tag tells mobile browsers how to scale the page. Without it, mobile devices render at desktop width.
Responsive Design
Uses CSS media queries or flexible layouts to adapt content to different screen sizes automatically.
Touch Icons
Apple touch icons and favicons displayed when users add the site to their home screen on mobile devices.
Readable Font Size
Base font size should be at least 16px on mobile to ensure text is readable without zooming.
Relative Units
Using em, rem, %, or vw instead of fixed px values allows content to scale properly across screen sizes.
No H-Scroll Risk
No elements wider than the viewport that would cause horizontal scrolling on mobile devices.
Tap Targets OK
Interactive elements (buttons, links) are at least 48x48px with enough spacing to prevent accidental taps.
No Fixed Widths
No elements with fixed pixel widths that could overflow on smaller screens and break the layout.
Viewport
width=device-width,initial-scale=1.0
1 recommendation
  • Mobile compatibility recommendation preview...

Typography & Readability

Noto Sans JP

WCAG Partial
68/100
Readability
/30
18/30

16px · LH 1.88

Hierarchy
/20
18/20

2x ratio · ✓ H1→H6

WCAG
/25
12/25

1:1 min contrast

Performance
/25
20/25

2 fonts · 1 req

Heading Font

Noto Sans JP

Sans32px

Body Font

Noto Sans JP

Sans16px

Contrast Ratio

1:1

19 issues

Reading Comfort

~34 CPL

Narrow lines
32px
h1
46px
h2
24px
h3
16px
p
Minor Second
Scale

✅ Excellent readability: 16px body text is ideal for all devices.

⚠️ Wide line spacing (1.88). 1.4–1.6 is optimal for body text.

⚠️ Partial contrast: 19 elements below WCAG AA threshold (min 1.0:1).

✅ Perfect heading hierarchy: Sequential h1→h2→h3 with single H1 — ideal for SEO & accessibility.

✅ Strong hierarchy: Headlines are 2.0x larger than body text.

❌ Pure vw font sizes: Viewport units alone break browser zoom (WCAG 1.4.4 fail). Use clamp(rem, vw, rem).

Color Palette

14 unique colors
Light
#ffffff
Background· 18.8%
#d89e81
Accent· 11.5%
#4bbfce
Accent· 8.8%
#80493f
Secondary· 8.8%
#c1897a
Secondary· 8.5%
#0f0907
Primary· 7.8%
#9f6d76
Secondary· 7%
#583542
Secondary· 6.2%

Business & Marketing Stack

2 Tools Detected

Growing

Behavior Analytics

2

User behavior and product analytics

1

Categories

2

Total Tools

0

Enterprise

0

Mid-Market

Assessment: Growing marketing technology adoption

Sponsored

Scripts & Styles

19 Resources

14
Scripts
5
Styles
2
Async
1
Defer

Top Script Sources

fujisan.ne.jp(10)googletagmanager.com(2)plugin.tabiato.me(1)challenges.cloudflare.com(1)

Website Identity

fujisan.ne.jp

Location detected: 🇯🇵 Japanvia tld
ja

Sponsored

Last analyzed: 10 May 2026 at 16:35

Historical Analysis & Change Tracking