15.9 sec in total
686 ms
14.9 sec
298 ms
Click here to check amazing Otemo Yan content for Japan. Otherwise, check out these important facts you probably never knew about otemo-yan.net
「熊本ブログおてもやん」はみんなで創る熊本の地域観光ブログサイトです。
Visit otemo-yan.netWe analyzed Otemo-yan.net page load time and found that the first response time was 686 ms and then it took 15.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
otemo-yan.net performance score
name
value
score
weighting
Value3.6 s
31/100
10%
Value6.6 s
8/100
25%
Value10.3 s
8/100
10%
Value1,780 ms
10/100
30%
Value0.711
7/100
15%
Value18.3 s
3/100
10%
686 ms
4394 ms
890 ms
1132 ms
48 ms
Our browser made a total of 227 requests to load all elements on the main page. We found that 52% of them (119 requests) were addressed to the original Otemo-yan.net, 16% (36 requests) were made to Img01.otemo-yan.net and 9% (21 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (5 sec) relates to the external source Img01.otemo-yan.net.
Page size can be reduced by 312.5 kB (12%)
2.7 MB
2.4 MB
In fact, the total size of Otemo-yan.net main page is 2.7 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. 60% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 64.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. This page needs HTML code to be minified as it can gain 18.1 kB, which is 23% 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 64.1 kB or 83% of the original size.
Potential reduce by 93.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. Otemo Yan images are well optimized though.
Potential reduce by 104.4 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 104.4 kB or 46% of the original size.
Potential reduce by 50.2 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. Otemo-yan.net needs all CSS files to be minified and compressed as it can save up to 50.2 kB or 88% of the original size.
Number of requests can be reduced by 101 (47%)
213
112
The browser has sent 213 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Otemo Yan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
otemo-yan.net
686 ms
www.otemo-yan.net
4394 ms
base.css
890 ms
box_index.css
1132 ms
jsapi
48 ms
jquery-1.6.4.min.js
1619 ms
common.js
679 ms
hide.js
680 ms
jquery.rollover.js
882 ms
jquery.scrollTo-min.js
1136 ms
right_top.js
1137 ms
footer-areaers.js
1324 ms
header.js
1337 ms
ga_analytics.js
1589 ms
rss_reader.php
671 ms
adsbygoogle.js
5 ms
brand
16 ms
rss_reader.php
822 ms
rss_reader.php
674 ms
brand
57 ms
rss_reader.php
1170 ms
rss_reader.php
769 ms
analytics.js
25 ms
bg_container.png
460 ms
event.html
461 ms
bg_tagline_002.png
460 ms
bg-li.png
458 ms
img_head-logo2.jpg
664 ms
img_head-img001.png
443 ms
nav01.png
454 ms
nav04.png
685 ms
nav07.png
689 ms
nav06.png
879 ms
otemoyanpart_info01.jpg
1315 ms
otemoyanpart_new01.jpg
1361 ms
sp-077422700s1456541626-s.jpg
1044 ms
banner-chesuto001.gif
459 ms
IMG_6700-s.JPG
1043 ms
IMG_6687-s.JPG
1050 ms
IMG_0816-s.JPG
1056 ms
FullSizeRender106378-s.jpg
1056 ms
sp-033446100s1456756835-s.jpg
1065 ms
IMG_4524-s.JPG
1907 ms
sp-056710100s1456751986-s.jpg
1917 ms
IMG_6733927551-s.JPG
1697 ms
DSC_2253-s.JPG
1712 ms
%E7%A5%88%E7%A5%B7%E4%BC%9A%EF%BC%96_1-s.jpg
1503 ms
blog21-s.jpg
1916 ms
%E5%B9%B3%E6%97%A5%E4%BD%93%E9%A8%931-s.jpg
2582 ms
sp-056014300s1456750037-s.jpg
2129 ms
sp-020591100s1456750764-s.jpg
2617 ms
app-064092200s1456740674-s.jpg
2783 ms
app-093799300s1456748943-s.jpg
3008 ms
12648164_792931110836490_1036532532_n-s.jpg
2574 ms
app-023377600s1456746461-s.jpg
2775 ms
sp-069587000s1456746161-s.jpg
3448 ms
FullSizeRender-k006k_1-s.jpg
3021 ms
2015-09-16s034ppp-s.JPG
3715 ms
sp-047826600s1456732803-s.jpg
3615 ms
sp-051438500s1455534181-s.jpg
3203 ms
2016-02-29s09.33.45-s.jpg
3880 ms
img_newentry.png
1111 ms
type_013.gif
1149 ms
type_014.gif
1148 ms
type_001.gif
1322 ms
type_021.gif
1572 ms
type_006.gif
1586 ms
type_002.gif
1597 ms
type_016.gif
1739 ms
type_003.gif
1782 ms
type_004.gif
1804 ms
btn_200entry.gif
2024 ms
btn_allblog.gif
2037 ms
btn_newblog.gif
2054 ms
img_newblog.png
2211 ms
type_010.gif
2213 ms
btn_login2.png
2473 ms
btn_regist.png
2706 ms
login_hatena.gif
2480 ms
img_search.png
2509 ms
dottedline19.gif
2671 ms
img_news.png
2672 ms
img_ranking.png
2918 ms
no1.gif
2924 ms
no2.gif
2950 ms
no3.gif
3126 ms
no4.gif
3132 ms
no5.gif
3161 ms
linkid.js
10 ms
collect
10 ms
collect
54 ms
collect
18 ms
collect
59 ms
%E3%83%97%E3%83%AC%E3%83%9F%E3%82%A2%E3%83%A0%E3%81%84%E3%81%A1%E3%81%94%E5%A4%A7%E7%A6%8Fk%E5%B0%8Fk-s.jpg
3473 ms
%E6%A3%AE%E5%8F%A3%E5%85%88%E7%94%9F%E3%81%AE%E8%89%B2%E9%89%9B%E7%AD%86%E4%BD%93%E9%A8%93%E6%95%99%E5%AE%A4-s.JPG
3662 ms
image_209-s.jpeg
4114 ms
DSCN1894-s.JPG
4296 ms
IMG_4662sk2k_1-s.JPG
3913 ms
%E7%99%BD-s.jpg
4168 ms
IMG_1316-s.JPG
4308 ms
no6.gif
3159 ms
ca-pub-1484749698222066.js
34 ms
zrt_lookup.html
32 ms
show_ads_impl.js
63 ms
bg_search.png
682 ms
google_custom_search_watermark.gif
44 ms
icon_arrow_orange.png
675 ms
IMG_1325-s.png
4721 ms
20130915_122125_20130917145858253-s.jpg
4976 ms
DSC_2596~2-s.jpg
4683 ms
likebox.php
214 ms
ads
374 ms
osd.js
10 ms
ads
345 ms
ads
311 ms
no7.gif
2952 ms
no8.gif
2974 ms
bg_container.png
3145 ms
bg-li.png
3137 ms
bg_tagline_002.png
3851 ms
event.html
3361 ms
banner-chesuto001.gif
3790 ms
jTuqQ-OPDr6.css
363 ms
n370yiaI2G6.css
423 ms
dbNRhrdsQao.css
494 ms
1-xIpmMldel.css
625 ms
Qs8JpkaZZWn.css
635 ms
cCIltMJutxu.css
643 ms
_rx8naC75Dy.js
695 ms
x5F9OMjKyLw.js
695 ms
ICDbTSzjQEg.js
560 ms
TTCre3391I0.js
650 ms
njO1TPvGzoR.js
690 ms
b_6HNn_J2BZ.js
693 ms
7cm7D75Y0Sf.js
759 ms
rFmE1g6Dkoz.js
894 ms
336JejShbZp.js
755 ms
11597879325985340688
119 ms
abg.js
51 ms
m_js_controller.js
49 ms
googlelogo_color_112x36dp.png
127 ms
9842298877725888730
98 ms
11501060655840636707
79 ms
icon_arrow_pink.png
3159 ms
s
65 ms
redir.html
115 ms
x_button_blue2.png
17 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
3 ms
iframe.html
18 ms
icon_arrow_orange.png
3129 ms
bg_search.png
3130 ms
no9.gif
2939 ms
no10.gif
2973 ms
11350450_1035741553120992_1513892952806430697_n.jpg
85 ms
safe_image.php
91 ms
11377341_1035741429787671_4179892011344924284_n.jpg
85 ms
10426581_606522742810492_9008604607014444026_n.jpg
84 ms
12208440_868172066623169_7548692940151165512_n.jpg
84 ms
12250064_1712291715669201_5626394365568769864_n.jpg
84 ms
12011354_1712575675638516_3268161832095994835_n.jpg
84 ms
11214179_110000379348464_4878542065371974181_n.jpg
82 ms
1958003_1572848549610019_7374928775751263742_n.jpg
85 ms
11350450_1035741553120992_1513892952806430697_n.jpg
87 ms
11377341_1035741429787671_4179892011344924284_n.jpg
87 ms
11108857_1003256613036153_5834935148251901596_n.jpg
88 ms
11096446_1003256889702792_5531820245741179824_n.jpg
86 ms
1525547_1003256973036117_7700480315281596788_n.jpg
85 ms
10806296_1003257033036111_1516585777551009814_n.jpg
88 ms
10398662_997769496918198_6158401282924074150_n.jpg
89 ms
11062045_997769793584835_9005727545127812860_n.jpg
89 ms
wL6VQj7Ab77.png
78 ms
s7jcwEQH7Sx.png
79 ms
QDwYpIaRyfG.png
77 ms
a-ZN6WoEOje.png
77 ms
I6-MnjEovm5.js
68 ms
vlXaquuXMrr.js
134 ms
no11.gif
2928 ms
no12.gif
2918 ms
no13.gif
3100 ms
no14.gif
2980 ms
no15.gif
2975 ms
no16.gif
2967 ms
no17.gif
2927 ms
no18.gif
2908 ms
activeview
14 ms
activeview
16 ms
no19.gif
3087 ms
no20.gif
2965 ms
img_inquiry.png
2985 ms
btn_inquriy.png
2967 ms
img_category.png
2924 ms
type_005.gif
2891 ms
type_040.gif
2911 ms
type_007.gif
2953 ms
type_008.gif
2945 ms
type_009.gif
2932 ms
type_011.gif
2935 ms
type_012.gif
2951 ms
type_015.gif
2917 ms
type_017.gif
2945 ms
type_018.gif
2945 ms
type_019.gif
2938 ms
type_020.gif
2944 ms
type_025.gif
2947 ms
type_038_2.gif
2931 ms
type_041.gif
2949 ms
base.css
234 ms
jquery.min.js
33 ms
type_022.gif
2769 ms
type_024.gif
2900 ms
base.css
2968 ms
handmage180.jpg
3662 ms
img_gourmet.png
3175 ms
img_roasso.png
3640 ms
img_birthday.png
2735 ms
type_birthday.gif
2900 ms
obj_03.gif
2960 ms
ico_point.gif
2994 ms
img_tag.png
2986 ms
img_kanren.png
3146 ms
jump_btn.gif
3152 ms
2012021922250000-s.jpg
3176 ms
nav01_on.png
3189 ms
nav04_on.png
3212 ms
nav07_on.png
3184 ms
nav06_on.png
3396 ms
2012021922250000-s.jpg
441 ms
otemo-yan.net 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
[aria-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
otemo-yan.net 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
otemo-yan.net 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 Otemo-yan.net 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 Otemo-yan.net 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.
otemo-yan.net
Open Graph description is not detected on the main page of Otemo Yan. 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: