Website review, no card needed
icmjapan.net website review
Visit site (opens in a new tab)Reviewed 26 October 202642 issues · 80 checks
This review found 42 issues worth fixing on icmjapan.net, 14 of them high impact, across 80 checks. The most urgent: avoid multiple page redirects. 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
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 7.6 s |
| May 16, 2026 | 7.7 s |
| May 23, 2026 | 7.7 s |
| May 30, 2026 | 7.9 s |
| Jun 6, 2026 | 8.0 s |
| Jun 13, 2026 | 8.0 s |
| Jun 20, 2026 | 8.0 s |
| Jun 27, 2026 | 8.1 s |
| Jul 4, 2026 | 7.7 s |
| Jul 11, 2026 | 7.8 s |
| Jul 18, 2026 | 7.4 s |
| Jul 25, 2026 | 6.2 s |
| Aug 1, 2026 | 6.3 s |
| Aug 8, 2026 | 5.9 s |
| Aug 15, 2026 | 5.5 s |
| Aug 22, 2026 | 5.4 s |
| Aug 29, 2026 | 4.8 s |
| Sep 5, 2026 | 4.7 s |
| Sep 12, 2026 | 4.6 s |
| Sep 19, 2026 | 4.7 s |
| Sep 26, 2026 | 4.9 s |
| Oct 3, 2026 | 4.9 s |
| Oct 10, 2026 | 4.8 s |
| Oct 17, 2026 | 4.6 s |
| Oct 24, 2026 | 4.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 173 ms |
| May 16, 2026 | 175 ms |
| May 23, 2026 | 179 ms |
| May 30, 2026 | 200 ms |
| Jun 6, 2026 | 200 ms |
| Jun 13, 2026 | 200 ms |
| Jun 20, 2026 | 218 ms |
| Jun 27, 2026 | 205 ms |
| Jul 4, 2026 | 204 ms |
| Jul 11, 2026 | 204 ms |
| Jul 18, 2026 | 203 ms |
| Jul 25, 2026 | 220 ms |
| Aug 1, 2026 | 215 ms |
| Aug 8, 2026 | 219 ms |
| Aug 15, 2026 | 205 ms |
| Aug 22, 2026 | 172 ms |
| Aug 29, 2026 | 178 ms |
| Sep 5, 2026 | 179 ms |
| Sep 12, 2026 | 180 ms |
| Sep 19, 2026 | 180 ms |
| Sep 26, 2026 | 177 ms |
| Oct 3, 2026 | 175 ms |
| Oct 10, 2026 | 169 ms |
| Oct 17, 2026 | 171 ms |
| Oct 24, 2026 | 176 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
Speed
Avoid multiple page redirects
5.0 sThe page goes through 1 redirect before it starts loading, costing about 5.0 s. Link and advertise the final URL directly.
Reduce unused JavaScript
2.5 s · 486 KiBAbout 486 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.5 s faster on a phone.
Mobile performance score: 65
65/100Your mobile performance score is 65 (desktop: 99). Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
269 KiB65 files are served with short cache lifetimes, so returning visitors download them again (269 KiB).
Render-blocking requests
200 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 200 ms.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 89 ms. During a long task the page ignores taps.
Phones get a much slower page than desktops
Desktop scores 99 but mobile only 65. A gap that wide usually means heavy scripts and images that hit phones hardest.
Improve image delivery
8 KiB1 image could be 8 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
2 third-party services on the page
2 third-party services load with your homepage (JSDelivr CDN and Other Google APIs/SDKs), adding 63 KiB and 0 ms of main-thread time.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 586 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user TTFB: 2.0 s
2.0 sReal visitors wait 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 9.2 s
9.2 sYour largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s.
First Contentful Paint: 4.1 s
4.1 sThe first text or image appears after 4.1 s on a phone. Good is under 1.8 s.
Time to Interactive: 10.1 s
10.1 sThe page becomes fully interactive after 10.1 s. Good is under 3.8 s.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.7 s
2.7 sReal visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.
45 images without width and height
45 images have no width and height attributes, so the layout jumps as each one loads.
Speed Index: 4.1 s
4.1 sVisually, the page fills in at 4.1 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 173 ms to 176 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 164 ms
164 msReal visitors wait 164 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.
Largest content (LCP) got 39% faster for real visitors
-39%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 7.6 s to 4.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.028
0.028The layout barely moves while loading (CLS 0.028, good is under 0.1).
Total Blocking Time: 37 ms
37 msScripts block the page for only 37 ms while loading. Good is under 200 ms.
Images and page weight
About 0.5 g of CO₂ per visit
0.46 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.46 g of CO₂e: 55.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.6 MB in 230 requests
1.6 MBYour homepage downloads 1.6 MB in 230 requests on a phone: scripts 1.0 MB (60), images 384 KiB (110) and stylesheets 141 KiB (34). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Unlabelled dropdowns
5 dropdowns have no label.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
14 images without alt text
14 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (26 elements)
All page content should be contained by landmarks: 26 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
9 form fields without a label
9 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
1 checks passed
32 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (14 characters)
Your title is only 14 characters: “TOP - ICMJAPAN”. 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.
28 links crawlers can't follow
28 links have no real href, so search engines can't follow them.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://icmjapan.net/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at icmjapan.net/robots.txt, the first file search crawlers ask for.
134 internal links, 17 external
The homepage links to 134 pages on icmjapan.net and 17 external pages.
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.
No llms.txt
There is no https://icmjapan.net/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (572 words), so crawlers that don't run JavaScript still read it.
Other pages
10 linked pages hidden from search
https://icmjapan.net/carDetails/bwvua8v5fbwvv5fbwv5gn, https://icmjapan.net/carDetails/bwvua8v5fbwvv5fbwvbwv, https://icmjapan.net/carDetails/bwvua8v5fbwvv5fbwviq7, https://icmjapan.net/carDetails/bwvua8v5fbwvv5fiq79s8, https://icmjapan.net/carDetails/bwvua8v5fbwvv5fiq7ua8 and https://icmjapan.net/carDetails/bwvua8v5fbwvv5fiq7v5f and 4 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
12 pages share 2 titles
/ and https://icmjapan.net/destination all use the title “TOP - ICMJAPAN”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without a meta description
https://icmjapan.net/destination, https://icmjapan.net/aboutUs, https://icmjapan.net/stocks, https://icmjapan.net/parts, https://icmjapan.net/terms and https://icmjapan.net/carDetails/bwvua8v5fbwvv5fbwv5gn and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
15 pages without an H1
https://icmjapan.net/destination, https://icmjapan.net/aboutUs, https://icmjapan.net/stocks, https://icmjapan.net/parts, https://icmjapan.net/terms and https://icmjapan.net/carDetails/bwvua8v5fbwvv5fbwv5gn and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://icmjapan.net/stocks took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 19 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
17 small tap targets
17 of 77 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.
9 low-resolution images
9 images are served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
1 checks passed
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
About 387 words of copy
The homepage carries about 387 words of visible text.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
6 cookies set on arrival
6Opening the homepage sets 6 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.
5 other companies contacted
Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 icmjapan.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Nuxt
- Hosting
- Google Cloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on icmjapan.net, including 13 speed issues, 9 SEO issues and 4 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.