Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

higashine.com

ひがしねどっとこむ – 東根市は地理的表示(GI)保護制度にも登録されている「東根さくらんぼ」や桃、ぶどう、りんご、ラ・フランスなど四季を通して新鮮なフルーツが楽しめる果樹園王国です!

Page Load Speed

9.5 sec in total

First Response

1.3 sec

Resources Loaded

7.8 sec

Page Rendered

402 ms

higashine.com screenshot

About Website

Welcome to higashine.com homepage info - get ready to check Higashine best content for Japan right away, or after learning these important things about higashine.com

 東北地方、山形県のほぼ中央に位置する「東根市」は、地理的表示(GI)保護制度に登録されている「東根さくらんぼ」に代表されるよう、さくらんぼの生産量が日本一で、さくらんぼのトップブランド「佐藤錦」発祥の地です。 「桃」や「ぶどう」、「りんご」、「ラ・フランス」など四季折々に旬のフルーツが楽しめる「果樹王国ひがしね」として知られ、高速交通網三種の神器、「高速道路・新幹線・空港」が集約し、山形県の交通...

Visit higashine.com

Key Findings

We analyzed Higashine.com page load time and found that the first response time was 1.3 sec and then it took 8.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

higashine.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value15.2 s

1/100

10%

TBT (Total Blocking Time)

Value750 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0.33

34/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

higashine.com

1283 ms

index.php

874 ms

styles.css

862 ms

lang_common.js

375 ms

index.php

818 ms

Our browser made a total of 127 requests to load all elements on the main page. We found that 75% of them (95 requests) were addressed to the original Higashine.com, 21% (27 requests) were made to Static.xx.fbcdn.net and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Higashine.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 114.6 kB (7%)

Content Size

1.7 MB

After Optimization

1.6 MB

In fact, the total size of Higashine.com main page is 1.7 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. 70% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 83.1 kB

  • Original 98.9 kB
  • After minification 98.8 kB
  • After compression 15.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 83.1 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 25.2 kB

  • Original 1.6 MB
  • After minification 1.5 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. Higashine images are well optimized though.

JavaScript Optimization

-24%

Potential reduce by 6.1 kB

  • Original 26.1 kB
  • After minification 23.5 kB
  • After compression 20.0 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 6.1 kB or 24% of the original size.

CSS Optimization

-53%

Potential reduce by 159 B

  • Original 302 B
  • After minification 198 B
  • After compression 143 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. Higashine.com needs all CSS files to be minified and compressed as it can save up to 159 B or 53% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (40%)

Requests Now

126

After Optimization

75

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

Accessibility Review

higashine.com accessibility score

73

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA IDs are not unique

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

higashine.com best practices score

83

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

Low

Detected JavaScript libraries

SEO Factors

higashine.com SEO score

91

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Higashine.com 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 Higashine.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.

Social Sharing Optimization

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