73.1 sec in total
4.7 sec
62.3 sec
6.1 sec
Welcome to d-will.jp homepage info - get ready to check D Will best content for Japan right away, or after learning these important things about d-will.jp
Visit d-will.jpWe analyzed D-will.jp page load time and found that the first response time was 4.7 sec and then it took 68.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 11 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
d-will.jp performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value6.2 s
11/100
25%
Value9.9 s
9/100
10%
Value340 ms
74/100
30%
Value0.573
12/100
15%
Value12.9 s
13/100
10%
4742 ms
1258 ms
1043 ms
1541 ms
1798 ms
Our browser made a total of 161 requests to load all elements on the main page. We found that 93% of them (150 requests) were addressed to the original D-will.jp, 2% (3 requests) were made to Platform.twitter.com and 1% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (20.3 sec) belongs to the original domain D-will.jp.
Page size can be reduced by 434.6 kB (5%)
8.0 MB
7.6 MB
In fact, the total size of D-will.jp main page is 8.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. 55% of websites need less resources to load. Images take 7.8 MB which makes up the majority of the site volume.
Potential reduce by 73.9 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 73.9 kB or 85% of the original size.
Potential reduce by 284.9 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. D Will images are well optimized though.
Potential reduce by 22.0 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 22.0 kB or 46% of the original size.
Potential reduce by 53.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. D-will.jp needs all CSS files to be minified and compressed as it can save up to 53.8 kB or 82% of the original size.
Number of requests can be reduced by 31 (21%)
149
118
The browser has sent 149 CSS, Javascripts, AJAX and image requests in order to completely render the main page of D Will. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
d-will.jp
4742 ms
fbevents.js
1258 ms
reset.css
1043 ms
header_fotter.css
1541 ms
side.css
1798 ms
main_col.css
1617 ms
content_box.css
460 ms
color.css
692 ms
form.css
1721 ms
button.css
1253 ms
tellerlist.css
1666 ms
reviewpoint.css
2066 ms
css
148 ms
jquery.js
477 ms
import.js
1835 ms
264 ms
tab.js
243 ms
easing.js
230 ms
slider.js
1830 ms
ticker.js
479 ms
DD_belatedPNG.js
475 ms
mousewheel.js
386 ms
smoothScroll.js
393 ms
tinyscrollbar.js
601 ms
script.js
646 ms
s_retargeting.js
2183 ms
bg.png
739 ms
h-bg.png
634 ms
rogo.png
640 ms
top-tell.png
1519 ms
slide-1.jpg
9778 ms
slide-2.jpg
7683 ms
slide-3.jpg
5225 ms
slide-4.jpg
5588 ms
slide-5.jpg
3110 ms
slide-6.jpg
7936 ms
g_menu_nonmem.png
9859 ms
tell.png
9123 ms
top_banner.png
20256 ms
expose_title.png
10306 ms
expose_title_sup_01.png
10072 ms
name-bg.png
9295 ms
list-sup1.png
9474 ms
operator_9_1.jpg
11682 ms
list-sup3.png
9964 ms
tellblock2.png
11876 ms
mv-door3.png
10355 ms
mv-door4.png
11800 ms
syousai-block.png
12215 ms
operator_9_1.jpg
16133 ms
tellblock3.png
12077 ms
operator_9_1.jpg
17060 ms
operator_9_1.jpg
13973 ms
operator_9_1.jpg
16123 ms
operator_9_1.jpg
15850 ms
tellblock1.png
15610 ms
operator_9_1.jpg
16373 ms
operator_9_1.jpg
20205 ms
operator_9_1.jpg
17625 ms
operator_9_1.jpg
20201 ms
operator_9_1.jpg
20124 ms
operator_9_1.jpg
19642 ms
nn_kutikomi_title.png
19075 ms
widgets.js
272 ms
kuchikomi.png
19632 ms
ga.js
157 ms
operator_9_1.jpg
19541 ms
__utm.gif
183 ms
button.71000885400e222c3c0eec823f8f93f0.js
283 ms
follow_button.fd774b599f565016d763dd860cb31c79.ja.html
153 ms
star.png
19751 ms
jot
296 ms
iine.png
17625 ms
operator_9_1.jpg
17979 ms
operator_9_1.jpg
19677 ms
operator_9_1.jpg
16328 ms
operator_9_1.jpg
16615 ms
all_tw_k_btn.png
15196 ms
b-tell.png
19953 ms
fav.png
14177 ms
register.png
19366 ms
bg.png
14746 ms
title.png
14524 ms
submit.png
14992 ms
twitter.png
14687 ms
facebook.png
14421 ms
youtube.png
13301 ms
ameba.png
13386 ms
s-faq.png
15130 ms
side_rank_neo.png
13741 ms
sq.png
13211 ms
t_t_rank_01.png
11635 ms
t_t_rank_02.png
10016 ms
t_t_rank_03.png
9949 ms
t_t_rank_04.png
9712 ms
neo_rank1.png
10835 ms
operator_9_1.jpg
10480 ms
neo_rank2.png
9062 ms
operator_9_1.jpg
10100 ms
neo_rank3.png
7396 ms
operator_9_1.jpg
9539 ms
neo_rank4.png
6984 ms
operator_9_1.jpg
8209 ms
neo_rank5.png
7221 ms
operator_9_1.jpg
9819 ms
neo_rank6.png
8632 ms
operator_9_1.jpg
12044 ms
neo_rank7.png
8796 ms
operator_9_1.jpg
10779 ms
neo_rank8.png
6481 ms
operator_9_1.jpg
9233 ms
neo_rank9.png
5892 ms
operator_9_1.jpg
10089 ms
neo_rank10.png
5600 ms
operator_9_1.jpg
8556 ms
operator_9_1.jpg
8308 ms
operator_9_1.jpg
9969 ms
operator_9_1.jpg
10553 ms
operator_9_1.jpg
14546 ms
operator_9_1.jpg
9085 ms
operator_9_1.jpg
13176 ms
operator_9_1.jpg
11007 ms
operator_9_1.jpg
11137 ms
operator_9_1.jpg
12690 ms
operator_9_1.jpg
12337 ms
operator_9_1.jpg
12272 ms
operator_9_1.jpg
12118 ms
operator_9_1.jpg
14593 ms
operator_9_1.jpg
13824 ms
operator_9_1.jpg
12870 ms
operator_9_1.jpg
16859 ms
operator_9_1.jpg
12597 ms
operator_9_1.jpg
15137 ms
operator_9_1.jpg
14005 ms
side_worriescat_banner.png
15871 ms
side_fortunecat_banner.png
13926 ms
niconico_side.png
16257 ms
baiking_side.png
17473 ms
w_side.png
16654 ms
iyashi_side.png
18165 ms
kirara_ame_side.png
17179 ms
ringo_side.png
17041 ms
kirara_side.png
19471 ms
side_nav_bn.png
18431 ms
side_nav_bn.png
20178 ms
side_nav_bn.png
19340 ms
side_nav_bn.png
20221 ms
side_nav_bn.png
18787 ms
side_media.png
16826 ms
s-first.png
17182 ms
s-fukuen.png
18081 ms
reputatio-title.png
16092 ms
reputatio-icon-m.png
15869 ms
reputatio-icon-a.png
15640 ms
title.png
14891 ms
icon_twitter.png
14305 ms
icon_twitter_bird.png
14036 ms
side_nav_180.png
18049 ms
bosyuu_link_225.png
17634 ms
g-bg.png
12688 ms
g-bottom.png
12834 ms
d-will.jp 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
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
d-will.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
d-will.jp 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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise D-will.jp 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 D-will.jp 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.
d-will.jp
Open Graph description is not detected on the main page of D Will. 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: