kenzai-navi.com website review

96 files are served with short cache lifetimes, so returning visitors download them again (6.7 MB).

21 files block the first paint until they finish downloading. Deferring or inlining them could save about 8.8 s.

About 543 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.9 s faster on a phone.

Your mobile performance score is 42 (desktop: 51). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

34 images could be 3.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

8 third-party services load with your homepage (Google Tag Manager, Adobe TypeKit and Google Maps and others), adding 4.5 MB and 1.0 s of main-thread time.

114 KiB could be saved by minifying CSS.

Adobe TypeKit costs a phone 237 ms of main-thread work and 3.5 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.

Google Tag Manager costs a phone 454 ms of main-thread work and 517 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.

A phone's processor spends 3.0 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

The page has 2,388 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

186 KiB could be saved by minifying JavaScript.

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

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

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.

The first text or image appears after 12.3 s on a phone. Good is under 1.8 s.

Your largest element takes 13.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “お客様ごとに最適なご遺体の安置環境を提案「おくりこ」 NEW”.

Visually, the page fills in at 17.9 s (Speed Index). Good is under 3.4 s.

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

Real visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.

Scripts block taps and scrolling for 495 ms in total while the page loads. Good is under 200 ms.

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

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

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

Your homepage downloads 12.3 MB in 167 requests on a phone: images 4.6 MB (60), other files 3.4 MB (16) and scripts 2.6 MB (35). Under 2 MB keeps phones on slow connections fast.

ホームページトップ広告用.jpg weighs 1.1 MB. On a phone connection a single image that size takes seconds.

6 images are downloaded at several times the size a phone draws them, for example 2054_18722_1792379067.jpg at 680 px wide, shown at 60 px. Resized copies would save about 709 KiB.

30 images (4.2 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.

18 images further down the page (1.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

1 button has no accessible name, so screen readers announce just “button”.

Some lists contain elements other than list items, which screen readers announce wrongly.

Some list items are not inside a list.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

14 images have no alt text, which hurts accessibility and image search.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

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

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

Your title is only 23 characters: “【建材ナビ】建築材料・建築資材専門の検索サイト”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No XML sitemap at https://www.kenzai-navi.com/sitemap.xml, so Google discovers your pages only by following links.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 685 pages on kenzai-navi.com and 23 external pages.

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.

There is no https://www.kenzai-navi.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.

https://www.kenzai-navi.com/info/mailmag.php is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

/ and https://www.kenzai-navi.com/categories all use the title “【建材ナビ】建築材料・建築資材専門の検索サイト”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.kenzai-navi.com/favorites, https://www.kenzai-navi.com/request and https://www.kenzai-navi.com/categories use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.kenzai-navi.com/info/topinfo/qa.php, whose canonical is https://www.kenzai-navi.com/info/topinfo/qa.html. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://www.kenzai-navi.com/guide2, https://www.kenzai-navi.com/favorites, https://www.kenzai-navi.com/request, https://www.kenzai-navi.com/info/topinfo/whatis.php, https://www.kenzai-navi.com/info/topinfo/howto.php and https://www.kenzai-navi.com/info/topinfo/qa.php 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.

https://www.kenzai-navi.com/guide2, https://www.kenzai-navi.com/favorites, https://www.kenzai-navi.com/request and https://www.kenzai-navi.com/info/mailmag.php took over 3 s to send their HTML from our server.

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

No viewport meta tag, so phones render the desktop layout zoomed out.

4 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://www.kenzai-navi.com/js/waslidemenu/css/waslidemenu.css?1793169044' because its MIM…”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Large scripts ship without source maps.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

The homepage has only about 22 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 11 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 24 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.