2.8 sec in total
478 ms
2.1 sec
211 ms
Click here to check amazing Ehealthyrecipe content for Japan. Otherwise, check out these important facts you probably never knew about ehealthyrecipe.com
eヘルシーレシピは、第一三共株式会社が、みなさまの健康維持や生活習慣病予防を食と運動の両面から応援するために提供する、無料のインターネットサービスです。
Visit ehealthyrecipe.comWe analyzed Ehealthyrecipe.com page load time and found that the first response time was 478 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
ehealthyrecipe.com performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value18.9 s
0/100
25%
Value11.1 s
6/100
10%
Value410 ms
67/100
30%
Value0.682
8/100
15%
Value9.1 s
33/100
10%
478 ms
317 ms
303 ms
28 ms
31 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 84% of them (38 requests) were addressed to the original Ehealthyrecipe.com, 7% (3 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Ehealthyrecipe.com.
Page size can be reduced by 151.3 kB (19%)
786.1 kB
634.7 kB
In fact, the total size of Ehealthyrecipe.com main page is 786.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 673.5 kB which makes up the majority of the site volume.
Potential reduce by 6.0 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 6.0 kB or 73% of the original size.
Potential reduce by 76.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. Obviously, Ehealthyrecipe needs image optimization as it can save up to 76.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 54.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 54.3 kB or 64% of the original size.
Potential reduce by 15.1 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. Ehealthyrecipe.com needs all CSS files to be minified and compressed as it can save up to 15.1 kB or 79% of the original size.
Number of requests can be reduced by 13 (32%)
41
28
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ehealthyrecipe. 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 as a result speed up the page load time.
ehealthyrecipe.com
478 ms
base.css
317 ms
index.css
303 ms
css
28 ms
jquery.min.js
31 ms
lib.js
350 ms
jquery.fancybox-1.3.4.min.js
475 ms
jquery.featureList-1.0.0.ehr.js
350 ms
base.js
349 ms
home.js
443 ms
ga.js
468 ms
btn_header_logo.gif
468 ms
btn_header_logo_tb.gif
504 ms
gnav_recipe.png
504 ms
gnav_on.png
588 ms
gnav_on2.png
629 ms
gnav_st.png
630 ms
gnav_st2.png
631 ms
gnav_school.png
632 ms
gnav_about.png
635 ms
im_mainvisual_01.jpg
1179 ms
im_mainvisual_02.jpg
939 ms
im_mainvisual_03.jpg
939 ms
im_mainvisual_04.jpg
1261 ms
im_home_nav_01.jpg
1103 ms
im_home_nav_02.jpg
946 ms
im_home_nav_03.jpg
1256 ms
btn_pagetop.png
1096 ms
btn_footer_logo.png
1106 ms
top_popup01_bg.png
1571 ms
top_popup01_bt1.png
1259 ms
top_popup01_bt2.png
1265 ms
top_popup01_bt3.png
1323 ms
top_popup01_bt4.png
1412 ms
top_popup02_bg.png
1415 ms
top_popup02_bt1.png
1416 ms
top_popup02_bt2.png
1420 ms
top_popup02_bt3.png
1468 ms
top_popup02_bt4.png
1568 ms
bg_footer_li.png
1252 ms
kYZt1bJ8UsGAPRGnkXPeFSwlidHJgAgmTjOEEzwu1L8.ttf
29 ms
32nyIRHyCu6iqEka_hbKspS3E-kSBmtLoNJPDtbj2Pk.ttf
40 ms
sKd0EMYPAh5PYCRKSryvWyZ2oysoEQEeKwjgmXLRnTc.ttf
45 ms
analytics.js
28 ms
collect
12 ms
ehealthyrecipe.com accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
ehealthyrecipe.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
ehealthyrecipe.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ehealthyrecipe.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Ehealthyrecipe.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.
ehealthyrecipe.com
Open Graph description is not detected on the main page of Ehealthyrecipe. 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: