3.2 sec in total
581 ms
2.4 sec
199 ms
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.picsWe 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.
hinode.pics performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value6.6 s
8/100
25%
Value6.8 s
35/100
10%
Value30 ms
100/100
30%
Value0
100/100
15%
Value5.5 s
70/100
10%
581 ms
51 ms
234 ms
480 ms
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 size can be reduced by 531.1 kB (43%)
1.2 MB
707.7 kB
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.
Potential reduce by 68.7 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.
Potential reduce by 10.0 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.
Potential reduce by 452.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.
Potential reduce by 31 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.
Number of requests can be reduced by 65 (60%)
108
43
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.
hinode.pics
581 ms
jquery-ui.css
51 ms
layoutMap
234 ms
index
480 ms
platform.js
137 ms
adsbygoogle.js
41 ms
jquery.min.js
68 ms
jquery-ui.min.js
87 ms
datepicker-ja.js
514 ms
js
40 ms
bookmark_button.js
759 ms
layoutmap
458 ms
jsapi
64 ms
index
699 ms
analytics.js
39 ms
title.png
325 ms
banner_plan_map.png
485 ms
arrow_marker.png
235 ms
social_buttons.png
328 ms
ca-pub-2804452756504734.js
188 ms
zrt_lookup.html
185 ms
show_ads_impl.js
105 ms
collect
62 ms
collect
199 ms
ads
263 ms
osd.js
22 ms
46 ms
common.js
12 ms
util.js
41 ms
marker.js
46 ms
map.js
45 ms
geometry.js
47 ms
poly.js
46 ms
ui+en.css
54 ms
format+en,default+en,ui+en,corechart+en.I.js
59 ms
246 ms
m_js_controller.js
26 ms
abg.js
46 ms
favicon
79 ms
googlelogo_color_112x36dp.png
57 ms
nessie_icon_tiamat_white.png
46 ms
s
27 ms
x_button_blue2.png
12 ms
onion.js
174 ms
openhand_8_8.cur
163 ms
streetview.js
156 ms
ui-bg_flat_75_ffffff_40x100.png
141 ms
ui-bg_highlight-soft_75_cccccc_1x100.png
70 ms
ui-icons_222222_256x240.png
68 ms
transparent.png
69 ms
ViewportInfoService.GetViewportInfo
155 ms
stats.js
63 ms
controls.js
56 ms
undo_poly.png
79 ms
ui
80 ms
7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js
78 ms
infowindow.js
76 ms
css
37 ms
geocoder.js
61 ms
sv4.png
59 ms
google4.png
35 ms
marker_region_02.png
283 ms
mapcnt6.png
34 ms
sv5.png
41 ms
google_white5.png
34 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
29 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
32 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
39 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
38 ms
arrow_marker.png
234 ms
tmapctrl.png
62 ms
cb_scout5.png
77 ms
tmapctrl4.png
76 ms
vt
40 ms
vt
38 ms
vt
40 ms
vt
23 ms
vt
24 ms
vt
25 ms
vt
27 ms
vt
31 ms
vt
27 ms
vt
32 ms
vt
27 ms
vt
30 ms
vt
32 ms
vt
34 ms
vt
35 ms
vt
29 ms
vt
43 ms
vt
44 ms
vt
35 ms
vt
45 ms
vt
41 ms
vt
48 ms
vt
46 ms
vt
45 ms
vt
41 ms
vt
43 ms
vt
50 ms
vt
49 ms
vt
45 ms
vt
45 ms
vt
50 ms
vt
55 ms
vt
44 ms
vt
55 ms
vt
44 ms
vt
45 ms
vt
48 ms
vt
49 ms
vt
46 ms
vt
41 ms
vt
44 ms
vt
43 ms
AuthenticationService.Authenticate
191 ms
hinode.pics accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
hinode.pics best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
hinode.pics SEO score
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
Document doesn't use legible font sizes
Tap targets are not sized appropriately
JA
JA
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.
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: