Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

gamer.ne.jp

最新ゲーム情報をお届け!ゲーム総合情報サイト Gamer

Page Load Speed

18.1 sec in total

First Response

585 ms

Resources Loaded

16.5 sec

Page Rendered

1 sec

gamer.ne.jp screenshot

About Website

Click here to check amazing Gamer content for Japan. Otherwise, check out these important facts you probably never knew about gamer.ne.jp

総合ゲーム情報サイト Gamerでは、PlayStation/Nintendo Switch/Xboxといったゲーム機をはじめ、iPhone/Android用スマートフォンゲームアプリ、アーケードやPCゲーム、さらにVR・ARといったゲームの最新情報を扱っています。インタビューやプレイレビュー、イベント情報や発売日カレンダー、ランキングも!

Visit gamer.ne.jp

Key Findings

We analyzed Gamer.ne.jp page load time and found that the first response time was 585 ms and then it took 17.5 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

gamer.ne.jp performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

65/100

25%

SI (Speed Index)

Value14.5 s

1/100

10%

TBT (Total Blocking Time)

Value4,490 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.783

5/100

15%

TTI (Time to Interactive)

Value17.7 s

4/100

10%

Network Requests Diagram

gamer.ne.jp

585 ms

www.gamer.ne.jp

1039 ms

reset.css

377 ms

style.css

530 ms

bookmark_button.js

363 ms

Our browser made a total of 323 requests to load all elements on the main page. We found that 8% of them (26 requests) were addressed to the original Gamer.ne.jp, 67% (217 requests) were made to Image.gamer.ne.jp and 2% (6 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Image.gamer.ne.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (43%)

Content Size

2.7 MB

After Optimization

1.6 MB

In fact, the total size of Gamer.ne.jp main page is 2.7 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. 70% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 483.7 kB

  • Original 589.7 kB
  • After minification 457.1 kB
  • After compression 106.0 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 132.6 kB, which is 22% 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 483.7 kB or 82% of the original size.

Image Optimization

-11%

Potential reduce by 146.7 kB

  • Original 1.3 MB
  • After minification 1.2 MB

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, Gamer needs image optimization as it can save up to 146.7 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

-64%

Potential reduce by 422.9 kB

  • Original 664.3 kB
  • After minification 649.2 kB
  • After compression 241.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 422.9 kB or 64% of the original size.

CSS Optimization

-86%

Potential reduce by 115.0 kB

  • Original 133.2 kB
  • After minification 132.3 kB
  • After compression 18.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. Gamer.ne.jp needs all CSS files to be minified and compressed as it can save up to 115.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (17%)

Requests Now

300

After Optimization

249

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

Accessibility Review

gamer.ne.jp accessibility score

71

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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

<frame> or <iframe> elements do not have a title

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

gamer.ne.jp best practices score

83

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

Page has valid source maps

SEO Factors

gamer.ne.jp SEO score

98

Search Engine Optimization Advices

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

    UTF-8

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

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