Tools & Wizards About Us

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

tonotono.net

フライトお天気

Page Load Speed

4.5 sec in total

First Response

613 ms

Resources Loaded

3.2 sec

Page Rendered

733 ms

About Website

Welcome to tonotono.net homepage info - get ready to check Tonotono best content for Japan right away, or after learning these important things about tonotono.net

フライトに関する必要な気象情報を集めたホームページです。メインページには日本国内とアジア圏のフライトについての情報があります。

Visit tonotono.net

Key Findings

We analyzed Tonotono.net page load time and found that the first response time was 613 ms and then it took 3.9 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

tonotono.net performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value38.3 s

0/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value320 ms

76/100

30%

CLS (Cumulative Layout Shift)

Value0.038

100/100

15%

TTI (Time to Interactive)

Value17.2 s

4/100

10%

Network Requests Diagram

tonotono.net

613 ms

www.tono2.net

1879 ms

A.style.css,q20231215-1.pagespeed.cf.EM31u9TuE1.css

226 ms

sunmoon.js,q1720525950+cookie.js+moon.js+moonage0.js,q1.pagespeed.jc.5MIN3JQtJ-.js

424 ms

ir00.js,q20240709205230+wv00.js,q20240709205230+vis00.js,q20240709205230.pagespeed.jc.q1rmO1RF9A.js

584 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that 8% of them (1 request) were addressed to the original Tonotono.net, 75% (9 requests) were made to Tono2.net and 17% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Tono2.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 111.1 kB (67%)

Content Size

164.7 kB

After Optimization

53.6 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Tonotono.net main page is 164.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. Only 5% of websites need less resources to load. HTML takes 96.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 76.7 kB

  • Original 96.7 kB
  • After minification 94.4 kB
  • After compression 20.0 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 76.7 kB or 79% of the original size.

JavaScript Optimization

-51%

Potential reduce by 34.0 kB

  • Original 66.3 kB
  • After minification 66.3 kB
  • After compression 32.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 34.0 kB or 51% of the original size.

CSS Optimization

-24%

Potential reduce by 400 B

  • Original 1.7 kB
  • After minification 1.7 kB
  • After compression 1.3 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. Tonotono.net needs all CSS files to be minified and compressed as it can save up to 400 B or 24% of the original size.

Requests Breakdown

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

Requests Now

10

After Optimization

5

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

tonotono.net accessibility score

58

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

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

tonotono.net 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

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

tonotono.net SEO score

81

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tonotono.net 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 Tonotono.net 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

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