Tools & Wizards About Us
muzakawasaki.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

muzakawasaki.com

川崎駅西口の複合施設 - ミューザ川崎

Page Load Speed

4.8 sec in total

First Response

959 ms

Resources Loaded

3.6 sec

Page Rendered

168 ms

muzakawasaki.com screenshot

About Website

Visit muzakawasaki.com now to see the best up-to-date Muzakawasaki content for Japan and also check out these interesting facts you probably never knew about muzakawasaki.com

ミューザ川崎はオフィス、ショップ＆レストラン、シンフォニーホールの施設を備えた、川崎駅西口の新たなランドマークタワーです。

Visit muzakawasaki.com

Key Findings

We analyzed Muzakawasaki.com page load time and found that the first response time was 959 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

muzakawasaki.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value12.3 s

0/100

25%

SI (Speed Index)

Value6.3 s

42/100

10%

TBT (Total Blocking Time)

Value830 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

muzakawasaki.com

959 ms

import.css

338 ms

js.js

352 ms

swfobject.js

550 ms

heightLine.js

552 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 93% of them (51 requests) were addressed to the original Muzakawasaki.com, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Addit.co.jp. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Muzakawasaki.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 146.7 kB (16%)

Content Size

936.7 kB

After Optimization

790.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Muzakawasaki.com main page is 936.7 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. 20% of websites need less resources to load. Images take 741.5 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 8.7 kB

  • Original 11.4 kB
  • After minification 10.0 kB
  • After compression 2.7 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 1.4 kB, which is 13% 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 8.7 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 5.4 kB

  • Original 741.5 kB
  • After minification 736.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. Muzakawasaki images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 97.5 kB

  • Original 142.9 kB
  • After minification 133.7 kB
  • After compression 45.5 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 97.5 kB or 68% of the original size.

CSS Optimization

-86%

Potential reduce by 35.2 kB

  • Original 40.8 kB
  • After minification 31.8 kB
  • After compression 5.7 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. Muzakawasaki.com needs all CSS files to be minified and compressed as it can save up to 35.2 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (33%)

Requests Now

51

After Optimization

34

  • Images
  • JavaScript
  • CSS

The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Muzakawasaki. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

muzakawasaki.com

muzakawasaki.com

959 ms

import.css

import.css

338 ms

js.js

js.js

352 ms

swfobject.js

swfobject.js

550 ms

heightLine.js

heightLine.js

552 ms

jquery.js

jquery.js

1101 ms

iepngfix.js

iepngfix.js

503 ms

iepngrollover.js

iepngrollover.js

513 ms

thickbox.js

thickbox.js

868 ms

yuga.js

yuga.js

835 ms

share.css

share.css

530 ms

separate.css

separate.css

581 ms

thickbox.css

thickbox.css

401 ms

analytics.js

analytics.js

29 ms

body_back.jpg

body_back.jpg

178 ms

logo.png

logo.png

169 ms

home_btn.jpg

home_btn.jpg

186 ms

access_btn.jpg

access_btn.jpg

186 ms

art_btn.jpg

art_btn.jpg

176 ms

gnavi01.png

gnavi01.png

185 ms

gnavi02.png

gnavi02.png

336 ms

gnavi03.png

gnavi03.png

350 ms

gnavi04.png

gnavi04.png

353 ms

gnavi05.png

gnavi05.png

369 ms

gnavi06.png

gnavi06.png

369 ms

contents_head.png

contents_head.png

920 ms

info_btn01.jpg

info_btn01.jpg

707 ms

info_btn02.jpg

info_btn02.jpg

871 ms

info_btn03.jpg

info_btn03.jpg

878 ms

top_img01.jpg

top_img01.jpg

1104 ms

r_syosai_btn.jpg

r_syosai_btn.jpg

551 ms

dgp2016.jpg

dgp2016.jpg

735 ms

contents_foot.png

contents_foot.png

873 ms

pagetop.jpg

pagetop.jpg

919 ms

foot_logo.png

foot_logo.png

1043 ms

loadingAnimation.gif

loadingAnimation.gif

559 ms

contents_bg.png

contents_bg.png

1022 ms

title_bg01.jpg

title_bg01.jpg

1034 ms

right_bg01.jpg

right_bg01.jpg

1084 ms

r_accsess_bg.jpg

r_accsess_bg.jpg

1268 ms

r_art_bg.jpg

r_art_bg.jpg

1360 ms

footer_bg.jpg

footer_bg.jpg

1200 ms

footer_back.jpg

footer_back.jpg

1209 ms

foot_home_icon.jpg

foot_home_icon.jpg

1267 ms

foot_sb_icon.jpg

foot_sb_icon.jpg

1267 ms

home_btn_on.jpg

home_btn_on.jpg

1373 ms

access_btn_on.jpg

access_btn_on.jpg

1385 ms

art_btn_on.jpg

art_btn_on.jpg

1449 ms

info_btn01_on.jpg

info_btn01_on.jpg

1634 ms

info_btn02_on.jpg

info_btn02_on.jpg

1817 ms

info_btn03_on.jpg

info_btn03_on.jpg

1863 ms

collect

collect

25 ms

collect

collect

64 ms

r_syosai_btn_on.jpg

r_syosai_btn_on.jpg

1405 ms

pagetop_on.jpg

pagetop_on.jpg

1411 ms

Accessibility Review

muzakawasaki.com accessibility score

71

Accessibility Issues

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

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

muzakawasaki.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

muzakawasaki.com SEO score

67

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Muzakawasaki.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 Muzakawasaki.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.

Social Sharing Optimization

muzakawasaki.com

Open Graph description is not detected on the main page of Muzakawasaki. 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: