Website review, no card needed
finekagu.com website review
Visit site (opens in a new tab)Reviewed 6 November 202638 issues · 83 checks
This review found 38 issues worth fixing on finekagu.com, 13 of them high impact, across 83 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
78C- #60,878 of 120,953 reviewed websitesbeats 44%
- #39,911 of 68,456 online storesbeats 36%
- #38,145 of 62,380 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.5 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.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 123 ms |
| May 23, 2026 | 122 ms |
| May 30, 2026 | 121 ms |
| Jun 6, 2026 | 122 ms |
| Jun 13, 2026 | 122 ms |
| Jun 20, 2026 | 122 ms |
| Jun 27, 2026 | 124 ms |
| Jul 4, 2026 | 124 ms |
| Jul 11, 2026 | 126 ms |
| Jul 18, 2026 | 126 ms |
| Jul 25, 2026 | 127 ms |
| Aug 1, 2026 | 128 ms |
| Aug 8, 2026 | 125 ms |
| Aug 15, 2026 | 125 ms |
| Aug 22, 2026 | 122 ms |
| Aug 29, 2026 | 122 ms |
| Sep 5, 2026 | 123 ms |
| Sep 12, 2026 | 124 ms |
| Sep 19, 2026 | 126 ms |
| Sep 26, 2026 | 128 ms |
| Oct 3, 2026 | 132 ms |
| Oct 10, 2026 | 133 ms |
| Oct 17, 2026 | 136 ms |
| Oct 24, 2026 | 134 ms |
| Oct 31, 2026 | 133 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.5 s
2.2 s
3.0 s
3.7 s
4.4 s
5.2 s
5.9 s
Speed
Reduce unused JavaScript
8.0 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 8.0 s faster on a phone.
Render-blocking requests
5.6 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.6 s.
Improve image delivery
600 ms · 1.2 MB7 images could be 1.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google CDN, Google Tag Manager and Shopify and others), adding 4.5 MB and 985 ms of main-thread time.
Use efficient cache lifetimes
900 ms · 132 KiB12 files are served with short cache lifetimes, so returning visitors download them again (132 KiB).
Mobile performance score: 50
50/100Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.
Google CDN adds 457 ms
457 msGoogle CDN costs a phone 457 ms of main-thread work and 1.1 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.
Reduce unused CSS
300 ms · 140 KiBAbout 140 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Shopify adds 127 ms
127 msShopify costs a phone 127 ms of main-thread work and 1.9 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.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 199 ms
199 msGoogle Tag Manager costs a phone 199 ms of main-thread work and 308 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.
Google Fonts adds 6 ms
6 msGoogle Fonts costs a phone 6 ms of main-thread work and 780 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
150 ms · 35 KiB35 KiB could be saved by minifying JavaScript.
Minify CSS
150 ms · 16 KiB16 KiB could be saved by minifying CSS.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 118 ms. During a long task the page ignores taps.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 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.
1 checks passed
Server response: 6 ms
6 msYour server sent the HTML in 6 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 12.7 s
12.7 sThe first text or image appears after 12.7 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 35.3 s
35.3 sYour largest element takes 35.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “BLACK FRIDAY 対象商品最大40%OFF、その他の商品10%OFF。11月30日23:59まで”.
Time to Interactive: 35.7 s
35.7 sThe page becomes fully interactive after 35.7 s. Good is under 3.8 s.
Speed Index: 13.4 s
13.4 sVisually, the page fills in at 13.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 264 ms
264 msScripts block taps and scrolling for 264 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 123 ms to 133 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 133 ms
133 msReal visitors wait 133 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: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 474 ms
474 msReal visitors wait 474 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 7.5 MB in 255 requests
7.5 MBYour homepage downloads 7.5 MB in 255 requests on a phone: scripts 2.1 MB (65), images 2.0 MB (20) and fonts 1.9 MB (31). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 3.8 MB together. On a phone connection a single image that size takes seconds.
7 images far larger than shown
2.3 MB7 images are downloaded at several times the size a phone draws them, for example bf2026_top_sp_20261106.gif at 1,500 px wide, shown at 390 px. Resized copies would save about 2.3 MB.
1 image in older formats
1 image (3.3 MB) is 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.
An image on the first screen is lazy-loaded
bf2026_top_sp_20261106.gif 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 2.1 g of CO₂ per visit
2.11 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.11 g of CO₂e: 253.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 46 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (77 characters)
Your title is 77 characters, so Google will cut it off around 60: “【公式】FINE KAGUオンラインストア|家具 照明器具 ライト ソファー テレビボード ダイニングテーブル 椅子 チェア – FINE KAGU 公式”.
2 H1 headlines
There are 2 <h1> headlines (“” and “暮らしに、心地よい余白を。”). One clear main headline is easier for people and search engines.
122 internal links, 3 external
The homepage links to 122 pages on finekagu.com and 3 external pages.
6 checks passed
Meta description: 118 characters
Your meta description is 118 characters: “ソファー、デスク、テーブル、椅子をはじめ、LEDシーリングライト、フロアーライト、シーリングファンライト、ペンダントライトなどの照明器具、間接照明、天井照明を多数取り揃えています。VENTOTAのソファ、ペット用フェンスなども送料無料!”.
Canonical URL set
The canonical URL is https://www.finekagu.com/.
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://www.finekagu.com/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 (204 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.finekagu.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
12 pages without a meta description
https://www.finekagu.com/pages/blackfriday2026, https://www.finekagu.com/collections/%E6%96%B0%E5%95%86%E5%93%81%E5%AE%B6%E5%85%B7, https://www.finekagu.com/collections/%E6%96%B0%E5%95%86%E5%93%81%E7%85%A7%E6%98%8E, https://www.finekagu.com/collections/sofa, https://www.finekagu.com/collections/tv-board and https://www.finekagu.com/collections/dining-1 and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
5 links to non-canonical URLs
Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://www.finekagu.com/collections/%E6%96%B0%E5%95%86%E5%93%81%E5%AE%B6%E5%85%B7, whose canonical is https://www.finekagu.com/collections/%e6%96%b0%e5%95%86%e5%93%81%e5%ae%b6%e5%85%b7. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
4 pages without an H1
https://www.finekagu.com/pages/blackfriday2026, https://www.finekagu.com/collections/ranking, https://www.finekagu.com/collections/light and https://www.finekagu.com/pages/coupon have no <h1> headline, so visitors and search engines get no clear main topic.
7 pages with very little text
https://www.finekagu.com/pages/blackfriday2026, https://www.finekagu.com/collections/ranking, https://www.finekagu.com/collections/light, https://www.finekagu.com/collections/bed, https://www.finekagu.com/collections/%E3%82%AC%E3%83%BC%E3%83%87%E3%83%B3%E3%83%95%E3%82%A1%E3%83%8B%E3%83%81%E3%83%A3%E3%83%BC-1 and https://www.finekagu.com/collections/%E5%B7%A5%E5%85%B7/%E9%9B%BB%E5%8B%95%E3%83%89%E3%83%A9%E3%82%A4%E3%83%90%E3%83%BC and 1 other 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 64 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
3 third-party cookies
3 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: net::ERR_CERT_AUTHORITY_INVALID”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
25 of 28 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 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.
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 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 175 words
The homepage has only about 175 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
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag 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.
18 cookies set on arrival
18Opening the homepage sets 18 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.
37 other companies contacted
Loading the homepage contacts 37 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 finekagu.com, 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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pagefly Ai Page Builder · Simprosys Google Shopping Feed · Delivery Pickup Edp · Rivyo Product Review · privy.com
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
- 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 38 issues on finekagu.com, including 17 speed issues, 2 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.