Report Summary

  • 6

    Performance

    Renders faster than
    30% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    47% of websites

  • 83

    SEO

    Google-friendlier than
    54% of websites

bioweather.net

健康 天気予報 バイオウェザーサービス

Page Load Speed

6.2 sec in total

First Response

561 ms

Resources Loaded

5.2 sec

Page Rendered

428 ms

bioweather.net screenshot

About Website

Click here to check amazing Bioweather content for Japan. Otherwise, check out these important facts you probably never knew about bioweather.net

生気象学に基づく健康気象予報Webサイト。バイオウェザーサービスは、気象・気候・環境などの変化の予測をもとに、健康に関する予報を行い、ぜん息、関節痛などの病気の予防や健康維持に役立てることを目指したサービスです。この健康に関する予報のことを医学気象予報と呼びます。

Visit bioweather.net

Key Findings

We analyzed Bioweather.net page load time and found that the first response time was 561 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

bioweather.net performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value18.2 s

0/100

25%

SI (Speed Index)

Value13.8 s

1/100

10%

TBT (Total Blocking Time)

Value12,460 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.578

12/100

15%

TTI (Time to Interactive)

Value23.4 s

1/100

10%

Network Requests Diagram

bioweather.net

561 ms

css

70 ms

application-ff014bf48a154cd1e74db34597841084.css

656 ms

application-a0674723490ef0e04da56fe1e2f2cdb3.js

1287 ms

gpt.js

18 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 50% of them (35 requests) were addressed to the original Bioweather.net, 7% (5 requests) were made to Tpc.googlesyndication.com and 4% (3 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Bioweather.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (45%)

Content Size

3.2 MB

After Optimization

1.8 MB

In fact, the total size of Bioweather.net main page is 3.2 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. 60% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 179.6 kB

  • Original 225.2 kB
  • After minification 222.2 kB
  • After compression 45.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 179.6 kB or 80% of the original size.

Image Optimization

-5%

Potential reduce by 71.5 kB

  • Original 1.5 MB
  • After minification 1.4 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. Bioweather images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 812.0 kB

  • Original 1.1 MB
  • After minification 930.4 kB
  • After compression 293.2 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 812.0 kB or 73% of the original size.

CSS Optimization

-91%

Potential reduce by 387.2 kB

  • Original 426.0 kB
  • After minification 257.1 kB
  • After compression 38.8 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. Bioweather.net needs all CSS files to be minified and compressed as it can save up to 387.2 kB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (29%)

Requests Now

66

After Optimization

47

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

Accessibility Review

bioweather.net accessibility score

64

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

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

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

bioweather.net best practices score

75

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

bioweather.net SEO score

83

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 Bioweather.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 Bioweather.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 Bioweather. 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: