Tools & Wizards About Us
e840.net screenshot

Report Summary

  • 93

    Performance

    Renders faster than
    92% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

e840.net

食と健康総合サイト「e840net」総合トップページ　食中毒など健康に関する情報を発信

Page Load Speed

6 sec in total

First Response

963 ms

Resources Loaded

4.8 sec

Page Rendered

243 ms

e840.net screenshot

About Website

Welcome to e840.net homepage info - get ready to check E 840 best content for Japan right away, or after learning these important things about e840.net

食と健康総合サイト「e840net」総合トップページ　栄養素や食中毒など食と健康に関する情報を定期的に発信中！

Visit e840.net

Key Findings

We analyzed E840.net page load time and found that the first response time was 963 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

e840.net performance score

93

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

86/100

10%

LCP (Largest Contentful Paint)

Value1.9 s

98/100

25%

SI (Speed Index)

Value4.2 s

78/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.03

100/100

15%

TTI (Time to Interactive)

Value3.7 s

90/100

10%

Network Requests Diagram

e840.net

963 ms

common.css

510 ms

jquery.js

1540 ms

ranking.js

297 ms

analytics.js

34 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 44% of them (19 requests) were addressed to the original E840.net, 14% (6 requests) were made to Rws.a8.net and 14% (6 requests) were made to Thumbnail.image.rakuten.co.jp. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain E840.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 141.8 kB (23%)

Content Size

619.3 kB

After Optimization

477.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of E840.net main page is 619.3 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. 25% of websites need less resources to load. Images take 421.1 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 16.4 kB

  • Original 22.7 kB
  • After minification 21.3 kB
  • After compression 6.2 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 16.4 kB or 73% of the original size.

Image Optimization

-2%

Potential reduce by 7.8 kB

  • Original 421.1 kB
  • After minification 413.4 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. E 840 images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 95.4 kB

  • Original 150.0 kB
  • After minification 148.4 kB
  • After compression 54.5 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 95.4 kB or 64% of the original size.

CSS Optimization

-87%

Potential reduce by 22.2 kB

  • Original 25.6 kB
  • After minification 19.5 kB
  • After compression 3.4 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. E840.net needs all CSS files to be minified and compressed as it can save up to 22.2 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (26%)

Requests Now

39

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 39 CSS, Javascripts, AJAX and image requests in order to completely render the main page of E 840. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

e840.net

e840.net

963 ms

common.css

common.css

510 ms

jquery.js

jquery.js

1540 ms

ranking.js

ranking.js

297 ms

analytics.js

analytics.js

34 ms

counter.cgi

counter.cgi

732 ms

e840topimage1.jpg

e840topimage1.jpg

578 ms

bg_pagetop.gif

bg_pagetop.gif

379 ms

blog.js

blog.js

567 ms

yjapan_logo_110_29.gif

yjapan_logo_110_29.gif

455 ms

006c75a92ba244c6b4cbe2709aa17d7b.gif

006c75a92ba244c6b4cbe2709aa17d7b.gif

1054 ms

btn_search_blue.gif

btn_search_blue.gif

462 ms

e840footerimage1.jpg

e840footerimage1.jpg

497 ms

e840footerimg001.jpg

e840footerimg001.jpg

953 ms

e840footerimg002.jpg

e840footerimg002.jpg

1112 ms

e840footerimg003.jpg

e840footerimg003.jpg

985 ms

e840footerimg004.jpg

e840footerimg004.jpg

1294 ms

e840footerimg07.jpg

e840footerimg07.jpg

663 ms

e840footerimg08.jpg

e840footerimg08.jpg

928 ms

e840footerimg01.jpg

e840footerimg01.jpg

991 ms

e840footerimg02.jpg

e840footerimg02.jpg

1121 ms

e840footerimg03.jpg

e840footerimg03.jpg

1128 ms

e840footerimg04.jpg

e840footerimg04.jpg

1181 ms

e840footerimg05.jpg

e840footerimg05.jpg

1158 ms

e840footerimg06.jpg

e840footerimg06.jpg

1297 ms

collect

collect

13 ms

collect

collect

55 ms

swfobject.js

swfobject.js

368 ms

bg_list.gif

bg_list.gif

375 ms

ranking.cgi

ranking.cgi

154 ms

ranking.cgi

ranking.cgi

649 ms

ranking.cgi

ranking.cgi

736 ms

rakuten.css

rakuten.css

340 ms

viking_main250.jpg

viking_main250.jpg

206 ms

0.gif

0.gif

1199 ms

imgrc0085958117.jpg

imgrc0085958117.jpg

430 ms

na3180.gif

na3180.gif

7 ms

border300_x.gif

border300_x.gif

164 ms

imgrc0065726758.jpg

imgrc0065726758.jpg

4 ms

0.gif

0.gif

366 ms

imgrc0065729380.jpg

imgrc0065729380.jpg

8 ms

wd-03-640.jpg

wd-03-640.jpg

4 ms

0.gif

0.gif

875 ms

Accessibility Review

e840.net accessibility score

61

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

e840.net best practices score

67

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

e840.net SEO score

90

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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 E840.net 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 E840.net 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

e840.net

Open Graph description is not detected on the main page of E 840. 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: