5.4 sec in total
445 ms
4.7 sec
273 ms
Welcome to kenchikukenken.co.jp homepage info - get ready to check Kenchikukenken best content for Japan right away, or after learning these important things about kenchikukenken.co.jp
建築系検索エンジンKenKen!は、建築に特化した専門検索エンジン。有名な建築家から地元の設計事務所・建設会社、近所の職人さん専門用語辞典まで、クチコミやランキングでチェック。プロも使っている建築情報サイト。
Visit kenchikukenken.co.jpWe analyzed Kenchikukenken.co.jp page load time and found that the first response time was 445 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
kenchikukenken.co.jp performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value6.8 s
7/100
25%
Value14.1 s
1/100
10%
Value4,720 ms
0/100
30%
Value0.449
20/100
15%
Value18.5 s
3/100
10%
445 ms
440 ms
310 ms
553 ms
5 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 48% of them (54 requests) were addressed to the original Kenchikukenken.co.jp, 9% (10 requests) were made to Pagead2.googlesyndication.com and 8% (9 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Kenchikukenken.co.jp.
Page size can be reduced by 209.8 kB (21%)
1.0 MB
808.0 kB
In fact, the total size of Kenchikukenken.co.jp main page is 1.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. Images take 673.9 kB which makes up the majority of the site volume.
Potential reduce by 49.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 49.7 kB or 77% of the original size.
Potential reduce by 19.3 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. Kenchikukenken images are well optimized though.
Potential reduce by 110.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 110.9 kB or 46% of the original size.
Potential reduce by 29.9 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. Kenchikukenken.co.jp needs all CSS files to be minified and compressed as it can save up to 29.9 kB or 80% of the original size.
Number of requests can be reduced by 40 (36%)
110
70
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kenchikukenken. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and as a result speed up the page load time.
kenchikukenken.co.jp
445 ms
www.kenchikukenken.co.jp
440 ms
kenken.css
310 ms
jquery.js
553 ms
adsbygoogle.js
5 ms
bookmark_button.js
858 ms
kenken.js
370 ms
pla.gif
1120 ms
banner_ad.gif
1672 ms
button-only@2x.png
496 ms
kenchiku-kenken.gif
360 ms
search_txt_box.gif
361 ms
baba.gif
494 ms
1352855072_30.jpg
495 ms
1432172204_144.jpg
496 ms
1312850426_88.jpg
495 ms
989403231_302.jpg
696 ms
1210121004_111.jpg
759 ms
next.gif
865 ms
1103611296_42.jpg
876 ms
1181708587_32.jpg
919 ms
1425863442_58.jpg
952 ms
1143687392_288.jpg
1032 ms
1300063160_34.jpg
1068 ms
996969080_220.jpg
1211 ms
993001656_407.jpg
1244 ms
997406146_497.jpg
1267 ms
1368078231_37.jpg
1301 ms
983625656_24.jpg
1423 ms
1308622020_1475.jpg
1461 ms
1081737329_45.jpg
1593 ms
962763556_81.jpg
1577 ms
1042709784_55.jpg
1596 ms
1240467754_45.jpg
1677 ms
1286250905_57.jpg
1780 ms
1400806594_129.jpg
1816 ms
1254704334_84.jpg
1909 ms
1267534052_66.jpg
1922 ms
1278310139_126.jpg
1963 ms
998703893_28.jpg
2056 ms
1365733062_80.jpg
2160 ms
1133935710_244.jpg
2196 ms
986198849_27.jpg
2217 ms
1265082350_1186.jpg
2251 ms
kenken-comic-banner100x.gif
2319 ms
ca-pub-2455933596343571.js
54 ms
zrt_lookup.html
145 ms
show_ads_impl.js
91 ms
hm_bn.gif
2592 ms
widgets.js
37 ms
plusone.js
228 ms
pla
114 ms
like.php
184 ms
ads
474 ms
osd.js
19 ms
ads
276 ms
cb=gapi.loaded_0
138 ms
cb=gapi.loaded_1
179 ms
fastbutton
349 ms
ads
388 ms
374 ms
rU2ubZ6l1Q5.js
511 ms
LVx-xkvaJ0b.png
562 ms
kenken_banner_20150414.gif
2189 ms
ads
321 ms
tenpodesign-kenken.gif
2151 ms
ads
393 ms
ads
418 ms
analytics.js
101 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
111 ms
like.php
104 ms
ads
240 ms
1307690472_3.jpg
2206 ms
1174882963_1.jpg
2100 ms
1285302828_1.jpg
2157 ms
976513029_591.jpg
2361 ms
postmessageRelay
98 ms
collect
18 ms
tweet_button.6a78875565a912489e9aef879c881358.ja.html
18 ms
abg.js
35 ms
api.js
75 ms
core:rpc:shindig.random:shindig.sha1.js
95 ms
2536007149-postmessagerelay.js
44 ms
cb=gapi.loaded_0
74 ms
cb=gapi.loaded_1
60 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
198 ms
__336_280.jpg
188 ms
sbhK2lTE.js
71 ms
1206493504_853.jpg
2202 ms
reset.css
134 ms
entry-button.css
139 ms
s
72 ms
m_js_controller.js
72 ms
googlelogo_color_112x36dp.png
190 ms
3406149572173005005
141 ms
x_button_blue2.png
141 ms
13931095799453922128
207 ms
cTrvNaRi.html
106 ms
1233204004_753.jpg
2209 ms
17208012729271950025
170 ms
12791075895705762602
86 ms
bbtn-s_v3.png
12 ms
t_1454468548.jpg
2137 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
12 ms
t_1455268622.jpg
2170 ms
info.gif
2161 ms
ken.gif
2231 ms
cate_arrow.gif
2233 ms
jot.html
3 ms
activeview
14 ms
activeview
16 ms
activeview
21 ms
activeview
19 ms
kenchikukenken.co.jp 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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
kenchikukenken.co.jp 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
kenchikukenken.co.jp 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
Tap targets are not sized appropriately
JA
JA
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kenchikukenken.co.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 Kenchikukenken.co.jp main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
kenchikukenken.co.jp
Open Graph data is detected on the main page of Kenchikukenken. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: