Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

partner.eloan.co.jp

【イー・ローン】ローンの検索・比較・申込み

Page Load Speed

13.4 sec in total

First Response

1.5 sec

Resources Loaded

11.6 sec

Page Rendered

273 ms

partner.eloan.co.jp screenshot

About Website

Visit partner.eloan.co.jp now to see the best up-to-date Partner Eloan content for Japan and also check out these interesting facts you probably never knew about partner.eloan.co.jp

ローン・融資をお求めの方へ。利用実績343万人、銀行系から専業系まで109社、1,232種類のローンの金利や融資の条件を比較。豊富なローンシミュレーションも。

Visit partner.eloan.co.jp

Key Findings

We analyzed Partner.eloan.co.jp page load time and found that the first response time was 1.5 sec and then it took 11.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

partner.eloan.co.jp performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value11.9 s

0/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value1,790 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.034

100/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

www.eloan.co.jp

1450 ms

import.css

1076 ms

color_green.css

372 ms

index.css

556 ms

grandMenu.css

560 ms

Our browser made a total of 212 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Partner.eloan.co.jp, 16% (33 requests) were made to Google.com and 12% (25 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Eloan.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 361.1 kB (31%)

Content Size

1.2 MB

After Optimization

811.7 kB

In fact, the total size of Partner.eloan.co.jp main page is 1.2 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. 35% of websites need less resources to load. Images take 788.9 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 58.4 kB

  • Original 73.2 kB
  • After minification 68.0 kB
  • After compression 14.8 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 58.4 kB or 80% of the original size.

Image Optimization

-9%

Potential reduce by 72.4 kB

  • Original 788.9 kB
  • After minification 716.5 kB

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. Partner Eloan images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 94.3 kB

  • Original 156.2 kB
  • After minification 139.5 kB
  • After compression 62.0 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 94.3 kB or 60% of the original size.

CSS Optimization

-88%

Potential reduce by 136.0 kB

  • Original 154.4 kB
  • After minification 104.7 kB
  • After compression 18.4 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. Partner.eloan.co.jp needs all CSS files to be minified and compressed as it can save up to 136.0 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 123 (67%)

Requests Now

183

After Optimization

60

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

Accessibility Review

partner.eloan.co.jp accessibility score

64

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Form elements do not have associated labels

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

partner.eloan.co.jp best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

partner.eloan.co.jp SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Partner.eloan.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Partner.eloan.co.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

Open Graph description is not detected on the main page of Partner Eloan. 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: