Tools & Wizards About Us

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

edwin.co.jp

【公式】EDWIN（エドウイン）ブランドサイト

Page Load Speed

5.7 sec in total

First Response

565 ms

Resources Loaded

4.5 sec

Page Rendered

642 ms

About Website

Visit edwin.co.jp now to see the best up-to-date EDWIN content for Japan and also check out these interesting facts you probably never knew about edwin.co.jp

EDWIN（エドウイン）の公式ブランドサイト。最新のイベントやニュース情報、採用情報をご案内しております。

Visit edwin.co.jp

Key Findings

We analyzed Edwin.co.jp page load time and found that the first response time was 565 ms and then it took 5.2 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

edwin.co.jp performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value15.2 s

0/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value1,640 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.31

38/100

15%

TTI (Time to Interactive)

Value18.6 s

3/100

10%

Network Requests Diagram

edwin.co.jp

565 ms

edwin.co.jp

711 ms

reset.css

175 ms

common.css

696 ms

css2

40 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 70% of them (66 requests) were addressed to the original Edwin.co.jp, 6% (6 requests) were made to Googletagmanager.com and 5% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Edwin.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 105.0 kB (1%)

Content Size

8.7 MB

After Optimization

8.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Edwin.co.jp main page is 8.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. Only a small number of websites need less resources to load. Images take 8.5 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 40.0 kB

  • Original 47.2 kB
  • After minification 29.8 kB
  • After compression 7.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. This page needs HTML code to be minified as it can gain 17.4 kB, which is 37% 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 40.0 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 25.0 kB

  • Original 8.5 MB
  • After minification 8.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. EDWIN images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 672 B

  • Original 139.7 kB
  • After minification 139.7 kB
  • After compression 139.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. This website has mostly compressed JavaScripts.

CSS Optimization

-80%

Potential reduce by 39.3 kB

  • Original 49.4 kB
  • After minification 36.8 kB
  • After compression 10.1 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. Edwin.co.jp needs all CSS files to be minified and compressed as it can save up to 39.3 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (36%)

Requests Now

91

After Optimization

58

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

edwin.co.jp accessibility score

85

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

edwin.co.jp best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

edwin.co.jp SEO score

92

Search Engine Optimization Advices

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

    UTF-8

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