Tools & Wizards About Us
tamogami.party screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

tamogami.party

tamogami.party | 田母神俊雄公式キュレーション – 第29代航空幕僚長　田母神俊雄のニュースキュレーションメディア。日本を守る！日本を育てる！日本を創る！

Page Load Speed

5.1 sec in total

First Response

576 ms

Resources Loaded

4.4 sec

Page Rendered

143 ms

tamogami.party screenshot

About Website

Visit tamogami.party now to see the best up-to-date Tamogami content for Japan and also check out these interesting facts you probably never knew about tamogami.party

日本を守る！日本を育てる！日本を創る！第29代航空幕僚長 田母神俊雄のニュースキュレーションメディア

Visit tamogami.party

Key Findings

We analyzed Tamogami.party page load time and found that the first response time was 576 ms and then it took 4.6 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

tamogami.party performance score

0

Network Requests Diagram

tamogami.party

576 ms

bootstrap.min.css

10 ms

style.css

7 ms

css

25 ms

font-awesome.min.css

17 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 39% of them (24 requests) were addressed to the original Tamogami.party, 8% (5 requests) were made to Pagead2.googlesyndication.com and 8% (5 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Tamogami.party.

Page Optimization Overview & Recommendations

Page size can be reduced by 261.0 kB (46%)

Content Size

563.7 kB

After Optimization

302.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tamogami.party main page is 563.7 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Javascripts take 201.7 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 30.0 kB

  • Original 38.3 kB
  • After minification 36.6 kB
  • After compression 8.3 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 30.0 kB or 78% of the original size.

Image Optimization

-8%

Potential reduce by 14.1 kB

  • Original 173.4 kB
  • After minification 159.3 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. Tamogami images are well optimized though.

JavaScript Optimization

-48%

Potential reduce by 96.2 kB

  • Original 201.7 kB
  • After minification 192.1 kB
  • After compression 105.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 96.2 kB or 48% of the original size.

CSS Optimization

-80%

Potential reduce by 120.8 kB

  • Original 150.3 kB
  • After minification 143.5 kB
  • After compression 29.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. Tamogami.party needs all CSS files to be minified and compressed as it can save up to 120.8 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (57%)

Requests Now

53

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

tamogami.party

tamogami.party

576 ms

bootstrap.min.css

bootstrap.min.css

10 ms

style.css

style.css

7 ms

css

css

25 ms

font-awesome.min.css

font-awesome.min.css

17 ms

swipebox.min.css

swipebox.min.css

17 ms

twitter-feed.css

twitter-feed.css

491 ms

wpp.css

wpp.css

479 ms

jquery.min.js

jquery.min.js

17 ms

jquery.swipebox.min.js

jquery.swipebox.min.js

510 ms

front.js

front.js

486 ms

bookmark_button.js

bookmark_button.js

559 ms

adsbygoogle.js

adsbygoogle.js

16 ms

jquery-migrate.min.js

jquery-migrate.min.js

540 ms

wp-embed.min.js

wp-embed.min.js

480 ms

bootstrap.min.js

bootstrap.min.js

14 ms

base.js

base.js

932 ms

analytics.js

analytics.js

12 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

926 ms

collect

collect

18 ms

ir

ir

289 ms

ir

ir

312 ms

ir

ir

316 ms

ir

ir

348 ms

1.png

1.png

1138 ms

np_logo.-4.png

np_logo.-4.png

1415 ms

1431412..jpg

1431412..jpg

1262 ms

4W9K2161-150x150.jpg

4W9K2161-150x150.jpg

791 ms

images.jpg

images.jpg

1535 ms

no-img.png

no-img.png

1824 ms

1431499.-100x100.jpg

1431499.-100x100.jpg

1884 ms

np_logo.-4-100x100.png

np_logo.-4-100x100.png

2218 ms

1374777.-100x100.jpg

1374777.-100x100.jpg

2515 ms

1431499.-150x150.jpg

1431499.-150x150.jpg

2859 ms

1431008.-150x150.jpg

1431008.-150x150.jpg

2986 ms

origin_1.-150x150.jpg

origin_1.-150x150.jpg

3307 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

17 ms

icomoon.woff

icomoon.woff

3273 ms

wf-IKpsHcfm0C9uaz9IeGKlknUw7DcFY8X2UkbwMLDg.woff

wf-IKpsHcfm0C9uaz9IeGKlknUw7DcFY8X2UkbwMLDg.woff

18 ms

nzoCWCz0e9c7Mr2Gl8bbgkk91NeiEk8oQQPCeZ5CN8w.woff

nzoCWCz0e9c7Mr2Gl8bbgkk91NeiEk8oQQPCeZ5CN8w.woff

55 ms

zhcz-_WihjSQC0oHJ9TCYBsxEYwM7FgeyaSgU71cLG0.woff

zhcz-_WihjSQC0oHJ9TCYBsxEYwM7FgeyaSgU71cLG0.woff

55 ms

IQHow_FEYlDC4Gzy_m8fcgFhaRv2pGgT5Kf0An0s4MM.woff

IQHow_FEYlDC4Gzy_m8fcgFhaRv2pGgT5Kf0An0s4MM.woff

55 ms

ca-pub-4117288787626293.js

ca-pub-4117288787626293.js

73 ms

zrt_lookup.html

zrt_lookup.html

102 ms

show_ads_impl.js

show_ads_impl.js

69 ms

426 ms

ads

ads

372 ms

osd.js

osd.js

3 ms

51zTMQLvbBL._SL110_.jpg

51zTMQLvbBL._SL110_.jpg

12 ms

5104igoiPjL._SL110_.jpg

5104igoiPjL._SL110_.jpg

12 ms

51MhkuYoCTL._SL110_.jpg

51MhkuYoCTL._SL110_.jpg

44 ms

41Ykq-dwfOL._SL110_.jpg

41Ykq-dwfOL._SL110_.jpg

8 ms

css

css

57 ms

m_js_controller.js

m_js_controller.js

48 ms

abg.js

abg.js

50 ms

favicon

favicon

44 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

18 ms

s

s

10 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

30 ms

x_button_blue2.png

x_button_blue2.png

14 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

2 ms

2UX7WLTfW3W8TclTUvlFyQ.woff

2UX7WLTfW3W8TclTUvlFyQ.woff

26 ms

SEO Factors

tamogami.party SEO score

0

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 Tamogami.party 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 Tamogami.party 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

tamogami.party

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