Tools & Wizards About Us
support.mobage.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

support.mobage.com

Game Apps and Social Games - Development Showcase - Silicon Studio

Page Load Speed

3.5 sec in total

First Response

72 ms

Resources Loaded

3 sec

Page Rendered

405 ms

support.mobage.com screenshot

About Website

Click here to check amazing Support Mobage content for Indonesia. Otherwise, check out these important facts you probably never knew about support.mobage.com

Learn about the game apps and social games we have developed. Silicon Studio utilizes knowledge of high end CG development skills and planning skills to team up with creative groups and develop all ge...

Visit support.mobage.com

Key Findings

We analyzed Support.mobage.com page load time and found that the first response time was 72 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster. This domain responded with an error, which can significantly jeopardize Support.mobage.com rating and web reputation

Performance Metrics

support.mobage.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value11.9 s

4/100

10%

TBT (Total Blocking Time)

Value540 ms

54/100

30%

CLS (Cumulative Layout Shift)

Value0.079

94/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

support.mobage.com

72 ms

hc

115 ms

en-us

295 ms

application-1b2d55858cc24c1731c9ebe753c7707b.css

175 ms

style-a9d6242cc7fa4479a068263ba0568322.css

188 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Support.mobage.com, 23% (22 requests) were made to Static.xx.fbcdn.net and 18% (17 requests) were made to P5.zdassets.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source P5.zdassets.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 823.3 kB (41%)

Content Size

2.0 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-89%

Potential reduce by 323.3 kB

  • Original 364.6 kB
  • After minification 188.7 kB
  • After compression 41.3 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 175.9 kB, which is 48% 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 323.3 kB or 89% of the original size.

Image Optimization

-1%

Potential reduce by 6.7 kB

  • Original 932.4 kB
  • After minification 925.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. Support Mobage images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 459.6 kB

  • Original 685.3 kB
  • After minification 684.6 kB
  • After compression 225.7 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 459.6 kB or 67% of the original size.

CSS Optimization

-71%

Potential reduce by 33.6 kB

  • Original 47.7 kB
  • After minification 47.5 kB
  • After compression 14.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. Support.mobage.com needs all CSS files to be minified and compressed as it can save up to 33.6 kB or 71% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (52%)

Requests Now

84

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

support.mobage.com

support.mobage.com

72 ms

hc

hc

115 ms

en-us

en-us

295 ms

application-1b2d55858cc24c1731c9ebe753c7707b.css

application-1b2d55858cc24c1731c9ebe753c7707b.css

175 ms

style-a9d6242cc7fa4479a068263ba0568322.css

style-a9d6242cc7fa4479a068263ba0568322.css

188 ms

jquery-bdfe7aceb5ca539ae586c3406122925c.js

jquery-bdfe7aceb5ca539ae586c3406122925c.js

225 ms

style.css

style.css

206 ms

purl.js

purl.js

207 ms

notification.js

notification.js

203 ms

css

css

136 ms

script-a9d6242cc7fa4479a068263ba0568322.js

script-a9d6242cc7fa4479a068263ba0568322.js

200 ms

locales-a26ad5c1eb40b0bd2446a5ee2a7ea5e60620573f.js

locales-a26ad5c1eb40b0bd2446a5ee2a7ea5e60620573f.js

198 ms

host.js

host.js

163 ms

vendor_enduser-0325158eb1165785cbd83854980be282.js

vendor_enduser-0325158eb1165785cbd83854980be282.js

341 ms

hc_enduser-7ffe1b02a55be169d47f9233d78dc25a.js

hc_enduser-7ffe1b02a55be169d47f9233d78dc25a.js

343 ms

analytics.js

analytics.js

881 ms

webfont.js

webfont.js

892 ms

dena-rev_2x.png

dena-rev_2x.png

99 ms

zZKHbeYK3DaIw7B7AUbdotD_WeYbd8U426MRNVFMYEwWJCXWeFR21xcHwfjRWrFrg-c3=w300

zZKHbeYK3DaIw7B7AUbdotD_WeYbd8U426MRNVFMYEwWJCXWeFR21xcHwfjRWrFrg-c3=w300

932 ms

8GqIGj8l1YloaBswladtyyyyQrRqbC-1RUoPVUPU0bSvER2HeWZeX78C5nxXnNhlPek=w300

8GqIGj8l1YloaBswladtyyyyQrRqbC-1RUoPVUPU0bSvER2HeWZeX78C5nxXnNhlPek=w300

931 ms

bb2_icon.png

bb2_icon.png

875 ms

FFRKLOGO.png

FFRKLOGO.png

264 ms

BG_google_icon-1024.png

BG_google_icon-1024.png

1204 ms

HLF_google_icon-1024.png

HLF_google_icon-1024.png

1259 ms

mmh_icon.png

mmh_icon.png

890 ms

mwoh_icon.png

mwoh_icon.png

890 ms

swgd_icon.png

swgd_icon.png

1014 ms

tfbt_icon.png

tfbt_icon.png

940 ms

RnR_Icon_Piggles_300.jpg

RnR_Icon_Piggles_300.jpg

924 ms

all.js

all.js

941 ms

icon-hamburger.svg

icon-hamburger.svg

783 ms

smile.png

smile.png

783 ms

ico-search_2x.png

ico-search_2x.png

811 ms

widgets.js

widgets.js

772 ms

ico.png

ico.png

34 ms

collect

collect

16 ms

29596.js

29596.js

373 ms

collect

collect

101 ms

135 ms

xd_arbiter.php

xd_arbiter.php

138 ms

ga-audiences

ga-audiences

70 ms

timeline.1b43d11859b7663a2225b885f87704a5.js

timeline.1b43d11859b7663a2225b885f87704a5.js

31 ms

syndication

syndication

101 ms

388334875347927040

388334875347927040

227 ms

7.woff

7.woff

96 ms

vkCK7CReuwGAveLCeOtDQ896i4THsbO+1z.woff

vkCK7CReuwGAveLCeOtDQ896i4THsbO+1z.woff

166 ms

Ma7ZyTkfvG4874SeB59WXsl.woff

Ma7ZyTkfvG4874SeB59WXsl.woff

253 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

36 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

66 ms

4qIGOhFt_normal.png

4qIGOhFt_normal.png

124 ms

CcLaphQUcAAVb51.jpg:large

CcLaphQUcAAVb51.jpg:large

256 ms

CcGMgddXIAAM3Hn.jpg:small

CcGMgddXIAAM3Hn.jpg:small

262 ms

CcFeXPqWwAAmyJw.jpg:small

CcFeXPqWwAAmyJw.jpg:small

312 ms

CcFmTOqXIAAMbYW.jpg:small

CcFmTOqXIAAMbYW.jpg:small

350 ms

CcA0XzYXIAA8uUC.jpg:small

CcA0XzYXIAA8uUC.jpg:small

317 ms

Cb_ithVUYAEmN6S.jpg:small

Cb_ithVUYAEmN6S.jpg:small

379 ms

Cbnb44ZWEAEKa45.jpg:small

Cbnb44ZWEAEKa45.jpg:small

320 ms

CbnaFOsW0AAsn9J.jpg:small

CbnaFOsW0AAsn9J.jpg:small

318 ms

7.ttf

7.ttf

130 ms

vkCK7CReuwGAveLCeOtDQ896i4THsbO+1z.ttf

vkCK7CReuwGAveLCeOtDQ896i4THsbO+1z.ttf

85 ms

ping

ping

91 ms

jot

jot

32 ms

like_box.php

like_box.php

184 ms

roNeOY-tz5Y.css

roNeOY-tz5Y.css

80 ms

UHhaxo8Cs3k.css

UHhaxo8Cs3k.css

100 ms

Qz9nHTUX1Wv.css

Qz9nHTUX1Wv.css

119 ms

_rx8naC75Dy.js

_rx8naC75Dy.js

164 ms

x5F9OMjKyLw.js

x5F9OMjKyLw.js

185 ms

ICDbTSzjQEg.js

ICDbTSzjQEg.js

134 ms

TTCre3391I0.js

TTCre3391I0.js

135 ms

C-h3nYPqETO.js

C-h3nYPqETO.js

154 ms

rFmE1g6Dkoz.js

rFmE1g6Dkoz.js

201 ms

7cm7D75Y0Sf.js

7cm7D75Y0Sf.js

197 ms

oRoBXlHCpEy.js

oRoBXlHCpEy.js

153 ms

336JejShbZp.js

336JejShbZp.js

197 ms

sj-JwAJi4AH.js

sj-JwAJi4AH.js

222 ms

DKRU1bYTkTw.js

DKRU1bYTkTw.js

197 ms

ZNPAadQNc33.js

ZNPAadQNc33.js

198 ms

W0OV23mIOyO.js

W0OV23mIOyO.js

228 ms

36TdwhIHusi.js

36TdwhIHusi.js

228 ms

12294709_897634490331467_5565492273679567241_n.jpg

12294709_897634490331467_5565492273679567241_n.jpg

120 ms

10689782_687231188038466_7029517932881173849_n.png

10689782_687231188038466_7029517932881173849_n.png

49 ms

12549080_10156446067165183_6721262294021383303_n.jpg

12549080_10156446067165183_6721262294021383303_n.jpg

84 ms

11889488_1686555624911814_1093380405126187917_n.jpg

11889488_1686555624911814_1093380405126187917_n.jpg

66 ms

12803092_861339150642684_3373451338330119882_n.jpg

12803092_861339150642684_3373451338330119882_n.jpg

64 ms

10408820_1704168209827866_8702427887487705190_n.jpg

10408820_1704168209827866_8702427887487705190_n.jpg

66 ms

1510848_153573125012785_3734124725438740001_n.jpg

1510848_153573125012785_3734124725438740001_n.jpg

68 ms

12552919_955868874492328_6793617300098041202_n.jpg

12552919_955868874492328_6793617300098041202_n.jpg

69 ms

12410518_10154377925326102_4290803300545025461_n.jpg

12410518_10154377925326102_4290803300545025461_n.jpg

81 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

25 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

26 ms

pUFVdPjIRct.png

pUFVdPjIRct.png

23 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

24 ms

vlXaquuXMrr.js

vlXaquuXMrr.js

35 ms

Accessibility Review

support.mobage.com accessibility score

88

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

support.mobage.com 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

support.mobage.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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Support.mobage.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Support.mobage.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

support.mobage.com

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