8.1 sec in total
1 sec
6 sec
1 sec
Welcome to webdedb.com homepage info - get ready to check WEBdeDB best content for Japan right away, or after learning these important things about webdedb.com
WEBdeDB ではホームページ制作を行う全てのクリエーターの為に、「いいデザインとは何か?」を検証し、参考にしていただく為のDBサイトです。ユーザー様からのWEBデザイン評価によりWEBデザインの検証を行っております。
Visit webdedb.comWe analyzed Webdedb.com page load time and found that the first response time was 1 sec and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
webdedb.com performance score
name
value
score
weighting
Value2.6 s
62/100
10%
Value7.0 s
6/100
25%
Value4.5 s
73/100
10%
Value260 ms
84/100
30%
Value0
100/100
15%
Value11.3 s
19/100
10%
1003 ms
534 ms
548 ms
554 ms
552 ms
Our browser made a total of 174 requests to load all elements on the main page. We found that 73% of them (127 requests) were addressed to the original Webdedb.com, 7% (12 requests) were made to Static.xx.fbcdn.net and 3% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Webdedb.com.
Page size can be reduced by 178.7 kB (16%)
1.1 MB
913.9 kB
In fact, the total size of Webdedb.com main page is 1.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. 50% of websites need less resources to load. Images take 849.5 kB which makes up the majority of the site volume.
Potential reduce by 95.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 95.3 kB or 89% of the original size.
Potential reduce by 1.5 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. WEBdeDB images are well optimized though.
Potential reduce by 68.7 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 68.7 kB or 58% of the original size.
Potential reduce by 13.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. Webdedb.com needs all CSS files to be minified and compressed as it can save up to 13.2 kB or 79% of the original size.
Number of requests can be reduced by 85 (50%)
171
86
The browser has sent 171 CSS, Javascripts, AJAX and image requests in order to completely render the main page of WEBdeDB. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
webdedb.com
1003 ms
base.css
534 ms
contents.css
548 ms
gb_styles.css
554 ms
rating.css
552 ms
AJS.js
719 ms
AJS_fx.js
556 ms
gb_scripts.js
693 ms
jkl-noerror.js
706 ms
reflection.js
732 ms
behavior.js
732 ms
rating.js
734 ms
ip.cgi
929 ms
jjquery-1.7.1.min.js
1054 ms
jquery.lazyload.js
892 ms
tanktic.js
595 ms
badge.js
11 ms
logo.gif
201 ms
0.gif
370 ms
0.gif
330 ms
0.gif
373 ms
0.gif
1070 ms
0.gif
390 ms
0.gif
1040 ms
0.gif
349 ms
bgt
336 ms
bgt
1060 ms
0.gif
378 ms
0.gif
360 ms
0.gif
361 ms
0.gif
389 ms
0.gif
356 ms
0.gif
399 ms
0.gif
1040 ms
0.gif
316 ms
0.gif
323 ms
0.gif
322 ms
0.gif
397 ms
bg_contents.gif
246 ms
bg_header.gif
345 ms
yakumono.gif
162 ms
bg_h3.gif
346 ms
bg_sitelink.gif
245 ms
bnr_160_110.gif
340 ms
bg_sitelink2.gif
347 ms
icon_sitelink1.gif
393 ms
icon_sitelink3.gif
369 ms
01.jpg
648 ms
icon_sitelink2.gif
594 ms
topic_banner.jpg
1026 ms
01.jpg
840 ms
icon_sitelink1-2.gif
597 ms
icon_sitelink3-2.gif
601 ms
icon_sitelink2-2.gif
690 ms
01.jpg
1716 ms
01.jpg
1561 ms
01.jpg
1283 ms
01.jpg
1777 ms
01.jpg
1185 ms
01.jpg
1534 ms
01.jpg
1354 ms
01.jpg
1442 ms
01.jpg
1695 ms
01.jpg
1602 ms
01.jpg
1706 ms
01.jpg
1728 ms
01.jpg
1763 ms
01.jpg
2102 ms
01.jpg
1878 ms
01.jpg
2379 ms
01.jpg
1897 ms
01.jpg
1922 ms
01.jpg
1941 ms
0.gif
339 ms
bg_sitelink.gif
284 ms
col1.gif
350 ms
col2.gif
359 ms
col3.gif
355 ms
col4.gif
378 ms
col5.gif
374 ms
col6.gif
572 ms
col7.gif
579 ms
col8.gif
582 ms
col9.gif
583 ms
col10.gif
588 ms
col11.gif
585 ms
icon_y.gif
599 ms
append.gif
697 ms
delicious.small.gif
698 ms
clip_16_16_b.gif
700 ms
addclip_icn.gif
746 ms
icon_pencil.gif
744 ms
bgt
718 ms
like.php
134 ms
1.png
36 ms
01.jpg
1938 ms
ga.js
31 ms
01.jpg
2087 ms
likebox.php
176 ms
analytics.js
23 ms
__utm.gif
57 ms
__utm.gif
55 ms
01.jpg
1854 ms
fy8tT2klpgR.js
176 ms
01.jpg
1879 ms
LVx-xkvaJ0b.png
150 ms
collect
14 ms
McLpmVM3wCm.css
88 ms
r6Aw0SZFbhw.css
79 ms
FAHeNGXgPup.js
107 ms
FJmpeSpHpjS.js
141 ms
0wM5s1Khldu.js
92 ms
1bNoFZUdlYZ.js
94 ms
01.jpg
1899 ms
01.jpg
1916 ms
01.jpg
2101 ms
01.jpg
1968 ms
01.jpg
2043 ms
01.jpg
2021 ms
168444_130678256994254_3403159_n.jpg
120 ms
10157358_927146897373107_813480215035047306_n.jpg
65 ms
11406991_662487343894635_5003085857862994264_n.jpg
77 ms
12806003_818488618277781_1935268440604485973_n.jpg
78 ms
wL6VQj7Ab77.png
42 ms
s7jcwEQH7Sx.png
44 ms
01.jpg
2448 ms
01.jpg
1885 ms
01.jpg
1956 ms
01.jpg
1937 ms
I6-MnjEovm5.js
26 ms
pQrUxxo5oQp.js
37 ms
01.jpg
1892 ms
01.jpg
1777 ms
01.jpg
1632 ms
01.jpg
1710 ms
01.jpg
1475 ms
01.jpg
1397 ms
01.jpg
1339 ms
01.jpg
1290 ms
01.jpg
1366 ms
01.jpg
1328 ms
01.jpg
1262 ms
01.jpg
1288 ms
01.jpg
1519 ms
01.jpg
1363 ms
01.jpg
1341 ms
01.jpg
1353 ms
01.jpg
1287 ms
01.jpg
1850 ms
01.jpg
1355 ms
01.jpg
1335 ms
01.jpg
1241 ms
01.jpg
1252 ms
01.jpg
1467 ms
01.jpg
1336 ms
01.jpg
1221 ms
01.jpg
1238 ms
bg_l.jpg
1283 ms
bg_h4.gif
1330 ms
bg_cat_li.gif
1256 ms
tic_bg.gif
1305 ms
tic_title.gif
1304 ms
bg_footermenu.gif
1307 ms
bg_h4-2.gif
1390 ms
bg_h4-2-2.gif
1314 ms
bg_right.gif
1301 ms
bg_right_footer.gif
1304 ms
bg_r.jpg
1306 ms
bg_footermenu2.gif
1262 ms
bg_copyright.gif
1287 ms
w_close.gif
201 ms
header_bg.gif
194 ms
g_close.gif
184 ms
indicator.gif
196 ms
webdedb.com 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
<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
<object> elements do not have alternate text
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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>).
webdedb.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Browser errors were logged to the console
webdedb.com SEO score
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
Document uses plugins
JA
N/A
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Webdedb.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Webdedb.com main page’s claimed encoding is shift_jis. 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.
webdedb.com
Open Graph description is not detected on the main page of WEBdeDB. 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: