fluid-emotion-spectrum.com
Fluid Emotion Spectrum | fluid-emotion-spectrum.com
1 failed · 5 warnings · 22 passed
Audited Sun, 26 Jul 2026 01:45:53 GMT · https://www.fluid-emotion-spectrum.com/
Meta & Head
22.2/25
Title, description, canonical, social tags — what search engines read first.
Canonical URLmedium impactlow effort
Canonical href is "https://fluid-emotion-spectrum.com" (host fluid-emotion-spectrum.com does not match page host www.fluid-emotion-spectrum.com)
This canonical tells search engines that another host owns the content, so they will typically index that URL and drop this one from results entirely. Unless this is deliberate syndication, update the href to this page's own URL on its own host — and make sure www vs non-www matches your preferred domain. The usual cause is a template copied between environments, so check that a staging or legacy domain isn't hard-coded in the site layout.
Open Graph tagsmedium impactlow effort
Missing Open Graph tags: og:image
Your Open Graph markup is incomplete, so social platforms fall back to guessed text or drop the preview image entirely when this page is shared — a broken card gets far fewer clicks than a complete one. Add the missing og:image tag to <head>. For og:image, use an absolute https:// URL to an image around 1200x630 pixels; relative paths are the usual reason previews break. Re-check with a platform's sharing debugger afterwards, since preview cards are cached.
7 passing checks
- Title tag<title> is "Fluid Emotion Spectrum | fluid-emotion-spectrum.com" (51 characters)
- Meta descriptionMeta description is "fluid-emotion-spectrum.com — 감정을 입력하면 AI가 실시간으로 분석해 색상과 파동으로 시각화하는 감정 스펙트럼 서비스입니다." (82 characters)
- Viewport meta tagViewport is "width=device-width, initial-scale=1"
- Character encoding declaredCharacter encoding is declared
- FaviconA <link rel="icon"> is present
- Twitter card tagtwitter:card is "summary"
- Page allows indexingNo restrictive robots meta tag
Content & Structure
17.9/25
Headings, copy depth, images, structured data, internal linking.
Word counthigh impactlow effort
231 words of visible text
Under 300 words, search engines typically classify a page as thin content, and thin pages rarely rank for anything competitive. Decide which query this page should answer, then write substantive copy — aim for 600+ words covering what it is, how it works, common questions, and concrete examples. If the page genuinely has nothing more to say, merge it into a stronger related page with a 301 redirect rather than padding it with filler that helps no one.
Structured data (JSON-LD)medium impactmedium effort
No JSON-LD structured data blocks found
Structured data makes your listing eligible for rich results — star ratings, FAQs, breadcrumbs, product prices — which occupy more space on the results page and draw more clicks than plain blue links. Add a <script type="application/ld+json"> block with a schema.org type that matches the page: Organization or WebSite for a homepage, Article for posts, Product for product pages. Only mark up content actually visible on the page — markup for invisible content violates Google's guidelines and can earn a manual action.
5 passing checks
- Single H1 heading1 h1 found: "Fluid Emotion Spectrum"
- Heading hierarchy8 headings in order without skipped levels
- HTML lang attribute<html lang="ko">
- JavaScript-dependent contentvisible text ~834 chars in the initial HTML
- Internal linking3 internal, 0 external links
Technical
23.3/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
Short redirect chainmedium impactlow effort
https://fluid-emotion-spectrum.com/ (308) → https://www.fluid-emotion-spectrum.com/
Every redirect hop adds a round-trip before the visitor sees anything, each hop can leak a little link equity, and crawlers abandon long chains — which can leave the destination page undiscovered. Trace the chain above and point the first URL directly at the final destination in a single 301; commonly this means merging separate http-to-https and non-www-to-www rules into one combined redirect. Also update internal links to reference the final URL directly, so most visitors never enter the chain at all.
Response compression enabledlow impactlow effort
no content-encoding header
This HTML is served uncompressed, so every visitor downloads far more bytes than necessary — text compresses extremely well, and the savings directly speed up first render on slow connections. Enable Brotli or gzip on your server or CDN: in nginx it's "gzip on;" (or the brotli module), in Apache it's mod_deflate via .htaccess, and on most CDNs it's a single toggle. Make sure compression covers all text types (HTML, CSS, JS, JSON, SVG), but skip already-compressed images — recompressing them wastes CPU for no gain.
10 passing checks
- Served over HTTPSfinal URL uses https://
- HTTP redirects to HTTPShttp:// redirects to https://
- No mixed content0 http:// subresource references
- robots.txt present and permissiverobots.txt exists and allows crawling
- XML sitemap availablesitemap.xml exists and is valid XML
- Fast time to first byte733 ms
- Reasonable HTML size15.1 KB
- Missing pages return 404missing paths return HTTP 404/410
- www and non-www resolve consistentlywww and non-www converge on the same host
- HTML5 doctype<!DOCTYPE html> present
Performance
Core Web Vitals scoring via Google PageSpeed is coming soon.
Share your score
Embed this live badge on your site — it updates whenever the audit is re-run.