6.8 sec in total
878 ms
3.7 sec
2.3 sec
Welcome to sun-sun.net homepage info - get ready to check Sun best content right away, or after learning these important things about sun-sun.net
ラカンの精神分析理論によって心の病を治療します
Visit sun-sun.netWe analyzed Sun-sun.net page load time and found that the first response time was 878 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
sun-sun.net performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value3.8 s
54/100
25%
Value4.7 s
68/100
10%
Value310 ms
78/100
30%
Value0
100/100
15%
Value7.3 s
50/100
10%
878 ms
348 ms
334 ms
560 ms
820 ms
Our browser made a total of 141 requests to load all elements on the main page. We found that 7% of them (10 requests) were addressed to the original Sun-sun.net, 27% (38 requests) were made to Maps.googleapis.com and 20% (28 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Sun-sun.net.
Page size can be reduced by 1.1 MB (38%)
2.8 MB
1.7 MB
In fact, the total size of Sun-sun.net main page is 2.8 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. 70% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 43.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 43.6 kB or 72% of the original size.
Potential reduce by 53.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. Sun images are well optimized though.
Potential reduce by 960.9 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 960.9 kB or 68% of the original size.
Potential reduce by 20.7 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. Sun-sun.net needs all CSS files to be minified and compressed as it can save up to 20.7 kB or 80% of the original size.
Number of requests can be reduced by 57 (44%)
129
72
The browser has sent 129 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sun. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 44 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
sun-sun.net
878 ms
smartphone.js
348 ms
styles-site.css
334 ms
1593776
560 ms
accnt.php
820 ms
embed
95 ms
kokoro-web_88_31.gif
1347 ms
maps
88 ms
maps
88 ms
ms
88 ms
QR_Code.jpg
803 ms
QR_Code.jpg
586 ms
QR_Code.jpg
589 ms
QR_Code.jpg
800 ms
img01.jpg
353 ms
mark.gif
180 ms
081124_1924~0001.jpg
340 ms
081211_1416~0001.jpg
511 ms
%E2%98%85%E2%98%85%E2%98%85.gif
353 ms
QR_Code.jpg
351 ms
DSC_0015.jpg
2083 ms
embed
161 ms
embed
497 ms
embed
468 ms
ms
80 ms
embed
423 ms
0992f33945a94632a64d2587cfa6f814embedcompiled_fastui_jp.css
4 ms
0992f33945a94632a64d2587cfa6f814embedcompiled__ja.js
19 ms
client.js
54 ms
cb=gapi.loaded_0
8 ms
postmessageRelay
34 ms
1593776
690 ms
3193398744-postmessagerelay.js
22 ms
rpc:shindig_random.js
31 ms
cb=gapi.loaded_0
3 ms
logo-plus.png
38 ms
googlelogo_color_46x16dp.png
48 ms
blank.gif
17 ms
menu_arrow_open.gif
3 ms
icon_print.gif
9 ms
btn_menu6.gif
11 ms
combined_v22.png
21 ms
proxy.html
38 ms
cb=gapi.loaded_0
4 ms
events
514 ms
events
271 ms
js
77 ms
init_embed.js
77 ms
rs=ABjfnFW3NcDEAUOJhqBLkb_g7tp8huHPRg
12 ms
css
101 ms
js
81 ms
rs=ABjfnFVQBvW88iCDiznX0A610DyzZZqHbg
79 ms
rs=ABjfnFVQBvW88iCDiznX0A610DyzZZqHbg
61 ms
common.js
54 ms
map.js
49 ms
overlay.js
54 ms
22-blue-dot.png&filter=ff&scale=1.0
343 ms
util.js
162 ms
marker.js
160 ms
geocoder.js
153 ms
controls.js
154 ms
places_impl.js
152 ms
selection_2x-000.png
38 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
261 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
336 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
403 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
426 ms
gen204
145 ms
common.js
161 ms
map.js
160 ms
google4.png
191 ms
overlay.js
189 ms
onion.js
165 ms
util.js
148 ms
onion.js
148 ms
search_impl.js
216 ms
StaticMapService.GetMapImage
461 ms
openhand_8_8.cur
276 ms
ViewportInfoService.GetViewportInfo
246 ms
stats.js
211 ms
StaticMapService.GetMapImage
197 ms
transparent.png
196 ms
stats.js
168 ms
mapcnt6.png
167 ms
trac.js
651 ms
1593776
476 ms
ViewportInfoService.GetViewportInfo
286 ms
ViewportInfoService.GetViewportInfo
153 ms
kh
309 ms
kh
290 ms
tmapctrl4.png
95 ms
ViewportInfoService.GetViewportInfo
213 ms
ViewportInfoService.GetViewportInfo
82 ms
kh
273 ms
kh
267 ms
controls.js
41 ms
vt
181 ms
vt
181 ms
vt
189 ms
vt
188 ms
vt
189 ms
vt
187 ms
vt
203 ms
entity11.png
125 ms
ViewportInfoService.GetViewportInfo
113 ms
tmapctrl.png
67 ms
vt
147 ms
vt
136 ms
vt
137 ms
vt
128 ms
vt
128 ms
vt
125 ms
vt
166 ms
vt
157 ms
vt
160 ms
vt
156 ms
vt
167 ms
vt
188 ms
vt
233 ms
vt
208 ms
vt
234 ms
vt
242 ms
vt
230 ms
vt
257 ms
vt
285 ms
vt
280 ms
vt
311 ms
vt
295 ms
vt
321 ms
viewer-icons001.png
75 ms
star4.png
71 ms
22-blue-dot.png&scale=1.0
56 ms
AuthenticationService.Authenticate
45 ms
MyMaps_Icons003.png
27 ms
mymaps_32.png
28 ms
v1_4593b7d7.png
30 ms
google-my-maps-logo-small-001.png
30 ms
kh
22 ms
AuthenticationService.Authenticate
26 ms
AuthenticationService.Authenticate
14 ms
cookiesync
534 ms
sun-sun.net accessibility score
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
Definition list items are not wrapped in <dl> 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
<frame> or <iframe> elements do not have a title
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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.
sun-sun.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
sun-sun.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 uses legible font sizes
Tap targets are not sized appropriately
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sun-sun.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 Sun-sun.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.
sun-sun.net
Open Graph description is not detected on the main page of Sun. 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: