6.1 sec in total
541 ms
5.3 sec
194 ms
Welcome to senha-yuzu.jp homepage info - get ready to check Senha Yuzu best content for Japan right away, or after learning these important things about senha-yuzu.jp
ゆず オフィシャルウェブサイト
Visit senha-yuzu.jpWe analyzed Senha-yuzu.jp page load time and found that the first response time was 541 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
senha-yuzu.jp performance score
name
value
score
weighting
Value6.8 s
1/100
10%
Value10.2 s
0/100
25%
Value6.8 s
35/100
10%
Value80 ms
99/100
30%
Value0
100/100
15%
Value7.1 s
52/100
10%
541 ms
326 ms
329 ms
68 ms
327 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 51% of them (67 requests) were addressed to the original Senha-yuzu.jp, 17% (22 requests) were made to Pbs.twimg.com and 14% (18 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Senha-yuzu.jp.
Page size can be reduced by 119.0 kB (8%)
1.6 MB
1.5 MB
In fact, the total size of Senha-yuzu.jp main page is 1.6 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. 65% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 20.2 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 20.2 kB or 74% of the original size.
Potential reduce by 26.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. Senha Yuzu images are well optimized though.
Potential reduce by 55.4 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 55.4 kB or 38% of the original size.
Potential reduce by 16.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. Senha-yuzu.jp needs all CSS files to be minified and compressed as it can save up to 16.4 kB or 81% of the original size.
Number of requests can be reduced by 75 (60%)
125
50
The browser has sent 125 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Senha Yuzu. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
senha-yuzu.jp
541 ms
screen.css
326 ms
index.css
329 ms
jquery.min.js
68 ms
gloval.js
327 ms
xmlHttpRequestObj.js
327 ms
newsList.js
352 ms
tvList.js
352 ms
radioList.js
651 ms
webList.js
652 ms
magazineList.js
653 ms
othersList.js
654 ms
common.js
678 ms
btn_buy.js
678 ms
jquery.easing.1.3.js
978 ms
jquery.bxSlider.min.js
977 ms
bxSlider.js
979 ms
DD_belatedPNG_0.0.8a-min.js
1003 ms
header.js
1002 ms
footer.js
1027 ms
conversion.js
21 ms
s_retargeting.js
524 ms
reset.css
980 ms
module.css
980 ms
bg_body.gif
165 ms
bnr_towablog.png
526 ms
slide_yuzunomi01.jpg
652 ms
slide_towa.jpg
817 ms
slide_goods_towa.jpg
981 ms
bnr_towa_album.jpg
527 ms
btn_sp.gif
490 ms
tle_news.gif
814 ms
more.gif
852 ms
tle_media.gif
853 ms
tle_facebook.gif
978 ms
facebook.gif
1141 ms
tle_twitter.gif
1142 ms
twitter.gif
1178 ms
sdk.js
28 ms
header_detail.js
1198 ms
59 ms
xd_arbiter.php
45 ms
xd_arbiter.php
67 ms
logo.gif
164 ms
bg_hd_login.gif
330 ms
yuzunowa.gif
328 ms
btn_login.gif
331 ms
btn_regist.gif
331 ms
btn_remind.gif
361 ms
youtube.gif
688 ms
news.gif
848 ms
media.gif
848 ms
live.gif
849 ms
discography.gif
849 ms
biography.gif
850 ms
goods.gif
1013 ms
fanclub.gif
1174 ms
archive.gif
1173 ms
yuuzmoba.gif
1177 ms
remote_xml.php
1713 ms
remote_xml.php
1206 ms
remote_xml.php
1344 ms
remote_xml.php
1509 ms
remote_xml.php
1504 ms
widgets.js
5 ms
senha.png
1484 ms
icon_pagetop.gif
1528 ms
ga.js
32 ms
__utm.gif
27 ms
41 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
33 ms
dot.png
1586 ms
icon_link_active.png
1729 ms
icon_link.png
1747 ms
51 ms
syndication
95 ms
345460060371156992
252 ms
page.php
203 ms
zeObnr8mnaC.css
49 ms
DTo1WfVsqMQ.css
67 ms
gPLjjXw4kx2.css
75 ms
LLJ7pJgsgEx.css
79 ms
_rx8naC75Dy.js
110 ms
t-KLv3gqZy0.js
82 ms
uLtKx7ldlvR.js
123 ms
xoyOB9tkUFt.js
93 ms
wyIfBc7KBcg.js
122 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
10 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
13 ms
5AiUspVz_normal.png
248 ms
_1LA_l-E_normal.jpg
242 ms
tAI-hgHi_normal.jpg
242 ms
srtwitter-logo_normal.jpg
246 ms
G_GSKBH3_normal.jpg
244 ms
IlUWwa_R_normal.jpeg
243 ms
V_tkhCfr_normal.png
246 ms
BkG8YMB6_normal.jpeg
242 ms
idvp5jki_normal.png
245 ms
CcWodTlUcAE5cbg.jpg:large
256 ms
CcTr43xUkAALvxL.jpg
262 ms
CbOk04aVAAAQE_X.jpg:large
264 ms
Cb8r6V7UcAED1rK.jpg:small
264 ms
Cb8rA5DUAAQpo_9.jpg:small
262 ms
Cbyfn_sUUAANjmU.jpg:small
328 ms
CbyefVEUcAEnR4h.jpg:small
372 ms
Cbxr0Y0UAAAfa64.jpg:small
264 ms
CbxgrNeUYAAvvs2.jpg:small
266 ms
CbtOEzpUEAAxj3x.jpg:small
284 ms
CbtPKtaUAAEJhcV.jpg:small
316 ms
CbotqFoUAAIaDh-.jpg:small
312 ms
CbkNN6nVAAAoWc4.jpg:small
272 ms
12108115_947172782007821_3766919993880565082_n.jpg
232 ms
safe_image.php
228 ms
lRyN50VcaFW.js
91 ms
12795571_1013338705391228_1228885302959746171_n.jpg
139 ms
12715677_1704665903079672_927133411573182298_n.jpg
153 ms
12744329_1704665949746334_1532761959748029091_n.jpg
187 ms
12728847_1008073942584371_5393599777683012866_n.jpg
161 ms
ZS8q378OQsF.png
92 ms
wL6VQj7Ab77.png
89 ms
CSXXCvknpgK.png
91 ms
7NEHk19WerA.png
91 ms
R9a_DtVRZgv.js
16 ms
cUDgRFxaoIk.js
17 ms
0JBr1QHp8Gi.js
17 ms
kDOzhTr2W91.js
17 ms
jot
26 ms
tv.gif
625 ms
radio.gif
514 ms
magazine.gif
515 ms
web.gif
551 ms
print.css
164 ms
senha-yuzu.jp accessibility score
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
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
senha-yuzu.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
senha-yuzu.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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Senha-yuzu.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 Senha-yuzu.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.
senha-yuzu.jp
Open Graph description is not detected on the main page of Senha Yuzu. 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: