Tools & Wizards About Us
hinode.pics screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    76% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

hinode.pics

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

Page Load Speed

3.2 sec in total

First Response

581 ms

Resources Loaded

2.4 sec

Page Rendered

199 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 581 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

hinode.pics performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.5 s

70/100

10%

Network Requests Diagram

hinode.pics

581 ms

jquery-ui.css

51 ms

layoutMap

234 ms

index

480 ms

platform.js

137 ms

Our browser made a total of 116 requests to load all elements on the main page. We found that 10% of them (12 requests) were addressed to the original Hinode.pics, 47% (55 requests) were made to Maps.google.com and 9% (11 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (759 ms) relates to the external source B.st-hatena.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 531.1 kB (43%)

Content Size

1.2 MB

After Optimization

707.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hinode.pics main page is 1.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 745.6 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 68.7 kB

  • Original 78.6 kB
  • After minification 77.1 kB
  • After compression 9.8 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 68.7 kB or 87% of the original size.

Image Optimization

-2%

Potential reduce by 10.0 kB

  • Original 414.3 kB
  • After minification 404.4 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. Hinode images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 452.3 kB

  • Original 745.6 kB
  • After minification 744.9 kB
  • After compression 293.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 452.3 kB or 61% of the original size.

CSS Optimization

-19%

Potential reduce by 31 B

  • Original 160 B
  • After minification 140 B
  • After compression 129 B

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. Hinode.pics needs all CSS files to be minified and compressed as it can save up to 31 B or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 65 (60%)

Requests Now

108

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 108 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 35 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

hinode.pics

hinode.pics

581 ms

jquery-ui.css

jquery-ui.css

51 ms

layoutMap

layoutMap

234 ms

index

index

480 ms

platform.js

platform.js

137 ms

adsbygoogle.js

adsbygoogle.js

41 ms

jquery.min.js

jquery.min.js

68 ms

jquery-ui.min.js

jquery-ui.min.js

87 ms

datepicker-ja.js

datepicker-ja.js

514 ms

js

js

40 ms

bookmark_button.js

bookmark_button.js

759 ms

layoutmap

layoutmap

458 ms

jsapi

jsapi

64 ms

index

index

699 ms

analytics.js

analytics.js

39 ms

title.png

title.png

325 ms

banner_plan_map.png

banner_plan_map.png

485 ms

arrow_marker.png

arrow_marker.png

235 ms

social_buttons.png

social_buttons.png

328 ms

ca-pub-2804452756504734.js

ca-pub-2804452756504734.js

188 ms

zrt_lookup.html

zrt_lookup.html

185 ms

show_ads_impl.js

show_ads_impl.js

105 ms

collect

collect

62 ms

collect

collect

199 ms

ads

ads

263 ms

osd.js

osd.js

22 ms

46 ms

common.js

common.js

12 ms

util.js

util.js

41 ms

marker.js

marker.js

46 ms

map.js

map.js

45 ms

geometry.js

geometry.js

47 ms

poly.js

poly.js

46 ms

ui+en.css

ui+en.css

54 ms

format+en,default+en,ui+en,corechart+en.I.js

format+en,default+en,ui+en,corechart+en.I.js

59 ms

246 ms

m_js_controller.js

m_js_controller.js

26 ms

abg.js

abg.js

46 ms

favicon

favicon

79 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

57 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

46 ms

s

s

27 ms

x_button_blue2.png

x_button_blue2.png

12 ms

onion.js

onion.js

174 ms

openhand_8_8.cur

openhand_8_8.cur

163 ms

streetview.js

streetview.js

156 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

141 ms

ui-bg_highlight-soft_75_cccccc_1x100.png

ui-bg_highlight-soft_75_cccccc_1x100.png

70 ms

ui-icons_222222_256x240.png

ui-icons_222222_256x240.png

68 ms

transparent.png

transparent.png

69 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

155 ms

stats.js

stats.js

63 ms

controls.js

controls.js

56 ms

undo_poly.png

undo_poly.png

79 ms

ui

ui

80 ms

7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js

7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js

78 ms

infowindow.js

infowindow.js

76 ms

css

css

37 ms

geocoder.js

geocoder.js

61 ms

sv4.png

sv4.png

59 ms

google4.png

google4.png

35 ms

marker_region_02.png

marker_region_02.png

283 ms

mapcnt6.png

mapcnt6.png

34 ms

sv5.png

sv5.png

41 ms

google_white5.png

google_white5.png

34 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

29 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

32 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

39 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

38 ms

arrow_marker.png

arrow_marker.png

234 ms

tmapctrl.png

tmapctrl.png

62 ms

cb_scout5.png

cb_scout5.png

77 ms

tmapctrl4.png

tmapctrl4.png

76 ms

vt

vt

40 ms

vt

vt

38 ms

vt

vt

40 ms

vt

vt

23 ms

vt

vt

24 ms

vt

vt

25 ms

vt

vt

27 ms

vt

vt

31 ms

vt

vt

27 ms

vt

vt

32 ms

vt

vt

27 ms

vt

vt

30 ms

vt

vt

32 ms

vt

vt

34 ms

vt

vt

35 ms

vt

vt

29 ms

vt

vt

43 ms

vt

vt

44 ms

vt

vt

35 ms

vt

vt

45 ms

vt

vt

41 ms

vt

vt

48 ms

vt

vt

46 ms

vt

vt

45 ms

vt

vt

41 ms

vt

vt

43 ms

vt

vt

50 ms

vt

vt

49 ms

vt

vt

45 ms

vt

vt

45 ms

vt

vt

50 ms

vt

vt

55 ms

vt

vt

44 ms

vt

vt

55 ms

vt

vt

44 ms

vt

vt

45 ms

vt

vt

48 ms

vt

vt

49 ms

vt

vt

46 ms

vt

vt

41 ms

vt

vt

44 ms

vt

vt

43 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

191 ms

Accessibility Review

hinode.pics accessibility score

80

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

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

89

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