Tools & Wizards About Us
gdatas.com screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

gdatas.com

無料ゲームデータ - 無料フラッシュゲーム満載！

Page Load Speed

23.1 sec in total

First Response

749 ms

Resources Loaded

22.1 sec

Page Rendered

245 ms

gdatas.com screenshot

About Website

Click here to check amazing Gdatas content for Japan. Otherwise, check out these important facts you probably never knew about gdatas.com

簡単に遊べる無料ゲームから本格的なものまである無料フラッシュゲーム集！脱出を始めRPGから遊びながら学べる脳トレーニング系などの無料ゲームを大量紹介。

Visit gdatas.com

Key Findings

We analyzed Gdatas.com page load time and found that the first response time was 749 ms and then it took 22.3 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. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

gdatas.com performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

91/100

10%

LCP (Largest Contentful Paint)

Value2.2 s

95/100

25%

SI (Speed Index)

Value6.3 s

42/100

10%

TBT (Total Blocking Time)

Value630 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

gdatas.com

749 ms

style2.css

348 ms

468x60.js

368 ms

show_ads.js

69 ms

adsbygoogle.js

158 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 29% of them (29 requests) were addressed to the original Gdatas.com, 10% (10 requests) were made to Pagead2.googlesyndication.com and 8% (8 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (19.6 sec) relates to the external source Wj.ax.xrea.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 127.4 kB (9%)

Content Size

1.4 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-75%

Potential reduce by 29.1 kB

  • Original 39.0 kB
  • After minification 38.7 kB
  • After compression 9.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 29.1 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 21.2 kB

  • Original 732.9 kB
  • After minification 711.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. Gdatas images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 70.0 kB

  • Original 613.3 kB
  • After minification 612.3 kB
  • After compression 543.3 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 70.0 kB or 11% of the original size.

CSS Optimization

-83%

Potential reduce by 7.1 kB

  • Original 8.5 kB
  • After minification 6.2 kB
  • After compression 1.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. Gdatas.com needs all CSS files to be minified and compressed as it can save up to 7.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (48%)

Requests Now

89

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gdatas.com

gdatas.com

749 ms

style2.css

style2.css

348 ms

468x60.js

468x60.js

368 ms

show_ads.js

show_ads.js

69 ms

adsbygoogle.js

adsbygoogle.js

158 ms

gdata.js

gdata.js

747 ms

sidelink.js

sidelink.js

369 ms

title.jpg

title.jpg

370 ms

counter.php

counter.php

146 ms

l.j

l.j

334 ms

rranking5.php

rranking5.php

736 ms

border

border

602 ms

banner2.gif

banner2.gif

24 ms

baner.gif

baner.gif

544 ms

banner2.gif

banner2.gif

220 ms

rranking.gif

rranking.gif

559 ms

janpaisuika.gif

janpaisuika.gif

177 ms

decobana.png

decobana.png

176 ms

eneciti.jpg

eneciti.jpg

188 ms

daifugou.jpg

daifugou.jpg

178 ms

mariobossedtion.jpg

mariobossedtion.jpg

398 ms

hoshisaga.jpg

hoshisaga.jpg

396 ms

aatetris.jpg

aatetris.jpg

397 ms

mahjong.jpg

mahjong.jpg

398 ms

hamusyougi.jpg

hamusyougi.jpg

529 ms

2chpoker.jpg

2chpoker.jpg

557 ms

othello.jpg

othello.jpg

701 ms

nanakacrash.jpg

nanakacrash.jpg

528 ms

chibibana.gif

chibibana.gif

529 ms

escapebanner.gif

escapebanner.gif

531 ms

ofbnr.gif

ofbnr.gif

702 ms

funkyland.gif

funkyland.gif

702 ms

88x31_02.gif

88x31_02.gif

703 ms

5000bana.gif

5000bana.gif

707 ms

kisekaebanner.gif

kisekaebanner.gif

743 ms

hangebana.jpg

hangebana.jpg

875 ms

atgames01.jpg

atgames01.jpg

878 ms

gungho02.jpg

gungho02.jpg

1578 ms

janryu04.jpg

janryu04.jpg

1578 ms

pangya06.jpg

pangya06.jpg

1235 ms

rr

rr

406 ms

adsbygoogle.js

adsbygoogle.js

156 ms

show_ads_impl.js

show_ads_impl.js

253 ms

banner2.gif

banner2.gif

14 ms

imp_spot_define.js

imp_spot_define.js

27 ms

zrt_lookup.html

zrt_lookup.html

56 ms

ads

ads

60 ms

imp_spot.ashx

imp_spot.ashx

678 ms

ads

ads

438 ms

NCT_20170606_C_468_60.jpg

NCT_20170606_C_468_60.jpg

253 ms

im-uid.js

im-uid.js

25 ms

imp_spot.ashx

imp_spot.ashx

172 ms

get

get

187 ms

ads

ads

360 ms

rr

rr

162 ms

rr

rr

489 ms

rr

rr

170 ms

rr

rr

191 ms

ads

ads

450 ms

counter_js.php

counter_js.php

73 ms

x.gif

x.gif

167 ms

l9.f

l9.f

19592 ms

ad_native.ashx

ad_native.ashx

184 ms

ts.gif

ts.gif

330 ms

ad_native.ashx

ad_native.ashx

349 ms

5.gif

5.gif

145 ms

1.gif

1.gif

160 ms

6.gif

6.gif

155 ms

0.gif

0.gif

153 ms

4.gif

4.gif

155 ms

null_image.gif

null_image.gif

10 ms

null_image.gif

null_image.gif

22 ms

null_image.gif

null_image.gif

11 ms

1352966249002594887

1352966249002594887

191 ms

abg_lite.js

abg_lite.js

51 ms

s

s

28 ms

window_focus.js

window_focus.js

49 ms

cookie_push_onload.html

cookie_push_onload.html

22 ms

qs_click_protection.js

qs_click_protection.js

48 ms

ufs_web_display.js

ufs_web_display.js

27 ms

one_click_handler_one_afma.js

one_click_handler_one_afma.js

48 ms

icon.png

icon.png

20 ms

i.match

i.match

411 ms

activeview

activeview

87 ms

pixel

pixel

39 ms

pixel

pixel

33 ms

pixel

pixel

31 ms

pixel

pixel

25 ms

pixel

pixel

26 ms

22 ms

WGg91BhL6Bhk3qTAPqmblqNZdzujbVjDoJfr3h8Q3EY.js

WGg91BhL6Bhk3qTAPqmblqNZdzujbVjDoJfr3h8Q3EY.js

6 ms

i.match

i.match

102 ms

pixel

pixel

30 ms

null_image.gif

null_image.gif

25 ms

sodar

sodar

70 ms

RestoreXidToMediaStorage.html

RestoreXidToMediaStorage.html

59 ms

ads

ads

141 ms

sodar2.js

sodar2.js

4 ms

runner.html

runner.html

8 ms

aframe

aframe

30 ms

feg8rL66UTsTrrlS9w_iUH8JqR_kCfLFdi2W6wljJCU.js

feg8rL66UTsTrrlS9w_iUH8JqR_kCfLFdi2W6wljJCU.js

7 ms

Accessibility Review

gdatas.com accessibility score

93

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

Links do not have a discernible name

Best Practices

gdatas.com best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

gdatas.com SEO score

77

Search Engine Optimization Advices

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 Gdatas.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 Gdatas.com 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

gdatas.com

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