shutterchanceworks.com
シャッターチャンス｜学校・園の出張撮影・卒業アルバム（東京・神奈川・埼玉・千葉）
4 failed · 2 warnings · 21 passed
Audited Thu, 30 Jul 2026 04:45:08 GMT · https://shutterchanceworks.com/
Meta & Head
22.2/25
Title, description, canonical, social tags — what search engines read first.
Viewport meta tagmedium impactlow effort
No viewport meta tag found
Google crawls and ranks the mobile version of your site first, and without a viewport tag phones render pages at desktop width — tiny, zoomed-out text that fails mobile-usability checks and drives visitors straight back to the results. Add <meta name="viewport" content="width=device-width, initial-scale=1"> inside <head> on every page. Resist adding user-scalable=no or maximum-scale=1 while you're there: disabling pinch-zoom hurts accessibility and gets flagged by audits.
8 passing checks
- Title tag<title> is "シャッターチャンス｜学校・園の出張撮影・卒業アルバム（東京・神奈川・埼玉・千葉）" (40 characters)
- Meta descriptionMeta description is "シャッターチャンスは、東京を中心に神奈川・埼玉・千葉の保育園・幼稚園・学校で、スナップ写真の撮影・販売、卒業アルバム制作、運動会・卒業式など行事の撮影、動画・ドローン空撮に対応。修学旅行は県外撮影も可能です。経験豊富なカメラマンが学校のルールに配慮し、一枚一枚丁寧に撮影します。" (139 characters)
- Canonical URLCanonical href is "https://shutterchanceworks.com/"
- Character encoding declaredCharacter encoding is declared
- FaviconA <link rel="icon"> is present
- Open Graph tagsAll core Open Graph tags present (og:title, og:description, og:image, og:url)
- Twitter card tagtwitter:card is "summary_large_image"
- Page allows indexingNo restrictive robots meta tag
Content & Structure
15.4/25
Headings, copy depth, images, structured data, internal linking.
Single H1 headinghigh impactlow effort
0 h1 headings found
The h1 is the visible headline of the page and one of the clearest signals to search engines of what it's about; with none present, engines lean on surrounding text and may misread the topic. Add exactly one h1 near the top that states the main topic in plain language and includes the primary keyword, e.g. <h1>Merge PDF Files Online</h1>. Don't fake it with a styled <div> — the semantic tag itself is what crawlers and screen readers actually read.
Internal linkingmedium impactmedium effort
0 internal, 0 external links
Search engines discover and rank your pages by following internal links; a page with none is a dead end for crawlers and visitors alike. Add contextual links to related pages on your own site — navigation, related-content sections, and in-body links all count. Aim for at least a handful of relevant internal links per page.
4 passing checks
- Word count1112 words of visible text
- Structured data (JSON-LD)JSON-LD types found: ProfessionalService
- HTML lang attribute<html lang="ja">
- JavaScript-dependent contentvisible text ~518 chars in the initial HTML
Technical
21.6/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
Reasonable HTML sizelow impactmedium effort
5.0 MB
A very large HTML document slows parsing on every visit and risks exceeding the portion of a file crawlers are willing to fetch — content past the cutoff may simply never be indexed. Slim it down: move large inline <script> and <style> blocks into external cacheable files, strip embedded JSON data blobs and base64-encoded images, and paginate or lazy-load very long listings. Check the most common culprit first: a framework serializing the entire page state or dataset into the document itself.
Fast time to first bytehigh impactmedium effort
1431 ms
Time to first byte is the floor under every other speed metric — the browser can't parse, render, or fetch anything until the first byte arrives, so a slow TTFB drags down all Core Web Vitals and tests crawlers' patience. Add caching in front of the origin: full-page caching at a CDN (Cloudflare, Fastly) helps most, followed by server-side caches (Redis, object caching) and indexes on slow database queries. Measure from locations near your actual users — tuning only your fastest region leaves distant visitors just as slow.
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.
9 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
- 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.