Tools & Wizards About Us
lake.jp screenshot

Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

lake.jp

SBI新生銀行カードローン エル【公式】

Page Load Speed

4.9 sec in total

First Response

562 ms

Resources Loaded

4 sec

Page Rendered

314 ms

lake.jp screenshot

About Website

Welcome to lake.jp homepage info - get ready to check Lake best content for Japan right away, or after learning these important things about lake.jp

SBI新生銀行カードローン エルでは、アプリや会員ページからお客さまのニーズにお応えするサービスをご提供しています。| SBI新生銀行カードローン エル公式：増額・追加のご利用やおまとめローンならSBI新生銀行カードローン エル

Visit lake.jp

Key Findings

We analyzed Lake.jp page load time and found that the first response time was 562 ms and then it took 4.3 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

lake.jp performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value9.1 s

13/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.061

97/100

15%

TTI (Time to Interactive)

Value4.3 s

84/100

10%

Network Requests Diagram

lake.jp

562 ms

lake.jp

1352 ms

common2.css

533 ms

top.css

714 ms

reikun_green_100.png

892 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that all of those requests were addressed to Lake.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Lake.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 385.7 kB (49%)

Content Size

784.9 kB

After Optimization

399.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 18.9 kB

  • Original 24.0 kB
  • After minification 20.9 kB
  • After compression 5.1 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 3.1 kB, which is 13% 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 18.9 kB or 79% of the original size.

Image Optimization

-40%

Potential reduce by 225.5 kB

  • Original 568.0 kB
  • After minification 342.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. Obviously, Lake needs image optimization as it can save up to 225.5 kB or 40% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 88.6 kB

  • Original 129.2 kB
  • After minification 121.0 kB
  • After compression 40.6 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 88.6 kB or 69% of the original size.

CSS Optimization

-83%

Potential reduce by 52.7 kB

  • Original 63.7 kB
  • After minification 51.8 kB
  • After compression 11.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. Lake.jp needs all CSS files to be minified and compressed as it can save up to 52.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (10%)

Requests Now

29

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lake.jp

lake.jp

562 ms

lake.jp

lake.jp

1352 ms

common2.css

common2.css

533 ms

top.css

top.css

714 ms

reikun_green_100.png

reikun_green_100.png

892 ms

bnr_main_app_11.png

bnr_main_app_11.png

1675 ms

bnr_main_08.png

bnr_main_08.png

1505 ms

bnr_main_app_03.png

bnr_main_app_03.png

1330 ms

bnr_sf.png

bnr_sf.png

1144 ms

bnr_disaster.png

bnr_disaster.png

965 ms

bnr_bank_product.png

bnr_bank_product.png

1073 ms

jquery2.js

jquery2.js

1559 ms

common.js

common.js

1088 ms

topBanner.js

topBanner.js

1162 ms

js_param.js

js_param.js

1268 ms

bnr_jba_gamble.png

bnr_jba_gamble.png

1345 ms

bnr_caa_go_jp.png

bnr_caa_go_jp.png

1344 ms

bnr_jba_stop.png

bnr_jba_stop.png

1451 ms

bg_header_main.png

bg_header_main.png

971 ms

sprite_main.png

sprite_main.png

1159 ms

bg_contents_main.jpg

bg_contents_main.jpg

983 ms

icn_note_big.png

icn_note_big.png

1084 ms

icn_arw_hd_r.png

icn_arw_hd_r.png

1137 ms

sprite_navi.png

sprite_navi.png

1334 ms

bg_navi_main.png

bg_navi_main.png

1161 ms

sprite_top.png

sprite_top.png

1551 ms

topApp.js

topApp.js

221 ms

topMbr.js

topMbr.js

273 ms

bnr_sf_o.png

bnr_sf_o.png

298 ms

bnr_disaster_o.png

bnr_disaster_o.png

298 ms

bnr_bank_product_o.png

bnr_bank_product_o.png

399 ms

Accessibility Review

lake.jp accessibility score

94

Accessibility Issues

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

lake.jp best practices score

75

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

Browser errors were logged to the console

SEO Factors

lake.jp SEO score

90

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

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lake.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 Lake.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

lake.jp

Open Graph data is detected on the main page of Lake. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: