nagoya-congress-center.jp favicon

nagoya-congress-center.jp

https://nagoya-congress-center.jp· First analyzed 28 May 2026· Updated 28 May 2026
Export
nagoya-congress-center.jp
Desktop screenshot of nagoya-congress-center.jp
Mobile screenshot of nagoya-congress-center.jp
Mobile

Sponsored

Hosting Provider

IP Address

219.94.192.74

Site Location

🇯🇵 Japanvia tld

Server Location

🇯🇵 Osaka, Japan

ASN

AS9371

Organization

SAKURA

Server

Nginx

Nameservers

04.dnsv.jp.01.dnsv.jp.02.dnsv.jp.03.dnsv.jp.

Performance

92

Core Web Vitals

Weight

First Contentful Paint
1.3 s10%
Speed Index
1.7 s10%
Largest Contentful Paint
25%
Total Blocking Time
0.0 ms30%
Cumulative Layout Shift
0.00025%
2.4 MB
65 requests

Image Optimization

Responsive
0–49
50–89
90–100

Architecture Stack

Monolithic
⚙️ SSR
WordPress
cms
ncc-kyukan-themeCustom

Technology Stack

6 Technologies Detected

Libraries

2

UI Components

1

Web Servers

1

SEO Analysis

D48/100
13
8
3
Meta Tags4/15
Content8/12
Headings3/8
Technical15/25
E-E-A-T0/7
Images1/7
Links5/5
URL5/5
Social0/5
Freshness0/4
Mobile4/4
Indexability3/3
N
nagoya-congress-center.jpnagoya-congress-center.jp

名古屋国際会議場

No description available for this page.

Title Length8 chars

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

Description Length0 chars

Recommended: 120-160 chars

Issues (3)

  • Missing meta description — important for click-through rates in SERPs
  • Missing H1 tag — every page should have exactly one H1
  • Most images missing alt text (11/20) — critical for accessibility and SEO

Crawlability

Sitemap
robots.txt

3 rules

Local SEO

Local Search Readiness

15/100
Poor
4 11 2

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

Sponsored

AI & LLM Readiness

F32/100
Bot Access
20/25
Machine Read.
5/25
Schema Data
0/25
Citation
7/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
def. listsnavheader/footer
Text ratio:4%
Words:154
Token eff.:Too Short
Sections/1K:13
Depth:3/5

Structured Data

No Schema

Citation Readiness

Opening Summary
Descriptive Headingsavg 1w
Canonical URL
Open Graph0/3
Twitter Card0/3
Language Tag
Publish Date
Author Info
Lists
Tables
TL;DR / Summary
About Page Link
Recommendations (11)
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.
B
74/100
11
Passed
4
Critical
1
Warnings
Images & Alt Text
15/20
Checks if images have descriptive alt text for screen readers and visually impaired users.
Semantic Structure
13/20
Evaluates proper use of HTML5 semantic elements (header, nav, main, footer) and heading hierarchy.
Forms & Inputs
10/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
13/15
Ensures all interactive elements are reachable and operable via keyboard (tab, enter, escape).
ARIA & Roles
8/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.
22/100
E
298 mg
CO₂e / view
2.4 MB
Page Weight
30%
Cleaner Than
New Visitor
341 mg
vs
Returning (cached)
170 mg
Annual (10K/mo)
35.8 kg
Emission Segments
Data Center
67 mg
Network
72 mg
Device
160 mg
Resource Breakdown
JavaScript
72.0 KB
Images
2.2 MB
CSS
65.9 KB
HTML
5.1 KB
Green Hosting Not Verified
SAKURA
7 recommendations
  • Carbon footprint recommendation preview...
F

Security Score

21%Critical
Interactive

HTTPS

No WAF

77d

Certificate Details

Type

Domain Validated (DV)

Certificate Authority

Let's Encrypt

Key Algorithm

RSA (2048 bit)

Signature

SHA-256 with RSA

TLS Version

TLSv1.2

HTTP Protocol

HTTP/2

Valid From

16.05.2026

Valid Until

14.08.2026

Subject Alternative Names (2)

nagoya-congress-center.jpwww.nagoya-congress-center.jp

SHA-256 Fingerprint

30:50:30:C0:20:2F:6F:60:94:9E:86:51:7C:90:4D:72:CF:94:21:9F...

Top Recommendations

Security recommendation preview

HTTP Headers

Developer Console

content-encoding
📦 Gzip(gzip)
content-length
4878
content-type
text/html; charset=UTF-8
date
Thu, 28 May 2026 13:56:40 GMT
link
<https://nagoya-congress-center.jp/wp-json/>; rel="https://a...
server
nginx
Good Warning Issue

Email Infrastructure

Custom Mail Server

Score

45

SPF
DKIM
DMARC

MX Records (1)

nagoya-cc.sakura.ne.jp

Domain Information

nagoya-congress-center.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.
C
63/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
2 recommendations
  • Mobile compatibility recommendation preview...

Typography & Readability

Open Sans

WCAG Partial
45/100
Readability
/30
13/30

13px · LH --

Hierarchy
/20
5/20
WCAG
/25
14/25

1.43:1 min contrast

Performance
/25
13/25

1 font · 2 req

Heading Font

Open Sans

Sans

Body Font

Open Sans

Sans13px

Contrast Ratio

1.43:1

9 issues

Reading Comfort

~48 CPL

Optimal (45–75)
18px
h2
13px
p

❌ Critical: 13px body text is too small. Minimum 14px, recommend 16px+.

✅ Optimal line length: ~48 chars/line (ideal 45–75 CPL).

⚠️ Partial contrast: 9 elements below WCAG AA threshold (min 1.4:1).

❌ Missing H1: Every page should have exactly one H1 element for SEO and accessibility.

⚠️ Text justify detected: Justified text creates uneven word spacing, hurting readability on web.

✅ Lean font stack: 1 font families keeps load times fast.

Color Palette

14 unique colors
2.16:1 Fail Dark
#6e7a82
Secondary· 4.9%
#adb8b8
Other· 4.4%
#f7fcff
Primary· 13.600000000000001%
#d3ecfc
Accent· 13.4%
#ce2a2d
Accent· 8.4%
#9fcceb
Accent· 7.7%
#b9cfd8
Secondary· 7%
#296985
Accent· 6.9%

Business & Marketing Stack

1 Tools Detected

Growing

Behavior Analytics

1

User behavior and product analytics

1

Categories

1

Total Tools

0

Enterprise

0

Mid-Market

Assessment: Growing marketing technology adoption

Sponsored

Scripts & Styles

22 Resources

12
Scripts
10
Styles
1
Async
0
Defer

Top Script Sources

nagoya-congress-center.jp(9)google.com(2)googletagmanager.com(1)

Website Identity

nagoya-congress-center.jp

Location detected: 🇯🇵 Japanvia tld
ja

Sponsored

Last analyzed: 28 May 2026 at 13:57

Historical Analysis & Change Tracking