Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

hitachinaka-rail.co.jp

ひたちなか海浜鉄道株式会社

Page Load Speed

7.9 sec in total

First Response

1.7 sec

Resources Loaded

6.1 sec

Page Rendered

173 ms

About Website

Welcome to hitachinaka-rail.co.jp homepage info - get ready to check Hitachinaka Rail best content for Japan right away, or after learning these important things about hitachinaka-rail.co.jp

茨城県ひたちなか市に本社を置き、茨城交通から湊線を引き継いで経営しているひたちなか市と茨城交通が出資する第三セクター方式の鉄道事業者です。勝田駅から阿字ヶ浦駅までの計10駅14.3kmを運行しています。

Visit hitachinaka-rail.co.jp

Key Findings

We analyzed Hitachinaka-rail.co.jp page load time and found that the first response time was 1.7 sec and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

hitachinaka-rail.co.jp performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value11.9 s

0/100

25%

SI (Speed Index)

Value23.5 s

0/100

10%

TBT (Total Blocking Time)

Value21,020 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.095

91/100

15%

TTI (Time to Interactive)

Value35.4 s

0/100

10%

Network Requests Diagram

www.hitachinaka-rail.co.jp

1711 ms

common.css

319 ms

home.css

320 ms

jquery-1.7.2.js

655 ms

common.js

329 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 72% of them (62 requests) were addressed to the original Hitachinaka-rail.co.jp, 21% (18 requests) were made to Platform.twitter.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Hitachinaka-rail.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 406.1 kB (33%)

Content Size

1.2 MB

After Optimization

843.2 kB

In fact, the total size of Hitachinaka-rail.co.jp main page is 1.2 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. 55% of websites need less resources to load. Images take 694.6 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 26.0 kB

  • Original 36.2 kB
  • After minification 36.0 kB
  • After compression 10.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 26.0 kB or 72% of the original size.

Image Optimization

-0%

Potential reduce by 1.6 kB

  • Original 694.6 kB
  • After minification 693.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. Hitachinaka Rail images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 170.1 kB

  • Original 268.8 kB
  • After minification 249.4 kB
  • After compression 98.7 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 170.1 kB or 63% of the original size.

CSS Optimization

-83%

Potential reduce by 208.4 kB

  • Original 249.7 kB
  • After minification 247.9 kB
  • After compression 41.3 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. Hitachinaka-rail.co.jp needs all CSS files to be minified and compressed as it can save up to 208.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 52 (61%)

Requests Now

85

After Optimization

33

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

Accessibility Review

hitachinaka-rail.co.jp accessibility score

100

Accessibility Issues

Best Practices

hitachinaka-rail.co.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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

hitachinaka-rail.co.jp SEO score

77

Search Engine Optimization Advices

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 Hitachinaka-rail.co.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 Hitachinaka-rail.co.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 description is not detected on the main page of Hitachinaka Rail. 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: