Tools & Wizards About Us
crefan.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

crefan.jp

クレジットカードおすすめ比較はクレファン

Page Load Speed

18.1 sec in total

First Response

1.6 sec

Resources Loaded

16.2 sec

Page Rendered

321 ms

crefan.jp screenshot

About Website

Click here to check amazing Crefan content for Japan. Otherwise, check out these important facts you probably never knew about crefan.jp

クレジットカードの比較ならクレファン！独自サービスの審査合否情報やカードレビューはもちろん、作り方や使い方に至るまで、数千枚のクレジットカードデータベースの中から年会費・ポイント・マイル・ETC・付帯保険など、さまざまな視点から最適な一枚を探し出せます。

Visit crefan.jp

Key Findings

We analyzed Crefan.jp page load time and found that the first response time was 1.6 sec and then it took 16.6 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

crefan.jp performance score

0

Network Requests Diagram

crefan.jp

1561 ms

jquery-1.8.1.min.js

411 ms

bootstrap.min.css

564 ms

docs.css

378 ms

adsbygoogle.js

18 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 71% of them (48 requests) were addressed to the original Crefan.jp, 7% (5 requests) were made to Pagead2.googlesyndication.com and 7% (5 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (13.9 sec) belongs to the original domain Crefan.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 329.7 kB (46%)

Content Size

710.6 kB

After Optimization

380.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Crefan.jp main page is 710.6 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. 45% of websites need less resources to load. Javascripts take 254.7 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 48.5 kB

  • Original 59.5 kB
  • After minification 51.3 kB
  • After compression 11.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 8.3 kB, which is 14% 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 48.5 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 3.4 kB

  • Original 212.4 kB
  • After minification 209.0 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. Crefan images are well optimized though.

JavaScript Optimization

-49%

Potential reduce by 123.6 kB

  • Original 254.7 kB
  • After minification 254.3 kB
  • After compression 131.1 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 123.6 kB or 49% of the original size.

CSS Optimization

-84%

Potential reduce by 154.2 kB

  • Original 183.9 kB
  • After minification 177.6 kB
  • After compression 29.7 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. Crefan.jp needs all CSS files to be minified and compressed as it can save up to 154.2 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (66%)

Requests Now

67

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

crefan.jp

crefan.jp

1561 ms

jquery-1.8.1.min.js

jquery-1.8.1.min.js

411 ms

bootstrap.min.css

bootstrap.min.css

564 ms

docs.css

docs.css

378 ms

adsbygoogle.js

adsbygoogle.js

18 ms

jquery.gpfloat-1.0.min.js

jquery.gpfloat-1.0.min.js

381 ms

bootstrap.min.js

bootstrap.min.js

402 ms

analytics.js

analytics.js

25 ms

logo.png

logo.png

205 ms

glyphicons-halflings.png

glyphicons-halflings.png

190 ms

glyphicons-halflings-white.png

glyphicons-halflings-white.png

190 ms

cf_icon_02.png

cf_icon_02.png

199 ms

00004104.jpg

00004104.jpg

205 ms

00004097.jpg

00004097.jpg

367 ms

00001142.jpg

00001142.jpg

377 ms

00003872.jpg

00003872.jpg

375 ms

00001145.jpg

00001145.jpg

381 ms

00004108.jpg

00004108.jpg

400 ms

00002540.jpg

00002540.jpg

403 ms

00003107.jpg

00003107.jpg

13018 ms

00003491.jpg

00003491.jpg

13018 ms

00001199.jpg

00001199.jpg

13018 ms

00002912.jpg

00002912.jpg

13018 ms

00000499.jpg

00000499.jpg

13018 ms

00003728.jpg

00003728.jpg

13016 ms

00000115.jpg

00000115.jpg

13378 ms

00003906.jpg

00003906.jpg

13380 ms

00001144.jpg

00001144.jpg

13393 ms

00002535.jpg

00002535.jpg

13405 ms

00001621.jpg

00001621.jpg

13390 ms

00004096.jpg

00004096.jpg

13368 ms

00004056.jpg

00004056.jpg

13546 ms

00001146.jpg

00001146.jpg

13560 ms

00000001.jpg

00000001.jpg

13562 ms

00000078.jpg

00000078.jpg

13578 ms

00004051.jpg

00004051.jpg

13580 ms

00002408.jpg

00002408.jpg

13598 ms

00003827.jpg

00003827.jpg

13723 ms

00001788.jpg

00001788.jpg

13742 ms

00002533.jpg

00002533.jpg

13744 ms

T_160226021003.png

T_160226021003.png

13765 ms

T_160226021002.jpg

T_160226021002.jpg

13768 ms

T_160129081930.jpeg

T_160129081930.jpeg

13792 ms

T_160127112026.gif

T_160127112026.gif

13885 ms

collect

collect

12 ms

ca-pub-8337871571936781.js

ca-pub-8337871571936781.js

118 ms

zrt_lookup.html

zrt_lookup.html

114 ms

show_ads_impl.js

show_ads_impl.js

78 ms

ads

ads

12845 ms

osd.js

osd.js

22 ms

ads

ads

250 ms

ads

ads

275 ms

T_151222110651.jpg

T_151222110651.jpg

13739 ms

42148_1503101730.jpg

42148_1503101730.jpg

13732 ms

no_image.jpg

no_image.jpg

13755 ms

11456_1101180929.jpg

11456_1101180929.jpg

13757 ms

47038_1512130938.jpg

47038_1512130938.jpg

13788 ms

cf_icon_01.png

cf_icon_01.png

13714 ms

4323639052555661292

4323639052555661292

12603 ms

abg.js

abg.js

12605 ms

m_js_controller.js

m_js_controller.js

12615 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

12648 ms

css

css

73 ms

x_button_blue2.png

x_button_blue2.png

76 ms

s

s

20 ms

cardloan_card_ad.jpg_1421730888715_cardloan_card_ad.jpg

cardloan_card_ad.jpg_1421730888715_cardloan_card_ad.jpg

30 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

9 ms

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

12 ms

SEO Factors

crefan.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Crefan.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 Crefan.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

crefan.jp

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