12.3 sec in total
2.4 sec
9.7 sec
236 ms
Click here to check amazing YUMI Ng content for Japan. Otherwise, check out these important facts you probably never knew about yuming.co.jp
<こちらはシンガーソングライター松任谷由実“ユーミン”のオフィシャルサイト「Yumi Matsutoya Of […]
Visit yuming.co.jpWe analyzed Yuming.co.jp page load time and found that the first response time was 2.4 sec and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
yuming.co.jp performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value14.4 s
0/100
25%
Value15.0 s
1/100
10%
Value6,490 ms
0/100
30%
Value0.202
61/100
15%
Value32.2 s
0/100
10%
2394 ms
1188 ms
22 ms
353 ms
355 ms
Our browser made a total of 100 requests to load all elements on the main page. We found that 76% of them (76 requests) were addressed to the original Yuming.co.jp, 4% (4 requests) were made to Platform.twitter.com and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Yuming.co.jp.
Page size can be reduced by 715.8 kB (44%)
1.6 MB
912.9 kB
In fact, the total size of Yuming.co.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. 45% of websites need less resources to load. Images take 785.1 kB which makes up the majority of the site volume.
Potential reduce by 38.0 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 38.0 kB or 77% of the original size.
Potential reduce by 102.4 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, YUMI Ng needs image optimization as it can save up to 102.4 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 287.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 287.7 kB or 64% of the original size.
Potential reduce by 287.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. Yuming.co.jp needs all CSS files to be minified and compressed as it can save up to 287.8 kB or 84% of the original size.
Number of requests can be reduced by 43 (45%)
95
52
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of YUMI Ng. 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 from 10 to 1 for CSS and as a result speed up the page load time.
yuming.co.jp
2394 ms
style.css
1188 ms
css
22 ms
tweets.css
353 ms
colorbox.css
355 ms
facebox2.css
422 ms
jquery.js
1353 ms
facebox2.js
916 ms
comment-reply.min.js
727 ms
wide_open_nb_blue.css
1016 ms
cforms.js
1169 ms
wpsf-js.php
872 ms
swfobject.js
996 ms
jquery.min.js
31 ms
jquery.mousewheel.js
1110 ms
jquery.jscrollpane.min.js
1593 ms
jquery.slider.min.js
1273 ms
lib.js
1163 ms
main.js
1538 ms
jquery.colorbox.1.3.32.js
1427 ms
calendar.css
1156 ms
ga.js
31 ms
background.png
573 ms
main.png
1259 ms
title.png
728 ms
Y-MODE9.jpg
1093 ms
wpsf-img.php
490 ms
SS2016.jpg
1002 ms
8dd224ae300f33b1851195b7c5ad5e57.jpg
1356 ms
4ac4ca027300ab8eec868240a4d523fd.jpg
1479 ms
Little-Prince.jpg
1757 ms
link_ymode.png
1318 ms
yblink.jpg
2031 ms
02.jpg
1775 ms
disco_icon.png
1695 ms
yumicat_normal.png
1920 ms
rss.png
1859 ms
yfc_join_us.png
2239 ms
LP_Poster.0820.ol_.jpg
2643 ms
sorayumi_icon-55x55.jpg
2137 ms
4f1b9d4a8673e89f20d6ce92b30ffb3c-55x55.jpg
2241 ms
onair.png
2294 ms
banner_yumingchord.png
2622 ms
banner_yuming371.png
2511 ms
banner_saikiraisan.png
2752 ms
banner_emi.png
2595 ms
banner_itunes_ma.png
2648 ms
facebookpage.png
2872 ms
yumingstaff_twitter.png
2944 ms
eclat_banner.png
2976 ms
c20949a91d49b324d46a4f7d698db968.jpg
3329 ms
littleprince_sbanner.jpg
3023 ms
GDE.jpg
3320 ms
8dd224ae300f33b1851195b7c5ad5e57.jpg
3431 ms
SS2016.jpg
3524 ms
Y-MODE9.jpg
3662 ms
iframe_api
172 ms
navi_button.png
3732 ms
cornerframebg.png
4000 ms
widgets.js
126 ms
inpage_linkid.js
117 ms
9vYsg5VgPHKK8SXYbf3sMrg27BfaRSB61e9iDGqjWqk.ttf
118 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
17 ms
__utm.gif
19 ms
www-widgetapi.js
65 ms
syndication
110 ms
527863233541967872
239 ms
Fqd5w_LIONU
72 ms
www-embed-player-vflZsBgOl.css
24 ms
www-embed-player.js
53 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
50 ms
ad_status.js
51 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
164 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
234 ms
information.png
3408 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
7 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
14 ms
Twitter_normal.png
255 ms
_YFC____normal.jpg
183 ms
tweet.png
3218 ms
goods.png
3115 ms
goodscopy.png
3041 ms
yfc.png
3013 ms
jot
26 ms
photocartoon.png
3091 ms
sorayumi.png
3106 ms
sorayumicopy.png
2929 ms
otakara.png
2922 ms
otakaracopy.png
2702 ms
hajimemashita.png
2711 ms
uso_balloon.png
3021 ms
footerback.png
2826 ms
loading.gif
3132 ms
closelabel.gif
2740 ms
loading.gif
2646 ms
tl.png
2599 ms
b.png
2816 ms
tr.png
2845 ms
bl.png
2621 ms
br.png
2549 ms
yuming.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
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Image elements do not have [alt] attributes
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>).
yuming.co.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
yuming.co.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Yuming.co.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 Yuming.co.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.
yuming.co.jp
Open Graph data is detected on the main page of YUMI Ng. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: