Tools & Wizards About Us
eiganokuni.com screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

eiganokuni.com

映画の國

Page Load Speed

3.9 sec in total

First Response

568 ms

Resources Loaded

3.2 sec

Page Rendered

103 ms

eiganokuni.com screenshot

About Website

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

映画の國　映画史上の名作５００タイトル以上を擁する紀伊國屋レーベルの魅力や新作NEWSをお知らせするサイトです。

Visit eiganokuni.com

Key Findings

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

Performance Metrics

eiganokuni.com performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value610 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value6.4 s

60/100

10%

Network Requests Diagram

eiganokuni.com

568 ms

www.eiganokuni.com

1088 ms

style.css

578 ms

jquery-1.4.3.min.js

929 ms

jquery.cross-slide.js

468 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 36% of them (21 requests) were addressed to the original Eiganokuni.com, 46% (27 requests) were made to Pbs.twimg.com and 7% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Eiganokuni.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 145.2 kB (8%)

Content Size

1.8 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-65%

Potential reduce by 7.7 kB

  • Original 11.8 kB
  • After minification 11.2 kB
  • After compression 4.1 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 7.7 kB or 65% of the original size.

Image Optimization

-1%

Potential reduce by 17.0 kB

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

JavaScript Optimization

-58%

Potential reduce by 71.4 kB

  • Original 122.8 kB
  • After minification 117.6 kB
  • After compression 51.4 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 71.4 kB or 58% of the original size.

CSS Optimization

-84%

Potential reduce by 49.1 kB

  • Original 58.2 kB
  • After minification 54.2 kB
  • After compression 9.0 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. Eiganokuni.com needs all CSS files to be minified and compressed as it can save up to 49.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (19%)

Requests Now

57

After Optimization

46

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eiganokuni.com

eiganokuni.com

568 ms

www.eiganokuni.com

www.eiganokuni.com

1088 ms

style.css

style.css

578 ms

jquery-1.4.3.min.js

jquery-1.4.3.min.js

929 ms

jquery.cross-slide.js

jquery.cross-slide.js

468 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

646 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

353 ms

title.jpg

title.jpg

184 ms

accessbtn.jpg

accessbtn.jpg

385 ms

menu.jpg

menu.jpg

339 ms

title_news.jpg

title_news.jpg

158 ms

arrow.jpg

arrow.jpg

146 ms

topic_fass.jpg

topic_fass.jpg

156 ms

dvdbd.jpg

dvdbd.jpg

291 ms

footerbunner06.jpg

footerbunner06.jpg

310 ms

footerbunner05.jpg

footerbunner05.jpg

313 ms

footerbunner02.jpg

footerbunner02.jpg

374 ms

footerbunner03.jpg

footerbunner03.jpg

434 ms

widgets.js

widgets.js

137 ms

ga.js

ga.js

10 ms

header_ida.jpg

header_ida.jpg

423 ms

header_sb3.jpg

header_sb3.jpg

759 ms

header_sb2.jpg

header_sb2.jpg

604 ms

__utm.gif

__utm.gif

12 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

138 ms

syndication

syndication

91 ms

346838468124631042

346838468124631042

268 ms

player-placeholder.png

player-placeholder.png

36 ms

proxy.jpg

proxy.jpg

81 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

33 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

106 ms

icon_normal.jpg

icon_normal.jpg

7 ms

jq--yFzH_normal.jpeg

jq--yFzH_normal.jpeg

10 ms

Mv4fgDci_normal.jpg

Mv4fgDci_normal.jpg

12 ms

jU2dRyJT_normal.jpg

jU2dRyJT_normal.jpg

11 ms

4BjV8TZk_normal.jpg

4BjV8TZk_normal.jpg

22 ms

G4vw-3GY_normal.jpeg

G4vw-3GY_normal.jpeg

21 ms

dSj_2c7e_normal.jpg

dSj_2c7e_normal.jpg

15 ms

RVAenvd0_normal.png

RVAenvd0_normal.png

15 ms

OY5LMJ5n_normal.jpg

OY5LMJ5n_normal.jpg

17 ms

___normal.JPG

___normal.JPG

23 ms

___01_normal.jpg

___01_normal.jpg

24 ms

RYnLsuDM_normal.jpeg

RYnLsuDM_normal.jpeg

131 ms

L6VGUxON_normal.jpeg

L6VGUxON_normal.jpeg

137 ms

MQ9LrWZL_normal.jpg

MQ9LrWZL_normal.jpg

26 ms

jNK_duPv_normal.jpeg

jNK_duPv_normal.jpeg

25 ms

w3_8TXdv_normal.jpg

w3_8TXdv_normal.jpg

133 ms

k1hCkiCx_normal.jpeg

k1hCkiCx_normal.jpeg

36 ms

Philo_Shinkan_normal.jpg

Philo_Shinkan_normal.jpg

36 ms

Cd0nFtlUEAArgHZ.jpg

Cd0nFtlUEAArgHZ.jpg

135 ms

CdvkLZhUAAEqj8h.jpg

CdvkLZhUAAEqj8h.jpg

134 ms

CdyaT4aUIAEcmxi.jpg

CdyaT4aUIAEcmxi.jpg

136 ms

CduJ2CQUkAIghgj.jpg

CduJ2CQUkAIghgj.jpg

137 ms

CduKK1OVAAAhv20.jpg

CduKK1OVAAAhv20.jpg

141 ms

CdcA9OGVIAEqQpD.jpg

CdcA9OGVIAEqQpD.jpg

146 ms

CdblvSeUsAEDv8p.jpg:small

CdblvSeUsAEDv8p.jpg:small

134 ms

CdbmdlqUIAEb3bb.jpg:small

CdbmdlqUIAEb3bb.jpg:small

135 ms

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

43 ms

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

121 ms

Accessibility Review

eiganokuni.com accessibility score

70

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

eiganokuni.com 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

eiganokuni.com SEO score

58

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eiganokuni.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Eiganokuni.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

eiganokuni.com

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