Report Summary

  • 52

    Performance

    Renders faster than
    70% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

ebten.jp

エビテン[ebten] | エンターブレインのオンラインショッピング

Page Load Speed

6.8 sec in total

First Response

871 ms

Resources Loaded

5.6 sec

Page Rendered

336 ms

ebten.jp screenshot

About Website

Click here to check amazing Ebten content for Japan. Otherwise, check out these important facts you probably never knew about ebten.jp

「エビテン(ebten)」、エンターブレインのオンラインショッピングサイト。誌面でおなじみの週刊ファミ通からセガ公式ショップまでバラエティ豊かな品揃えと店舗で営業中

Visit ebten.jp

Key Findings

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

Performance Metrics

ebten.jp performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

49/100

25%

SI (Speed Index)

Value3.6 s

87/100

10%

TBT (Total Blocking Time)

Value1,500 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value6.4 s

59/100

10%

Network Requests Diagram

ebten.jp

871 ms

import.css

314 ms

structure.css

489 ms

component.css

652 ms

jquery-1.8.2.min.js

975 ms

Our browser made a total of 130 requests to load all elements on the main page. We found that 95% of them (124 requests) were addressed to the original Ebten.jp, 2% (2 requests) were made to Google-analytics.com and 2% (2 requests) were made to Cdn.contx.net. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Ebten.jp.

Page Optimization Overview & Recommendations

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

Content Size

6.3 MB

After Optimization

5.9 MB

In fact, the total size of Ebten.jp main page is 6.3 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. 50% of websites need less resources to load. Images take 5.8 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 49.6 kB

  • Original 57.5 kB
  • After minification 39.4 kB
  • After compression 7.9 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. This page needs HTML code to be minified as it can gain 18.1 kB, which is 31% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 49.6 kB or 86% of the original size.

Image Optimization

-1%

Potential reduce by 36.9 kB

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

JavaScript Optimization

-64%

Potential reduce by 146.3 kB

  • Original 229.4 kB
  • After minification 223.9 kB
  • After compression 83.1 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 146.3 kB or 64% of the original size.

CSS Optimization

-86%

Potential reduce by 171.1 kB

  • Original 198.3 kB
  • After minification 129.3 kB
  • After compression 27.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. Ebten.jp needs all CSS files to be minified and compressed as it can save up to 171.1 kB or 86% of the original size.

Requests Breakdown

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

Requests Now

128

After Optimization

97

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

Accessibility Review

ebten.jp accessibility score

78

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 input fields do not have accessible names

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

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

ebten.jp best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

ebten.jp SEO score

85

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ebten.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 Ebten.jp main page’s claimed encoding is euc-jp. 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 Ebten. 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: