7.4 sec in total
744 ms
5.9 sec
749 ms
Welcome to yim.co.jp homepage info - get ready to check Yim best content for Japan right away, or after learning these important things about yim.co.jp
みなとみらいにおでかけなら、横浜ワールドポーターズ。「いろんな世界がここにある」をコンセプトに、ショッピング、美味しいグルメが集結!ランチ・ディナーが美味しいレストラン、映画館等、お子様連れはもちろん、デートでも楽しめます。
Visit yim.co.jpWe analyzed Yim.co.jp page load time and found that the first response time was 744 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
yim.co.jp performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value13.5 s
0/100
25%
Value10.6 s
7/100
10%
Value1,090 ms
24/100
30%
Value0.185
66/100
15%
Value16.4 s
5/100
10%
744 ms
1378 ms
45 ms
372 ms
1086 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 75% of them (73 requests) were addressed to the original Yim.co.jp, 6% (6 requests) were made to Googletagmanager.com and 4% (4 requests) were made to Sp-trk.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Yim.co.jp.
Page size can be reduced by 314.5 kB (11%)
2.8 MB
2.5 MB
In fact, the total size of Yim.co.jp main page is 2.8 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 2.4 MB which makes up the majority of the site volume.
Potential reduce by 48.4 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. This page needs HTML code to be minified as it can gain 22.8 kB, which is 40% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 48.4 kB or 85% of the original size.
Potential reduce by 44.1 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. Yim images are well optimized though.
Potential reduce by 51.3 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 51.3 kB or 41% of the original size.
Potential reduce by 170.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. Yim.co.jp needs all CSS files to be minified and compressed as it can save up to 170.8 kB or 89% of the original size.
Number of requests can be reduced by 50 (53%)
95
45
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yim. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
yim.co.jp
744 ms
www.yim.co.jp
1378 ms
slick.css
45 ms
slick.css
372 ms
style.css
1086 ms
custom.css
545 ms
jquery.min.js
31 ms
slick.min.js
56 ms
progressbar.min.js
41 ms
slick.min.js
558 ms
script.js
748 ms
slider.js
562 ms
custom.js
576 ms
load.js
723 ms
gtm.js
153 ms
top.png
348 ms
sisetu.png
347 ms
flor.png
350 ms
gurume.png
349 ms
news.png
345 ms
access.png
346 ms
xapp.png
492 ms
instapp.png
493 ms
wpapp.png
492 ms
scname_image.png
491 ms
scname_image_sm.png
492 ms
mushi.png
493 ms
language.png
826 ms
arrow2.png
825 ms
sisetu-black.png
824 ms
flor-black.png
824 ms
gurume-black.png
825 ms
news-black.png
825 ms
access-black.png
1012 ms
wp.png
1010 ms
sub_banner.jpg
1400 ms
sub_banner.jpg
1571 ms
sub_banner.jpg
1545 ms
sub_banner.jpg
1185 ms
sub_banner.jpg
1947 ms
ext_banner1.gif
1198 ms
ext_banner1.png
1367 ms
ext_banner1.png
1384 ms
ext_banner1.png
1546 ms
ext_banner1.png
1571 ms
ext_banner1.gif
1591 ms
ext_banner1.png
1725 ms
section-red.png
1727 ms
1200x750_image.jpg
1758 ms
1200x750_image.jpg
2131 ms
1200x750_image.jpg
1898 ms
js
60 ms
ytag.js
830 ms
analytics.js
28 ms
destination
161 ms
destination
160 ms
destination
159 ms
uwt.js
155 ms
u
349 ms
dfj2t4d6
370 ms
fbevents.js
41 ms
lt.js
154 ms
collect
121 ms
collect
171 ms
js
119 ms
1200x750_image.jpg
1563 ms
section-blue.png
1564 ms
1200x750_image.jpg
1601 ms
1200x750_image.jpg
1742 ms
1200x750_image.jpg
1743 ms
err.gif
909 ms
1200x750_image.jpg
1674 ms
section-green.png
1644 ms
image.jpg
1680 ms
image.jpg
1779 ms
image.jpg
1780 ms
image.jpg
2016 ms
section-yellow.png
1828 ms
adsct
421 ms
adsct
352 ms
dfj2t4d6
203 ms
ny5olfnk
81 ms
mushi-white.png
1499 ms
fashion.png
1538 ms
fashiongoods.png
1626 ms
interior.png
1626 ms
hobby.png
1683 ms
restaurant.png
1683 ms
sweets.png
1544 ms
amusement.png
1620 ms
service.png
1446 ms
ext_banner2.jpg
1500 ms
ext_banner2.jpg
1332 ms
ext_banner2.jpg
1315 ms
ext_banner2.jpg
1348 ms
section-lightblue.png
1265 ms
top-btn.png
1265 ms
yim.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-hidden="true"] elements contain focusable descendents
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
Form elements do not have associated labels
Links do not have a discernible name
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
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>).
yim.co.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
yim.co.jp SEO score
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 Yim.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 Yim.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.
yim.co.jp
Open Graph description is not detected on the main page of Yim. 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: