Tools & Wizards About Us
gaeamobile.net screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    68% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

gaeamobile.net

盖娅互娱

Page Load Speed

1.6 sec in total

First Response

86 ms

Resources Loaded

1.2 sec

Page Rendered

249 ms

gaeamobile.net screenshot

About Website

Click here to check amazing Gaeamobile content for China. Otherwise, check out these important facts you probably never knew about gaeamobile.net

盖娅互娱是一家坚持全球化视野、深耕原创精品内容、具有鲜明特征的在线文娱集团。自2014年成立以来，聚焦围绕核心内容，打造平台-内容-研发深度融合发展的发展战略，逐步打造了由七创社（国漫IP内容开发全产业链厂牌）、旅法师营地（以竞技卡牌用户为基础，融合资讯门户、直播电商、内容生产、游戏分发、全球游戏产品代理发行运营能力的用户平台社区）、帕格索斯（具备深厚积累的研发工作室集群）等板块组成的业务平台，并...

Visit gaeamobile.net

Key Findings

We analyzed Gaeamobile.net page load time and found that the first response time was 86 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

gaeamobile.net performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value8.6 s

1/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

86 ms

bootstrap.min.css

137 ms

slick.css

131 ms

fonts.css

151 ms

index.css

134 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 60% of them (24 requests) were addressed to the original Gaeamobile.net, 40% (16 requests) were made to Gaeamobile.com. The less responsive or slowest element that took the longest time to load (495 ms) relates to the external source Gaeamobile.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 351.3 kB (40%)

Content Size

874.9 kB

After Optimization

523.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gaeamobile.net main page is 874.9 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. 65% of websites need less resources to load. Images take 490.0 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 20.0 kB

  • Original 22.8 kB
  • After minification 14.4 kB
  • After compression 2.9 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 8.4 kB, which is 37% 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 20.0 kB or 87% of the original size.

Image Optimization

-11%

Potential reduce by 51.9 kB

  • Original 490.0 kB
  • After minification 438.1 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, Gaeamobile needs image optimization as it can save up to 51.9 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-74%

Potential reduce by 169.6 kB

  • Original 229.9 kB
  • After minification 201.0 kB
  • After compression 60.4 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 169.6 kB or 74% of the original size.

CSS Optimization

-83%

Potential reduce by 109.9 kB

  • Original 132.1 kB
  • After minification 128.2 kB
  • After compression 22.2 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. Gaeamobile.net needs all CSS files to be minified and compressed as it can save up to 109.9 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (26%)

Requests Now

35

After Optimization

26

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

86 ms

bootstrap.min.css

bootstrap.min.css

137 ms

slick.css

slick.css

131 ms

fonts.css

fonts.css

151 ms

index.css

index.css

134 ms

header-footer.css

header-footer.css

152 ms

jquery.min.js

jquery.min.js

206 ms

bootstrap.min.js

bootstrap.min.js

193 ms

slick.min.js

slick.min.js

205 ms

masonry.pkgd.min.js

masonry.pkgd.min.js

232 ms

index.js

index.js

205 ms

header-footer.js

header-footer.js

235 ms

logo-dark1.png

logo-dark1.png

361 ms

show.jpg

show.jpg

189 ms

show.jpg

show.jpg

184 ms

show.jpg

show.jpg

189 ms

show.jpg

show.jpg

193 ms

show.jpg

show.jpg

34 ms

show.jpg

show.jpg

36 ms

show.jpg

show.jpg

177 ms

show.jpg

show.jpg

177 ms

show.jpg

show.jpg

182 ms

show.jpg

show.jpg

182 ms

show.jpg

show.jpg

184 ms

show.jpg

show.jpg

495 ms

show.jpg

show.jpg

176 ms

show.jpg

show.jpg

179 ms

show.jpg

show.jpg

178 ms

show.png

show.png

177 ms

logo1.png

logo1.png

191 ms

switch-down.png

switch-down.png

189 ms

learn-more.png

learn-more.png

187 ms

go-to-detail.png

go-to-detail.png

185 ms

share-logo.png

share-logo.png

184 ms

arrow-left.png

arrow-left.png

68 ms

arrow-right.png

arrow-right.png

66 ms

Antonio-Light.ttf

Antonio-Light.ttf

200 ms

Montserrat-Regular.ttf

Montserrat-Regular.ttf

132 ms

Montserrat-Bold.ttf

Montserrat-Bold.ttf

133 ms

Antonio-Bold.ttf

Antonio-Bold.ttf

134 ms

Accessibility Review

gaeamobile.net accessibility score

73

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

gaeamobile.net 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

gaeamobile.net SEO score

64

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

gaeamobile.net

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