Tools & Wizards About Us
hinode.pics screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

hinode.pics

日の出日の入時刻方角マップ

Page Load Speed

3.8 sec in total

First Response

593 ms

Resources Loaded

3.1 sec

Page Rendered

61 ms

hinode.pics screenshot

About Website

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

「日の出」と「日の入り」の方角・時刻を表示する定番サイト。地図上のクリックした場所の日の出・日の入の時間と方角を表示するだけの、非常に簡単なサイトです。現在地ボタンもあるので、今いる場所の日の出と日の入時刻を確認するのも簡単です。また、都道府県別の年間の日の出日の入り時刻グラフもあります。

Visit hinode.pics

Key Findings

We analyzed Hinode.pics page load time and found that the first response time was 593 ms and then it took 3.2 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

hinode.pics performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

3/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value660 ms

45/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.6 s

47/100

10%

Network Requests Diagram

hinode.pics

593 ms

hinode.pics

884 ms

jquery-ui.css

37 ms

leaflet.css

54 ms

MarkerCluster.css

65 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 23% of them (7 requests) were addressed to the original Hinode.pics, 20% (6 requests) were made to Hinode.azureedge.net and 13% (4 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Hinode.pics.

Page Optimization Overview & Recommendations

Page size can be reduced by 146.2 kB (28%)

Content Size

521.1 kB

After Optimization

374.9 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Hinode.pics main page is 521.1 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 484.1 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 16.2 kB

  • Original 21.8 kB
  • After minification 19.7 kB
  • After compression 5.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 16.2 kB or 74% of the original size.

Image Optimization

-22%

Potential reduce by 3.4 kB

  • Original 15.2 kB
  • After minification 11.8 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. Obviously, Hinode needs image optimization as it can save up to 3.4 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-26%

Potential reduce by 126.7 kB

  • Original 484.1 kB
  • After minification 484.1 kB
  • After compression 357.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 126.7 kB or 26% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (56%)

Requests Now

27

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hinode.pics

hinode.pics

593 ms

hinode.pics

hinode.pics

884 ms

jquery-ui.css

jquery-ui.css

37 ms

leaflet.css

leaflet.css

54 ms

MarkerCluster.css

MarkerCluster.css

65 ms

MarkerCluster.Default.css

MarkerCluster.Default.css

71 ms

layoutMap

layoutMap

209 ms

index

index

420 ms

js

js

96 ms

adsbygoogle.js

adsbygoogle.js

65 ms

jquery.min.js

jquery.min.js

42 ms

jquery-ui.min.js

jquery-ui.min.js

53 ms

bookmark_button.js

bookmark_button.js

42 ms

layoutMap202008

layoutMap202008

942 ms

leaflet.markercluster.js

leaflet.markercluster.js

70 ms

jsapi

jsapi

42 ms

map

map

1651 ms

loader.js

loader.js

17 ms

title.png

title.png

111 ms

icon_home.png

icon_home.png

105 ms

icon_google_maps.png

icon_google_maps.png

106 ms

loading_002.gif

loading_002.gif

158 ms

social_buttons.png

social_buttons.png

105 ms

icon_Instagram.png

icon_Instagram.png

104 ms

show_ads_impl.js

show_ads_impl.js

104 ms

zrt_lookup.html

zrt_lookup.html

30 ms

ads

ads

74 ms

ajax-loader.gif

ajax-loader.gif

347 ms

ads

ads

338 ms

ca-pub-2804452756504734

ca-pub-2804452756504734

107 ms

Accessibility Review

hinode.pics accessibility score

74

Accessibility Issues

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

Form elements do not have associated labels

High

Links do not have a discernible name

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

hinode.pics 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

hinode.pics SEO score

82

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

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 Hinode.pics 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 Hinode.pics 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

hinode.pics

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