18.7 sec in total
625 ms
17.3 sec
742 ms
Visit y-pure.com now to see the best up-to-date Y Pure content for Japan and also check out these interesting facts you probably never knew about y-pure.com
Visit y-pure.comWe analyzed Y-pure.com page load time and found that the first response time was 625 ms and then it took 18 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.
y-pure.com performance score
name
value
score
weighting
Value3.0 s
49/100
10%
Value6.7 s
8/100
25%
Value6.7 s
35/100
10%
Value0 ms
100/100
30%
Value0.259
48/100
15%
Value3.7 s
90/100
10%
625 ms
1448 ms
667 ms
31 ms
52 ms
Our browser made a total of 103 requests to load all elements on the main page. We found that 54% of them (56 requests) were addressed to the original Y-pure.com, 14% (14 requests) were made to Ing.y-pure.com and 11% (11 requests) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (13.6 sec) belongs to the original domain Y-pure.com.
Page size can be reduced by 650.8 kB (12%)
5.4 MB
4.7 MB
In fact, the total size of Y-pure.com main page is 5.4 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 4.6 MB which makes up the majority of the site volume.
Potential reduce by 85.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 85.2 kB or 90% of the original size.
Potential reduce by 126.7 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. Y Pure images are well optimized though.
Potential reduce by 405.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 405.8 kB or 61% of the original size.
Potential reduce by 33.0 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. Y-pure.com needs all CSS files to be minified and compressed as it can save up to 33.0 kB or 82% of the original size.
Number of requests can be reduced by 24 (25%)
96
72
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Y Pure. 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 7 to 1 for CSS and as a result speed up the page load time.
y-pure.com
625 ms
www.y-pure.com
1448 ms
index.css
667 ms
jquery.min.js
31 ms
jquery-ui.min.js
52 ms
mosaic.1.0.1.js
335 ms
index.js
335 ms
js
43 ms
mapstyle.js
340 ms
perfect-scrollbar.js
910 ms
slick.css
333 ms
slick.min.js
886 ms
html5reset.css
235 ms
reset-fonts-grids.css
533 ms
reset-min.css
361 ms
caption.css
531 ms
analytics.js
20 ms
1752_thumbnail0pc.jpg
4214 ms
bg_body.png
9635 ms
icon1.png
499 ms
icon5.png
520 ms
icon9.png
519 ms
new.png
376 ms
icon3.png
677 ms
icon7.png
914 ms
icon8.png
1051 ms
icon6.png
1066 ms
icon4.png
1101 ms
icon2.png
1173 ms
1814_thumbnail0pc.jpg
1216 ms
1809_thumbnail0pc.jpg
2249 ms
1810_thumbnail0pc.jpg
1221 ms
1812_thumbnail0pc.jpg
1572 ms
1811_thumbnail0pc.jpg
1732 ms
1798_thumbnail0pc.jpg
2859 ms
1796_thumbnail0pc.jpg
2904 ms
1791_thumbnail0pc.jpg
3376 ms
1186_thumbnail0pc.jpg
3392 ms
1770_thumbnail0pc.jpg
4017 ms
1527_thumbnail0pc.jpg
5024 ms
1756_thumbnail0pc.jpg
4257 ms
1755_thumbnail0pc.jpg
7095 ms
collect
11 ms
collect
66 ms
ga-audiences
41 ms
f_btn_pg01.png
1152 ms
f_btn_pure.png
1286 ms
f_btn_amuse.png
1471 ms
f_btn_pg02.png
1330 ms
f_btn_fantasy.png
1557 ms
cara_l.png
13594 ms
heading_h2.png
2298 ms
logo.png
2199 ms
enter.png
2362 ms
exit.png
2111 ms
r18.png
2692 ms
bg_heading.png
2569 ms
s_news.png
3013 ms
btn_more.png
2893 ms
list02.png
2925 ms
s_newface.png
3576 ms
progress.gif
3462 ms
bg_footer.png
3641 ms
f_btn_01.png
4130 ms
f_btn_02.png
4040 ms
up.png
4138 ms
f_cast.png
10768 ms
s_map.png
4576 ms
icon01.png
4481 ms
slick.woff
4503 ms
f_logo.png
5510 ms
s_mobile.png
5003 ms
f_qr.png
5293 ms
icon02.png
5336 ms
icon03.png
5485 ms
list01.png
5274 ms
common.js
18 ms
util.js
36 ms
stats.js
34 ms
AuthenticationService.Authenticate
239 ms
map.js
9 ms
marker.js
37 ms
onion.js
19 ms
ViewportInfoService.GetViewportInfo
42 ms
controls.js
38 ms
transparent.png
41 ms
css
78 ms
google4.png
63 ms
ico.png
344 ms
mapcnt6.png
48 ms
sv5.png
48 ms
vt
118 ms
vt
116 ms
vt
118 ms
tmapctrl.png
27 ms
cb_scout5.png
36 ms
tmapctrl4.png
36 ms
imgs8.png
36 ms
google_white5.png
35 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
24 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
58 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
58 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
58 ms
y-pure.com 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.
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
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
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.
y-pure.com 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
y-pure.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
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 Y-pure.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 Y-pure.com 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.
y-pure.com
Open Graph description is not detected on the main page of Y Pure. 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: