Tools & Wizards About Us
g-player.com screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

g-player.com

レトロゲームFAN

Page Load Speed

2.7 sec in total

First Response

541 ms

Resources Loaded

2 sec

Page Rendered

133 ms

g-player.com screenshot

About Website

Welcome to g-player.com homepage info - get ready to check G Player best content for Japan right away, or after learning these important things about g-player.com

レトロゲームが今でも遊べるのかどうかを検証しています。

Visit g-player.com

Key Findings

We analyzed G-player.com page load time and found that the first response time was 541 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

g-player.com performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

64/100

25%

SI (Speed Index)

Value6.2 s

44/100

10%

TBT (Total Blocking Time)

Value4,440 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.308

38/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

g-player.com

541 ms

g-player.com

715 ms

sample.css

180 ms

title.jpg

349 ms

hard1.png

523 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 63% of them (10 requests) were addressed to the original G-player.com, 13% (2 requests) were made to Ssl.google-analytics.com and 6% (1 request) were made to Www25.a8.net. The less responsive or slowest element that took the longest time to load (732 ms) relates to the external source Www25.a8.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 17.1 kB (16%)

Content Size

106.0 kB

After Optimization

88.9 kB

  • HTML
  • JavaScript

In fact, the total size of G-player.com main page is 106.0 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Javascripts take 82.6 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 17.1 kB

  • Original 23.4 kB
  • After minification 20.9 kB
  • After compression 6.4 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 2.6 kB, which is 11% 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 17.1 kB or 73% of the original size.

JavaScript Optimization

-0%

Potential reduce by 52 B

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

Requests Breakdown

We found no issues to fix!

Requests Now

5

After Optimization

5

  • Images
  • JavaScript

The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of G Player. According to our analytics all requests are already optimized.

Network Requests Diagram

g-player.com

g-player.com

541 ms

g-player.com

g-player.com

715 ms

sample.css

sample.css

180 ms

title.jpg

title.jpg

349 ms

hard1.png

hard1.png

523 ms

hard2.png

hard2.png

524 ms

hard3.png

hard3.png

524 ms

all_consolselect.png

all_consolselect.png

525 ms

bgt

bgt

732 ms

0.gif

0.gif

682 ms

widget.js

widget.js

2 ms

adsbygoogle.js

adsbygoogle.js

48 ms

famicom.jpg

famicom.jpg

525 ms

ga.js

ga.js

62 ms

direct.png

direct.png

349 ms

__utm.gif

__utm.gif

11 ms

Accessibility Review

g-player.com accessibility score

81

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

g-player.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

g-player.com SEO score

58

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise G-player.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 G-player.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

g-player.com

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