11.9 sec in total
1.1 sec
10.6 sec
202 ms
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
≪セゾン≫カードでおなじみのクレディセゾングループ【セゾンファンデックス】。シニアや事業者のお金の悩みを解決し、暮らしに安心を届けます。かんたん安心カードローン|不動産担保ローン|リースバック
Visit fundex.co.jpWe 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.
fundex.co.jp performance score
1124 ms
337 ms
689 ms
555 ms
369 ms
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.
Page size can be reduced by 236.3 kB (36%)
661.5 kB
425.2 kB
In fact, the total size of Fundex.co.jp main page is 661.5 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.
Potential reduce by 68.6 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 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.
Potential reduce by 97.6 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, 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.
Potential reduce by 59.7 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 59.7 kB or 48% of the original size.
Potential reduce by 10.3 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. 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.
Number of requests can be reduced by 77 (47%)
164
87
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.
index.html
1124 ms
import.css
337 ms
top.css
689 ms
topMainVisual.css
555 ms
openWindow.js
369 ms
clickable.js
398 ms
faq.js
676 ms
topmainVisual.js
708 ms
AC_RunActiveContent.js
1121 ms
reset.css
591 ms
clearfix.css
629 ms
base.css
694 ms
header.css
719 ms
footer.css
731 ms
side.css
948 ms
ojs
323 ms
347 ms
540 ms
ga.js
46 ms
imgFaqClose.gif
179 ms
body.png
341 ms
header1.png
347 ms
logo.png
530 ms
saisonfundex.png
762 ms
company.png
392 ms
inquiry.png
542 ms
sitemap.png
687 ms
network.png
706 ms
saisoncardInternational.png
938 ms
header5.png
884 ms
header2.png
881 ms
header3.png
1042 ms
imgMainTitle.png
1210 ms
individual_.png
1304 ms
business.png
1397 ms
estate.png
1427 ms
divMainVisual.png
1283 ms
thIndiviVip.png
1811 ms
thSupport.png
1778 ms
thIndiviEstate.png
1997 ms
tdIndiviVip1.png
1875 ms
tdSupport1.png
2129 ms
tdIndiviEstate1.png
1949 ms
tdIndiviVipBack1.png
2454 ms
tdIndiviVip4.png
2499 ms
vipSummary2030.png
2254 ms
tdIndiviVip2.png
2313 ms
vipSummaryRegular.png
2374 ms
tdIndiviVip3.png
2508 ms
tdSupportBack1.png
2968 ms
tdSupport2.png
2987 ms
summaryPremeditated.png
2738 ms
tdSupport3.png
3010 ms
summarySupportFree.png
2857 ms
tdIndiviEstateBack1.png
3230 ms
__utm.gif
10 ms
entry.js
584 ms
tdIndiviEstate4.png
3065 ms
summaryFree.png
2883 ms
summaryReform.png
3133 ms
summaryInvestment.png
2983 ms
summaryPurchase.png
2838 ms
tdIndiviEstate2.png
3276 ms
actag
341 ms
ojs2
349 ms
tdIndiviVipBack2.png
3088 ms
applyIndiviVip.png
3082 ms
tdSupportBack2.png
3119 ms
applySupport.png
3057 ms
tdIndiviEstateBack2.png
3132 ms
applyIndiviEstate.png
3355 ms
tag.js
539 ms
lb
35 ms
sync0
361 ms
conversion.js
99 ms
s_retargeting.js
579 ms
thBusinessVip.png
3660 ms
thBusinessEstate.png
3152 ms
tdBusinessVip1.png
3307 ms
tdBusinessEstate1.png
3552 ms
tdBusinessVip2.png
3561 ms
tdBusinessEstate2.png
3779 ms
CREATIVE_IMGn.js
494 ms
summaryBusinessVip.png
3092 ms
applyBusinessVip.png
3299 ms
summaryBusinessEstate.png
3336 ms
applyBusinessEstate.png
3439 ms
thHousingProject.png
3575 ms
339 ms
373 ms
tdHousingProject1.png
3557 ms
housingLeft.png
3610 ms
summaryHousing1.png
3415 ms
scheck
315 ms
summaryHousing2.png
3385 ms
summaryHousing.png
3481 ms
inquiryHousing.png
3607 ms
banLadies.png
3718 ms
pixel
34 ms
segmentation.js
43 ms
so.js
624 ms
pixel
26 ms
cnt
355 ms
h2TieUp.png
3531 ms
sync
337 ms
tieUpLower.png
3260 ms
sync
356 ms
tieUpUrban.png
3235 ms
banTry.png
3460 ms
usync
344 ms
simulationBg.png
3463 ms
banRequest.png
3452 ms
saison_fl35.gif
3501 ms
btnMember1.png
3669 ms
js
209 ms
netLower.png
3273 ms
service.png
3616 ms
sideNav1.gif
3501 ms
v3
204 ms
sosync
314 ms
40 ms
31 ms
337 ms
bl_track.cgi
357 ms
cc.html
52 ms
so.js
346 ms
41 ms
39 ms
cc.js
22 ms
sideNav2.gif
3404 ms
sideNav3.gif
3459 ms
sideNav4.gif
3467 ms
16 ms
sync
538 ms
sync_before
213 ms
sync_before
161 ms
sync_before
234 ms
idsync
323 ms
sync
350 ms
18 ms
sideNav6.gif
3560 ms
js
309 ms
sideH3Notice.gif
3391 ms
sync
610 ms
cs
297 ms
iconArrow.gif
3324 ms
pixel
28 ms
sd
72 ms
sync
532 ms
is
799 ms
Pug
23 ms
v3
202 ms
12 ms
L21rdC82ODEvcGlkLzQzNzc1MDA4L3QvMA
36 ms
beacon_call.js
37 ms
sosync
160 ms
img
177 ms
17 ms
beacon.html
21 ms
beacon
26 ms
sd
72 ms
pixel
26 ms
Pug
17 ms
set
301 ms
cs
174 ms
tap.php
10 ms
sync
7 ms
dotBg.gif
3228 ms
sync
347 ms
h2Info.gif
3268 ms
15 ms
sync_before
158 ms
sync_before
190 ms
tap.php
6 ms
19 ms
sync
311 ms
cs
148 ms
sd
73 ms
btnClose.gif
3056 ms
mapuser
159 ms
sync
208 ms
h2Link.gif
2971 ms
banRule.jpg
3033 ms
banJFSA.gif
3113 ms
pFooterUpper.png
3107 ms
imgPFooter2.gif
3065 ms
fundex.co.jp SEO score
JA
JA
SHIFT_JIS
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.
fundex.co.jp
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: