Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

efight.jp

eFight【イーファイト】格闘技情報を毎日配信!-official site

Page Load Speed

10 sec in total

First Response

418 ms

Resources Loaded

8.7 sec

Page Rendered

929 ms

efight.jp screenshot

About Website

Welcome to efight.jp homepage info - get ready to check EFight best content for Japan right away, or after learning these important things about efight.jp

eFight【イーファイト】は格闘技ニュース速報、格闘技試合速報、コラム、動画からカラダ作りまで、武道や格闘技に関する情報を網羅しています。イーファイトのeは大会などのエンターテインメントeやエンジョイ、エナジーのe、また「いいファイト(いいfight)」という意味もあります。格闘技情報を通してみなさんが毎日いいファイトできるよう日々更新していきます

Visit efight.jp

Key Findings

We analyzed Efight.jp page load time and found that the first response time was 418 ms and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

efight.jp performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

24/100

25%

SI (Speed Index)

Value31.8 s

0/100

10%

TBT (Total Blocking Time)

Value9,660 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value36.2 s

0/100

10%

Network Requests Diagram

efight.jp

418 ms

efight.jp

1173 ms

gtm.js

72 ms

js

115 ms

superfish.css

385 ms

Our browser made a total of 204 requests to load all elements on the main page. We found that 88% of them (179 requests) were addressed to the original Efight.jp, 2% (4 requests) were made to Google.com and 1% (3 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Efight.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 433.0 kB (6%)

Content Size

7.8 MB

After Optimization

7.4 MB

In fact, the total size of Efight.jp main page is 7.8 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.6 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 171.9 kB

  • Original 202.4 kB
  • After minification 199.1 kB
  • After compression 30.5 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 171.9 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 216.7 kB

  • Original 6.6 MB
  • After minification 6.4 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. EFight images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 36.2 kB

  • Original 943.8 kB
  • After minification 943.4 kB
  • After compression 907.6 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

-25%

Potential reduce by 8.3 kB

  • Original 33.4 kB
  • After minification 33.2 kB
  • After compression 25.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. Efight.jp needs all CSS files to be minified and compressed as it can save up to 8.3 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 49 (24%)

Requests Now

202

After Optimization

153

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

Accessibility Review

efight.jp accessibility score

85

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

Links do not have a discernible name

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

efight.jp 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

efight.jp SEO score

84

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

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

Social Sharing Optimization

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