all-birds-japan.com
Allbirds Japan - オールバーズスニーカー,靴,サンダル店舗東京日本
1 failed · 8 warnings · 20 passed
Audited Sun, 12 Jul 2026 23:30:49 GMT · https://www.all-birds-japan.com/
Meta & Head
21.5/25
Title, description, canonical, social tags — what search engines read first.
Meta descriptionhigh impactlow effort
Meta description is "オールバーズの日本セール！オールバーズ店舗東京. 日本でオールバーズスニーカー,靴,サンダル,服をオンラインで購入。送料無料と返品無料。" (68 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.
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 "Allbirds Japan - オールバーズスニーカー,靴,サンダル店舗東京日本" (41 characters)
- Canonical URLCanonical href is "https://www.all-birds-japan.com/"
- 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_large_image"
- Page allows indexingrobots: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
Content & Structure
24.2/25
Headings, copy depth, images, structured data, internal linking.
Heading hierarchylow impactlow effort
Heading level jumps from h1 ("Allbirds Japan") to h3 ("Allbirds Cruiser キャンバス メンズ スニーカー 白")
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: "Allbirds Japan"
- Word count3215 words of visible text
- Image alt text61 of 63 images have alt text
- Structured data (JSON-LD)JSON-LD types found: WebPage, BreadcrumbList, WebSite, Organization
- HTML lang attribute<html lang="ja">
- JavaScript-dependent contentvisible text ~9058 chars in the initial HTML
- Internal linking190 internal, 5 external links
Technical
16.5/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
Fast time to first bytehigh impactmedium effort
4022 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.
HTTP redirects to HTTPSmedium impactlow effort
http:// version serves content without redirecting
Your http:// URLs serve content instead of redirecting, so search engines can crawl and index two parallel copies of every page and split ranking signals between them. Add a permanent 301 redirect from http to https at the server or CDN level — in nginx, "return 301 https://$host$request_uri;" in the port-80 server block; in Apache, a RewriteRule in .htaccess; on Cloudflare, enable "Always Use HTTPS". Use a 301, not a 302 — temporary redirects don't consolidate ranking signals — and preserve the full path in the redirect target.
No mixed contentmedium impactlow effort
2 http:// subresource references
Some images, scripts, or styles load over insecure http:// on this HTTPS page; browsers block insecure scripts outright and flag the page, which breaks functionality and undermines the padlock users look for. Update each reference to https:// — most hosts serve the same asset on both schemes — or re-host assets whose origins don't support TLS. Adding <meta http-equiv="Content-Security-Policy" content="upgrade-insecure-requests"> is a quick safety net, but fix the underlying URLs too: hard-coded http:// links in databases and old content are the usual source.
Short redirect chainmedium impactlow effort
https://all-birds-japan.com/ (301) → https://www.all-birds-japan.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.
XML sitemap availablemedium impactlow effort
no sitemap.xml found
Without an XML sitemap, search engines discover pages only by following links, so new, deep, or weakly linked pages get found slowly or not at all. Generate one at /sitemap.xml — most frameworks and CMSs have a generator built in or as a plugin — listing every canonical, indexable URL, then add "Sitemap: https://www.example.com/sitemap.xml" to robots.txt and submit it in Google Search Console. Keep it clean: listing redirected, noindexed, or 404 URLs erodes crawler trust in the whole file.
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.
6 passing checks
- Served over HTTPSfinal URL uses https://
- robots.txt present and permissiverobots.txt exists and allows crawling
- Reasonable HTML size262.2 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.