Tools & Wizards About Us
anni.tokyo screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

anni.tokyo

Minecraft Annihilation情報サイト

Page Load Speed

4.9 sec in total

First Response

352 ms

Resources Loaded

2.5 sec

Page Rendered

2 sec

anni.tokyo screenshot

About Website

Welcome to anni.tokyo homepage info - get ready to check Anni best content for Japan right away, or after learning these important things about anni.tokyo

Minecraftで遊べる無料ゲームAnniの情報サイト

Visit anni.tokyo

Key Findings

We analyzed Anni.tokyo page load time and found that the first response time was 352 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 70% of websites can load faster.

Performance Metrics

anni.tokyo performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

78/100

25%

SI (Speed Index)

Value14.7 s

1/100

10%

TBT (Total Blocking Time)

Value2,480 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.343

32/100

15%

TTI (Time to Interactive)

Value32.7 s

0/100

10%

Network Requests Diagram

anni.tokyo

352 ms

poole.css

23 ms

syntax.css

26 ms

hyde.css

24 ms

magnific-popup.css

23 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 32% of them (26 requests) were addressed to the original Anni.tokyo, 11% (9 requests) were made to Pagead2.googlesyndication.com and 10% (8 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Anni.tokyo.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (25%)

Content Size

7.0 MB

After Optimization

5.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Anni.tokyo main page is 7.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. Only a small number of websites need less resources to load. Images take 6.0 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 34.4 kB

  • Original 46.1 kB
  • After minification 46.1 kB
  • After compression 11.6 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 34.4 kB or 75% of the original size.

Image Optimization

-25%

Potential reduce by 1.5 MB

  • Original 6.0 MB
  • After minification 4.5 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, Anni needs image optimization as it can save up to 1.5 MB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-20%

Potential reduce by 184.9 kB

  • Original 919.8 kB
  • After minification 919.6 kB
  • After compression 734.9 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 184.9 kB or 20% of the original size.

CSS Optimization

-4%

Potential reduce by 2.6 kB

  • Original 66.0 kB
  • After minification 66.0 kB
  • After compression 63.5 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. Anni.tokyo has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 40 (54%)

Requests Now

74

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

anni.tokyo

anni.tokyo

352 ms

poole.css

poole.css

23 ms

syntax.css

syntax.css

26 ms

hyde.css

hyde.css

24 ms

magnific-popup.css

magnific-popup.css

23 ms

ga.js

ga.js

21 ms

jquery.min.js

jquery.min.js

10 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

38 ms

zoom-image.js

zoom-image.js

36 ms

adsbygoogle.js

adsbygoogle.js

180 ms

analytics.js

analytics.js

131 ms

hOsKO7MV0wE

hOsKO7MV0wE

227 ms

ss.png

ss.png

1319 ms

example.png

example.png

555 ms

status-effect-hud-preference.001.png

status-effect-hud-preference.001.png

550 ms

status-effect-hud-preference.002.png

status-effect-hud-preference.002.png

551 ms

background-on.png

background-on.png

552 ms

name-off.png

name-off.png

556 ms

01.png

01.png

665 ms

02.png

02.png

668 ms

08.png

08.png

669 ms

03.png

03.png

717 ms

04.png

04.png

717 ms

05.png

05.png

873 ms

01.png

01.png

1044 ms

02.png

02.png

1847 ms

03.png

03.png

1046 ms

04.png

04.png

1045 ms

05.png

05.png

1148 ms

06.png

06.png

1151 ms

collect

collect

92 ms

collect

collect

101 ms

show_ads_impl.js

show_ads_impl.js

464 ms

www-player.css

www-player.css

14 ms

js

js

435 ms

www-embed-player.js

www-embed-player.js

34 ms

base.js

base.js

80 ms

wQkdmVX08K_HD_9NHn0QjGfgu04J0GwVvAmYELAxlpM.js

wQkdmVX08K_HD_9NHn0QjGfgu04J0GwVvAmYELAxlpM.js

178 ms

embed.js

embed.js

125 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

190 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

203 ms

zrt_lookup.html

zrt_lookup.html

185 ms

ads

ads

634 ms

Create

Create

166 ms

ads

ads

478 ms

GenerateIT

GenerateIT

14 ms

reactive_library.js

reactive_library.js

146 ms

load_preloaded_resource.js

load_preloaded_resource.js

81 ms

icon.png

icon.png

32 ms

abg_lite.js

abg_lite.js

65 ms

s

s

32 ms

window_focus.js

window_focus.js

77 ms

qs_click_protection.js

qs_click_protection.js

78 ms

ufs_web_display.js

ufs_web_display.js

33 ms

5f7468413707c3abfd197d65a482477f.js

5f7468413707c3abfd197d65a482477f.js

282 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

257 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

264 ms

pixel

pixel

269 ms

17166486116265420778

17166486116265420778

293 ms

abg_lite.js

abg_lite.js

44 ms

omrhp.js

omrhp.js

262 ms

309 ms

Q12zgMmT.js

Q12zgMmT.js

254 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

276 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

275 ms

gen_204

gen_204

251 ms

css

css

150 ms

css

css

161 ms

pixel

pixel

91 ms

pixel

pixel

114 ms

62bHydCX.html

62bHydCX.html

38 ms

activeview

activeview

103 ms

382696.gif

382696.gif

94 ms

ckySkFmwfmQXT3S4i881M7X0Dq040p3kAeEpVWKJmn8.js

ckySkFmwfmQXT3S4i881M7X0Dq040p3kAeEpVWKJmn8.js

19 ms

rum

rum

29 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

22 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

28 ms

font

font

28 ms

pixel

pixel

17 ms

pixel

pixel

17 ms

bounce

bounce

14 ms

rum

rum

34 ms

Accessibility Review

anni.tokyo accessibility score

77

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

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

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

anni.tokyo 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

anni.tokyo SEO score

80

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

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 Anni.tokyo 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 Anni.tokyo 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

anni.tokyo

Open Graph data is detected on the main page of Anni. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: