7.3 sec in total
1.1 sec
6 sec
241 ms
Welcome to fujisawa-kanko.jp homepage info - get ready to check Fujisawa Kanko best content for Japan right away, or after learning these important things about fujisawa-kanko.jp
神奈川県藤沢市(湘南・江の島エリア)の公式観光情報サイトです。イベント、ショッピング、宿泊、グルメ情報が満載。オススメの観光スポットやモデルコースもご紹介しています。
Visit fujisawa-kanko.jpWe analyzed Fujisawa-kanko.jp page load time and found that the first response time was 1.1 sec and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
fujisawa-kanko.jp performance score
1146 ms
514 ms
868 ms
35 ms
59 ms
Our browser made a total of 158 requests to load all elements on the main page. We found that 73% of them (116 requests) were addressed to the original Fujisawa-kanko.jp, 12% (19 requests) were made to Static.xx.fbcdn.net and 6% (10 requests) were made to Scontent-iad3-1.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Fujisawa-kanko.jp.
Page size can be reduced by 151.9 kB (31%)
497.1 kB
345.3 kB
In fact, the total size of Fujisawa-kanko.jp main page is 497.1 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. 55% of websites need less resources to load. Images take 393.9 kB which makes up the majority of the site volume.
Potential reduce by 36.7 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 24.3 kB, which is 57% 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 36.7 kB or 87% of the original size.
Potential reduce by 83.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, Fujisawa Kanko needs image optimization as it can save up to 83.6 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 4.8 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 4.8 kB or 17% of the original size.
Potential reduce by 26.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. Fujisawa-kanko.jp needs all CSS files to be minified and compressed as it can save up to 26.7 kB or 80% of the original size.
Number of requests can be reduced by 56 (36%)
156
100
The browser has sent 156 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fujisawa Kanko. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
fujisawa-kanko.jp
1146 ms
fujisawa.css
514 ms
fujisawa.js
868 ms
brand
35 ms
brand
59 ms
small.css
179 ms
big.css
237 ms
analytics.js
65 ms
bg_02.gif
179 ms
logo.gif
173 ms
logo2.gif
293 ms
lang_menu_bg.gif
353 ms
lang_menu_05.gif
1020 ms
lang_menu_07.gif
2006 ms
lang_menu_09.gif
361 ms
lang_menu_11.gif
2008 ms
lang_menu_13.gif
438 ms
headermenu_27.gif
513 ms
font_29.gif
537 ms
font_31.gif
582 ms
font_33.gif
684 ms
listmark_36.gif
713 ms
rss_35.gif
726 ms
menu_o_48.gif
853 ms
menu_49.gif
891 ms
menu_50.gif
870 ms
menu_51.gif
1023 ms
sub_bg_53.gif
1016 ms
sub_55.gif
1068 ms
sub_57-1.gif
1168 ms
sub_58-1.gif
1159 ms
sub_59.gif
1193 ms
sub_61.gif
1244 ms
sub_63.gif
1304 ms
sub_65.gif
1338 ms
sub_67.gif
1362 ms
sub_68.gif
1421 ms
hl_bg_84.gif
1448 ms
left_c_bg_95.gif
1506 ms
time_88.gif
1532 ms
listmark_top.gif
1598 ms
calendar_100.gif
1592 ms
calendar_98.gif
1677 ms
%E3%81%A4%E3%82%8B%E3%81%AE%E5%89%9B%E5%A3%AB%E5%B0%86%E6%A3%8B-thumb-73x60-3732.jpg
361 ms
%E3%82%A8%E3%83%8E%E3%82%B7%E3%83%9E%E3%83%88%E3%83%AC%E3%82%B8%E3%83%A3%E3%83%BC2016-thumb-73x60-3677.jpg
435 ms
%E6%81%8B%E4%BA%BA%E3%81%AE%E4%B8%98%E5%85%A5%E5%8F%A31-thumb-73x60-3726.jpg
457 ms
%E6%98%A5%E3%81%BE%E3%81%A4%E3%82%8A2016-thumb-73x60-3731.jpg
1280 ms
%E5%A5%B3%E7%8E%8B%E5%8B%9F%E9%9B%862016-thumb-73x60-3695.jpg
2315 ms
%E3%83%91%E3%83%BC%E3%82%AF%E9%A7%90%E8%BB%8A%E5%A0%B4HP-thumb-73x60-3466.jpg
2221 ms
enopass-thumb-73x60-457.jpg
539 ms
%E3%81%95%E3%81%A4%E3%81%BE%E3%82%84%E5%AF%BF%E5%8F%B8%E6%95%99%E5%AE%A42015-thumb-73x60-3416.gif
579 ms
IMG_2073-thumb-448x336-3749.jpg
762 ms
all.js
270 ms
banner_40.gif
1675 ms
blog.js
579 ms
collect
12 ms
banner_38.gif
1576 ms
banner_37.gif
1610 ms
banner_34.gif
1565 ms
55 ms
xd_arbiter.php
217 ms
xd_arbiter.php
422 ms
banner_39.gif
1549 ms
banner_29.gif
1541 ms
qr_115.gif
1525 ms
banner_36.gif
1514 ms
qr_112.gif
1516 ms
banner_30.gif
1454 ms
swfobject.js
374 ms
banner_33.gif
1538 ms
banner_31.gif
1515 ms
banner_32.gif
1504 ms
banner_41.gif
1377 ms
banner_42.gif
1359 ms
event_bg.gif
1343 ms
ping
38 ms
event_h2bg.gif
1376 ms
event_90.gif
1407 ms
event_93.gif
1376 ms
like_box.php
189 ms
event_99.gif
1329 ms
event_97.gif
1212 ms
event_114.gif
1234 ms
event_117.gif
1322 ms
tDNjHICHo4x.css
286 ms
DJoUM5oOMjZ.css
353 ms
9dswh4qJ9um.css
422 ms
Xs6HzWIlE4l.css
554 ms
aW71gM3uZZD.css
562 ms
_rx8naC75Dy.js
620 ms
x5F9OMjKyLw.js
640 ms
ICDbTSzjQEg.js
489 ms
TTCre3391I0.js
492 ms
njO1TPvGzoR.js
574 ms
b_6HNn_J2BZ.js
574 ms
7cm7D75Y0Sf.js
687 ms
rFmE1g6Dkoz.js
821 ms
336JejShbZp.js
660 ms
news_90.gif
1324 ms
pickup_bg.gif
1262 ms
pickup_125.gif
1232 ms
pickup_25.gif
1209 ms
pickup_26.gif
1196 ms
pickup_28.gif
1211 ms
pickup_29.gif
1230 ms
pickup_30.gif
1210 ms
pickup_31.gif
1144 ms
pickup_32.gif
1144 ms
pickup_33.gif
1135 ms
pickup_34.gif
1100 ms
pickup_35.gif
1168 ms
turuno.jpg
1472 ms
fujisawa1_126.gif
1065 ms
fujisawa1_140.gif
1027 ms
qr_103.gif
1055 ms
access_95.gif
1055 ms
access_105.gif
1081 ms
access_118.gif
1085 ms
access_124.gif
1079 ms
footer_157.gif
1066 ms
fujisawasi.gif
1161 ms
547967_322574201161790_1395775934_n.jpg
141 ms
safe_image.php
140 ms
269245_322745564477987_365213961_n.jpg
135 ms
12743547_957080611044476_6660854372839886686_n.jpg
135 ms
12734044_951482768270927_5665678265957801785_n.jpg
134 ms
12743823_951482814937589_81117989500281801_n.jpg
136 ms
12744039_950918414994029_8959045078009887222_n.jpg
137 ms
12715219_950918434994027_2585954282349961080_n.jpg
137 ms
12718184_950918448327359_434668626368084069_n.jpg
138 ms
12745571_950918461660691_8502190898504196353_n.jpg
140 ms
12688178_949635938455610_2210444168060485716_n.jpg
139 ms
wL6VQj7Ab77.png
124 ms
s7jcwEQH7Sx.png
124 ms
QDwYpIaRyfG.png
124 ms
footer_161.gif
1033 ms
footer_167.gif
1033 ms
footer_165.gif
1016 ms
enopobanar.jpg
1052 ms
seacandle.gif
1179 ms
footer_163.gif
1157 ms
I6-MnjEovm5.js
76 ms
vlXaquuXMrr.js
76 ms
kamakura.gif
1053 ms
footer_175.gif
1036 ms
footer_178.gif
1033 ms
footer_180.gif
1060 ms
footer_183.gif
1132 ms
bg_188.gif
1182 ms
fujisawa1_127.gif
1078 ms
normal.css
180 ms
sub_o_55.gif
179 ms
pickup_o_129.gif
172 ms
pickup_o_130.gif
198 ms
pickup_o_132.gif
173 ms
pickup_o_133.gif
174 ms
pickup_o_135.gif
147 ms
pickup_o_136.gif
292 ms
fujisawa-kanko.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fujisawa-kanko.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 Fujisawa-kanko.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.
fujisawa-kanko.jp
Open Graph description is not detected on the main page of Fujisawa Kanko. 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: