Tools & Wizards About Us
jp.wazap.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

jp.wazap.com

ゲーム・裏技・攻略 - ワザップ! - 全てのゲーム情報を一つのサイトで

Page Load Speed

5 sec in total

First Response

530 ms

Resources Loaded

4 sec

Page Rendered

427 ms

jp.wazap.com screenshot

About Website

Visit jp.wazap.com now to see the best up-to-date Jp Wazap content for Japan and also check out these interesting facts you probably never knew about jp.wazap.com

ゲーム・裏技・攻略 - ゲーム総合情報ポータル「ワザップ!」は日本最大のゲーム情報サイト！ゲームニュース、ゲーム動画、裏技、攻略、レビュー、質問など間単に閲覧でき、メンバー同士で情報を交換したり、無料ゲームをも楽しめるゲームSNSです。

Visit jp.wazap.com

Key Findings

We analyzed Jp.wazap.com page load time and found that the first response time was 530 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

jp.wazap.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value14.9 s

1/100

10%

TBT (Total Blocking Time)

Value2,900 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.126

83/100

15%

TTI (Time to Interactive)

Value23.6 s

1/100

10%

Network Requests Diagram

jp.wazap.com

530 ms

thickbox.css

384 ms

i2i_header.css

385 ms

reset.css

388 ms

common.css

588 ms

Our browser made a total of 184 requests to load all elements on the main page. We found that 2% of them (4 requests) were addressed to the original Jp.wazap.com, 13% (24 requests) were made to Img.jp.wazap.com and 11% (21 requests) were made to Static.jp.wazap.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Img.jp.wazap.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 577.0 kB (28%)

Content Size

2.0 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jp.wazap.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. 70% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 62.7 kB

  • Original 83.2 kB
  • After minification 79.3 kB
  • After compression 20.5 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 62.7 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 30.0 kB

  • Original 1.1 MB
  • After minification 1.1 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. Jp Wazap images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 375.5 kB

  • Original 692.2 kB
  • After minification 676.8 kB
  • After compression 316.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 375.5 kB or 54% of the original size.

CSS Optimization

-80%

Potential reduce by 108.9 kB

  • Original 135.8 kB
  • After minification 107.2 kB
  • After compression 27.0 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. Jp.wazap.com needs all CSS files to be minified and compressed as it can save up to 108.9 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 105 (64%)

Requests Now

164

After Optimization

59

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jp.wazap.com

jp.wazap.com

530 ms

thickbox.css

thickbox.css

384 ms

i2i_header.css

i2i_header.css

385 ms

reset.css

reset.css

388 ms

common.css

common.css

588 ms

function.css

function.css

398 ms

ecl.js

ecl.js

405 ms

wazap_1.3.js

wazap_1.3.js

598 ms

protothickboxCustomize.js

protothickboxCustomize.js

572 ms

fingerprint.js

fingerprint.js

573 ms

jquery.min.js

jquery.min.js

29 ms

jquery.scrollTo.js

jquery.scrollTo.js

578 ms

common.js

common.js

597 ms

element.js

element.js

47 ms

show_ads.js

show_ads.js

4 ms

conversion.js

conversion.js

47 ms

css

css

60 ms

dc.js

dc.js

77 ms

analytics.js

analytics.js

76 ms

gpt.js

gpt.js

18 ms

ico-siteid.png

ico-siteid.png

647 ms

siteid.png

siteid.png

212 ms

651486_75x75.jpg

651486_75x75.jpg

487 ms

ico_attention.png

ico_attention.png

212 ms

17.png

17.png

212 ms

16.png

16.png

212 ms

11.png

11.png

200 ms

39.png

39.png

200 ms

704906_50x50.png

704906_50x50.png

421 ms

704905_100x100.png

704905_100x100.png

607 ms

706738_100x100.png

706738_100x100.png

581 ms

695083_100x100.png

695083_100x100.png

639 ms

692855_100x100.jpg

692855_100x100.jpg

429 ms

5714_50x50.jpg

5714_50x50.jpg

590 ms

633881_50x50.png

633881_50x50.png

641 ms

705355_50x50.jpg

705355_50x50.jpg

713 ms

597893_50x50.jpg

597893_50x50.jpg

837 ms

597894_63x63.jpg

597894_63x63.jpg

837 ms

686347_63x63.jpg

686347_63x63.jpg

837 ms

704906_63x63.png

704906_63x63.png

842 ms

705356_63x63.jpg

705356_63x63.jpg

892 ms

652604_63x63.jpg

652604_63x63.jpg

840 ms

704851_63x63.jpg

704851_63x63.jpg

1046 ms

701858_63x63.jpg

701858_63x63.jpg

1058 ms

703491_63x63.jpg

703491_63x63.jpg

1058 ms

704844_63x63.png

704844_63x63.png

1057 ms

687922_63x63.jpg

687922_63x63.jpg

1112 ms

372138_63x63.jpg

372138_63x63.jpg

1112 ms

v0SdcGFAl2aezM9Vq_aFTQ.ttf

v0SdcGFAl2aezM9Vq_aFTQ.ttf

75 ms

DvlFBScY1r-FMtZSYIYoYw.ttf

DvlFBScY1r-FMtZSYIYoYw.ttf

95 ms

translateelement.css

translateelement.css

76 ms

main.js

main.js

93 ms

collect

collect

22 ms

__utm.gif

__utm.gif

12 ms

pubads_impl_81.js

pubads_impl_81.js

11 ms

collect

collect

26 ms

container.html

container.html

10 ms

bg.jpg

bg.jpg

2407 ms

bg-gnav.png

bg-gnav.png

315 ms

ico-indexContentSub.png

ico-indexContentSub.png

735 ms

headline-contentSection.png

headline-contentSection.png

534 ms

ico-label.png

ico-label.png

501 ms

headline-contentSection-half.png

headline-contentSection-half.png

324 ms

fontello.woff

fontello.woff

561 ms

element_main.js

element_main.js

49 ms

tag.js

tag.js

27 ms

ca-pub-3859050685269056.js

ca-pub-3859050685269056.js

76 ms

zrt_lookup.html

zrt_lookup.html

112 ms

show_ads_impl.js

show_ads_impl.js

74 ms

tag

tag

95 ms

widgets.js

widgets.js

70 ms

ads

ads

198 ms

osd.js

osd.js

10 ms

ads

ads

213 ms

ads

ads

297 ms

83 ms

__utm.gif

__utm.gif

56 ms

ga.js

ga.js

127 ms

so.js

so.js

425 ms

pixel_p.js

pixel_p.js

422 ms

blade_track_jp.js

blade_track_jp.js

459 ms

ya.js

ya.js

459 ms

conversion_async.js

conversion_async.js

52 ms

adv.js

adv.js

253 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

51 ms

timeline.1b43d11859b7663a2225b885f87704a5.js

timeline.1b43d11859b7663a2225b885f87704a5.js

69 ms

counter.wz

counter.wz

161 ms

loadingAnimation.gif

loadingAnimation.gif

245 ms

ads

ads

325 ms

57 ms

7255130700865501476

7255130700865501476

128 ms

abg.js

abg.js

136 ms

m_js_controller.js

m_js_controller.js

144 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

117 ms

follow_button.6a78875565a912489e9aef879c881358.en.html

follow_button.6a78875565a912489e9aef879c881358.en.html

37 ms

syndication

syndication

168 ms

400442477582090241

400442477582090241

269 ms

69 ms

94 ms

info.json

info.json

226 ms

103 ms

ads.js

ads.js

204 ms

102 ms

75 ms

s

s

19 ms

x_button_blue2.png

x_button_blue2.png

20 ms

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js

25 ms

4480503366930488092

4480503366930488092

46 ms

dg_gateway.js

dg_gateway.js

76 ms

fb6c695453424dfcbf2d5f322b087de7_1.png

fb6c695453424dfcbf2d5f322b087de7_1.png

329 ms

jload

jload

140 ms

adv_inner.js

adv_inner.js

80 ms

2121787287090019553

2121787287090019553

71 ms

translate_24dp.png

translate_24dp.png

62 ms

l

l

125 ms

cleardot.gif

cleardot.gif

57 ms

js

js

240 ms

adv.aspx

adv.aspx

531 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

52 ms

cookie_enabled_get.html

cookie_enabled_get.html

397 ms

pb.js

pb.js

531 ms

403 ms

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

timeline.4d087f49a21e27038d9769d7c976b8fa.default.css

53 ms

mon

mon

31 ms

365 ms

icon_128_normal.png

icon_128_normal.png

141 ms

adv.aspx

adv.aspx

477 ms

dt

dt

203 ms

googlelogo_color_68x28dp.png

googlelogo_color_68x28dp.png

125 ms

te_ctrl3.gif

te_ctrl3.gif

124 ms

loading.gif

loading.gif

125 ms

te_bk.gif

te_bk.gif

54 ms

v3

v3

171 ms

sosync

sosync

318 ms

js

js

338 ms

pixel_p

pixel_p

151 ms

bl_track.cgi

bl_track.cgi

342 ms

pixel

pixel

23 ms

Pug

Pug

19 ms

sync.ad-stir.com

sync.ad-stir.com

299 ms

sync

sync

8 ms

sync

sync

437 ms

is

is

344 ms

sd

sd

4 ms

google

google

150 ms

dgcore.js

dgcore.js

19 ms

adSiteVisit.js

adSiteVisit.js

24 ms

22 ms

sync

sync

360 ms

sync_before

sync_before

187 ms

sync_before

sync_before

162 ms

sync_before

sync_before

191 ms

idsync

idsync

313 ms

sync

sync

318 ms

jot.html

jot.html

10 ms

tr_adv.ashx

tr_adv.ashx

178 ms

tr_adv.ashx

tr_adv.ashx

165 ms

18 ms

sosync

sosync

309 ms

I%21J7mNKWZmk5SSgbkfsrtw%3D%3D

I%21J7mNKWZmk5SSgbkfsrtw%3D%3D

400 ms

cs

cs

311 ms

pixel

pixel

27 ms

sd

sd

19 ms

sync

sync

361 ms

activeview

activeview

13 ms

adfunnel

adfunnel

151 ms

sync

sync

485 ms

is

is

405 ms

Pug

Pug

28 ms

15 ms

sync_before

sync_before

171 ms

16 ms

adgeneration

adgeneration

153 ms

tap.php

tap.php

14 ms

nendRt.js

nendRt.js

37 ms

xrost

xrost

163 ms

oct.js

oct.js

2 ms

adsct

adsct

89 ms

adsct

adsct

38 ms

pta.js

pta.js

324 ms

onetag.ad

onetag.ad

295 ms

sd

sd

4 ms

d.js

d.js

413 ms

34afac76.js

34afac76.js

483 ms

Accessibility Review

jp.wazap.com accessibility score

80

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

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

High

Links do not have a discernible name

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

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

jp.wazap.com best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

jp.wazap.com SEO score

92

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

    N/A

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jp.wazap.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Jp.wazap.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

jp.wazap.com

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