Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

momastore.jp

MoMA Design Store

Page Load Speed

5.7 sec in total

First Response

428 ms

Resources Loaded

4.9 sec

Page Rendered

439 ms

momastore.jp screenshot

About Website

Visit momastore.jp now to see the best up-to-date MoMA Store content for Japan and also check out these interesting facts you probably never knew about momastore.jp

MoMA Design Storeはニューヨーク近代美術館のキュレーターが厳選したMoMAの代表的なプロダクトから雑貨、インテリアまでグッドデザインを取り揃えたMoMA公式店。お買い上げいただく収益の一部はニューヨーク近代美術館の運営に使われ、アートのサポートにつながります。プレゼントにもおすすめ。【1万5千円以上で送料無料】

Visit momastore.jp

Key Findings

We analyzed Momastore.jp page load time and found that the first response time was 428 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

momastore.jp performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value690 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.553

13/100

15%

TTI (Time to Interactive)

Value14.7 s

8/100

10%

Network Requests Diagram

momastore.jp

428 ms

default.aspx

386 ms

font-awesome.min.css

35 ms

font.css

19 ms

style.css

20 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 72% of them (71 requests) were addressed to the original Momastore.jp, 11% (11 requests) were made to D.rcmd.jp and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Momastore.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 92.7 kB (14%)

Content Size

656.1 kB

After Optimization

563.4 kB

In fact, the total size of Momastore.jp main page is 656.1 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. 60% of websites need less resources to load. Images take 363.7 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 56.7 kB

  • Original 69.9 kB
  • After minification 53.4 kB
  • After compression 13.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. This page needs HTML code to be minified as it can gain 16.5 kB, which is 24% 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 56.7 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 9.0 kB

  • Original 363.7 kB
  • After minification 354.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. MoMA Store images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 14.1 kB

  • Original 170.6 kB
  • After minification 170.2 kB
  • After compression 156.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. This website has mostly compressed JavaScripts.

CSS Optimization

-25%

Potential reduce by 12.8 kB

  • Original 51.9 kB
  • After minification 49.8 kB
  • After compression 39.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. Momastore.jp needs all CSS files to be minified and compressed as it can save up to 12.8 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 54 (57%)

Requests Now

94

After Optimization

40

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

Accessibility Review

momastore.jp accessibility score

74

Accessibility Issues

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

High

[aria-hidden="true"] elements contain focusable descendents

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

momastore.jp best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

momastore.jp SEO score

75

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 Momastore.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 Momastore.jp 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

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