Catalog / ifsx.io
65

SEO audit for ifsx.io

잎스

saas

Health 65/100 (fair) · 9 pages crawled · generated 2026-08-26

Download Markdown report (feed to ChatGPT / Claude / Cursor)

for life, for business, all-in-one platform

Screenshot of ifsx.io
9
pages crawled
9
indexable pages
0
errors
39
warnings
82
notices
4
orphan pages
0
broken links
Category breakdown
CategoryScoreErrorsWarningsNotices
Security 70 0 9 9
Agent Readiness 77 0 7 7
Headings 77 0 7 1
Content 80 0 6 9
Duplicate 80 0 6 5
Links 87 0 4 8
Meta Description 100 0 0 9
Performance 100 0 0 16
Structured Data 100 0 0 9
Titles 100 0 0 9
Findings

Warnings (6 rules)

warning Control has no accessible name

Rule agent.control_no_name · Agent Readiness · 7 occurrence(s)

warning Thin content (low word count)

Rule content.thin · Content · 6 occurrence(s)

warning Duplicate <title> across pages

Rule duplicate.title · Duplicate · 6 occurrence(s)

warning Missing <h1>

Rule h1.missing · Headings · 7 occurrence(s)

warning Content-Type header doesn't match the actual content

Rule headers.content_type_mismatch · Security · 9 occurrence(s)

  • https://www.ifsx.io/ — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.ifsx.io/about — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.ifsx.io/displays/touchs — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.ifsx.io/inquries/inquires — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.ifsx.io/inquries/meetings — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.ifsx.io/inquries/thanks — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.ifsx.io/inquries/thanks-meeting — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.ifsx.io/kiosks/photos/events — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".
  • https://www.ifsx.io/kiosks/photos/pricing — the Content-Type is "text/html" with no charset — the HTTP charset is authoritative and browsers otherwise guess the encoding, which can garble non-ASCII text (mojibake). Declare it explicitly: "text/html; charset=utf-8".

warning Orphan page (no internal inlinks)

Rule links.orphan · Links · 4 occurrence(s)

Notices (14 rules)

notice No llms.txt for AI agents

Rule agent.llms_txt_missing · Agent Readiness · 1 occurrence(s)

  • https://www.ifsx.io/ — no llms.txt found at the site root — add one so AI agents get a curated site summary

notice No main landmark for AI agents

Rule agent.no_main_landmark · Agent Readiness · 6 occurrence(s)

notice Low text-to-HTML ratio

Rule content.low_ratio · Content · 9 occurrence(s)

notice Duplicate meta description across pages

Rule duplicate.meta_desc · Duplicate · 5 occurrence(s)

notice Multiple <h1> elements

Rule h1.multiple · Headings · 1 occurrence(s)

notice Likely hero image lacks fetchpriority=high

Rule images.hero_no_fetchpriority · Performance · 7 occurrence(s)

  • https://www.ifsx.io/ — the likely hero/LCP image (kmudmuu4tigpqxqm9vqgmclq.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.ifsx.io/about — the likely hero/LCP image (bcbafgnrlzfkzfzqlsw94copuc.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.ifsx.io/displays/touchs — the likely hero/LCP image (c9iuy0mx2ks4ec7d2u5rstfga.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.ifsx.io/inquries/inquires — the likely hero/LCP image (jynrbundqb11uvka6bb6dvkmmb0.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.ifsx.io/inquries/meetings — the likely hero/LCP image (jynrbundqb11uvka6bb6dvkmmb0.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.ifsx.io/kiosks/photos/events — the likely hero/LCP image (io1d5eixe13xufn655cazb100.jpg) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.
  • https://www.ifsx.io/kiosks/photos/pricing — the likely hero/LCP image (pxcgeowgstf3xfeuwek1xa63lg.png) has no fetchpriority="high" — adding it tells the browser to fetch the hero earlier in the waterfall, reducing Largest Contentful Paint. This is a low-severity nudge; verify the flagged image is actually your LCP element.

notice Internal link has no anchor text / accessible name

