Analyze

fundex.co.jp: 各種ローンは「ローン百選」へ - セゾンファンデックス【公式サイト】

各種ローンのご相談なら≪セゾン≫カードでおなじみのクレディセゾングループ【セゾンファンデックス】。様々な商品が取り揃ったセゾンの「ローン百選」の中からあなたに合ったローンをお選びください。

Page load speed analysis

  • 50/100

    Normal result
  • 7

    Successful tests
  • 1

    Failed test
  • First response

    1.1 sec

  • Resources loaded

    10.6 sec

  • Page rendered

    202 ms

  • Total page load time

    11.9 sec

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

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

Page optimization

  • HTML 88.8 kB
    Images 435.9 kB
    Javascripts 147.0 kB
    CSS 13.4 kB

    In fact, the total size of Fundex.co.jp main page is 685.2 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 435.9 kB which makes up the majority of the site volume.

    • Original 88.8 kB
    • After minification 77.5 kB
    • After compression 20.3 kB

    HTML optimization

    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 11.3 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 68.6 kB or 77% of the original size.

    • Original 435.9 kB
    • After optimization 338.3 kB

    Image optimization

    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, Fundex needs image optimization as it can save up to 97.6 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

    • Original 147.0 kB
    • After minification 138.3 kB
    • After compression 46.3 kB

    JavaScript optimization

    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 100.7 kB or 68% of the original size.

    • Original 13.4 kB
    • After minification 9.5 kB
    • After compression 3.1 kB

    CSS optimization

    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. Fundex.co.jp needs all CSS files to be minified and compressed as it can save up to 10.3 kB or 77% of the original size.

Network requests diagram

  • index.html
  • import.css
  • top.css
  • topMainVisual.css
  • openWindow.js
  • clickable.js
  • faq.js
  • topmainVisual.js
  • AC_RunActiveContent.js
  • reset.css
  • clearfix.css
  • base.css
  • header.css
  • footer.css
  • side.css
  • ojs
  • ga.js
  • imgFaqClose.gif
  • body.png
  • header1.png
  • logo.png
  • saisonfundex.png
  • company.png
  • inquiry.png
  • sitemap.png
  • network.png
  • saisoncardInternational.png
  • header5.png
  • header2.png
  • header3.png
  • imgMainTitle.png
  • individual_.png
  • business.png
  • estate.png
  • divMainVisual.png
  • thIndiviVip.png
  • thSupport.png
  • thIndiviEstate.png
  • tdIndiviVip1.png
  • tdSupport1.png
  • tdIndiviEstate1.png
  • tdIndiviVipBack1.png
  • tdIndiviVip4.png
  • vipSummary2030.png
  • tdIndiviVip2.png
  • vipSummaryRegular.png
  • tdIndiviVip3.png
  • tdSupportBack1.png
  • tdSupport2.png
  • summaryPremeditated.png
  • tdSupport3.png
  • summarySupportFree.png
  • tdIndiviEstateBack1.png
  • __utm.gif
  • entry.js
  • tdIndiviEstate4.png
  • summaryFree.png
  • summaryReform.png
  • summaryInvestment.png
  • summaryPurchase.png
  • tdIndiviEstate2.png
  • actag
  • ojs2
  • tdIndiviVipBack2.png
  • applyIndiviVip.png
  • tdSupportBack2.png
  • applySupport.png
  • tdIndiviEstateBack2.png
  • applyIndiviEstate.png
  • tag.js
  • lb
  • sync0
  • conversion.js
  • s_retargeting.js
  • thBusinessVip.png
  • thBusinessEstate.png
  • tdBusinessVip1.png
  • tdBusinessEstate1.png
  • tdBusinessVip2.png
  • tdBusinessEstate2.png
  • CREATIVE_IMGn.js
  • summaryBusinessVip.png
  • applyBusinessVip.png
  • summaryBusinessEstate.png
  • applyBusinessEstate.png
  • thHousingProject.png
  • tdHousingProject1.png
  • housingLeft.png
  • summaryHousing1.png
  • scheck
  • summaryHousing2.png
  • summaryHousing.png
  • inquiryHousing.png
  • banLadies.png
  • pixel
  • segmentation.js
  • so.js
  • pixel
  • cnt
  • h2TieUp.png
  • sync
  • tieUpLower.png
  • sync
  • tieUpUrban.png
  • banTry.png
  • usync
  • simulationBg.png
  • banRequest.png
  • saison_fl35.gif
  • btnMember1.png
  • js
  • netLower.png
  • service.png
  • sideNav1.gif
  • v3
  • sosync
  • bl_track.cgi
  • cc.html
  • so.js
  • cc.js
  • sideNav2.gif
  • sideNav3.gif
  • sideNav4.gif
  • sync
  • sync_before
  • sync_before
  • sync_before
  • idsync
  • sync
  • sideNav6.gif
  • js
  • sideH3Notice.gif
  • sync
  • cs
  • iconArrow.gif
  • pixel
  • sd
  • sync
  • is
  • Pug
  • v3
  • L21rdC82ODEvcGlkLzQzNzc1MDA4L3QvMA
  • beacon_call.js
  • sosync
  • img
  • beacon.html
  • beacon
  • sd
  • pixel
  • Pug
  • set
  • cs
  • tap.php
  • sync
  • dotBg.gif
  • sync
  • h2Info.gif
  • sync_before
  • sync_before
  • tap.php
  • sync
  • cs
  • sd
  • btnClose.gif
  • mapuser
  • sync
  • h2Link.gif
  • banRule.jpg
  • banJFSA.gif
  • pFooterUpper.png
  • imgPFooter2.gif

Our browser made a total of 186 requests to load all elements on the main page. We found that 57% of them (106 requests) were addressed to the original Fundex.co.jp, 9% (16 requests) were made to Tg.socdm.com and 3% (5 requests) were made to Dex.advg.jp. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Fundex.co.jp.

Additional info on fundex.co.jp

Requests

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

27

Javascripts

123

Images

7

CSS

7

AJAX

164

All

Possible request optimization

1

Javascripts

78

Images

1

CSS

7

AJAX

77

Optimized

87

All

Normal result

IP address

This IP address is dedicated to Fundex.co.jp. This is the best domain hosting practice .

Normal result

IP Trace

fundex.co.jp

210.154.147.150

DNS records

Type Host Target/ip TTL Other
A

fundex.co.jp

210.154.147.150 299
NS

fundex.co.jp

dns02.netsurf.ad.jp 299
NS

fundex.co.jp

ns.fundex.co.jp 299
SOA

fundex.co.jp

299 Mname: ns.fundex.co.jp
Rname: root.fundex.co.jp
Serial: 2018030100
Refresh: 300
Retry: 900
Expire: 2592000
Minimum-ttl: 300
MX

fundex.co.jp

ns.fundex.co.jp 299 Pri: 10

Language and encoding

Normal result

Language

JA ja language flag

Detected

JA ja language flag

Claimed

Encoding

SHIFT_JIS

Claimed

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

HTTPS certificate

SSL Certificate

Fundex.co.jp has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Normal result

Visitor World Map

Country of origin for 100% of all visits is Japan. It’s good for Fundex.co.jp that their server is also located in Japan, as that enables the majority of their visitors to benefit from a much faster page load time.

Good result

Poor result

Social Sharing Optimization

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

fundex.co.jp

Share this report in social media

Analyze another website

Analyze