11.7 sec in total
1.8 sec
9.1 sec
771 ms
Visit fujisan.ne.jp now to see the best up-to-date Fujisan content for Japan and also check out these interesting facts you probably never knew about fujisan.ne.jp
富士河口湖町の公式観光情報サイト。富士山と湖が織りなす絶景スポット、四季の自然、グルメや体験、モデルコースまで幅広く紹介。静かな観光や地域の魅力を深く楽しむ旅の情報が見つかります。
Visit fujisan.ne.jpWe analyzed Fujisan.ne.jp page load time and found that the first response time was 1.8 sec and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
fujisan.ne.jp performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value13.2 s
0/100
25%
Value16.8 s
0/100
10%
Value1,380 ms
16/100
30%
Value0.001
100/100
15%
Value18.5 s
3/100
10%
1836 ms
48 ms
357 ms
677 ms
510 ms
Our browser made a total of 122 requests to load all elements on the main page. We found that 87% of them (106 requests) were addressed to the original Fujisan.ne.jp, 4% (5 requests) were made to Cdn.ds-ai.net and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Fujisan.ne.jp.
Page size can be reduced by 402.8 kB (8%)
5.1 MB
4.7 MB
In fact, the total size of Fujisan.ne.jp main page is 5.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 70% of websites need less resources to load. Images take 4.4 MB which makes up the majority of the site volume.
Potential reduce by 162.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 162.1 kB or 84% of the original size.
Potential reduce by 178.8 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. Fujisan images are well optimized though.
Potential reduce by 57.9 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 57.9 kB or 14% of the original size.
Potential reduce by 4.0 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. Fujisan.ne.jp has all CSS files already compressed.
Number of requests can be reduced by 60 (50%)
120
60
The browser has sent 120 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fujisan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
fujisan.ne.jp
1836 ms
viewport-extra.min.js
48 ms
reset.css
357 ms
pc.min.css
677 ms
jquery.fancybox.min.css
510 ms
photoswipe.min.css
511 ms
default-skin.min.css
522 ms
animate.min.css
532 ms
design.css
536 ms
page.css
682 ms
froala_editor.pkgd.min.css
31 ms
custom.css
33 ms
jquery-3.5.1.min.js
845 ms
jquery-migrate-1.4.1.min.js
708 ms
resize_img.min.js
707 ms
jquery.easing.min.js
715 ms
jquery.cookie.min.js
845 ms
tap.min.js
848 ms
msg.js
880 ms
camera.min.css
883 ms
vegas.min.css
892 ms
pc.min.css
1015 ms
jquery.dbpas.carousel.min.css
1015 ms
pc.min.css
1015 ms
js
75 ms
all.css
3 ms
font-awesome.css
2 ms
jquery.fancybox.min.js
919 ms
photoswipe.min.js
1103 ms
photoswipe-ui-default.min.js
921 ms
photoswipe-set-customize.min.js
1075 ms
progressbar.min.js
1076 ms
jquery.easing.1.3.min.js
1074 ms
jquery.touchSwipe.min.js
1108 ms
camera.min.js
1111 ms
three.min.js
1517 ms
theta_bg.min.js
1182 ms
covervid.min.js
1184 ms
jquery.tubular.1.0.min.js
1239 ms
vegas.min.js
1240 ms
jquery.ba-throttle-debounce.min.js
1258 ms
jquery.dbpas.carousel.min.js
1351 ms
fontplus.js
1074 ms
ds-chat.js
869 ms
imgCycle.min.js
1351 ms
marquee.min.js
1233 ms
onload.min.js
1082 ms
scrollmenu.min.js
1104 ms
analysis.min.js
1205 ms
js
64 ms
analytics.js
57 ms
202112011201282670.jpg
1988 ms
202110260804592309.png
1489 ms
202109221339071611.png
1489 ms
202109131431185534.jpeg
1489 ms
202403111347002745.png
1822 ms
202301171708153735.png
1489 ms
202312110914304631.png
2196 ms
202201141001259562.jpg
1833 ms
202201141007228405.jpg
1835 ms
202201141000363705.jpg
1656 ms
202206131513594032.jpg
1825 ms
202312050923384770.png
2331 ms
202404181020485668.png
2002 ms
202109291014243117.jpg
2007 ms
202109291021371099.jpg
2012 ms
202201131441166421.jpg
2154 ms
202109291026025570.jpg
2120 ms
202109291025293035.jpg
2128 ms
collect
111 ms
202109291022418461.jpg
2150 ms
202109291019549749.jpg
2126 ms
1261 ms
202201131452014832.jpg
2109 ms
202109291020351364.jpg
2116 ms
fontawesome-webfont.woff
25 ms
202109301158175861.jpg
2132 ms
202109301158295582.jpg
2233 ms
collect
39 ms
202109301158504088.jpg
2191 ms
202109301159027658.jpg
2197 ms
202109301159229333.jpg
2160 ms
202103151359523548.jpg
2159 ms
202103151404053502.jpg
2163 ms
202103151404537581.jpg
2184 ms
202103151405499997.jpg
2189 ms
202103151406554188.jpg
2136 ms
202103151408116018.jpg
2158 ms
202206101421156182.png
2309 ms
iframe_api
849 ms
202103151409362647.jpg
2051 ms
202103151410168027.jpg
1366 ms
202103151410577770.jpg
1361 ms
202103151417337694.jpg
1376 ms
202103151418021961.jpg
1396 ms
202103151418507894.jpg
1428 ms
www-widgetapi.js
7 ms
202103151419308566.jpg
1355 ms
202104140214094048.png
1196 ms
202104140214382147.png
1207 ms
202107051336349580.png
1224 ms
202104140214193151.png
1223 ms
202104140213577264.png
1109 ms
am_bgimg.png
1347 ms
am_logo.png
1180 ms
back.png
1860 ms
catch_frame.png
1070 ms
header_bg.png
1059 ms
header.png
1091 ms
bg.png
1165 ms
menu_b.png
1073 ms
menu_b.png
1073 ms
menu_b.png
1110 ms
menu_b.png
1161 ms
menu_b.png
1173 ms
menu_b.png
1205 ms
footer_bg.png
1082 ms
footer.png
1126 ms
sprite.png
1174 ms
camera-loader.gif
1178 ms
202112011201282670.jpg
1735 ms
202112011202232519.jpg
891 ms
fujisan.ne.jp accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
Links do not have a discernible name
fujisan.ne.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
fujisan.ne.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Document uses legible font sizes
Tap targets are not sized appropriately
![]()
JA
![]()
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fujisan.ne.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 Fujisan.ne.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.
fujisan.ne.jp
Open Graph data is detected on the main page of Fujisan. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: