Tools & Wizards About Us
ku-satsu.tokyo screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

ku-satsu.tokyo

ku-satsu.tokyo

Page Load Speed

4.6 sec in total

First Response

748 ms

Resources Loaded

3.5 sec

Page Rendered

325 ms

ku-satsu.tokyo screenshot

About Website

Visit ku-satsu.tokyo now to see the best up-to-date Ku Satsu content for Japan and also check out these interesting facts you probably never knew about ku-satsu.tokyo

空撮人（そらとりびと）は空撮、drone（ドローン）、専用ラジコン、その他空撮に関する最新情報を発信する空撮総合メディアサイトです。

Visit ku-satsu.tokyo

Key Findings

We analyzed Ku-satsu.tokyo page load time and found that the first response time was 748 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

ku-satsu.tokyo performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value12.0 s

0/100

25%

SI (Speed Index)

Value13.3 s

2/100

10%

TBT (Total Blocking Time)

Value4,180 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.402

25/100

15%

TTI (Time to Interactive)

Value20.6 s

2/100

10%

Network Requests Diagram

ku-satsu.tokyo

748 ms

9b82fa73426b1154ddcee05f36fbc4f1.css

334 ms

b3edf7227a6d6c8e62809e55576ed7f1.css

353 ms

front.css

364 ms

styles.css

376 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 55% of them (36 requests) were addressed to the original Ku-satsu.tokyo, 11% (7 requests) were made to Pagead2.googlesyndication.com and 8% (5 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Ku-satsu.tokyo.

Page Optimization Overview & Recommendations

Page size can be reduced by 593.4 kB (26%)

Content Size

2.3 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ku-satsu.tokyo main page is 2.3 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. 65% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 42.9 kB

  • Original 56.3 kB
  • After minification 54.3 kB
  • After compression 13.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 42.9 kB or 76% of the original size.

Image Optimization

-13%

Potential reduce by 221.2 kB

  • Original 1.7 MB
  • After minification 1.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, Ku Satsu needs image optimization as it can save up to 221.2 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-63%

Potential reduce by 221.4 kB

  • Original 352.0 kB
  • After minification 351.8 kB
  • After compression 130.6 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 221.4 kB or 63% of the original size.

CSS Optimization

-85%

Potential reduce by 107.8 kB

  • Original 127.2 kB
  • After minification 98.2 kB
  • After compression 19.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. Ku-satsu.tokyo needs all CSS files to be minified and compressed as it can save up to 107.8 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (50%)

Requests Now

62

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ku-satsu.tokyo

ku-satsu.tokyo

748 ms

9b82fa73426b1154ddcee05f36fbc4f1.css

9b82fa73426b1154ddcee05f36fbc4f1.css

334 ms

b3edf7227a6d6c8e62809e55576ed7f1.css

b3edf7227a6d6c8e62809e55576ed7f1.css

353 ms

front.css

front.css

364 ms

styles.css

styles.css

376 ms

style.css

style.css

600 ms

font-awesome.css

font-awesome.css

406 ms

show_ads.js

show_ads.js

6 ms

logo.png

logo.png

974 ms

adsbygoogle.js

adsbygoogle.js

4 ms

flexslider.css

flexslider.css

388 ms

public.css

public.css

386 ms

platform.js

platform.js

108 ms

2c8ab1ee26dd6a53b67e14938dfdddd7.js

2c8ab1ee26dd6a53b67e14938dfdddd7.js

928 ms

c64a45a9aa2c17cb7d9ae3f9e9c6a72e-1023x397.png

c64a45a9aa2c17cb7d9ae3f9e9c6a72e-1023x397.png

1304 ms

main2-1023x398.png

main2-1023x398.png

1086 ms

hoken-436x272.png

hoken-436x272.png

1150 ms

takara_rc-436x272.png

takara_rc-436x272.png

1698 ms

Xiaomi-436x272.png

Xiaomi-436x272.png

759 ms

primeair1-436x272.png

primeair1-436x272.png

832 ms

solo-436x272.png

solo-436x272.png

1561 ms

secom_airship-436x272.png

secom_airship-436x272.png

1350 ms

MillenniumFalcon-436x272.png

MillenniumFalcon-436x272.png

1473 ms

QuadH2o-436x272.png

QuadH2o-436x272.png

1364 ms

ca-pub-9177522925634639.js

ca-pub-9177522925634639.js

74 ms

zrt_lookup.html

zrt_lookup.html

70 ms

show_ads_impl.js

show_ads_impl.js

71 ms

slide_bg.png

slide_bg.png

1650 ms

3865331ed04fa6e08a48fd13e8bcc949-272x182.png

3865331ed04fa6e08a48fd13e8bcc949-272x182.png

1725 ms

8eb19d2d0c8203443b919472b23ab5bf-272x182.png

8eb19d2d0c8203443b919472b23ab5bf-272x182.png

1754 ms

580e7244514a3520a56b8ac97175aef7-272x182.png

580e7244514a3520a56b8ac97175aef7-272x182.png

1815 ms

f6f923b047b5d124fdca78947067d3c3-272x182.png

f6f923b047b5d124fdca78947067d3c3-272x182.png

1848 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1993 ms

vantage-icons.woff

vantage-icons.woff

1869 ms

ads

ads

245 ms

osd.js

osd.js

9 ms

BEBOP.png

BEBOP.png

1816 ms

more-icon.png

more-icon.png

1850 ms

drone.png

drone.png

1935 ms

dji.png

dji.png

1934 ms

arrow.png

arrow.png

1945 ms

ads

ads

224 ms

ads

ads

270 ms

7123934206994709493

7123934206994709493

46 ms

abg.js

abg.js

46 ms

m_js_controller.js

m_js_controller.js

60 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

167 ms

x_button_blue2.png

x_button_blue2.png

40 ms

s

s

46 ms

favicon

favicon

215 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

86 ms

favicon

favicon

121 ms

analytics.js

analytics.js

59 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

1647 ms

ga.js

ga.js

66 ms

sdk.js

sdk.js

32 ms

widgets.js

widgets.js

145 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

15 ms

95 ms

collect

collect

83 ms

xd_arbiter.php

xd_arbiter.php

83 ms

xd_arbiter.php

xd_arbiter.php

103 ms

__utm.gif

__utm.gif

114 ms

gallery-prev.png

gallery-prev.png

1630 ms

gallery-next.png

gallery-next.png

1631 ms

activeview

activeview

13 ms

Accessibility Review

ku-satsu.tokyo accessibility score

88

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

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

Best Practices

ku-satsu.tokyo best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

ku-satsu.tokyo 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

    N/A

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ku-satsu.tokyo can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Ku-satsu.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

ku-satsu.tokyo

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