Website review, no card needed

freee.co.jp logo

freee.co.jp website review

Visit site (opens in a new tab)Reviewed 28 October 202646 issues · 85 checks

This review found 46 issues worth fixing on freee.co.jp, 20 of them high impact, across 85 checks. The most urgent: google Tag Manager adds 4.2 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.7 s1.4 sMay 9Oct 241.5 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.5 s
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Oct 24, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
353 ms248 msMay 9Oct 24341 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026261 ms
May 16, 2026260 ms
May 23, 2026261 ms
May 30, 2026265 ms
Jun 6, 2026275 ms
Jun 13, 2026287 ms
Jun 20, 2026300 ms
Jun 27, 2026308 ms
Jul 4, 2026309 ms
Jul 11, 2026308 ms
Jul 18, 2026305 ms
Jul 25, 2026304 ms
Aug 1, 2026302 ms
Aug 8, 2026301 ms
Aug 15, 2026301 ms
Aug 22, 2026307 ms
Aug 29, 2026312 ms
Sep 5, 2026320 ms
Sep 12, 2026325 ms
Sep 19, 2026327 ms
Sep 26, 2026327 ms
Oct 3, 2026329 ms
Oct 10, 2026329 ms
Oct 17, 2026333 ms
Oct 24, 2026341 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

Full-page screenshot of freee.co.jp (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. freee.co.jp at 0.4 s0.4 s
  2. freee.co.jp at 0.8 s0.8 s
  3. freee.co.jp at 1.1 s1.1 s
  4. freee.co.jp at 1.5 s1.5 s
  5. freee.co.jp at 1.9 s1.9 s
  6. freee.co.jp at 2.3 s2.3 s
  7. freee.co.jp at 2.6 s2.6 s
  8. freee.co.jp at 3.0 s3.0 s

Speed

14 to fix28
  • Google Tag Manager adds 4.2 s

    4.2 s

    Google Tag Manager costs a phone 4.2 s of main-thread work and 2.3 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.

  • Reduce unused JavaScript

    1.4 s · 1.5 MB

    About 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Reduce unused CSS

    1.5 s · 273 KiB

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

  • Render-blocking requests

    1.4 s

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

  • Main-thread work: 10.5 s

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

  • Mobile performance score: 28

    28/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 3.6 MB and 5.6 s of main-thread time.

  • Improve image delivery

    1.9 MB

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

  • 20 long tasks on the main thread

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

  • Use efficient cache lifetimes

    579 KiB

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

  • Facebook adds 504 ms

    504 ms

    Facebook costs a phone 504 ms of main-thread work and 361 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.

  • Legacy JavaScript

    400 ms · 80 KiB

    Polyfills for old browsers add 80 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.

  • TikTok adds 314 ms

    314 ms

    TikTok costs a phone 314 ms of main-thread work and 288 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.

  • Flipdesk adds 146 ms

    146 ms

    Flipdesk costs a phone 146 ms of main-thread work and 546 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.

  • 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: 71 ms

    71 ms

    Your server sent the HTML in 71 ms, well inside Google's 600 ms guideline.

Core Web Vitals

8 to fix67
  • 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.

  • Largest Contentful Paint: 36.5 s

    36.5 s

    Your largest element takes 36.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “個人・副業者向け 気合やがんばりは要らない まかせていい確定申告 いますぐ無料ではじめる あっぱれ アプリ累計ダウンロ…”.

  • Total Blocking Time: 5.3 s

    5.3 s

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

  • Time to Interactive: 63.6 s

    63.6 s

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

  • Speed Index: 9.0 s

    9.0 s

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

  • First Contentful Paint: 4.5 s

    4.5 s

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

  • Real-user INP: 238 ms

    238 ms

    Real visitors wait 238 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Tap response (INP) got 29% slower for real visitors

    +29%

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

5 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.3 s

    1.3 s

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

  • Real-user TTFB: 395 ms

    395 ms

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

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

5 to fix14
  • Page weight: 12.1 MB in 312 requests

    12.1 MB

    Your homepage downloads 12.1 MB in 312 requests on a phone: fonts 5.3 MB (3), scripts 4.2 MB (95) and images 2.2 MB (90). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    kv_img_individual_202610_sp.png weighs 1.9 MB. On a phone connection a single image that size takes seconds.

  • 1 image far larger than shown

    966 KiB

    1 image is downloaded at several times the size a phone draws it, for example kv_img_individual_202610_sp.png at 1,528 px wide, shown at 358 px. Resized copies would save about 966 KiB.

  • 1 image in older formats

    1 image (1.9 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

    kv_img_individual_202610_sp.png 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 3.4 g of CO₂ per visit

    3.43 g

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

Accessibility

1 to fixGoogle 10099
  • Page should contain a level-one heading (1 element)

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

2 checks passed
  • Every image has alt text

    All 117 images in the HTML carry an alt attribute.

  • 42 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: 42 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10083
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (15 characters)

    Your title is only 15 characters: “クラウド会計ソフト|freee”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 137 internal links, 42 external

    The homepage links to 137 pages on freee.co.jp and 42 external pages.

6 checks passed
  • Meta description: 104 characters

    Your meta description is 104 characters: “freeeはすべてのスモールビジネスを支える統合型経営プラットフォームです。従来バラバラに存在していた業務やデータをフロントオフィスからバックオフィスまで一気通貫させ、誰もが自由に経営を行えること目指します。”.

  • Canonical URL set

    The canonical URL is https://www.freee.co.jp/.

  • Structured data in place

    Structured data found: Organization.

  • 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.freee.co.jp/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://www.freee.co.jp/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.

  • Organization data: 6 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.

Other pages

4 to fix68
  • 2 pages without a title

    https://www.freee.co.jp/accounting/individual and https://www.freee.co.jp/opening have no <title>, so Google invents the link text in results.

  • 2 linked pages hidden from search

    https://www.freee.co.jp/resources/01 and https://www.freee.co.jp/hr/resources/top are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

  • 2 pages without a meta description

    https://www.freee.co.jp/accounting/individual and https://www.freee.co.jp/opening have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://www.freee.co.jp/accounting/individual and https://www.freee.co.jp/opening have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.freee.co.jp/products has 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.

  • 2 pages slow to respond

    https://www.freee.co.jp/hr/resources/top and https://www.freee.co.jp/consolidated-accounting took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

3 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Titles are unique

    Every page we checked has its own title.

Best practices

4 to fixGoogle 5474
  • 10 broken images

    10 images failed to load on a phone, for example https://pixelfnt-us.dsp-api.moloco.com/v1/cm/init?source=MOLOCO_PIXEL.

  • 6 third-party cookies

    6 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 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.”).

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SOCKET_NOT_CONNECTED”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

    11 of 11 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

7 to fix44
  • 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.

  • 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 phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • Thin social proof

    Social proof on the homepage: 4 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 21 words

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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.

1 checks passed
  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

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

  • 28 cookies set on arrival

    28

    Opening the homepage sets 28 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.

  • 67 other companies contacted

    Loading the homepage contacts 67 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 freee.co.jp, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Tag Manager
Hosting
Akamai

Company

Founded
2012
Headquarters
Tokyo

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on freee.co.jp, including 22 speed issues, 2 SEO issues and 7 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25