Access mano-a-mano.jp. 時計ベルト専門店 mano a mano

mano-a-mano.jp screenshot

31

Performance

Renders faster than
51% of other websites
69

Accessibility

Visual factors better than
that of 34% of websites
75

Best Practices

More advanced features
available than in
35% of websites
89

SEO

Google-friendlier than
66% of websites

First Response

591 ms

Resources Loaded

8.1 sec

Page Rendered

1.4 sec

mano-a-mano.jp screenshot

About Website

Click here to check amazing Mano A content for Japan. Otherwise, check out these important facts you probably never knew about mano-a-mano.jp

当店は国内最多の8,000種類以上のベルトを取り扱う、時計ベルト専門店 mano a mano(マーノ・ア・マーノ)です。イタリアが誇る世界最大級の時計ベルトメーカーMORELLATO（モレラート）社の日本総代理店です。

Visit mano-a-mano.jp

Key Findings

We analyzed Mano-a-mano.jp page load time and found that the first response time was 591 ms and then it took 9.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value12.0 s

4/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0.246

51/100

15%

TTI (Time to Interactive)

Value14.4 s

9/100

10%

mano-a-mano.jp

591 ms

www.mano-a-mano.jp

968 ms

import.css

386 ms

presentationCycle.css

384 ms

index.css

390 ms

Our browser made a total of 209 requests to load all elements on the main page. We found that 10% of them (20 requests) were addressed to the original Mano-a-mano.jp, 60% (125 requests) were made to Image.rakuten.co.jp and 19% (39 requests) were made to Rakuten.ne.jp. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Image.rakuten.co.jp.

Content Size

5.5 MB

After Optimization

5.1 MB

In fact, the total size of Mano-a-mano.jp main page is 5.5 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 69.0 kB

Original 83.6 kB
After minification 67.9 kB
After compression 14.6 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 15.7 kB, which is 19% 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 69.0 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 146.3 kB

Original 5.1 MB
After minification 5.0 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. Mano A images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 132.0 kB

Original 214.3 kB
After minification 210.2 kB
After compression 82.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 132.0 kB or 62% of the original size.

CSS Optimization

-79%

Potential reduce by 20.7 kB

Original 26.3 kB
After minification 20.5 kB
After compression 5.6 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. Mano-a-mano.jp needs all CSS files to be minified and compressed as it can save up to 20.7 kB or 79% of the original size.

Requests Now

204

After Optimization

181

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

Accessibility Issues

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.

High

ARIA input fields do not have accessible names

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.

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

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

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

Search Engine Optimization Advices

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

High

Image elements do not have [alt] attributes

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/).

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 Mano-a-mano.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 Mano-a-mano.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

mano-a-mano.jp

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