Tools & Wizards About Us
mallage.com screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

mallage.com

双日商業開発株式会社

Page Load Speed

8.2 sec in total

First Response

612 ms

Resources Loaded

7.1 sec

Page Rendered

512 ms

mallage.com screenshot

About Website

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

双日商業開発株式会社は価値ある商業施設を創造するために求められること、人と街をむすび、笑顔があふれるコミュニティを実現します。

Visit mallage.com

Key Findings

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

Performance Metrics

mallage.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value11.6 s

4/100

10%

TBT (Total Blocking Time)

Value710 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.626

9/100

15%

TTI (Time to Interactive)

Value15.2 s

7/100

10%

Network Requests Diagram

mallage.com

612 ms

www.mallage.com

580 ms

www.sojitz-sc.com

1673 ms

gtm.js

60 ms

index.css

1251 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Mallage.com, 77% (43 requests) were made to Sojitz-sc.com and 7% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Sojitz-sc.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (18%)

Content Size

6.9 MB

After Optimization

5.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mallage.com main page is 6.9 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 5.5 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 36.5 kB

  • Original 42.5 kB
  • After minification 29.7 kB
  • After compression 6.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. This page needs HTML code to be minified as it can gain 12.9 kB, which is 30% 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 36.5 kB or 86% of the original size.

Image Optimization

-3%

Potential reduce by 163.4 kB

  • Original 5.5 MB
  • After minification 5.4 MB

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. Mallage images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 745.7 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 269.1 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 745.7 kB or 73% of the original size.

CSS Optimization

-93%

Potential reduce by 274.8 kB

  • Original 296.5 kB
  • After minification 215.8 kB
  • After compression 21.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. Mallage.com needs all CSS files to be minified and compressed as it can save up to 274.8 kB or 93% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (10%)

Requests Now

49

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mallage.com

mallage.com

612 ms

www.mallage.com

www.mallage.com

580 ms

www.sojitz-sc.com

www.sojitz-sc.com

1673 ms

gtm.js

gtm.js

60 ms

index.css

index.css

1251 ms

css

css

47 ms

js

js

54 ms

analytics.js

analytics.js

16 ms

collect

collect

105 ms

collect

collect

33 ms

js

js

52 ms

bundle.js

bundle.js

2148 ms

header_bg.jpg

header_bg.jpg

212 ms

logo.svg

logo.svg

421 ms

logo_white.svg

logo_white.svg

606 ms

icon_print.svg

icon_print.svg

611 ms

icon_mail.svg

icon_mail.svg

631 ms

img01.jpg

img01.jpg

638 ms

img02.jpg

img02.jpg

639 ms

img03.jpg

img03.jpg

807 ms

img01.jpg

img01.jpg

813 ms

img02.jpg

img02.jpg

839 ms

anc03.svg

anc03.svg

849 ms

img01.jpg

img01.jpg

852 ms

img02.jpg

img02.jpg

1007 ms

img03.jpg

img03.jpg

1016 ms

kv01.jpg

kv01.jpg

1049 ms

kv02.jpg

kv02.jpg

1692 ms

kv03.jpg

kv03.jpg

1275 ms

kv04.jpg

kv04.jpg

1409 ms

kv_txt.png

kv_txt.png

1227 ms

kv01_open.jpg

kv01_open.jpg

1683 ms

kv02_open.jpg

kv02_open.jpg

1528 ms

kv03_open.jpg

kv03_open.jpg

2841 ms

kv04_open.jpg

kv04_open.jpg

2969 ms

arrow_black.svg

arrow_black.svg

1613 ms

business.jpg

business.jpg

1732 ms

profile.jpg

profile.jpg

2216 ms

img01.jpg

img01.jpg

1895 ms

img02.jpg

img02.jpg

2323 ms

img03.jpg

img03.jpg

1935 ms

img04.jpg

img04.jpg

2106 ms

img05.jpg

img05.jpg

2139 ms

img06.jpg

img06.jpg

2317 ms

img07.jpg

img07.jpg

2342 ms

img08.jpg

img08.jpg

2619 ms

arrow_black_box.svg

arrow_black_box.svg

2428 ms

dg45_pLmvrkcOkBnKsOzXyGWTBcmgwL9VjvYIg.ttf

dg45_pLmvrkcOkBnKsOzXyGWTBcmgwL9VjvYIg.ttf

21 ms

dg45_pLmvrkcOkBnKsOzXyGWTBcmg-X6VjvYIg.ttf

dg45_pLmvrkcOkBnKsOzXyGWTBcmg-X6VjvYIg.ttf

38 ms

NotoSansCJKjp-Regular.otf

NotoSansCJKjp-Regular.otf

2965 ms

NotoSansCJKjp-Medium.otf

NotoSansCJKjp-Medium.otf

2133 ms

arrow_white_box.svg

arrow_white_box.svg

2137 ms

icon_tel.svg

icon_tel.svg

2147 ms

collect

collect

54 ms

ajax-loader.gif

ajax-loader.gif

1599 ms

js

js

47 ms

Accessibility Review

mallage.com accessibility score

85

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

mallage.com best practices score

83

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

Missing source maps for large first-party JavaScript

SEO Factors

mallage.com SEO score

82

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

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

Social Sharing Optimization

mallage.com

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