Website review, no card needed
prosusshop.jp website review
Visit site (opens in a new tab)Reviewed 6 November 202642 issues · 86 checks
This review found 42 issues worth fixing on prosusshop.jp, 18 of them high impact, across 86 checks. The most urgent: hcaptcha.com adds 2.5 s. 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
74C- #86,708 of 124,112 reviewed websitesbeats 26%
- #54,492 of 69,777 online storesbeats 18%
- #51,194 of 63,466 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.4 s |
| May 23, 2026 | 4.6 s |
| May 30, 2026 | 4.6 s |
| Jun 6, 2026 | 4.6 s |
| Jun 13, 2026 | 4.9 s |
| Jun 20, 2026 | 5.0 s |
| Jun 27, 2026 | 5.2 s |
| Jul 4, 2026 | 5.3 s |
| Jul 11, 2026 | 5.2 s |
| Jul 18, 2026 | 5.0 s |
| Jul 25, 2026 | 4.1 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.6 s |
| Aug 22, 2026 | 3.7 s |
| Aug 29, 2026 | 4.0 s |
| Sep 5, 2026 | 4.1 s |
| Sep 12, 2026 | 4.2 s |
| Sep 19, 2026 | 4.2 s |
| Sep 26, 2026 | 4.2 s |
| Oct 3, 2026 | 4.4 s |
| Oct 10, 2026 | 4.5 s |
| Oct 17, 2026 | 4.7 s |
| Oct 24, 2026 | 4.7 s |
| Oct 31, 2026 | 4.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 216 ms |
| May 23, 2026 | 207 ms |
| May 30, 2026 | 204 ms |
| Jun 6, 2026 | 219 ms |
| Jun 13, 2026 | 219 ms |
| Jun 20, 2026 | 216 ms |
| Jun 27, 2026 | 215 ms |
| Jul 4, 2026 | 215 ms |
| Jul 11, 2026 | 220 ms |
| Jul 18, 2026 | 218 ms |
| Jul 25, 2026 | 204 ms |
| Aug 1, 2026 | 191 ms |
| Aug 8, 2026 | 178 ms |
| Aug 15, 2026 | 175 ms |
| Aug 22, 2026 | 178 ms |
| Aug 29, 2026 | 175 ms |
| Sep 5, 2026 | 176 ms |
| Sep 12, 2026 | 175 ms |
| Sep 19, 2026 | 172 ms |
| Sep 26, 2026 | 171 ms |
| Oct 3, 2026 | 168 ms |
| Oct 10, 2026 | 163 ms |
| Oct 17, 2026 | 163 ms |
| Oct 24, 2026 | 161 ms |
| Oct 31, 2026 | 162 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
Speed
hcaptcha.com adds 2.5 s
2.5 shcaptcha.com costs a phone 2.5 s of main-thread work and 4.4 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
1.1 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 38
38/100Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 9.0 s
A phone's processor spends 9.0 s on main-thread work while loading, 5.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (hcaptcha.com, Google Tag Manager and Google CDN and others), adding 6.4 MB and 3.7 s of main-thread time.
Reduce unused JavaScript
300 ms · 1.8 MBAbout 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Reduce unused CSS
450 ms · 116 KiBAbout 116 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Improve image delivery
450 ms · 66 KiB3 images could be 66 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
Google Tag Manager adds 370 ms
370 msGoogle Tag Manager costs a phone 370 ms of main-thread work and 516 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.
Use efficient cache lifetimes
388 KiB18 files are served with short cache lifetimes, so returning visitors download them again (388 KiB).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 377 ms. During a long task the page ignores taps.
Google CDN adds 295 ms
295 msGoogle CDN costs a phone 295 ms of main-thread work and 736 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 CSS
150 ms · 12 KiB12 KiB could be saved by minifying CSS.
Legacy JavaScript
43 KiBPolyfills for old browsers add 43 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: 12 ms
12 msYour server sent the HTML in 12 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 LCP: 4.9 s
4.9 sReal visitors wait 4.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.5 s
4.5 sReal visitors see the first content after 4.5 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 19.1 s
19.1 sYour largest element takes 19.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 25.9 s
25.9 sVisually, the page fills in at 25.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 64.4 s
64.4 sThe page becomes fully interactive after 64.4 s. Good is under 3.8 s.
Total Blocking Time: 1.7 s
1.7 sScripts block taps and scrolling for 1.7 s in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.4 s to 4.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user INP: 158 ms
158 msReal visitors wait 158 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user TTFB: 323 ms
323 msReal visitors wait 323 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 24% faster for real visitors
-24%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 216 ms to 162 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, good is under 0.1).
Images and page weight
Page weight: 11.8 MB in 378 requests
11.8 MBYour homepage downloads 11.8 MB in 378 requests on a phone: scripts 5.0 MB (96), fonts 2.7 MB (34) and HTML 1.8 MB (11). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
202610_shinki_popup.jpg 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).
4 images in older formats
4 images (169 KiB) 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.
About 3.4 g of CO₂ per visit
3.35 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.35 g of CO₂e: 402.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
39 text elements with low contrast
39 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
19 links without text
19 visible links have no text or label, so screen readers cannot say where they go.
13 form fields without a label
13 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (2 elements)
Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.
1 checks passed
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 10 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “【消防・防災設備のプロサス公式オンラインショップ】THE PROSUS SHOP - ザ・プロサス・ショップ|株式会社プロサス|消防・防災設”.
138 internal links, 1 external
The homepage links to 138 pages on prosusshop.jp and 1 external page.
7 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “【消防設備のプロフェッショナル】株式会社プロサスの公式通販「THE PROSUS SHOP - ザ・プロサスショップ」のWEBサイトです。株式会社プロサスは、創業以来40年以上、消防設備・防災設備の販売、レンタル・点検、消防用設備資材の卸…”.
One H1 headline
Your main headline reads: “THE PROSUS SHOP”.
Canonical URL set
The canonical URL is https://prosusshop.jp/.
Structured data in place
Structured data found: BreadcrumbList, 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://prosusshop.jp/sitemap.xml.
AI search readiness
3 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.
llms.txt published
The site publishes https://prosusshop.jp/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://prosusshop.jp/pages/wishlist and https://prosusshop.jp/collections/all-products have no meta description, so Google writes the search snippet from whatever text it finds.
3 links to non-canonical URLs
Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://prosusshop.jp/blogs/news/%E5%B9%B4%E6%9C%AB%E5%B9%B4%E5%A7%8B%E3%81%AE%E5%96%B6%E6%A5%AD%E3%81%AB%E3%81%A4%E3%81%84%E3%81%A6-1, whose canonical is https://prosusshop.jp/blogs/news/%e5%b9%b4%e6%9c%ab%e5%b9%b4%e5%a7%8b%e3%81%ae%e5%96%b6%e6%a5%ad%e3%81%ab%e3%81%a4%e3%81%84%e3%81%a6-1. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
5 pages without an H1
https://prosusshop.jp/pages/wishlist, https://prosusshop.jp/collections/all, https://prosusshop.jp/collections/all-products, https://prosusshop.jp/collections/2027%E5%B9%B4%E8%A3%BD%E4%BA%88%E7%B4%84 and https://prosusshop.jp/collections/outlet%E3%82%A2%E3%82%A4%E3%83%86%E3%83%A0%E5%93%81-%E5%9C%A8%E5%BA%AB%E3%82%BB%E3%83%BC%E3%83%AB-%E6%9C%80%E5%A4%A750-off have no <h1> headline, so visitors and search engines get no clear main topic.
9 pages with very little text
https://prosusshop.jp/blogs/news/%E5%B9%B4%E6%9C%AB%E5%B9%B4%E5%A7%8B%E3%81%AE%E5%96%B6%E6%A5%AD%E3%81%AB%E3%81%A4%E3%81%84%E3%81%A6-1, https://prosusshop.jp/pages/wishlist, https://prosusshop.jp/collections/all, https://prosusshop.jp/collections/all-products, https://prosusshop.jp/pages/maker and https://prosusshop.jp/blogs/news and 3 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.
7 pages slow to respond
https://prosusshop.jp/collections/all, https://prosusshop.jp/collections/all-products, https://prosusshop.jp/pages/maker, https://prosusshop.jp/blogs/news, https://prosusshop.jp/pages/faq and https://prosusshop.jp/collections/2027%E5%B9%B4%E8%A3%BD%E4%BA%88%E7%B4%84 and 1 other took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 62 found) and read each the way a search engine does.
4 checks passed
Linked pages load
9 pages of 15 loaded without an error (the rest turned automated requests away).
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 9 pages that loaded have a <title>.
Best practices
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“The Protected Audience API is deprecated and will be removed in a future release.”).
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Uncaught ReferenceError: BOOMR is not defined”.
2 checks passed
Tap targets are thumb-sized
28 of 33 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 44 words
The homepage has only about 44 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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “THE PROSUS SHOP”.
2 calls to action
The homepage has 2 calls to action, for example “THE PROSUS SHOP”.
2 short forms
2 short forms (2 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
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 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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
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 prosusshop.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 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Helium Customer Fields · Klaviyo Email Marketing Sms · Comparable Products · Powerful Form Builder · Rebolt Bundle Products · Swish Wishlist King · Bundle Products By Thimatic · amp-cdn.tokyo · mixlogue.jp · kxcdn.com · letters.co.jp · storecrm.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 42 issues on prosusshop.jp, including 19 speed issues, 1 SEO issue 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.