nexgengolf.jp website review

Your mobile performance score is 75. Pages that score under 90 lose visitors before the first paint.

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

4 images could be 100 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

About 33 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

About 27 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.

4 third-party services load with your homepage (Clarity, Shopify and shop.app and others), adding 240 KiB and 128 ms of main-thread time.

4 long tasks block the main thread while loading, the longest for 66 ms. During a long task the page ignores taps.

3 files are served with short cache lifetimes, so returning visitors download them again (14 KiB).

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Your largest element takes 25.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

The page becomes fully interactive after 26.9 s. Good is under 3.8 s.

1 image have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 115 ms to 125 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.8 MB in 146 requests on a phone: fonts 4.0 MB (2), images 798 KiB (15) and other files 749 KiB (87). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example bnr_service_ballprint.png at 1,000 px wide, shown at 254 px. Resized copies would save about 31 KiB.

1 image further down the page (74 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 1.65 g of CO₂e: 197.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 tap target is too small or too close together to hit reliably with a finger.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

58 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 visible links have no text or label, so screen readers cannot say where they go.

Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is only 19 characters: “ネクスジェン ゴルフ ―NEXGEN―”. Between 30 and 65 characters leaves room to say what you do and for whom.

The homepage links to 54 pages on nexgengolf.jp and 5 external pages.

https://www.nexgengolf.jp/collections/club, https://www.nexgengolf.jp/collections/shaft, https://www.nexgengolf.jp/collections/accessory, https://www.nexgengolf.jp/blogs/news, https://www.nexgengolf.jp/pages/event and https://www.nexgengolf.jp/collections/service-menu and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.nexgengolf.jp/pages/event has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.nexgengolf.jp/collections/club, https://www.nexgengolf.jp/collections/shaft, https://www.nexgengolf.jp/collections/accessory, https://www.nexgengolf.jp/blogs/news, https://www.nexgengolf.jp/pages/event and https://www.nexgengolf.jp/collections/service-menu and 7 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.

https://www.nexgengolf.jp/collections/shaft, https://www.nexgengolf.jp/blogs/news, https://www.nexgengolf.jp/pages/concept, https://www.nexgengolf.jp/blogs/news/261009, https://www.nexgengolf.jp/blogs/news/260930 and https://www.nexgengolf.jp/blogs/news/260914 and 1 other took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 23 found) and read each the way a search engine does.

6 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 65 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.

Opening the homepage sets 14 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.