4.7 sec in total
798 ms
3.5 sec
380 ms
Visit ehitomi.com now to see the best up-to-date Ehitomi content for Japan and also check out these interesting facts you probably never knew about ehitomi.com
朝のルテイン公式販売店【ひとみの専門店】水溶性ルテインで驚くほどのクッキリ・はっきり感を実現。業界最高レベルのルテイン40mg。100万本突破の実績で、アイサプリクチコミ評価No.1、医療従事者が選んだアイサプリNo.1獲得。目のサプリ利用満足度3冠達成!
Visit ehitomi.comWe analyzed Ehitomi.com page load time and found that the first response time was 798 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
ehitomi.com performance score
name
value
score
weighting
Value2.3 s
74/100
10%
Value11.5 s
0/100
25%
Value4.6 s
71/100
10%
Value180 ms
91/100
30%
Value0.002
100/100
15%
Value8.4 s
38/100
10%
798 ms
529 ms
402 ms
1682 ms
178 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 88% of them (36 requests) were addressed to the original Ehitomi.com, 5% (2 requests) were made to Sitest.jp and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Ehitomi.com.
Page size can be reduced by 188.8 kB (27%)
700.1 kB
511.2 kB
In fact, the total size of Ehitomi.com main page is 700.1 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. 30% of websites need less resources to load. Images take 517.6 kB which makes up the majority of the site volume.
Potential reduce by 11.4 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 11.4 kB or 70% of the original size.
Potential reduce by 69.7 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, Ehitomi needs image optimization as it can save up to 69.7 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 62.8 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 62.8 kB or 55% of the original size.
Potential reduce by 45.0 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. Ehitomi.com needs all CSS files to be minified and compressed as it can save up to 45.0 kB or 86% of the original size.
Number of requests can be reduced by 3 (8%)
39
36
The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ehitomi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
ehitomi.com
798 ms
jquery-1.11.3.min.js
529 ms
site_common.js
402 ms
sitest_js
1682 ms
style-PC.css
178 ms
ga.js
94 ms
site_logo.png
176 ms
icon_cart.png
202 ms
icon_account.png
349 ms
icon_site_logo.png
350 ms
icon_facebook.png
390 ms
header_tel.png
391 ms
global_navi_about.png
401 ms
global_navi_contents.png
409 ms
global_navi_faq.png
521 ms
global_navi_guide.png
523 ms
global_navi_company.png
584 ms
global_navi_blog.png
584 ms
promotion_banner.jpg
1798 ms
icon_about.png
613 ms
icon01.png
693 ms
item_photo.jpg
871 ms
btn_detail.png
777 ms
btn_usually.png
778 ms
arrow_buy.png
816 ms
sp_arrow_buy.png
866 ms
btn_subscription.png
1169 ms
icon_contents.png
996 ms
top_contents_photo.jpg
1231 ms
icon_blog.png
1040 ms
top_blog_photo.jpg
1047 ms
icon_voice.png
1167 ms
top_voice_photo.jpg
1214 ms
members_photo.jpg
1398 ms
btn_link01.png
1361 ms
btn_link02.png
1363 ms
icon_news.png
1389 ms
__utm.gif
14 ms
collect
69 ms
589 ms
style-SP.css
177 ms
ehitomi.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.
ehitomi.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
Browser errors were logged to the console
ehitomi.com 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 uses legible font sizes
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ehitomi.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 Ehitomi.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.
ehitomi.com
Open Graph description is not detected on the main page of Ehitomi. 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: