mulstol.pro
翠香茶舗株式会社 - 香り豊かな日本茶をお届け
0 failed · 7 warnings · 22 passed
Audited Mon, 13 Jul 2026 20:30:46 GMT · https://mulstol.pro/
Meta & Head
18.1/25
Title, description, canonical, social tags — what search engines read first.
Title taghigh impactlow effort
<title> is "翠香茶舗株式会社 - 香り豊かな日本茶をお届け" (23 characters)
Search engines truncate titles past roughly 60 characters and often rewrite very short or vague ones, so the message you wrote may never actually be shown. Rewrite the title to 30–60 characters that lead with the primary keyword and end with your brand, e.g. "Merge PDF Files Online Free | YourBrand". Front-load the important words, since truncation always cuts from the end. Don't pad a short title with repeated keywords just to hit the range — clarity wins clicks, not length.
Meta descriptionhigh impactlow effort
Meta description is "翠香茶舗株式会社のお問い合わせページです。日本茶のご相談、ご注文、取引に関するご連絡を承ります。" (48 characters)
Search engines truncate descriptions past roughly 160 characters, and very short ones waste the snippet space that persuades searchers to pick your listing over the next one. Rewrite it to 70–160 characters: state what the page offers, work the primary keyword in naturally (matching words get bolded in results), and end with a benefit or call to action. Don't cram in keywords — the description influences clicks, not rankings, so write it for humans.
Canonical URLmedium impactlow effort
Canonical href is "index.html" (not an absolute URL)
Crawlers resolve relative canonical URLs against whatever URL they happened to fetch, so a relative href can silently point your ranking signals at a parameterized or duplicate address. Replace it with the full absolute URL including scheme and host, e.g. <link rel="canonical" href="https://www.example.com/pricing/">. Generate it server-side from a configured base URL rather than from the incoming request's Host header, so staging domains and proxies can't leak into it.
Faviconlow impactlow effort
No <link rel="icon"> and /favicon.ico does not respond
Google displays favicons beside mobile search results, and browsers show them in tabs, bookmarks, and history — a missing icon makes your listing look generic and less trustworthy next to competitors. Create an icon of at least 48x48 pixels, serve it at /favicon.ico, and reference it with <link rel="icon" href="/favicon.png" type="image/png"> in <head>. Make sure robots.txt doesn't block the icon's path — search engines must be able to crawl it to display it.
Twitter card taglow impactlow effort
No twitter:card meta tag found
X (Twitter) layers its own card markup on top of Open Graph, and without a twitter:card tag your shared links may render as plain text instead of a large image preview. Add <meta name="twitter:card" content="summary_large_image"> alongside your Open Graph tags; X will fill in the title, description, and picture from og:title, og:description, and og:image. Keep og:image an absolute URL — a relative or missing image is the usual reason cards show up without a picture.
4 passing checks
- Viewport meta tagViewport is "width=device-width, initial-scale=1.0"
- Character encoding declaredCharacter encoding is declared
- Open Graph tagsAll core Open Graph tags present (og:title, og:description, og:image, og:url)
- Page allows indexingrobots: index, follow
Content & Structure
24.2/25
Headings, copy depth, images, structured data, internal linking.
Heading hierarchylow impactlow effort
Heading level jumps from h2 ("お客様の声") to h4 ("佐藤 美咲")
Headings form the page's outline; when levels jump (h2 straight to h4), search engines and screen readers get a broken table of contents and the relationship between sections turns ambiguous. Fix the jump by stepping down one level at a time — promote the deeper heading, or add the missing intermediate level. The usual cause is choosing heading tags for their default font size; set sizes in CSS instead and let the tags reflect actual document structure.
7 passing checks
- Single H1 heading1 h1 found: "一杯のお茶に、翠の香りと丁寧な時間を。"
- Word count2485 words of visible text
- Image alt text41 of 41 images have alt text
- Structured data (JSON-LD)JSON-LD types found: LocalBusiness, FAQPage
- HTML lang attribute<html lang="ja">
- JavaScript-dependent contentvisible text ~12793 chars in the initial HTML
- Internal linking4 internal, 0 external links
Technical
24.4/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
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.
11 passing checks
- Served over HTTPSfinal URL uses https://
- HTTP redirects to HTTPShttp:// redirects to https://
- No mixed content0 http:// subresource references
- Short redirect chainno redirects; URL resolves directly
- robots.txt present and permissiverobots.txt exists and allows crawling
- XML sitemap availablesitemap.xml exists and is valid XML
- Fast time to first byte191 ms
- Reasonable HTML size77.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.