5.9 sec in total
545 ms
5.1 sec
269 ms
Click here to check amazing Donan content for Japan. Otherwise, check out these important facts you probably never knew about donan.org
北海道・函館や道南地方の観光・温泉・イベント情報を紹介!道南の伝説も発掘中
Visit donan.orgWe analyzed Donan.org page load time and found that the first response time was 545 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
donan.org performance score
name
value
score
weighting
Value7.6 s
0/100
10%
Value9.4 s
1/100
25%
Value10.7 s
7/100
10%
Value740 ms
40/100
30%
Value0.055
98/100
15%
Value15.4 s
7/100
10%
545 ms
1724 ms
117 ms
78 ms
257 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 38% of them (44 requests) were addressed to the original Donan.org, 12% (14 requests) were made to I0.wp.com and 9% (11 requests) were made to C0.wp.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source I0.wp.com.
Page size can be reduced by 677.3 kB (34%)
2.0 MB
1.3 MB
In fact, the total size of Donan.org main page is 2.0 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. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 88.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. 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 88.7 kB or 79% of the original size.
Potential reduce by 29.4 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. Donan images are well optimized though.
Potential reduce by 319.6 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 319.6 kB or 26% of the original size.
Potential reduce by 239.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. Donan.org needs all CSS files to be minified and compressed as it can save up to 239.7 kB or 70% of the original size.
Number of requests can be reduced by 67 (60%)
112
45
The browser has sent 112 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Donan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
donan.org
545 ms
donan.org
1724 ms
adsbygoogle.js
117 ms
js
78 ms
show_ads_impl.js
257 ms
style.css
970 ms
responsive-pc.css
491 ms
font-awesome.min.css
702 ms
style.css
528 ms
calendar.css
530 ms
thread-simple.css
561 ms
responsive.css
653 ms
narrow.css
710 ms
media.css
709 ms
extension.css
748 ms
style.css
978 ms
responsive.css
876 ms
style.min.css
26 ms
mediaelementplayer-legacy.min.css
30 ms
wp-mediaelement.min.css
31 ms
screen.min.css
701 ms
dashicons.min.css
6 ms
thickbox.css
5 ms
amazonjs.css
699 ms
jquery.min.js
7 ms
jquery-migrate.min.js
25 ms
frontend-gtag.min.js
750 ms
rakuten_widget.js
1272 ms
eventorganiser-front-end.min.css
763 ms
javascript.js
763 ms
javascript.js
763 ms
image-cdn.js
763 ms
front.min.js
763 ms
e-202424.js
18 ms
feed2.js
777 ms
qtip2.js
1145 ms
core.min.js
7 ms
controlgroup.min.js
7 ms
checkboxradio.min.js
7 ms
button.min.js
15 ms
datepicker.min.js
14 ms
moment.min.js
1122 ms
fullcalendar.min.js
1307 ms
event-manager.min.js
944 ms
js
85 ms
googlemaps-adapter.js
929 ms
frontend.min.js
937 ms
IMGP6296.jpg
152 ms
header-back-bottom_s1.png
468 ms
topgifanicar.gif
639 ms
hometitle.png
495 ms
footer_logo.png
630 ms
IMGP3520.jpg
1998 ms
15_3.jpg
1206 ms
DSC_0936.jpg
167 ms
DSC_0798.jpg
163 ms
wp-1460892193920.jpeg
1427 ms
IMGP5001.jpg
166 ms
responsive_asodou_ss.png
250 ms
wp-1453597204494-e1453611010676.jpeg
180 ms
hatsuzakura.jpg
185 ms
jurakuen-title3-e1335792204828.png
1670 ms
IMGP37871.jpg
2204 ms
3159931362_7136c50422_m.jpg
1205 ms
DSCN5479s.jpg
2036 ms
cse.js
142 ms
menu_kankou.png
685 ms
menu_onsen.png
686 ms
menu_rekishi.png
706 ms
menu_omoshiro.png
743 ms
menu_event.png
755 ms
menu_nikki.png
798 ms
icomoon.ttf
798 ms
zrt_lookup.html
109 ms
ads
647 ms
fontawesome-webfont.woff
1167 ms
cse_element__ja.js
25 ms
default+ja.css
61 ms
default.css
63 ms
mw_dynamic_view.html
196 ms
footer_bg.png
561 ms
async-ads.js
61 ms
branding.png
56 ms
clear.png
35 ms
admin-ajax.php
231 ms
reactive_library.js
145 ms
pc_pcview_all.css
3 ms
front_merged.js
15 ms
mtwidget04.affiliate.rakuten.co.jp
1190 ms
getMWConf.php
181 ms
loading.gif
8 ms
buttons.gif
7 ms
13113165188462818874
205 ms
load_preloaded_resource.js
60 ms
icon.png
15 ms
abg_lite.js
58 ms
window_focus.js
58 ms
qs_click_protection.js
58 ms
ufs_web_display.js
38 ms
60efddb729a951d3495fe79f6eb41a86.js
206 ms
fullscreen_api_adapter.js
185 ms
interstitial_ad_frame.js
197 ms
faf71a0e8da85c808301846dcd34a748.js
208 ms
4a5cba740e22a750e003929b84bc8a1f.js
214 ms
feedback_grey600_24dp.png
249 ms
settings_grey600_24dp.png
249 ms
css
217 ms
14763004658117789537
62 ms
s
138 ms
print.css
271 ms
css
69 ms
VKtwqYIMw_jEtcsYEdk2t0uWx1X5nCbHNvrRSJpikmk.js
119 ms
font
215 ms
font
223 ms
font
173 ms
font
227 ms
activeview
90 ms
donan.org accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
donan.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
donan.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Donan.org 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 Donan.org 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.
donan.org
Open Graph data is detected on the main page of Donan. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: