Website review, no card needed
furucrm.com website review
Visit site (opens in a new tab)Reviewed 8 November 202631 issues · 76 checks
This review found 31 issues worth fixing on furucrm.com, 8 of them high impact, across 76 checks. The most urgent: page weight: 13.8 MB in 61 requests. 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
87BClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
1.0 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Use efficient cache lifetimes
3.7 MB9 files are served with short cache lifetimes, so returning visitors download them again (3.7 MB).
Improve image delivery
2.2 MB1 image could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
6 third-party services on the page
6 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and web.app and others), adding 5.7 MB and 902 ms of main-thread time.
Mobile performance score: 88
88/100Your mobile performance score is 88. Pages that score under 90 lose visitors before the first paint.
Google CDN adds 799 ms
799 msGoogle CDN costs a phone 799 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 JavaScript
577 KiBAbout 577 KiB of JavaScript is downloaded but never used on this page.
Amazon Web Services adds 0 ms
0 msAmazon Web Services costs a phone 0 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.
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Fonts adds 7 ms
7 msGoogle Fonts costs a phone 7 ms of main-thread work and 831 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.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 222 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
44 KiBAbout 44 KiB of CSS is downloaded but never applied on this page.
Minify CSS
7 KiB7 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: 138 ms
138 msYour server sent the HTML in 138 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 24.3 s
24.3 sThe page becomes fully interactive after 24.3 s. Good is under 3.8 s.
Total Blocking Time: 354 ms
354 msScripts block taps and scrolling for 354 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
Speed Index: 3.7 s
3.7 sVisually, the page fills in at 3.7 s (Speed Index). Good is under 3.4 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Largest Contentful Paint: 1.9 s
1.9 sYour largest element renders in 1.9 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “— A MANIFESTO furuCRMは、CRM特化の業務知見と、Salesforce・AWS・Azure・Her…”.
Cumulative Layout Shift: 0.027
0.027The layout barely moves while loading (CLS 0.027, good is under 0.1).
Images and page weight
Page weight: 13.8 MB in 61 requests
13.8 MBYour homepage downloads 13.8 MB in 61 requests on a phone: images 11.3 MB (14), scripts 1.1 MB (10) and fonts 771 KiB (26). Under 2 MB keeps phones on slow connections fast.
7 images over 500 KB
7 images weigh 10.5 MB together. On a phone connection a single image that size takes seconds.
4 images far larger than shown
2.5 MB4 images are downloaded at several times the size a phone draws them, for example Tokyo2.jpg at 1,331 px wide, shown at 358 px. Resized copies would save about 2.5 MB.
12 images in older formats
12 images (11.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.
11 images below the first screen load straight away
11 images further down the page (9.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.9 g of CO₂ per visit
3.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.90 g of CO₂e: 468.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
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.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 14 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (69 characters)
Your meta description is only 69 characters: “furuCRM株式会社 — Salesforce・AI・マルチクラウドで業務を解き直す。日本・韓国・ベトナム3拠点から DX を届けます。”. 70 to 160 characters is enough to sell the click.
25 internal links, 14 external
The homepage links to 25 pages on furucrm.com and 14 external pages.
6 checks passed
One H1 headline
Your main headline reads: “業務処理を、 AIで、解き直す。”.
Title: 31 characters
Your title is a healthy 31 characters: “furuCRM — Data・CRM・AIでビジネスを加速する”.
Canonical URL set
The canonical URL is https://www.furucrm.com/.
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.furucrm.com/sitemap.xml/.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://www.furucrm.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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (563 words), so crawlers that don't run JavaScript still read it.
Other pages
8 pages without an H1
https://www.furucrm.com/salesforce, https://www.furucrm.com/agentforce, https://www.furucrm.com/mulesoft, https://www.furucrm.com/devopscenterplus, https://www.furucrm.com/salescloud and https://www.furucrm.com/servicecloud and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://www.furucrm.com/mulesoft, https://www.furucrm.com/blog/ai-agent-action-skill-design and https://www.furucrm.com/line4sfs 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 23 found) and read each the way a search engine does.
6 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 14 pages that loaded have a meta description.
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 14 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 (“Unload event listeners are deprecated and will be removed.”).
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_FAILED”.
1 checks passed
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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.
About 550 words of copy
The homepage carries about 550 words of visible text.
4 checks passed
2 calls to action
The homepage has 2 calls to action, for example “[email protected]” and “Contact”.
1 short form
A short form (6 fields at most) is right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 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.
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 furucrm.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on furucrm.com, including 14 speed issues, 2 SEO issues and 4 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.