Website review, no card needed
fangamer.jp website review
Visit site (opens in a new tab)Reviewed 6 November 202634 issues · 84 checks
This review found 34 issues worth fixing on fangamer.jp, 11 of them high impact, across 84 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
83B- #27,607 of 120,920 reviewed websitesbeats 72%
- #18,174 of 68,447 online storesbeats 67%
- #17,616 of 62,371 Shopify storesbeats 65%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 914 ms |
| May 23, 2026 | 910 ms |
| May 30, 2026 | 893 ms |
| Jun 6, 2026 | 905 ms |
| Jun 13, 2026 | 920 ms |
| Jun 20, 2026 | 901 ms |
| Jun 27, 2026 | 883 ms |
| Jul 4, 2026 | 883 ms |
| Jul 11, 2026 | 882 ms |
| Jul 18, 2026 | 885 ms |
| Jul 25, 2026 | 882 ms |
| Aug 1, 2026 | 866 ms |
| Aug 8, 2026 | 866 ms |
| Aug 15, 2026 | 876 ms |
| Aug 22, 2026 | 896 ms |
| Aug 29, 2026 | 931 ms |
| Sep 5, 2026 | 955 ms |
| Sep 12, 2026 | 997 ms |
| Sep 19, 2026 | 988 ms |
| Sep 26, 2026 | 992 ms |
| Oct 3, 2026 | 991 ms |
| Oct 10, 2026 | 970 ms |
| Oct 17, 2026 | 979 ms |
| Oct 24, 2026 | 977 ms |
| Oct 31, 2026 | 1.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 82 ms |
| May 23, 2026 | 81 ms |
| May 30, 2026 | 82 ms |
| Jun 6, 2026 | 82 ms |
| Jun 13, 2026 | 83 ms |
| Jun 20, 2026 | 84 ms |
| Jun 27, 2026 | 84 ms |
| Jul 4, 2026 | 83 ms |
| Jul 11, 2026 | 83 ms |
| Jul 18, 2026 | 83 ms |
| Jul 25, 2026 | 83 ms |
| Aug 1, 2026 | 84 ms |
| Aug 8, 2026 | 83 ms |
| Aug 15, 2026 | 84 ms |
| Aug 22, 2026 | 85 ms |
| Aug 29, 2026 | 86 ms |
| Sep 5, 2026 | 87 ms |
| Sep 12, 2026 | 87 ms |
| Sep 19, 2026 | 87 ms |
| Sep 26, 2026 | 86 ms |
| Oct 3, 2026 | 86 ms |
| Oct 10, 2026 | 86 ms |
| Oct 17, 2026 | 86 ms |
| Oct 24, 2026 | 87 ms |
| Oct 31, 2026 | 87 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.2 s
1.6 s
2.0 s
2.3 s
2.7 s
3.1 s
Speed
Render-blocking requests
1.1 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 71
71/100Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
803 KiB13 images could be 803 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
2,197 HTML elements
The page has 2,197 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
250 ms · 47 KiBAbout 47 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 250 ms faster on a phone.
Reduce unused JavaScript
150 ms · 52 KiBAbout 52 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 22 KiB15 files are served with short cache lifetimes, so returning visitors download them again (22 KiB).
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 127 ms. During a long task the page ignores taps.
5 third-party services on the page
5 third-party services load with your homepage (Shopify, Mailchimp and Adobe TypeKit and others), adding 157 KiB and 23 ms of main-thread time.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 367 ms of it running JavaScript. That is comfortably low.
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 5.7 s
5.7 sYour largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Hero banner background”.
Speed Index: 5.3 s
5.3 sVisually, the page fills in at 5.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Time to Interactive: 5.8 s
5.8 sThe page becomes fully interactive after 5.8 s. Good is under 3.8 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 82 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 89 ms
89 msReal visitors wait 89 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 405 ms
405 msReal visitors wait 405 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 41 ms
41 msScripts block the page for only 41 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.3 MB in 193 requests
2.3 MBYour homepage downloads 2.3 MB in 193 requests on a phone: images 1.1 MB (40), other files 841 KiB (99) and scripts 268 KiB (43). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
11 KiB1 image is downloaded at several times the size a phone draws it, for example AA_back1_x520.png at 1,300 px wide, shown at 390 px. Resized copies would save about 11 KiB.
2 images below the first screen load straight away
2 images further down the page (84 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.7 g of CO₂ per visit
0.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.66 g of CO₂e: 78.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Hidden but focusable
38 elements hidden from screen readers can still receive keyboard focus.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (4 elements)
ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (23 elements).
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 9 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (14 characters)
Your title is only 14 characters: “Fangamer Japan”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
One H1 headline
Your <h1> is empty.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
248 internal links, 7 external
The homepage links to 248 pages on fangamer.jp and 7 external pages.
4 checks passed
Meta description: 74 characters
Your meta description is 74 characters: “Tシャツ、ぬいぐるみ、フィギュア、アートブック、ポスター、ピンバッジ、ステッカーなど、様々なゲームソフトのオフィシャルグッズを製作・販売しています。”.
Canonical URL set
The canonical URL is https://www.fangamer.jp/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.fangamer.jp/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (220 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.fangamer.jp/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages are broken
Your homepage links to https://www.fangamer.jp/%E6%96%B0%E5%95%86%E5%93%81&%E3%83%94%E3%83%83%E3%82%AF%E3%82%A2%E3%83%83%E3%83%97/collections/new-and-featured and https://www.fangamer.jp/%E3%82%A2%E3%83%91%E3%83%AC%E3%83%AB/collections/apparel, which answer with an error. Visitors hit a dead end and search engines drop them.
1 page points its canonical at the homepage
https://www.fangamer.jp/products/gift-card declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
1 linked page hidden from search
https://www.fangamer.jp/collections/sale is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
/ and https://www.fangamer.jp/products/gift-card all use the title “Fangamer Japan”. Search engines can't tell which page to show for a search, so each competes with the others.
12 pages share a meta description
https://www.fangamer.jp/collections/new-and-featured, https://www.fangamer.jp/collections/restocked, https://www.fangamer.jp/collections/combos, https://www.fangamer.jp/collections/sale, https://www.fangamer.jp/collections/gifts-under-2000 and https://www.fangamer.jp/products/gift-card and 6 others use the same meta description. A description written for each page earns more clicks.
6 pages with very little text
https://www.fangamer.jp/collections/fangamer, https://www.fangamer.jp/collections/combos, https://www.fangamer.jp/collections/outerwear, https://www.fangamer.jp/collections/custom-collection-1, https://www.fangamer.jp/collections/hats and https://www.fangamer.jp/collections/socks have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 131 found) and read each the way a search engine does.
3 checks passed
Every page has a meta description
All 13 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
33 of 37 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Only about 189 words
The homepage has only about 189 words of visible text; thin pages give Google and first-time buyers little to go on.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
2 checks passed
3 short forms
3 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
5 cookies set on arrival
5Opening the homepage sets 5 cookies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at fangamer.jp, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 2 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Judge Me Reviews · chimpstatic.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on fangamer.jp, including 9 speed issues, 3 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.