Website review, no card needed
grandties.jp website review
Visit site (opens in a new tab)Reviewed 10 November 202628 issues · 71 checks
This review found 28 issues worth fixing on grandties.jp, 6 of them high impact, across 71 checks. The most urgent: 28 text elements with low contrast. 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
81B- #36,940 of 108,858 reviewed websitesbeats 60%
- #24,671 of 61,765 online storesbeats 54%
- #23,816 of 56,365 Shopify storesbeats 51%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.1 s |
| May 30, 2026 | 1.1 s |
| Jun 20, 2026 | 1.0 s |
| Jun 27, 2026 | 968 ms |
| Jul 4, 2026 | 923 ms |
| Jul 11, 2026 | 906 ms |
| Aug 29, 2026 | 1.0 s |
| Oct 17, 2026 | 1.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 77 ms |
| Jul 4, 2026 | 74 ms |
| Jul 11, 2026 | 73 ms |
| Oct 17, 2026 | 83 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
Mobile performance score: 83
83/100Your mobile performance score is 83. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
957 KiB25 images could be 957 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Render-blocking requests
500 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
3 third-party services on the page
3 third-party services load with your homepage (Shopify, zegsuapps.com and shop.app), adding 1.2 MB and 91 ms of main-thread time.
1,822 HTML elements
The page has 1,822 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
zegsuapps.com adds 31 ms
31 mszegsuapps.com costs a phone 31 ms of main-thread work and 874 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.
Shopify adds 60 ms
60 msShopify costs a phone 60 ms of main-thread work and 329 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.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 102 ms. During a long task the page ignores taps.
Reduce unused JavaScript
21 KiBAbout 21 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
11 KiB5 files are served with short cache lifetimes, so returning visitors download them again (11 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.
2 checks passed
Main-thread work: 1.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 384 ms of it running JavaScript. That is comfortably low.
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 4.4 s
4.4 sYour largest element takes 4.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 8.1 s
8.1 sThe page becomes fully interactive after 8.1 s. Good is under 3.8 s.
Speed Index: 3.6 s
3.6 sVisually, the page fills in at 3.6 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 77 ms to 83 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
3 checks passed
Cumulative Layout Shift: 0.057
0.057The layout barely moves while loading (CLS 0.057, good is under 0.1).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 26 ms
26 msScripts block the page for only 26 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.0 MB in 239 requests
3.0 MBYour homepage downloads 3.0 MB in 239 requests on a phone: images 1.3 MB (53), other files 752 KiB (84) and fonts 440 KiB (3). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
GrandTies_JP_website_soft_cooler_image.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 0.9 g of CO₂ per visit
0.86 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.86 g of CO₂e: 102.9 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
28 text elements with low contrast
28 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 35 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 2 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.
Title is short (15 characters)
Your title is only 15 characters: “GRANDTIES JAPAN”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
One H1 headline
Your <h1> is empty.
85 internal links, 2 external
The homepage links to 85 pages on grandties.jp and 2 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://grandties.jp/.
Structured data in place
Structured data found: Organization and WebSite.
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://grandties.jp/sitemap.xml.
AI search readiness
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.
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.
llms.txt published
The site publishes https://grandties.jp/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
14 pages without a meta description
https://grandties.jp/collections/%E3%83%9E%E3%82%B0%E3%82%AB%E3%83%83%E3%83%97, https://grandties.jp/collections/%E3%83%86%E3%82%A4%E3%82%AF%E3%82%A2%E3%82%A6%E3%83%88-%E3%82%BF%E3%83%B3%E3%83%96%E3%83%A9%E3%83%BC, https://grandties.jp/collections/%E3%83%AF%E3%82%A4%E3%83%89%E3%83%9E%E3%82%A6%E3%82%B9%E3%83%9C%E3%83%88%E3%83%AB, https://grandties.jp/collections/%E3%83%88%E3%83%A9%E3%83%99%E3%83%A9%E3%83%BC%E3%83%9C%E3%83%88%E3%83%AB, https://grandties.jp/collections/%E3%83%88%E3%83%A9%E3%82%A4%E3%82%BF%E3%83%B3-%E3%82%B9%E3%83%9D%E3%83%BC%E3%83%84%E3%83%9C%E3%83%88%E3%83%AB and https://grandties.jp/collections/%E3%83%9A%E3%83%83%E3%83%88%E3%83%9C%E3%83%88%E3%83%AB and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
13 links to non-canonical URLs
Your homepage links to 13 pages by a URL that isn't their canonical one, for example https://grandties.jp/collections/%E3%83%9E%E3%82%B0%E3%82%AB%E3%83%83%E3%83%97, whose canonical is https://grandties.jp/collections/%e3%83%9e%e3%82%b0%e3%82%ab%e3%83%83%e3%83%97. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
14 pages without an H1
https://grandties.jp/collections/%E3%83%9E%E3%82%B0%E3%82%AB%E3%83%83%E3%83%97, https://grandties.jp/collections/%E3%83%86%E3%82%A4%E3%82%AF%E3%82%A2%E3%82%A6%E3%83%88-%E3%82%BF%E3%83%B3%E3%83%96%E3%83%A9%E3%83%BC, https://grandties.jp/collections/%E3%83%AF%E3%82%A4%E3%83%89%E3%83%9E%E3%82%A6%E3%82%B9%E3%83%9C%E3%83%88%E3%83%AB, https://grandties.jp/collections/%E3%83%88%E3%83%A9%E3%83%99%E3%83%A9%E3%83%BC%E3%83%9C%E3%83%88%E3%83%AB, https://grandties.jp/collections/%E3%83%88%E3%83%A9%E3%82%A4%E3%82%BF%E3%83%B3-%E3%82%B9%E3%83%9D%E3%83%BC%E3%83%84%E3%83%9C%E3%83%88%E3%83%AB and https://grandties.jp/collections/%E3%83%9A%E3%83%83%E3%83%88%E3%83%9C%E3%83%88%E3%83%AB and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
11 pages with very little text
https://grandties.jp/collections/%E3%83%86%E3%82%A4%E3%82%AF%E3%82%A2%E3%82%A6%E3%83%88-%E3%82%BF%E3%83%B3%E3%83%96%E3%83%A9%E3%83%BC, https://grandties.jp/collections/%E3%83%88%E3%83%A9%E3%83%99%E3%83%A9%E3%83%BC%E3%83%9C%E3%83%88%E3%83%AB, https://grandties.jp/collections/%E3%83%88%E3%83%A9%E3%82%A4%E3%82%BF%E3%83%B3-%E3%82%B9%E3%83%9D%E3%83%BC%E3%83%84%E3%83%9C%E3%83%88%E3%83%AB, https://grandties.jp/collections/%E3%83%9A%E3%83%83%E3%83%88%E3%83%9C%E3%83%88%E3%83%AB, https://grandties.jp/collections/%E3%83%9A%E3%83%83%E3%83%88%E3%83%9C%E3%82%A6%E3%83%AB and https://grandties.jp/collections/%E3%83%9A%E3%83%83%E3%83%88%E3%83%99%E3%83%83%E3%83%89 and 5 others 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.
4 pages slow to respond
https://grandties.jp/collections/%E3%83%AF%E3%82%A4%E3%83%89%E3%83%9E%E3%82%A6%E3%82%B9%E3%83%9C%E3%83%88%E3%83%AB, https://grandties.jp/collections/%E3%83%88%E3%83%A9%E3%82%A4%E3%82%BF%E3%83%B3-%E3%82%B9%E3%83%9D%E3%83%BC%E3%83%84%E3%83%9C%E3%83%88%E3%83%AB, https://grandties.jp/collections/%E3%83%9A%E3%83%83%E3%83%88%E3%83%9C%E3%83%88%E3%83%AB and https://grandties.jp/collections/%E3%83%9A%E3%83%83%E3%83%88%E3%83%99%E3%83%83%E3%83%89 took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 43 found) and read each the way a search engine does.
4 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
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 14 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
44 of 48 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 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.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 65 words
The homepage has only about 65 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
1 call to action
The homepage has 1 call to action, for example “Contact”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Amazon Ads 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.
8 other companies contacted
Loading the homepage contacts 8 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 grandties.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 1 app. It is code from another company running for your shoppers.
Apps your storefront loads
Pagefly Ai Page Builder
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 28 issues on grandties.jp, including 11 speed issues, 4 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.