Report Summary

  • 57

    Performance

    Renders faster than
    73% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

live-j.jp

ジョルダンライブ! - ジョルダン

Page Load Speed

4 sec in total

First Response

19 ms

Resources Loaded

3.8 sec

Page Rendered

126 ms

live-j.jp screenshot

About Website

Click here to check amazing Live J content for Japan. Otherwise, check out these important facts you probably never knew about live-j.jp

現場から運行情報を生中継する読者投稿型運行情報サイト『ジョルダンライブ!』では、ユーザの投稿した運行情報をリアルタイムで掲載。どこよりも早い運行情報をお届けします。

Visit live-j.jp

Key Findings

We analyzed Live-j.jp page load time and found that the first response time was 19 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

live-j.jp performance score

57

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

93/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

62/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value1,180 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.9 s

35/100

10%

Network Requests Diagram

live-j.jp

19 ms

live-j.jp

396 ms

reset.css

743 ms

ad.css

731 ms

logo_jl_l.gif

708 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that all of those requests were addressed to Live-j.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Live-j.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 10.9 kB (75%)

Content Size

14.4 kB

After Optimization

3.6 kB

In fact, the total size of Live-j.jp main page is 14.4 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. HTML takes 13.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 10.4 kB

  • Original 13.2 kB
  • After minification 13.2 kB
  • After compression 2.8 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 10.4 kB or 79% of the original size.

CSS Optimization

-38%

Potential reduce by 480 B

  • Original 1.2 kB
  • After minification 1.2 kB
  • After compression 769 B

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. Live-j.jp needs all CSS files to be minified and compressed as it can save up to 480 B or 38% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (84%)

Requests Now

25

After Optimization

4

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

Accessibility Review

live-j.jp accessibility score

89

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

Best Practices

live-j.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

live-j.jp SEO score

87

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

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

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Live-j.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 Live-j.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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