6.4 sec in total
554 ms
5.3 sec
486 ms
Click here to check amazing Shec content for Japan. Otherwise, check out these important facts you probably never knew about shec.jp
新宿駅 東口徒歩1分の眼科、新宿東口眼科医院。平日は7時半まで受付、土日祝も診療している眼科です。日帰り白内障手術応需、小児眼科医が常勤で勤務しています。
Visit shec.jpWe analyzed Shec.jp page load time and found that the first response time was 554 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
shec.jp performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value8.4 s
2/100
25%
Value7.6 s
25/100
10%
Value320 ms
76/100
30%
Value0
100/100
15%
Value7.6 s
46/100
10%
554 ms
1194 ms
6 ms
1135 ms
507 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 88% of them (79 requests) were addressed to the original Shec.jp, 2% (2 requests) were made to Google-analytics.com and 2% (2 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Shec.jp.
Page size can be reduced by 383.4 kB (27%)
1.4 MB
1.0 MB
In fact, the total size of Shec.jp main page is 1.4 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. 25% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 46.3 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 7.5 kB, which is 12% 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 46.3 kB or 77% of the original size.
Potential reduce by 79.6 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. Shec images are well optimized though.
Potential reduce by 180.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 180.3 kB or 72% of the original size.
Potential reduce by 77.2 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. Shec.jp needs all CSS files to be minified and compressed as it can save up to 77.2 kB or 83% of the original size.
Number of requests can be reduced by 11 (13%)
88
77
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shec. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
shec.jp
554 ms
www.shec.jp
1194 ms
jquery.min.js
6 ms
jquery.min.js
1135 ms
reset.css
507 ms
index_pc.css
1071 ms
index_sp.css
909 ms
nav.js
366 ms
flexslider.css
577 ms
jquery.flexslider.js
1196 ms
dclock04.js
494 ms
masonry.pkgd.js
1187 ms
analytics.js
10 ms
collect
12 ms
banner_logo_195_60.gif
894 ms
back.gif
175 ms
header_logo.png
170 ms
header_ac.png
189 ms
header_moving.png
189 ms
header_ike.png
188 ms
header_fp_rp.png
334 ms
header_tel.png
337 ms
gn01.png
373 ms
gn02.png
373 ms
gn03.png
371 ms
gn04.png
518 ms
nav_01.png
518 ms
nav_02.png
530 ms
nav_03.png
537 ms
nav_04.png
543 ms
nav_05.png
661 ms
nav_06.png
652 ms
ban_cat_l.png
1533 ms
ban_cat_entry_m.png
881 ms
slide_top.jpg
1291 ms
slider6.jpg
1534 ms
slider2.jpg
1130 ms
slider3.jpg
1061 ms
slider4.jpg
1248 ms
slider5.jpg
1623 ms
resv.gif
1294 ms
time.png
1423 ms
time_sp.png
1678 ms
bn_night_index.png
1500 ms
bn_night_sp.png
1596 ms
ban_cat_entry_top.jpg
1676 ms
bn_03.jpg
1708 ms
bn_02.jpg
1718 ms
bn_firstcl.png
1774 ms
bn_04.png
1794 ms
sdk.js
269 ms
bn_kafun_pc.png
1680 ms
bn_01.jpg
1702 ms
rsv_00.png
1696 ms
rsv_01retina.png
1722 ms
rsv_02dryeye.png
1768 ms
rsv_03gla.png
1683 ms
rsv_04mc.png
1677 ms
rsv_05cat.png
1683 ms
QRcode_mobile.gif
1674 ms
157 ms
p_feature.jpg
1723 ms
xd_arbiter.php
213 ms
xd_arbiter.php
424 ms
p_staff.jpg
1783 ms
p_staff_sp.png
1663 ms
map.png
1890 ms
fb_qr.png
1724 ms
dr2.jpg
1904 ms
rsv_09shikawa.png
1758 ms
like.php
159 ms
rsv_07retina.png
1694 ms
rsv_08dryeye.png
1760 ms
wy1X4hBW7e7.js
486 ms
LVx-xkvaJ0b.png
545 ms
rsv_10mc.png
1592 ms
rsv_11gla.png
1430 ms
rsv_12cat.png
1380 ms
rsv_13shinkawa.png
1356 ms
dr3.jpg
1296 ms
rsv_14namikawa.png
1326 ms
dr1.jpg
1223 ms
news.gif
1170 ms
ar_right.png
1140 ms
access.gif
1217 ms
mailm.gif
1191 ms
fb.png
1173 ms
doct.gif
1139 ms
footer_logo.png
1153 ms
ar_footer.gif
1139 ms
shec.jp 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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.
shec.jp 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
Detected JavaScript libraries
shec.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
![]()
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shec.jp 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 Shec.jp 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.
shec.jp
Open Graph description is not detected on the main page of Shec. 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: