14.2 sec in total
5.4 sec
8.6 sec
195 ms
Welcome to starseye.com homepage info - get ready to check Starseye best content for Japan right away, or after learning these important things about starseye.com
眼科スターアイクリニックは、港区赤坂溜池山王と埼玉県新座市志木の2院体制にて、一般眼科、近視抑制や矯正のオルソケラトロジー、白内障や緑内障の治療(手術)、コンタクトレンズの処方、眼科ドックを行っています。目のことにつきましては、お気軽にご相談ください。
Visit starseye.comWe analyzed Starseye.com page load time and found that the first response time was 5.4 sec and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
starseye.com performance score
name
value
score
weighting
Value7.2 s
1/100
10%
Value15.0 s
0/100
25%
Value22.0 s
0/100
10%
Value22,080 ms
0/100
30%
Value0.676
8/100
15%
Value101.0 s
0/100
10%
5357 ms
295 ms
312 ms
312 ms
546 ms
Our browser made a total of 112 requests to load all elements on the main page. We found that 98% of them (110 requests) were addressed to the original Starseye.com, 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.4 sec) belongs to the original domain Starseye.com.
Page size can be reduced by 257.1 kB (29%)
900.8 kB
643.8 kB
In fact, the total size of Starseye.com main page is 900.8 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. 45% of websites need less resources to load. Images take 743.1 kB which makes up the majority of the site volume.
Potential reduce by 32.1 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. This page needs HTML code to be minified as it can gain 5.8 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 32.1 kB or 81% of the original size.
Potential reduce by 142.1 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, Starseye needs image optimization as it can save up to 142.1 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 30.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 30.2 kB or 53% of the original size.
Potential reduce by 52.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. Starseye.com needs all CSS files to be minified and compressed as it can save up to 52.7 kB or 85% of the original size.
Number of requests can be reduced by 43 (39%)
111
68
The browser has sent 111 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Starseye. 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 9 to 1 for CSS and as a result speed up the page load time.
starseye.com
5357 ms
rollover.js
295 ms
event.js
312 ms
import.css
312 ms
top_akasaka.css
546 ms
fontchanger.css
393 ms
fsize_m.css
440 ms
fsize_s.css
467 ms
fsize_l.css
468 ms
common.js
588 ms
css_browser_selector.js
585 ms
font.js
622 ms
heightLine.js
623 ms
SpryMenuBarHorizontal.css
682 ms
SpryMenuBar.js
907 ms
swfobject.js
731 ms
fontsize.js
617 ms
default.css
468 ms
common.css
622 ms
copyright.js
347 ms
cat1.jpg
936 ms
bg_body.jpg
175 ms
txt_logo.jpg
158 ms
txt_h1.jpg
393 ms
btn_header_to_akasaka_second.jpg
304 ms
txt_tel_akasaka_all.jpg
197 ms
bg_btn_box.jpg
158 ms
arw_next.gif
322 ms
btn_lang_eg.gif
323 ms
ph_top_01.jpg
354 ms
ph_top_02.jpg
395 ms
ph_top_03.jpg
464 ms
pct_interview_title.jpg
500 ms
btn_interview_03.jpg
491 ms
btn_interview_02.jpg
535 ms
btn_interview_01.jpg
593 ms
pct_sidemenu_bottom.gif
577 ms
bnr_taidan.jpg
623 ms
btn_beauty_top.jpg
652 ms
pla.jpg
657 ms
btn_experience_top.jpg
722 ms
btn_akasaka_lenses.jpg
759 ms
ttl_akasaka.gif
788 ms
btn_media_top.jpg
778 ms
btn_institution_top.jpg
1073 ms
droono1845.png
1063 ms
ttl_news.jpg
896 ms
btn_to_news.gif
948 ms
ttls_medical.jpg
929 ms
ph_top_medical01.jpg
983 ms
arw_guide_link.gif
1080 ms
ph_top_medical02.jpg
1075 ms
ph_top_medical03.jpg
1130 ms
ph_top_medical04.jpg
1180 ms
ph_top_medical05.jpg
1227 ms
ph_top_medical06.jpg
1228 ms
ph_top_medical07.jpg
1210 ms
ga.js
7 ms
__utm.gif
15 ms
ph_top_medical10.jpg
1102 ms
ph_top_medical08.jpg
1161 ms
mds_accessmap.jpg
1210 ms
btn_to_access.gif
1196 ms
pct_maptop.gif
1088 ms
icon_metro.gif
1086 ms
arw_05.gif
1108 ms
arw_credit.jpg
1147 ms
btn_fontsize_s.gif
1187 ms
btn_fontsize_m_on.gif
1152 ms
btn_fontsize_l.gif
1077 ms
bg_menu_top_f_single.jpg
1073 ms
bg_menu_top.jpg
1103 ms
pct_sidemenu_top.gif
1150 ms
bg_sidemenu.gif
1110 ms
bg_akasaka.gif
1109 ms
bg_akasaka_txt.jpg
1097 ms
ttl_news_bg_btn.jpg
1133 ms
bg_guideBox.gif
1132 ms
bg_box.gif
1155 ms
arw_guide.gif
1079 ms
bg_info_right.gif
1081 ms
mds_accessmap_bg_btn.jpg
1087 ms
pct_info_right_bottom.gif
1089 ms
bg_footerArea.jpg
1030 ms
cat1_o.jpg
199 ms
btn_header_to_akasaka_second_o.jpg
179 ms
btn_lang_eg_o.gif
159 ms
btn_interview_03_o.jpg
205 ms
btn_interview_02_o.jpg
149 ms
btn_interview_01_o.jpg
195 ms
bnr_taidan_o.jpg
169 ms
btn_beauty_top_o.jpg
300 ms
pla_o.jpg
316 ms
btn_experience_top_o.jpg
327 ms
btn_akasaka_lenses_o.jpg
350 ms
btn_media_top_o.jpg
393 ms
btn_institution_top_o.jpg
413 ms
btn_to_news_o.gif
446 ms
ph_top_medical01_o.jpg
485 ms
ph_top_medical02_o.jpg
485 ms
ph_top_medical03_o.jpg
521 ms
ph_top_medical04_o.jpg
588 ms
ph_top_medical05_o.jpg
609 ms
ph_top_medical06_o.jpg
592 ms
ph_top_medical07_o.jpg
641 ms
ph_top_medical10_o.jpg
640 ms
ph_top_medical08_o.jpg
708 ms
btn_to_access_o.gif
788 ms
pct_maptop_o.gif
744 ms
bg_menu_click_31.jpg
805 ms
bg_menu_keep_31.jpg
795 ms
bg_menu_top_single.jpg
795 ms
starseye.com 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
Links do not have a discernible name
starseye.com 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
starseye.com 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
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Starseye.com 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 Starseye.com 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.
starseye.com
Open Graph description is not detected on the main page of Starseye. 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: