Website review, no card needed
acemagic.jp website review
Visit site (opens in a new tab)Reviewed 27 October 202638 issues · 87 checks
This review found 38 issues worth fixing on acemagic.jp, 23 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. 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
75C- #79,478 of 121,091 reviewed websitesbeats 30%
- #50,688 of 68,525 online storesbeats 22%
- #47,893 of 62,445 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.0 s |
| May 23, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 222 ms |
| May 16, 2026 | 220 ms |
| May 23, 2026 | 220 ms |
| May 30, 2026 | 220 ms |
| Jun 6, 2026 | 223 ms |
| Jun 13, 2026 | 222 ms |
| Jun 20, 2026 | 220 ms |
| Jun 27, 2026 | 222 ms |
| Jul 4, 2026 | 226 ms |
| Jul 11, 2026 | 230 ms |
| Jul 18, 2026 | 230 ms |
| Jul 25, 2026 | 227 ms |
| Aug 1, 2026 | 218 ms |
| Aug 8, 2026 | 210 ms |
| Aug 15, 2026 | 218 ms |
| Aug 22, 2026 | 217 ms |
| Aug 29, 2026 | 211 ms |
| Sep 5, 2026 | 207 ms |
| Sep 12, 2026 | 203 ms |
| Sep 19, 2026 | 199 ms |
| Sep 26, 2026 | 201 ms |
| Oct 3, 2026 | 198 ms |
| Oct 10, 2026 | 193 ms |
| Oct 17, 2026 | 196 ms |
| Oct 24, 2026 | 198 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
Reduce unused JavaScript
18.0 s · 3.3 MBAbout 3.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 18.0 s faster on a phone.
Reduce unused CSS
2.4 s · 209 KiBAbout 209 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.4 s faster on a phone.
YouTube adds 1.9 s
1.9 sYouTube costs a phone 1.9 s of main-thread work and 5.7 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
1.9 s21 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Mobile performance score: 48
48/100Your mobile performance score is 48 (desktop: 40). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.8 s
A phone's processor spends 9.8 s on main-thread work while loading, 5.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,352 HTML elements
The page has 3,352 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Tag Manager and Clarity and others), adding 6.9 MB and 2.4 s of main-thread time.
Shopify adds 90 ms
90 msShopify costs a phone 90 ms of main-thread work and 326 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 146 ms. During a long task the page ignores taps.
Improve image delivery
44 KiB4 images could be 44 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
28 KiBPolyfills for old browsers add 28 KiB JavaScript that modern phones do not need.
Use efficient cache lifetimes
25 KiB12 files are served with short cache lifetimes, so returning visitors download them again (25 KiB).
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.
1 checks passed
Server response: 13 ms
13 msYour server sent the HTML in 13 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.
First Contentful Paint: 26.9 s
26.9 sThe first text or image appears after 26.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 36.1 s
36.1 sYour largest element takes 36.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 26.9 s
26.9 sVisually, the page fills in at 26.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 53.4 s
53.4 sThe page becomes fully interactive after 53.4 s. Good is under 3.8 s.
Real-user INP: 207 ms
207 msReal visitors wait 207 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 331 ms
331 msScripts block taps and scrolling for 331 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 506 ms
506 msReal visitors wait 506 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 222 ms to 198 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 9.6 MB in 360 requests
9.6 MBYour homepage downloads 9.6 MB in 360 requests on a phone: scripts 6.3 MB (136), images 988 KiB (47) and other files 808 KiB (96). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (70 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 2.7 g of CO₂ per visit
2.71 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.71 g of CO₂e: 325.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Invalid ARIA attributes
2 elements use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (2 elements)
Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.
8 text elements with low contrast
8 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (6 elements)
Interactive controls must not be nested: 6 elements on the page fail this check, rated serious by axe-core.
ARIA input fields must have an accessible name (2 elements)
ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
Scrollable region must have keyboard access (2 elements)
Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (18 elements)
All page content should be contained by landmarks: 18 elements on the page fail this check, rated moderate by axe-core.
12 form fields without a label
12 form fields have no label, so screen readers announce an empty box and autofill guesses.
Elements marked as presentational should be consistently ignored (2 elements)
Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3, h2 → 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. (3 elements).
1 checks passed
54 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 63 WCAG 2.2 A/AA and best-practice rules on the phone render: 54 passed and 9 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
One H1 headline
Your <h1> is empty.
225 internal links, 13 external
The homepage links to 225 pages on acemagic.jp and 13 external pages.
7 checks passed
Meta description: 105 characters
Your meta description is 105 characters: “コスパの高い製品からプロ仕様のミニPCやノートパソコンを通販する公式サイトです。ACEMAGICの最新情報や特別セール、サポート情報をご提供します。国内配送・送料無料・2年保証など、パソコンの購入が簡単で安心!”.
Title: 42 characters
Your title is a healthy 42 characters: “ACEMAGICミニPCとノートパソコンの通販公式サイト – ACEMAGIC JP”.
Canonical URL set
The canonical URL is https://acemagic.jp/.
Structured data in place
Structured data found: Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://acemagic.jp/sitemap.xml.
AI search readiness
4 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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,173 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://acemagic.jp/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://acemagic.jp/products/m1-minipc has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://acemagic.jp/collections/mini-pc and https://acemagic.jp/collections/laptops have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 50 found) and read each the way a search engine does.
5 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.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
15 small tap targets
15 of 53 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
A 15-field form
Your longest form asks for 15 fields (0 required). Every extra field lowers completion.
Only about 177 words
The homepage has only about 177 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.
3 checks passed
Social proof on the page
Social proof on the homepage: 9 testimonial or review blocks, 1 customer or partner logo and 1 trust badge.
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.
20 cookies set on arrival
20Opening the homepage sets 20 cookies, 1 of them by other companies (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.
31 other companies contacted
Loading the homepage contacts 31 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 acemagic.jp, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2024.
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Analytics | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on acemagic.jp, including 16 speed issues, 1 SEO issue 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.