Tools & Wizards About Us
m-keys.com screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

m-keys.com

楽天

Page Load Speed

4 sec in total

First Response

694 ms

Resources Loaded

3.1 sec

Page Rendered

249 ms

m-keys.com screenshot

About Website

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

楽天スーパーセール・お買い物マラソセールの開催予定を中心にお得に買い物できる情報をご紹介しています。

Visit m-keys.com

Key Findings

We analyzed M-keys.com page load time and found that the first response time was 694 ms and then it took 3.3 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

m-keys.com performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

71/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

84/100

25%

SI (Speed Index)

Value4.5 s

72/100

10%

TBT (Total Blocking Time)

Value1,120 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.1 s

41/100

10%

Network Requests Diagram

m-keys.com

694 ms

jquery.min.js

21 ms

config.js

172 ms

styles.css

344 ms

textstyles.css

347 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 29% of them (24 requests) were addressed to the original M-keys.com, 16% (13 requests) were made to Pagead2.googlesyndication.com and 11% (9 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Ba.afl.rakuten.co.jp.

Page Optimization Overview & Recommendations

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

Content Size

512.6 kB

After Optimization

441.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of M-keys.com main page is 512.6 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. 50% of websites need less resources to load. Javascripts take 309.5 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 14.4 kB

  • Original 20.5 kB
  • After minification 20.3 kB
  • After compression 6.1 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 14.4 kB or 70% of the original size.

Image Optimization

-5%

Potential reduce by 8.2 kB

  • Original 164.8 kB
  • After minification 156.5 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. M Keys images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 46.0 kB

  • Original 309.5 kB
  • After minification 309.5 kB
  • After compression 263.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 46.0 kB or 15% of the original size.

CSS Optimization

-16%

Potential reduce by 2.8 kB

  • Original 17.9 kB
  • After minification 17.9 kB
  • After compression 15.1 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. M-keys.com needs all CSS files to be minified and compressed as it can save up to 2.8 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (65%)

Requests Now

74

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of M Keys. 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 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

m-keys.com

m-keys.com

694 ms

jquery.min.js

jquery.min.js

21 ms

config.js

config.js

172 ms

styles.css

styles.css

344 ms

textstyles.css

textstyles.css

347 ms

show_ads.js

show_ads.js

79 ms

2nd_gets.php

2nd_gets.php

300 ms

header.jpg

header.jpg

339 ms

tables.css

tables.css

173 ms

commonstyles.css

commonstyles.css

184 ms

red015wjwj.jpg

red015wjwj.jpg

175 ms

top_bg.gif

top_bg.gif

342 ms

h1_bg.gif

h1_bg.gif

174 ms

top_inner_bg.gif

top_inner_bg.gif

332 ms

search_input.gif

search_input.gif

343 ms

searchbutton.gif

searchbutton.gif

344 ms

topmenu_bg.gif

topmenu_bg.gif

344 ms

topmenu_li.gif

topmenu_li.gif

352 ms

rss_button.gif

rss_button.gif

496 ms

headerbox_bg.gif

headerbox_bg.gif

572 ms

h3_bg.gif

h3_bg.gif

522 ms

adsbygoogle.js

adsbygoogle.js

203 ms

menu_h4.gif

menu_h4.gif

475 ms

menu_title_bg.gif

menu_title_bg.gif

475 ms

menulist_li_bg.gif

menulist_li_bg.gif

490 ms

menu_bg.png

menu_bg.png

627 ms

pagetop_button.png

pagetop_button.png

643 ms

footer_bg.gif

footer_bg.gif

643 ms

2020030900000.gif

2020030900000.gif

296 ms

right_white.gif

right_white.gif

295 ms

show_ads_impl.js

show_ads_impl.js

482 ms

1341 ms

zrt_lookup.html

zrt_lookup.html

26 ms

ads

ads

405 ms

ads

ads

300 ms

ads

ads

636 ms

gen_204

gen_204

59 ms

pixel

pixel

65 ms

dv3.js

dv3.js

265 ms

window_focus.js

window_focus.js

17 ms

qs_click_protection.js

qs_click_protection.js

21 ms

ufs_web_display.js

ufs_web_display.js

15 ms

pixel

pixel

47 ms

pixel

pixel

52 ms

81023225b0f193d07d052e50ea38e692.js

81023225b0f193d07d052e50ea38e692.js

23 ms

load_preloaded_resource.js

load_preloaded_resource.js

10 ms

9fe8b22c2539940296c5f72a286520e3.js

9fe8b22c2539940296c5f72a286520e3.js

35 ms

abg_lite.js

abg_lite.js

11 ms

e92e9b19fdbae9b3a3ef41360efccaf5.js

e92e9b19fdbae9b3a3ef41360efccaf5.js

145 ms

rum

rum

151 ms

14763004658117789537

14763004658117789537

132 ms

icon.png

icon.png

130 ms

s

s

116 ms

css

css

162 ms

pixel

pixel

134 ms

bounce

bounce

113 ms

pixel

pixel

138 ms

3220453402618369976

3220453402618369976

109 ms

abg_lite.js

abg_lite.js

92 ms

omrhp.js

omrhp.js

97 ms

Q12zgMmT.js

Q12zgMmT.js

82 ms

gen_204

gen_204

164 ms

ad

ad

64 ms

62bHydCX.html

62bHydCX.html

13 ms

rum

rum

26 ms

pixel

pixel

25 ms

activeview

activeview

109 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

100 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

100 ms

pixel

pixel

96 ms

VKtwqYIMw_jEtcsYEdk2t0uWx1X5nCbHNvrRSJpikmk.js

VKtwqYIMw_jEtcsYEdk2t0uWx1X5nCbHNvrRSJpikmk.js

73 ms

pixel

pixel

94 ms

3850322528129912769

3850322528129912769

69 ms

DsR2kPoxtp.gif

DsR2kPoxtp.gif

193 ms

dcm

dcm

213 ms

ca

ca

120 ms

activeview

activeview

130 ms

rum

rum

108 ms

setuid

setuid

110 ms

pixel

pixel

105 ms

pixel

pixel

103 ms

activeview

activeview

107 ms

rum

rum

62 ms

Accessibility Review

m-keys.com accessibility score

75

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.

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

m-keys.com best practices score

67

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

High

Page has valid source maps

SEO Factors

m-keys.com SEO score

90

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

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 M-keys.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 M-keys.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

m-keys.com

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