8.8 sec in total
1.7 sec
6.4 sec
679 ms
Click here to check amazing 21 Wife content for Japan. Otherwise, check out these important facts you probably never knew about 21wife.com
Visit 21wife.comWe analyzed 21wife.com page load time and found that the first response time was 1.7 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.
21wife.com performance score
name
value
score
weighting
Value1.9 s
87/100
10%
Value5.5 s
19/100
25%
Value3.4 s
89/100
10%
Value150 ms
95/100
30%
Value0.005
100/100
15%
Value5.3 s
73/100
10%
1659 ms
1513 ms
438 ms
188 ms
558 ms
Our browser made a total of 229 requests to load all elements on the main page. We found that 25% of them (57 requests) were addressed to the original 21wife.com, 29% (66 requests) were made to K-y.pw and 9% (21 requests) were made to Dl-city.net. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain 21wife.com.
Page size can be reduced by 156.0 kB (32%)
491.5 kB
335.5 kB
In fact, the total size of 21wife.com main page is 491.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Images take 370.5 kB which makes up the majority of the site volume.
Potential reduce by 45.5 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 45.5 kB or 81% of the original size.
Potential reduce by 70.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. Obviously, 21 Wife needs image optimization as it can save up to 70.3 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 35.8 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 35.8 kB or 60% of the original size.
Potential reduce by 4.4 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. 21wife.com needs all CSS files to be minified and compressed as it can save up to 4.4 kB or 77% of the original size.
Number of requests can be reduced by 93 (41%)
225
132
The browser has sent 225 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 21 Wife. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
21wife.com
1659 ms
style.css
1513 ms
fontsize.js
438 ms
15205.js
188 ms
l.j
558 ms
bana.css
692 ms
analytics.js
147 ms
200x40.gif
1023 ms
bt_logo.gif
387 ms
banner_20040_1.png
586 ms
bnr46860.jpg
1407 ms
banner200_40.gif
462 ms
bnr_200_40.gif
619 ms
200x40_bann.gif
1205 ms
200x40_bann.gif
1157 ms
bnr_200_40.gif
617 ms
banner_200_40.jpg
604 ms
tokyo_200_40.jpg
1133 ms
88x31_gotanda.gif
616 ms
468x60_ani.gif
1552 ms
88dp.gif
604 ms
rn468_60.gif
964 ms
88x31.gif
610 ms
bana_20040.gif
365 ms
88x31.gif
613 ms
fubaito20040_2.gif
606 ms
fzk200_40r.gif
769 ms
88_31.gif
947 ms
ban88.gif
350 ms
200_40.gif
667 ms
b_200_40.gif
750 ms
88_31.gif
1348 ms
dj200_40br.gif
864 ms
vanilla468-60.gif
828 ms
g00.gif
685 ms
200x40.gif
886 ms
dlcity468.gif
1182 ms
banner_468_60_white.jpg
931 ms
bn-46860-a.gif
944 ms
deliheru_banner_20040.jpg
1534 ms
hu-ou_468-60.gif
1112 ms
fuzokujapan468-60.gif
720 ms
fuzoku_ent_468x60.gif
759 ms
top_bn.gif
1399 ms
dhnavi88-31.gif
1773 ms
banner12_200.gif
2065 ms
tokyo20040_1.gif
949 ms
200x40.gif
797 ms
rank200x40.gif
521 ms
88-31.gif
799 ms
linkb-220x55.gif
919 ms
tm11.gif
942 ms
dl-citytokyo.gif
786 ms
dl-cityclick.gif
795 ms
dl-city01.gif
812 ms
dl-city02.gif
821 ms
dl-city03.gif
828 ms
dl-city04.gif
1176 ms
dl-city05.gif
1191 ms
dl-city06.gif
1214 ms
dl-city07.gif
1217 ms
dl-city08.gif
1234 ms
dl-city09.gif
1571 ms
dl-city010.gif
1568 ms
dl-city011.gif
1620 ms
dl-city012.gif
1639 ms
dl-city020.gif
1648 ms
dl-city014.gif
1644 ms
dl-city015.gif
2047 ms
dl-city016.gif
2067 ms
dl-city017.gif
2119 ms
dl-city018.gif
2099 ms
banner_20040_2.png
553 ms
banner_20040_3_5.png
550 ms
tm10.gif
923 ms
tm9.gif
931 ms
tm8.gif
932 ms
tm7.gif
933 ms
tm6.gif
940 ms
tm5.gif
1110 ms
tm4.gif
1119 ms
tm3.gif
1124 ms
tm2.gif
1125 ms
tm1.gif
1124 ms
tm22.gif
1127 ms
tm21.gif
1301 ms
tm20.gif
1304 ms
tm19.gif
1307 ms
tm18.gif
1309 ms
tm17.gif
1308 ms
tm16.gif
1312 ms
tm15.gif
1491 ms
tm14.gif
1499 ms
tm13.gif
1502 ms
tm12.gif
1501 ms
om11.gif
1503 ms
om10.gif
1504 ms
om9.gif
1686 ms
om8.gif
1695 ms
om7.gif
1701 ms
om6.gif
1700 ms
om5.gif
1702 ms
om4.gif
1731 ms
om3.gif
1925 ms
om2.gif
1987 ms
om1.gif
1989 ms
om22.gif
2388 ms
om21.gif
2393 ms
om20.gif
1994 ms
bt_01.gif
460 ms
bt_02.gif
468 ms
bt_03.gif
469 ms
bt_04.gif
470 ms
bt_05.gif
473 ms
bt_06.gif
688 ms
bt_07.gif
803 ms
bt_08.gif
805 ms
bt_09.gif
812 ms
g01.gif
638 ms
g02.gif
633 ms
g03.gif
640 ms
g04.gif
643 ms
g05.gif
678 ms
g06.gif
975 ms
g07.gif
980 ms
g08.gif
981 ms
g09.gif
991 ms
g10.gif
998 ms
tokyo_bn.gif
1240 ms
kanagawa_bn.gif
1250 ms
saitama_bn.gif
1250 ms
chiba_bn.gif
1256 ms
hokaidou_bn.gif
1257 ms
osaka_bn.gif
1407 ms
hyogo_bn.gif
1419 ms
aichi_bn.gif
1424 ms
miyagi_bn.gif
1438 ms
fukuoka_bn.gif
1439 ms
top_bg.gif
280 ms
top_img1n-2.jpg
809 ms
top_img2-3.jpg
453 ms
top_img3-2.jpg
451 ms
top_btn1.gif
470 ms
top_btn2.gif
469 ms
line10x350.gif
497 ms
line118x10.gif
627 ms
topbanner_chuo.gif
628 ms
topbanner_blank.gif
672 ms
top_map205.png
1970 ms
oss_shop_468_60.gif
1123 ms
hitojuku468x60.jpg
1150 ms
tokyo-deli-ban200-40.gif
803 ms
jukujo-fuzoku-joho-title200-40.gif
869 ms
yorunavi200x40_2.gif
980 ms
fuzoku-info-200-40.jpg
980 ms
linkbana.gif
2155 ms
fuzokujapan88-31.gif
1153 ms
fcol_banner_200_40.jpg
1158 ms
hito_juku_naviban200-40.gif
1328 ms
okusannbana4.gif
1319 ms
title200-40.gif
1328 ms
tokyo-fuzoku-joho-title.jpg
1335 ms
20040[1].gif
1514 ms
dcbn_200x40b.gif
1534 ms
fuzokuten_logo_468-60.jpg
1718 ms
dcbn_shibuya200x40.gif
1519 ms
r30-200-50-01.jpg
1715 ms
200_40-woyag[1].gif
2171 ms
200-40.gif
1776 ms
deriheruokoku-200-40.gif
2153 ms
fuzoku_no_tomo200-40.gif
3886 ms
mrslove200_40.gif
2018 ms
mrs_search200_40_new.gif
2153 ms
88x31_tokyo.gif
528 ms
banner88x31.gif
715 ms
x.gif
249 ms
l79.f
2294 ms
ts.gif
376 ms
bt_background.png
812 ms
200dg[1].gif
2191 ms
collect
34 ms
tuma200-40.gif
2082 ms
deli-net200_40.gif
1892 ms
shinachan200.gif
1913 ms
vip-wife-rank_200x40.gif
2098 ms
vip-deli-rank_200x40.gif
2470 ms
vip-rank_200x40.gif
3382 ms
deri-ou-banner-kanto.gif
1943 ms
200x40.gif
1952 ms
deli_200-40.gif
2119 ms
deliheritengoku(200_40).gif
1990 ms
fu-bee200x40.gif
2238 ms
f_3gyou_com_20040.gif
2150 ms
om19.gif
1219 ms
om18.gif
1262 ms
om17.gif
1261 ms
om16.gif
1267 ms
om15.gif
1404 ms
om14.gif
1437 ms
loveworkbanner_200x40.gif
2055 ms
deliden200x60.gif
2208 ms
om13.gif
1274 ms
om12.gif
1276 ms
qm11.gif
1411 ms
qm10.gif
1460 ms
qm9.gif
1471 ms
qm8.gif
1482 ms
delinetjapanlogo.gif
2116 ms
spacer.gif
2123 ms
qm7.gif
1309 ms
qm6.gif
1308 ms
qm5.gif
1467 ms
qm4.gif
1499 ms
qm3.gif
1509 ms
qm2.gif
1516 ms
qm1.gif
1337 ms
qm22.gif
1331 ms
qm21.gif
1486 ms
qm20.gif
1541 ms
qm19.gif
1555 ms
qm18.gif
1561 ms
qm17.gif
1379 ms
qm16.gif
1370 ms
qm15.gif
1511 ms
qm14.gif
1560 ms
qm13.gif
1580 ms
qm12.gif
1569 ms
top_btn1h.gif
219 ms
top_btn2h.gif
219 ms
21wife.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
Image elements do not have [alt] attributes
Links do not have a discernible name
21wife.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
21wife.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
JA
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 21wife.com 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 21wife.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.
21wife.com
Open Graph description is not detected on the main page of 21 Wife. 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: