Tools & Wizards About Us
m.otenki.com screenshot

Report Summary

  • 94

    Performance

    Renders faster than
    93% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

m.otenki.com

お天気.com

Page Load Speed

5.7 sec in total

First Response

1.5 sec

Resources Loaded

3.9 sec

Page Rendered

320 ms

m.otenki.com screenshot

About Website

Welcome to m.otenki.com homepage info - get ready to check M Otenki best content for Japan right away, or after learning these important things about m.otenki.com

『普通の天気で満足していますか?』業界最大級・独自のピンポイント天気があなたの生活を劇的に変えてくれます。週間天気は予定が立てやすいよう、1時間〜3時間ごとに見る事ができ、雨雲レーダーは傘を持っていくかの判断材料に。

Visit m.otenki.com

Key Findings

We analyzed M.otenki.com page load time and found that the first response time was 1.5 sec and then it took 4.2 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

m.otenki.com performance score

94

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value2.2 s

94/100

25%

SI (Speed Index)

Value4.5 s

73/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value3.0 s

95/100

10%

Network Requests Diagram

m.otenki.com

1519 ms

outcss.php

537 ms

outjs.php

1299 ms

analytics.js

70 ms

outimg.php

358 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 78% of them (18 requests) were addressed to the original M.otenki.com, 9% (2 requests) were made to Google-analytics.com and 9% (2 requests) were made to Js.ptengine.jp. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain M.otenki.com.

Page Optimization Overview & Recommendations

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

Content Size

127.6 kB

After Optimization

42.1 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of M.otenki.com main page is 127.6 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. 15% of websites need less resources to load. Javascripts take 97.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 21.5 kB

  • Original 26.7 kB
  • After minification 20.5 kB
  • After compression 5.2 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. This page needs HTML code to be minified as it can gain 6.2 kB, which is 23% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 21.5 kB or 80% of the original size.

Image Optimization

-73%

Potential reduce by 2.6 kB

  • Original 3.6 kB
  • After minification 970 B

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, M Otenki needs image optimization as it can save up to 2.6 kB or 73% 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 61.3 kB

  • Original 97.2 kB
  • After minification 97.2 kB
  • After compression 36.0 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 61.3 kB or 63% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (38%)

Requests Now

21

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

m.otenki.com

m.otenki.com

1519 ms

outcss.php

outcss.php

537 ms

outjs.php

outjs.php

1299 ms

analytics.js

analytics.js

70 ms

outimg.php

outimg.php

358 ms

63652.gif

63652.gif

205 ms

outimg.php

outimg.php

371 ms

outimg.php

outimg.php

386 ms

outimg.php

outimg.php

390 ms

outimg.php

outimg.php

409 ms

outimg.php

outimg.php

408 ms

outimg.php

outimg.php

537 ms

outimg.php

outimg.php

556 ms

outimg.php

outimg.php

577 ms

outimg.php

outimg.php

581 ms

63914.gif

63914.gif

611 ms

63901.gif

63901.gif

609 ms

63650.gif

63650.gif

713 ms

63671.gif

63671.gif

737 ms

pta.js

pta.js

485 ms

collect

collect

16 ms

collect

collect

60 ms

2cd556a0.js

2cd556a0.js

494 ms

Accessibility Review

m.otenki.com accessibility score

66

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

Image elements do not have [alt] attributes

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

m.otenki.com 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

User Experience

Impact

Issue

High

Serves images with low resolution

SEO Factors

m.otenki.com SEO score

92

Search Engine Optimization Advices

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

    JA

  • Encoding

    SHIFT_JIS

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

m.otenki.com

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