9.8 sec in total
1.2 sec
7.6 sec
916 ms
Welcome to hideyuki-kawabe.com homepage info - get ready to check Hideyuki Kawabe best content right away, or after learning these important things about hideyuki-kawabe.com
株式会社webtechのべーやんこと川邊英之が日々の想いを綴る公式ブログ
Visit hideyuki-kawabe.comWe analyzed Hideyuki-kawabe.com page load time and found that the first response time was 1.2 sec and then it took 8.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
hideyuki-kawabe.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value11.0 s
0/100
25%
Value8.5 s
18/100
10%
Value520 ms
56/100
30%
Value1.003
2/100
15%
Value16.9 s
5/100
10%
1240 ms
175 ms
24 ms
326 ms
318 ms
Our browser made a total of 205 requests to load all elements on the main page. We found that 14% of them (28 requests) were addressed to the original Hideyuki-kawabe.com, 10% (21 requests) were made to Facebook.com and 10% (20 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Hideyuki-kawabe.com.
Page size can be reduced by 576.2 kB (10%)
5.8 MB
5.3 MB
In fact, the total size of Hideyuki-kawabe.com main page is 5.8 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.0 MB which makes up the majority of the site volume.
Potential reduce by 123.3 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 123.3 kB or 86% of the original size.
Potential reduce by 20.2 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. Hideyuki Kawabe images are well optimized though.
Potential reduce by 297.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 297.9 kB or 57% of the original size.
Potential reduce by 134.8 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. Hideyuki-kawabe.com needs all CSS files to be minified and compressed as it can save up to 134.8 kB or 84% of the original size.
Number of requests can be reduced by 89 (44%)
202
113
The browser has sent 202 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hideyuki Kawabe. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
hideyuki-kawabe.com
1240 ms
widget.css
175 ms
css
24 ms
genericons.css
326 ms
style.css
318 ms
wpp.css
331 ms
jquery.js
511 ms
jquery-migrate.min.js
329 ms
q2w3-fixed-widget.min.js
356 ms
sharebar.js
471 ms
jquery.js
645 ms
jsapi
21 ms
adsbygoogle.js
5 ms
bookmark_button.js
757 ms
rakuten_widget.js
1022 ms
masonry.min.js
474 ms
jquery.masonry.min.js
479 ms
functions.js
519 ms
sdk.js
170 ms
17 ms
default+en.css
4 ms
default+en.I.js
6 ms
analytics.js
15 ms
lines.png
183 ms
button-only@2x.png
218 ms
logo.png
214 ms
top_bunner_01.gif
364 ms
sanadamaru.jpg
1384 ms
eva.gif
422 ms
amazoncloud.jpg
1684 ms
victor.jpg
475 ms
sensyuraku.jpg
2576 ms
dreamweaver.jpg
1684 ms
twitter.jpg
1395 ms
smap.jpg
1682 ms
crayon.jpg
2158 ms
uemura1.jpg
1759 ms
enday_top.jpg
1955 ms
20160115.jpg
2274 ms
ca-pub-6171456493193446.js
67 ms
zrt_lookup.html
64 ms
show_ads_impl.js
63 ms
collect
22 ms
113 ms
xd_arbiter.php
772 ms
xd_arbiter.php
318 ms
tweet_button.html
89 ms
ads
347 ms
tweet_button.html
43 ms
osd.js
62 ms
tweet_button.html
57 ms
jot
166 ms
jot
159 ms
239 ms
242 ms
239 ms
ads
261 ms
tweet_button.html
22 ms
jot
171 ms
jot
173 ms
tweet_button.html
27 ms
tweet_button.html
20 ms
tweet_button.html
38 ms
jot
132 ms
jot
127 ms
ads
321 ms
jot
113 ms
ads
163 ms
jot
80 ms
tweet_button.html
37 ms
jot
70 ms
tweet_button.html
30 ms
tweet_button.html
32 ms
tweet_button.html
37 ms
jot
58 ms
jot
59 ms
jot
53 ms
jot
46 ms
jot
33 ms
reset.css
17 ms
entry-button.css
17 ms
tweet_button.html
28 ms
jot
41 ms
button-counter.gif
22 ms
m_js_controller.js
40 ms
abg.js
65 ms
jot
47 ms
jot
119 ms
jot
107 ms
favicon
163 ms
favicon
158 ms
favicon
215 ms
googlelogo_color_112x36dp.png
205 ms
nessie_icon_tiamat_white.png
122 ms
s
138 ms
x_button_blue2.png
130 ms
jot
133 ms
favicon
110 ms
ads
237 ms
482 ms
481 ms
483 ms
483 ms
482 ms
481 ms
753 ms
746 ms
753 ms
mtwidget04.affiliate.rakuten.co.jp
1039 ms
mtwidget04.affiliate.rakuten.co.jp
1028 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
32 ms
plusone.js
182 ms
likebox.php
139 ms
12614732496400057829
34 ms
like.php
169 ms
like.php
171 ms
like.php
183 ms
like.php
241 ms
like.php
175 ms
like.php
243 ms
like.php
514 ms
like.php
238 ms
like.php
505 ms
like.php
507 ms
like.php
511 ms
like.php
508 ms
like.php
510 ms
like.php
578 ms
like.php
597 ms
like.php
596 ms
like.php
615 ms
like.php
574 ms
like.php
575 ms
cb=gapi.loaded_0
57 ms
cb=gapi.loaded_1
77 ms
fastbutton
132 ms
fastbutton
211 ms
fastbutton
210 ms
fastbutton
125 ms
fastbutton
124 ms
fastbutton
203 ms
fastbutton
199 ms
fastbutton
195 ms
fastbutton
313 ms
fastbutton
466 ms
fastbutton
459 ms
fastbutton
456 ms
hDvwL1_H7g-.css
520 ms
udqjbTyb5Ue.css
569 ms
q68gy-v_YMF.js
630 ms
FJmpeSpHpjS.js
648 ms
0wM5s1Khldu.js
565 ms
1bNoFZUdlYZ.js
567 ms
postmessageRelay
251 ms
rs=AGLTcCMZnOZwP_q6pCwQUYCN0BCxu9nBPg
100 ms
wy1X4hBW7e7.js
630 ms
LVx-xkvaJ0b.png
504 ms
cb=gapi.loaded_0
337 ms
cb=gapi.loaded_1
272 ms
3193398744-postmessagerelay.js
261 ms
rpc:shindig_random.js
241 ms
cb=gapi.loaded_0
10 ms
298907_261636863873133_109835760_n.jpg
180 ms
wL6VQj7Ab77.png
79 ms
s7jcwEQH7Sx.png
79 ms
12301463_760519590759159_4683966511825203333_n.jpg
217 ms
12651311_924413307639852_3058717070015846823_n.jpg
256 ms
10325596_653044424764681_8794507268096393028_n.jpg
294 ms
10478185_669808146478030_6288717909725922484_n.jpg
450 ms
12308366_833752956735673_4722984285172424295_n.jpg
296 ms
541656_457550590990248_1755622953_n.jpg
341 ms
198004_10150117881108347_3291730_n.jpg
294 ms
423062_276354302435903_1849612953_n.jpg
296 ms
1544970_631116773652095_3065489302336935132_n.jpg
333 ms
305781_183710978370001_1781297771_n.jpg
334 ms
525895_106040432872289_259599573_n.jpg
334 ms
pc_pcview_all.css
13 ms
front_merged.js
25 ms
mtwidget03.affiliate.ashiato.rakuten.co.jp
673 ms
getMWConf.php
302 ms
mtwidget03.affiliate.ashiato.rakuten.co.jp
793 ms
getMWConf.php
329 ms
loading.gif
7 ms
buttons.gif
6 ms
activeview
11 ms
activeview
15 ms
I6-MnjEovm5.js
41 ms
pQrUxxo5oQp.js
79 ms
motegi_kago_m02.jpg
42 ms
a.gif
479 ms
e114677h_l.jpg
26 ms
sd_2014_bnr3.jpg
105 ms
a.gif
394 ms
50408_xx4.jpg
210 ms
60209_xx2.jpg
218 ms
2011ryohc-01.jpg
215 ms
Gfeeds
770 ms
Gfeeds
774 ms
ui
27 ms
t.gif
328 ms
merumaga_0616-7.jpg
1351 ms
hukuiwai720.jpg
1684 ms
puremiamsugata3.jpg
2334 ms
kawaturunakadare1.jpg
2007 ms
sinraikurorabel01.jpg
2172 ms
hideyuki-kawabe.com 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
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
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.
hideyuki-kawabe.com 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
hideyuki-kawabe.com SEO score
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
N/A
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hideyuki-kawabe.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Hideyuki-kawabe.com 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.
hideyuki-kawabe.com
Open Graph description is not detected on the main page of Hideyuki Kawabe. 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: