Website review, no card needed
kameda-netshop.jp website review
Visit site (opens in a new tab)Reviewed 9 November 202653 issues · 96 checks
This review found 53 issues worth fixing on kameda-netshop.jp, 19 of them high impact, across 96 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
54F- #123,288 of 124,112 reviewed websitesbeats 0%
- #69,695 of 69,786 online storesbeats 0%
- #63,415 of 63,472 Shopify storesbeats 0%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 2.0 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 2.0 s |
| Nov 7, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 204 ms |
| May 30, 2026 | 208 ms |
| Jun 6, 2026 | 214 ms |
| Jun 13, 2026 | 216 ms |
| Jun 20, 2026 | 219 ms |
| Jun 27, 2026 | 216 ms |
| Jul 4, 2026 | 214 ms |
| Jul 11, 2026 | 218 ms |
| Jul 18, 2026 | 213 ms |
| Jul 25, 2026 | 211 ms |
| Aug 1, 2026 | 205 ms |
| Aug 8, 2026 | 198 ms |
| Aug 15, 2026 | 199 ms |
| Aug 22, 2026 | 199 ms |
| Aug 29, 2026 | 200 ms |
| Sep 5, 2026 | 203 ms |
| Sep 12, 2026 | 203 ms |
| Sep 19, 2026 | 208 ms |
| Sep 26, 2026 | 217 ms |
| Oct 3, 2026 | 221 ms |
| Oct 10, 2026 | 234 ms |
| Oct 17, 2026 | 244 ms |
| Oct 24, 2026 | 244 ms |
| Oct 31, 2026 | 234 ms |
| Nov 7, 2026 | 213 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
1.1 s
2.1 s
3.2 s
4.2 s
5.3 s
6.3 s
7.4 s
8.4 s
Speed
Reduce unused JavaScript
2.1 s · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Render-blocking requests
2.9 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.9 s.
Mobile performance score: 22
22/100Your mobile performance score is 22. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
2.2 MB24 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, preordernowapp.com and Facebook and others), adding 1.9 MB and 1.6 s of main-thread time.
Use efficient cache lifetimes
150 ms · 591 KiB39 files are served with short cache lifetimes, so returning visitors download them again (591 KiB).
Google Tag Manager adds 586 ms
586 msGoogle Tag Manager costs a phone 586 ms of main-thread work and 683 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.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
preordernowapp.com adds 362 ms
362 mspreordernowapp.com costs a phone 362 ms of main-thread work and 71 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.
Minify JavaScript
300 ms · 66 KiB66 KiB could be saved by minifying JavaScript.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 311 ms. During a long task the page ignores taps.
2,985 HTML elements
The page has 2,985 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Facebook adds 238 ms
238 msFacebook costs a phone 238 ms of main-thread work and 311 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 99 ms
99 msShopify costs a phone 99 ms of main-thread work and 554 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.
Reduce unused CSS
150 ms · 75 KiBAbout 75 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
31 KiBPolyfills for old browsers add 31 KiB JavaScript that modern phones do not need.
Minify CSS
22 KiB22 KiB could be saved by minifying CSS.
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: 23 ms
23 msYour server sent the HTML in 23 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 CLS: 1.03
1.03For real visitors the layout shifts by 1.03 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 24.2 s
24.2 sYour largest element takes 24.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Previous Next 1 2 3 4 5 6 7 8 9 セール new 【数量限定】亀田のありがとうセット(1…”.
Time to Interactive: 37.9 s
37.9 sThe page becomes fully interactive after 37.9 s. Good is under 3.8 s.
Cumulative Layout Shift: 1.279
1.279The layout shifts by 1.279 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 11.2 s
11.2 sVisually, the page fills in at 11.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
Real-user INP: 322 ms
322 msReal visitors wait 322 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 506 ms
506 msScripts block taps and scrolling for 506 ms in total while the page loads. Good is under 200 ms.
41 images without width and height
41 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 204 ms to 213 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.1 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 427 ms
427 msReal visitors wait 427 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 9.9 MB in 294 requests
9.9 MBYour homepage downloads 9.9 MB in 294 requests on a phone: images 6.9 MB (86), scripts 2.3 MB (115) and fonts 268 KiB (10). Under 2 MB keeps phones on slow connections fast.
About 2.8 g of CO₂ per visit
2.81 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.81 g of CO₂e: 337.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
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
22 images without alt text
22 images have no alt text, which hurts accessibility and image search.
Unlabelled dropdowns
8 dropdowns have no label.
Invalid ARIA attributes
3 elements use ARIA attributes their role does not allow, which confuses screen readers.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children. (3 elements).
[aria-*] attributes do not have valid values
[aria-*] attributes do not have valid values (2 elements).
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Hidden but focusable
18 elements hidden from screen readers can still receive keyboard focus.
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA input fields do not have accessible names
ARIA input fields do not have accessible names (4 elements).
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
ARIA toggle fields do not have accessible names
ARIA toggle fields do not have accessible names (2 elements).
Definition list items are not wrapped in <dl> elements
Definition list items are not wrapped in <dl> elements (1 element).
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Headings skip levels
Headings skip levels (h1 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
Elements with role="none" or role="presentation" have conflicts
Elements with role="none" or role="presentation" have conflicts (3 elements).
1 checks passed
13 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 14 WCAG 2.2 A/AA and best-practice rules on the phone render: 13 passed and 1 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 (27 characters)
Your title is only 27 characters: “【公式】亀田のあられ・おせんべいなら亀田製菓通販いちば”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“亀田製菓の公式通販店 亀田のあられ・おせんべい、人気のサラダホープも購入可能!” and “亀田製菓の公式通販店 亀田のあられ・おせんべい、人気のサラダホープも購入可能!”). One clear main headline is easier for people and search engines.
Structured data has 3 problems
Structured data found (Organization and WebSite) but with 3 problems, for example “Organization: sameAs is not an absolute URL ("#")”.
18 links crawlers can't follow
18 links have no real href, so search engines can't follow them.
238 internal links, 7 external
The homepage links to 238 pages on kameda-netshop.jp and 7 external pages.
5 checks passed
Meta description: 143 characters
Your meta description is 143 characters: “亀田製菓の公式通販ショップ。「亀田の柿の種」、新潟限定で人気の「サラダホープ」、期間限定の商品や、ここでしか買えない詰め合わせセットまで、多数ご用意しております。人気の尾西食品の長期保存食品(非常食)も販売中!5,400円以上で送料無料、…”.
Canonical URL set
The canonical URL is https://www.kameda-netshop.jp/.
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://www.kameda-netshop.jp/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
2 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.
llms.txt published
The site publishes https://www.kameda-netshop.jp/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a meta description
https://www.kameda-netshop.jp/collections/soft and https://www.kameda-netshop.jp/collections/hard use the same meta description. A description written for each page earns more clicks.
8 pages with very little text
https://www.kameda-netshop.jp/collections/outlet, https://www.kameda-netshop.jp/collections/happy-turn-box, https://www.kameda-netshop.jp/collections/onishi-foods, https://www.kameda-netshop.jp/collections/assorted, https://www.kameda-netshop.jp/collections/hard and https://www.kameda-netshop.jp/collections/hailstone and 2 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 92 found) and read each the way a search engine does.
7 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 meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
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
No mobile viewport
No viewport meta tag, so phones render the desktop layout zoomed out.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 low-resolution images
2 images are served at too low a resolution for sharp phone screens.
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: 8 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 14 words
The homepage has only about 14 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
36 short forms
36 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo 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.
21 cookies set on arrival
21Opening the homepage sets 21 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.
43 other companies contacted
Loading the homepage contacts 43 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 kameda-netshop.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 15 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Blockify Fraud Filter · App Unity Tracking Ga4 · Minmaxify Order Limits · Helium Customer Fields · Powerful Form Builder · Region Restrictions · Shopify App Delivery Date · Promolayer · Subscription Test · firebaseapp.com · hulkapps.com · klaviyo.com · powr.io · cloudfront.net · Hulk Product Options
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
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Shopify
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 kameda-netshop.jp, including 24 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.