Tools & Wizards About Us
maneo.jp screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

maneo.jp

ソーシャルレンディング | maneo（マネオ） | あなたの投資が中小企業をサポート!!

Page Load Speed

5.2 sec in total

First Response

344 ms

Resources Loaded

4.5 sec

Page Rendered

349 ms

maneo.jp screenshot

About Website

Visit maneo.jp now to see the best up-to-date Maneo content for Japan and also check out these interesting facts you probably never knew about maneo.jp

あなたの投資が、中小企業をサポート(法人向けに不動産,飲食店などの事業資金を融資させていただいております)。maneoはソーシャルレンディングのパイオニアとして、お金を媒介とした密度の高いコミュニケーションインフラの創出を目指します。

Visit maneo.jp

Key Findings

We analyzed Maneo.jp page load time and found that the first response time was 344 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

maneo.jp performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value1,320 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0.277

44/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

maneo.jp

344 ms

maneo.jp

675 ms

www.maneo.jp

907 ms

gtm.js

61 ms

format.css

295 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 56% of them (50 requests) were addressed to the original Maneo.jp, 12% (11 requests) were made to Platform.twitter.com and 10% (9 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Maneo.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 122.6 kB (9%)

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Maneo.jp main page is 1.4 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 52.4 kB

  • Original 64.3 kB
  • After minification 54.3 kB
  • After compression 11.9 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 10.1 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 52.4 kB or 81% of the original size.

Image Optimization

-4%

Potential reduce by 42.0 kB

  • Original 1.1 MB
  • After minification 1.0 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Maneo images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 7.2 kB

  • Original 159.5 kB
  • After minification 158.6 kB
  • After compression 152.3 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-26%

Potential reduce by 21.0 kB

  • Original 82.2 kB
  • After minification 81.6 kB
  • After compression 61.1 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Maneo.jp needs all CSS files to be minified and compressed as it can save up to 21.0 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (49%)

Requests Now

86

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Maneo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

maneo.jp

maneo.jp

344 ms

maneo.jp

maneo.jp

675 ms

www.maneo.jp

www.maneo.jp

907 ms

gtm.js

gtm.js

61 ms

format.css

format.css

295 ms

common.css

common.css

341 ms

style.css

style.css

683 ms

append.css

append.css

674 ms

fund.css

fund.css

511 ms

jquery.js

jquery.js

692 ms

migrate.js

migrate.js

516 ms

common.js

common.js

516 ms

init.js

init.js

680 ms

common.css

common.css

690 ms

all.js

all.js

30 ms

slider-pro.min.css

slider-pro.min.css

702 ms

jquery.sliderPro.min.js

jquery.sliderPro.min.js

843 ms

home.js

home.js

850 ms

jquery.yycountdown.js

jquery.yycountdown.js

852 ms

ajaxfundlist.js

ajaxfundlist.js

853 ms

chat.js

chat.js

1009 ms

adsbygoogle.js

adsbygoogle.js

117 ms

js

js

49 ms

jquery.scrollTo-min.js

jquery.scrollTo-min.js

42 ms

jquery.localscroll-min.js

jquery.localscroll-min.js

34 ms

all.js

all.js

5 ms

30 ms

header_ico_sheet.png

header_ico_sheet.png

413 ms

logo_maneo5.png

logo_maneo5.png

170 ms

header_ico_sheet.png

header_ico_sheet.png

385 ms

img_mainvisual2.jpg

img_mainvisual2.jpg

676 ms

ico_oshirase1.png

ico_oshirase1.png

177 ms

btn_all.gif

btn_all.gif

171 ms

main_visual.jpg

main_visual.jpg

516 ms

main_visual.jpg

main_visual.jpg

390 ms

main_visual.jpg

main_visual.jpg

389 ms

main_visual.jpg

main_visual.jpg

487 ms

main_visual.jpg

main_visual.jpg

522 ms

main_visual.jpg

main_visual.jpg

564 ms

main_visual.jpg

main_visual.jpg

564 ms

main_visual.jpg

main_visual.jpg

664 ms

main_visual.jpg

main_visual.jpg

691 ms

main_visual.jpg

main_visual.jpg

695 ms

main_visual.jpg

main_visual.jpg

739 ms

main_visual.jpg

main_visual.jpg

738 ms

main_visual.jpg

main_visual.jpg

837 ms

main_visual.jpg

main_visual.jpg

848 ms

main_visual.jpg

main_visual.jpg

864 ms

bnr_gi.png

bnr_gi.png

1028 ms

bnr_cl.png

bnr_cl.png

903 ms

bnr_gaia.png

bnr_gaia.png

1070 ms

btn_navi.png

btn_navi.png

1006 ms

ico_oshirase0.png

ico_oshirase0.png

1016 ms

img_market.png

img_market.png

1031 ms

btn_all.gif

btn_all.gif

1071 ms

btn_spread.png

btn_spread.png

1510 ms

widgets.js

widgets.js

109 ms

likebox.php

likebox.php

87 ms

bk_footerBack.jpg

bk_footerBack.jpg

1097 ms

bk_footer.jpg

bk_footer.jpg

1116 ms

btn_toTop.png

btn_toTop.png

1117 ms

gtm.js

gtm.js

34 ms

analytics.js

analytics.js

14 ms

collect

collect

13 ms

collect

collect

30 ms

js

js

55 ms

MyrfBA0EM9-.css

MyrfBA0EM9-.css

18 ms

SHojUHmeyWm.js

SHojUHmeyWm.js

69 ms

teTZ2tZqwkq.js

teTZ2tZqwkq.js

66 ms

D0hW5UcG2V4.js

D0hW5UcG2V4.js

68 ms

qnn7MVQZYOT.js

qnn7MVQZYOT.js

114 ms

7CmGfGBVS6H.js

7CmGfGBVS6H.js

113 ms

OWkNLphO4cA.js

OWkNLphO4cA.js

119 ms

p55HfXW__mM.js

p55HfXW__mM.js

118 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

173 ms

360082454_752899390175300_5794488850628638375_n.jpg

360082454_752899390175300_5794488850628638375_n.jpg

110 ms

359815461_752899393508633_3789140449852573400_n.jpg

359815461_752899393508633_3789140449852573400_n.jpg

135 ms

VuRstRCPjmu.png

VuRstRCPjmu.png

39 ms

settings

settings

76 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

29 ms

sociallendingJP

sociallendingJP

76 ms

polyfills-3b821eda8863adcc4a4b.js

polyfills-3b821eda8863adcc4a4b.js

26 ms

runtime-a697c5a1ae32bd7e4d42.js

runtime-a697c5a1ae32bd7e4d42.js

50 ms

modules.20f98d7498a59035a762.js

modules.20f98d7498a59035a762.js

79 ms

main-fd9ef5eb169057cda26d.js

main-fd9ef5eb169057cda26d.js

80 ms

_app-88bf420a57d49e33be53.js

_app-88bf420a57d49e33be53.js

82 ms

%5BscreenName%5D-c33f0b02841cffc3e9b4.js

%5BscreenName%5D-c33f0b02841cffc3e9b4.js

82 ms

_buildManifest.js

_buildManifest.js

84 ms

_ssgManifest.js

_ssgManifest.js

88 ms

chat.css

chat.css

12 ms

Accessibility Review

maneo.jp accessibility score

67

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

maneo.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

maneo.jp SEO score

97

Search Engine Optimization Advices

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Maneo.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Maneo.jp main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

maneo.jp

Open Graph description is not detected on the main page of Maneo. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: