Website review, no card needed
29-kanekichi.com website review
Visit site (opens in a new tab)Reviewed 10 November 202653 issues · 91 checks
This review found 53 issues worth fixing on 29-kanekichi.com, 20 of them high impact, across 91 checks. The most urgent: improve image delivery. 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
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.4 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.3 s |
| Sep 5, 2026 | 1.2 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.2 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.1 s |
| Nov 7, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 89 ms |
| May 30, 2026 | 87 ms |
| Jun 6, 2026 | 85 ms |
| Jun 13, 2026 | 82 ms |
| Jun 20, 2026 | 82 ms |
| Jun 27, 2026 | 80 ms |
| Jul 4, 2026 | 82 ms |
| Jul 25, 2026 | 91 ms |
| Sep 5, 2026 | 92 ms |
| Sep 12, 2026 | 92 ms |
| Sep 19, 2026 | 91 ms |
| Sep 26, 2026 | 92 ms |
| Oct 3, 2026 | 102 ms |
| Oct 10, 2026 | 104 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.7 s
1.4 s
2.2 s
2.9 s
3.6 s
4.3 s
5.0 s
5.8 s
Speed
Improve image delivery
1.1 s · 6.4 MB33 images could be 6.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Use efficient cache lifetimes
1.5 s · 5.3 MB37 files are served with short cache lifetimes, so returning visitors download them again (5.3 MB).
Avoid multiple page redirects
3.0 sThe page goes through 1 redirect before it starts loading, costing about 3.0 s. Link and advertise the final URL directly.
Render-blocking requests
1.2 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Facebook and estore.jp and others), adding 4.8 MB and 752 ms of main-thread time.
Mobile performance score: 50
50/100Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
160 ms · 629 KiBAbout 629 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 160 ms faster on a phone.
YouTube adds 356 ms
356 msYouTube costs a phone 356 ms of main-thread work and 997 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.
shopserve.jp adds 0 ms
0 msshopserve.jp costs a phone 0 ms of main-thread work and 3.3 MB 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.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 131 ms. During a long task the page ignores taps.
Reduce unused CSS
123 KiBAbout 123 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need.
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.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 937 ms of it running JavaScript. That is comfortably low.
Server response: 153 ms
153 msYour server sent the HTML in 153 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 38.2 s
38.2 sThe page becomes fully interactive after 38.2 s. Good is under 3.8 s.
Speed Index: 14.5 s
14.5 sVisually, the page fills in at 14.5 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 8.3 s
8.3 sYour largest element takes 8.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “近江牛 特選和風とろ生ローストビーフ”.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
36 images without width and height
36 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.189
0.189The layout shifts by 0.189 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 89 ms to 104 ms 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: 0.9 s
0.9 sReal visitors wait 0.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 107 ms
107 msReal visitors wait 107 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: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 344 ms
344 msReal visitors wait 344 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 18% faster for real visitors
-18%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 168 ms
168 msScripts block the page for only 168 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 9.2 MB in 149 requests
9.2 MBYour homepage downloads 9.2 MB in 149 requests on a phone: images 7.5 MB (88), scripts 1.5 MB (30) and stylesheets 112 KiB (14). Under 2 MB keeps phones on slow connections fast.
5 images over 500 KB
5 images weigh 3.2 MB together. On a phone connection a single image that size takes seconds.
18 images far larger than shown
2.5 MB18 images are downloaded at several times the size a phone draws them, for example award-winning.jpg at 1,920 px wide, shown at 300 px. Resized copies would save about 2.5 MB.
29 images in older formats
29 images (7.4 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
22 images below the first screen load straight away
22 images further down the page (6.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.6 g of CO₂ per visit
2.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.61 g of CO₂e: 313.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Unlabelled dropdowns
1 dropdown has no label.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
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 (42 elements)
All page content should be contained by landmarks: 42 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.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
Tables do not use <caption> instead of cells with the [colspan] attribute to indicate a caption.
Tables do not use <caption> instead of cells with the [colspan] attribute to indicate a caption. (1 element).
1 checks passed
34 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (10 characters)
Your title is only 10 characters: “近江牛専門店かねきち”. 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.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (176 characters)
Your meta description is 176 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No robots.txt
There is no robots.txt at 29-kanekichi.com/robots.txt, the first file search crawlers ask for.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
One H1 headline
Your <h1> is empty.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
82 internal links, 5 external
The homepage links to 82 pages on 29-kanekichi.com and 5 external pages.
1 checks passed
XML sitemap found
Your XML sitemap is reachable at https://www.29-kanekichi.com/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.
No llms.txt
There is no https://www.29-kanekichi.com/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.
1 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.
Other pages
1 linked page is broken
Your homepage links to https://www.29-kanekichi.com/_ga/FORM/contact.cgi, which answers with an error. Visitors hit a dead end and search engines drop it.
1 page without a title
https://www.29-kanekichi.com/smp/freepage_detail.php has no <title>, so Google invents the link text in results.
6 pages share a title
/, https://www.29-kanekichi.com/hpgen/HPB/shop/shoppinguide.html, https://www.29-kanekichi.com/hpgen/HPB/shop/sitemap.html, https://www.29-kanekichi.com/SHOP/g11464/list.html, https://www.29-kanekichi.com/SHOP/g11469/list.html and https://www.29-kanekichi.com/SHOP/g11471/list.html all use the title “近江牛専門店かねきち”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.29-kanekichi.com/smp/freepage_detail.php has no meta description, so Google writes the search snippet from whatever text it finds.
4 pages share a meta description
https://www.29-kanekichi.com/hpgen/HPB/shop/shoppinguide.html, https://www.29-kanekichi.com/SHOP/rating_list.html, https://www.29-kanekichi.com/hpgen/HPB/shop/sitemap.html and https://www.29-kanekichi.com/hpgen/HPB/entries/34.html use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://www.29-kanekichi.com/smp/freepage_detail.php has no <h1> headline, so visitors and search engines get no clear main topic.
14 pages with very little text
https://www.29-kanekichi.com/SHOP/keyword/ro-stuto250g, https://www.29-kanekichi.com/SHOP/keyword/motunabeset, https://www.29-kanekichi.com/SHOP/keyword/10024091, https://www.29-kanekichi.com/hpgen/HPB/shop/shoppinguide.html, https://www.29-kanekichi.com/SHOP/rating_list.html and https://www.29-kanekichi.com/hpgen/HPB/shop/sitemap.html and 8 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.
2 pages slow to respond
https://www.29-kanekichi.com/SHOP/keyword/10024091 and https://www.29-kanekichi.com/hpgen/HPB/shop/shoppinguide.html took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 56 found) and read each the way a search engine does.
2 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
No mobile viewport
No viewport meta tag, so phones render the desktop layout zoomed out.
3 broken images
3 images failed to load on a phone, for example https://www.29-kanekichi.com/hpgen/smp/img/crown.png.
37 small tap targets
37 of 63 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.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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.
Only about 123 words
The homepage has only about 123 words of visible text; thin pages give Google and first-time buyers little to go on.
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 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
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: a star rating and 3 trust badges.
Analytics in place
Analytics detected: Google Analytics and Meta Pixel.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and Meta Pixel (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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
17 other companies contacted
Loading the homepage contacts 17 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 29-kanekichi.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- NTT DOCOMO BUSINESS,Inc.
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 53 issues on 29-kanekichi.com, including 15 speed issues, 8 SEO issues and 3 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.