Rule links.no_anchor_text · Links · 7 occurrence(s)

  • https://www.ifsx.io/ — 3 internal link(s) have no anchor text, aria-label, or image alt — they pass no keyword signal and are unusable to screen readers. Add descriptive text or an aria-label.
  • https://www.ifsx.io/about — 5 internal link(s) have no anchor text, aria-label, or image alt — they pass no keyword signal and are unusable to screen readers. Add descriptive text or an aria-label.
  • https://www.ifsx.io/displays/touchs — 5 internal link(s) have no anchor text, aria-label, or image alt — they pass no keyword signal and are unusable to screen readers. Add descriptive text or an aria-label.
  • https://www.ifsx.io/inquries/inquires — 2 internal link(s) have no anchor text, aria-label, or image alt — they pass no keyword signal and are unusable to screen readers. Add descriptive text or an aria-label.
  • https://www.ifsx.io/inquries/meetings — 3 internal link(s) have no anchor text, aria-label, or image alt — they pass no keyword signal and are unusable to screen readers. Add descriptive text or an aria-label.
  • https://www.ifsx.io/kiosks/photos/events — 5 internal link(s) have no anchor text, aria-label, or image alt — they pass no keyword signal and are unusable to screen readers. Add descriptive text or an aria-label.
  • https://www.ifsx.io/kiosks/photos/pricing — 2 internal link(s) have no anchor text, aria-label, or image alt — they pass no keyword signal and are unusable to screen readers. Add descriptive text or an aria-label.

notice Page has only one internal inlink (fragile crawl path)

Rule links.single_inlink · Links · 1 occurrence(s)

  • https://www.ifsx.io/displays/touchs — only one internal link points here — if that source changes, this page becomes an orphan. Add more contextual internal links to strengthen the crawl path.

notice Meta description too short

Rule meta_desc.too_short · Meta Description · 9 occurrence(s)

notice Large DOM (over 1500 elements) slows rendering & interaction

Rule perf.dom_size_large · Performance · 2 occurrence(s)

  • https://www.ifsx.io/displays/touchs — the page has 1586 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.
  • https://www.ifsx.io/kiosks/photos/events — the page has 1567 DOM elements (recommended maximum is around 1500) — a large DOM increases style-recalculation, layout and paint cost, hurting LCP and INP. Flatten deep nesting, paginate long lists/tables, and lazy-render off-screen elements.

notice Legacy image format (jpg/png/gif) with no next-gen fallback

Rule perf.images_legacy_format · Performance · 7 occurrence(s)

  • https://www.ifsx.io/ — 4 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.ifsx.io/about — 16 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.ifsx.io/displays/touchs — 67 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.ifsx.io/inquries/inquires — 3 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.ifsx.io/inquries/meetings — 6 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.ifsx.io/kiosks/photos/events — 147 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.
  • https://www.ifsx.io/kiosks/photos/pricing — 2 image(s) use a legacy format (jpg/png/gif) with no next-gen <picture> fallback. Serve WebP or AVIF (with a <picture> typed <source>) to cut image transfer weight and improve LCP.

notice No structured data detected

Rule schema.none · Structured Data · 9 occurrence(s)

notice Missing recommended security headers

Rule security.missing_headers · Security · 9 occurrence(s)

notice Title is very short

Rule title.too_short · Titles · 9 occurrence(s)

Pages (showing 9 of 9)
URLStatusIndexableWordsIn-links
https://www.ifsx.io/
잎스		 200 yes 12 9
https://www.ifsx.io/about
잎스		 200 yes 283 7
https://www.ifsx.io/inquries/inquires
문의하기 - iFSX		 200 yes 84 4
https://www.ifsx.io/kiosks/photos/events
포토키오스크 - IFSX		 200 yes 946 2
https://www.ifsx.io/displays/touchs
디스플레이 - IFSX		 200 yes 758 1
https://www.ifsx.io/inquries/meetings
문의하기 - iFSX		 200 yes 95 0
https://www.ifsx.io/inquries/thanks
문의하기 - iFSX		 200 yes 10 0
https://www.ifsx.io/inquries/thanks-meeting
문의하기 - iFSX		 200 yes 10 0
https://www.ifsx.io/kiosks/photos/pricing
요금제 안내 - IFSX		 200 yes 135 0

Audit your own site — free

157 checks, internal PageRank, render-diff. No signup, results in ~30s.

Scan your site →