Tools & Wizards About Us
starseye.com screenshot

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

starseye.com

眼科スターアイクリニック｜港区赤坂と新座市志木の2院体制にて一般眼科、オルソ、白内障、緑内障などの治療

Page Load Speed

9.5 sec in total

First Response

611 ms

Resources Loaded

8.2 sec

Page Rendered

700 ms

starseye.com screenshot

About Website

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.com

Key Findings

We analyzed Starseye.com page load time and found that the first response time was 611 ms and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

starseye.com performance score

4

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value50.9 s

0/100

25%

SI (Speed Index)

Value12.9 s

2/100

10%

TBT (Total Blocking Time)

Value2,730 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.678

8/100

15%

TTI (Time to Interactive)

Value95.9 s

0/100

10%

Network Requests Diagram

starseye.com

611 ms

www.starseye.com

1506 ms

js

68 ms

css2

33 ms

normalize.css

176 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 94% of them (67 requests) were addressed to the original Starseye.com, 1% (1 request) were made to Googletagmanager.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Starseye.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 366.7 kB (9%)

Content Size

4.3 MB

After Optimization

3.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Starseye.com main page is 4.3 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. 40% of websites need less resources to load. Images take 4.0 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 41.1 kB

  • Original 49.8 kB
  • After minification 41.5 kB
  • After compression 8.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. This page needs HTML code to be minified as it can gain 8.2 kB, which is 17% 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 41.1 kB or 83% of the original size.

Image Optimization

-8%

Potential reduce by 319.7 kB

  • Original 4.0 MB
  • After minification 3.7 MB

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. Starseye images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 126 B

  • Original 130.2 kB
  • After minification 130.2 kB
  • After compression 130.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-10%

Potential reduce by 5.8 kB

  • Original 56.6 kB
  • After minification 56.6 kB
  • After compression 50.8 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 has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 25 (36%)

Requests Now

69

After Optimization

44

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

starseye.com

starseye.com

611 ms

www.starseye.com

www.starseye.com

1506 ms

js

js

68 ms

css2

css2

33 ms

normalize.css

normalize.css

176 ms

swiper.css

swiper.css

352 ms

common.css

common.css

850 ms

style.min.css

style.min.css

524 ms

srpw-frontend.css

srpw-frontend.css

525 ms

libs.js

libs.js

1050 ms

swiper.js

swiper.js

1017 ms

base.js

base.js

607 ms

wp-embed.min.js

wp-embed.min.js

697 ms

script.js

script.js

699 ms

qik2rij.js

qik2rij.js

529 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

233 ms

logo.png

logo.png

222 ms

ic_main01.svg

ic_main01.svg

220 ms

ic_main02.svg

ic_main02.svg

223 ms

ic_main03.svg

ic_main03.svg

320 ms

ic_arr_down.svg

ic_arr_down.svg

325 ms

ic01.svg

ic01.svg

339 ms

ic02.svg

ic02.svg

342 ms

ic03.svg

ic03.svg

351 ms

ic04.svg

ic04.svg

405 ms

ic05.svg

ic05.svg

538 ms

ic06.svg

ic06.svg

533 ms

ic07.svg

ic07.svg

536 ms

ic08.svg

ic08.svg

535 ms

yen_real.png

yen_real.png

539 ms

ic_main04.svg

ic_main04.svg

607 ms

ic_main05.svg

ic_main05.svg

674 ms

ic_main07.svg

ic_main07.svg

678 ms

ic_tt_sp.png

ic_tt_sp.png

687 ms

header_kureka.png

header_kureka.png

721 ms

ic_sub.svg

ic_sub.svg

699 ms

ic_arr02.svg

ic_arr02.svg

808 ms

ic_sp01.svg

ic_sp01.svg

849 ms

ic_sp02.svg

ic_sp02.svg

847 ms

ic_sp03.svg

ic_sp03.svg

864 ms

ic_sp04.svg

ic_sp04.svg

874 ms

starseye_top.png

starseye_top.png

2329 ms

banner02.png

banner02.png

3822 ms

banner03.png

banner03.png

2068 ms

banner04.png

banner04.png

1888 ms

icArr.png

icArr.png

1040 ms

ic_phone02.svg

ic_phone02.svg

1050 ms

img_sc_001.png

img_sc_001.png

1736 ms

img_sc_005.png

img_sc_005.png

1826 ms

ic11.png

ic11.png

1800 ms

ic10.png

ic10.png

1850 ms

feature_ic01.svg

feature_ic01.svg

1873 ms

feature01.png

feature01.png

1882 ms

feature_ic02.svg

feature_ic02.svg

2020 ms

feature02.png

feature02.png

2012 ms

feature_ic03.svg

feature_ic03.svg

1949 ms

feature03.png

feature03.png

1954 ms

feature_ic04.svg

feature_ic04.svg

2077 ms

feature04.png

feature04.png

2076 ms

logo_sub.png

logo_sub.png

2091 ms

ic_tt02.png

ic_tt02.png

2049 ms

p.gif

p.gif

51 ms

ft_img01.png

ft_img01.png

2001 ms

ft_img02.png

ft_img02.png

2055 ms

ft_img03.png

ft_img03.png

2051 ms

ft_img04.png

ft_img04.png

2081 ms

ft_imgEx02.png

ft_imgEx02.png

2090 ms

ft_imgEx03.png

ft_imgEx03.png

2129 ms

ft_img05.png

ft_img05.png

2087 ms

ic_arr.svg

ic_arr.svg

2089 ms

ft_img.png

ft_img.png

2111 ms

Accessibility Review

starseye.com accessibility score

94

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

Links do not have a discernible name

Best Practices

starseye.com 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

SEO Factors

starseye.com SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

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 Starseye.com 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 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.

Social Sharing Optimization

starseye.com

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