Tools & Wizards About Us
mgame.jp screenshot

Report Summary

  • 70

    Performance

    Renders faster than
    81% of other websites

  • 50

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

mgame.jp

オンラインゲームポータルの新しい形　エムゲーム！　-　基本無料でRPG・ライトゲームが遊べる！

Page Load Speed

7.1 sec in total

First Response

1.4 sec

Resources Loaded

5.5 sec

Page Rendered

134 ms

mgame.jp screenshot

About Website

Welcome to mgame.jp homepage info - get ready to check Mgame best content for Turkey right away, or after learning these important things about mgame.jp

無料で遊べるオンラインゲーム！ MMORPGからコミニティまで完全完備！

Visit mgame.jp

Key Findings

We analyzed Mgame.jp page load time and found that the first response time was 1.4 sec and then it took 5.6 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

mgame.jp performance score

70

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value5.9 s

49/100

10%

TBT (Total Blocking Time)

Value150 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value3.4 s

93/100

10%

Network Requests Diagram

mgame.jp

1405 ms

common.css

390 ms

gnb.css

392 ms

top.css

402 ms

top_gnb.css

397 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 19% of them (15 requests) were addressed to the original Mgame.jp, 77% (61 requests) were made to Image.mgame.jp and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Image.mgame.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 316.5 kB (62%)

Content Size

512.4 kB

After Optimization

196.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 21.3 kB

  • Original 25.9 kB
  • After minification 18.1 kB
  • After compression 4.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 7.8 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 21.3 kB or 82% of the original size.

Image Optimization

-61%

Potential reduce by 262.7 kB

  • Original 431.6 kB
  • After minification 168.9 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. Obviously, Mgame needs image optimization as it can save up to 262.7 kB or 61% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 34 B

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

CSS Optimization

-86%

Potential reduce by 32.4 kB

  • Original 37.8 kB
  • After minification 29.0 kB
  • After compression 5.4 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. Mgame.jp needs all CSS files to be minified and compressed as it can save up to 32.4 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 36 (46%)

Requests Now

78

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mgame.jp

mgame.jp

1405 ms

common.css

common.css

390 ms

gnb.css

gnb.css

392 ms

top.css

top.css

402 ms

top_gnb.css

top_gnb.css

397 ms

avatar.viewer.js

avatar.viewer.js

406 ms

makePCookie.js

makePCookie.js

400 ms

writeEmbed.js

writeEmbed.js

782 ms

main.js

main.js

791 ms

rpg_game_info.js

rpg_game_info.js

787 ms

top.js

top.js

2136 ms

copyright.css

copyright.css

787 ms

bg_body.gif

bg_body.gif

1264 ms

bg_header.png

bg_header.png

1435 ms

logo.gif

logo.gif

1445 ms

submenu_admin_off.gif

submenu_admin_off.gif

1288 ms

dotted_line_vertical.gif

dotted_line_vertical.gif

1297 ms

submenu_mint_off.gif

submenu_mint_off.gif

1303 ms

submenu_question_off.gif

submenu_question_off.gif

1413 ms

submenu_contact_off.gif

submenu_contact_off.gif

1456 ms

submenu_mailmaga_off.gif

submenu_mailmaga_off.gif

1468 ms

submenu_sitemap_off.gif

submenu_sitemap_off.gif

1479 ms

submenu_logout_off.gif

submenu_logout_off.gif

1565 ms

btn_gmb01_top_on.png

btn_gmb01_top_on.png

1594 ms

btn_gmb02_game_off.png

btn_gmb02_game_off.png

1607 ms

btn_gmb08_mia_off.png

btn_gmb08_mia_off.png

1623 ms

btn_gmb04_blog_off.png

btn_gmb04_blog_off.png

1640 ms

btn_gmb05_circ_off.png

btn_gmb05_circ_off.png

1654 ms

btn_onlineindex.jpg

btn_onlineindex.jpg

1719 ms

1450949745.jpg

1450949745.jpg

2078 ms

150918PM_03.jpg

150918PM_03.jpg

1935 ms

1450950105.jpg

1450950105.jpg

3129 ms

ico_15.gif

ico_15.gif

1810 ms

ico_14.gif

ico_14.gif

1829 ms

ico_21.gif

ico_21.gif

1871 ms

footer_ci.gif

footer_ci.gif

1983 ms

profile.css

profile.css

390 ms

profile_top.css

profile_top.css

393 ms

mjscript.js

mjscript.js

200 ms

Ymark.gif

Ymark.gif

1391 ms

login_box_fuji.png

login_box_fuji.png

440 ms

guide_beginner_head.png

guide_beginner_head.png

284 ms

left_box_02.gif

left_box_02.gif

358 ms

btn_guide_beginner.gif

btn_guide_beginner.gif

415 ms

left_box_03.png

left_box_03.png

438 ms

guide_head.png

guide_head.png

498 ms

guide_game.gif

guide_game.gif

522 ms

guide_mya.gif

guide_mya.gif

588 ms

guide_blog.gif

guide_blog.gif

591 ms

guide_circle.gif

guide_circle.gif

616 ms

guide_mint.gif

guide_mint.gif

659 ms

left_box_01.png

left_box_01.png

688 ms

ttl_information.gif

ttl_information.gif

762 ms

left_s_box_01.gif

left_s_box_01.gif

745 ms

left_s_box_02.gif

left_s_box_02.gif

792 ms

left_dotline.gif

left_dotline.gif

821 ms

left_s_box_03.gif

left_s_box_03.gif

852 ms

ttl_game.png

ttl_game.png

898 ms

game_box_02.gif

game_box_02.gif

934 ms

ttl_mmorpg.gif

ttl_mmorpg.gif

969 ms

btn_knight.gif

btn_knight.gif

982 ms

btn_lost.gif

btn_lost.gif

1017 ms

btn_hero.gif

btn_hero.gif

1053 ms

btn_operation_reload.gif

btn_operation_reload.gif

1278 ms

btn_nk.gif

btn_nk.gif

1146 ms

btn_darkfall_top.jpg

btn_darkfall_top.jpg

1305 ms

btn_lapis.gif

btn_lapis.gif

1183 ms

game_box_03.png

game_box_03.png

1207 ms

ttl_event.gif

ttl_event.gif

1323 ms

ga.js

ga.js

8 ms

__utm.gif

__utm.gif

13 ms

ttl_blog.gif

ttl_blog.gif

1286 ms

ico_blog.gif

ico_blog.gif

1280 ms

ico_list.gif

ico_list.gif

1327 ms

bg_footer.png

bg_footer.png

1280 ms

dotted_line_vertical.gif

dotted_line_vertical.gif

1263 ms

footer_caution_spac.gif

footer_caution_spac.gif

1235 ms

point.gif

point.gif

1187 ms

footer_credit.gif

footer_credit.gif

1198 ms

Accessibility Review

mgame.jp accessibility score

50

Accessibility Issues

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

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

Form elements do not have associated labels

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

Best Practices

mgame.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

mgame.jp 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 Mgame.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 Mgame.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

mgame.jp

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