Tools & Wizards About Us
cortese.jp screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

cortese.jp

オーダーシャツ専門店コルテーゼ 2着15,290円（税込）～

Page Load Speed

4.5 sec in total

First Response

523 ms

Resources Loaded

3.2 sec

Page Rendered

789 ms

cortese.jp screenshot

About Website

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

東京のオーダーシャツ直営4店舗、国内自社工場の高品質2着税込15290円～、オンライン12870円～。最高級コストパフォーマンス。「王様の仕立て屋」の片瀬さん紹介店舗。

Visit cortese.jp

Key Findings

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

Performance Metrics

cortese.jp performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value27.3 s

0/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value2,130 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.023

100/100

15%

TTI (Time to Interactive)

Value22.0 s

1/100

10%

Network Requests Diagram

cortese.jp

523 ms

www.cortese.jp

545 ms

ress.min.css

52 ms

style.css

182 ms

css2

43 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 44% of them (27 requests) were addressed to the original Cortese.jp, 23% (14 requests) were made to Static.xx.fbcdn.net and 8% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Cortese.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 218.7 kB (4%)

Content Size

5.6 MB

After Optimization

5.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cortese.jp main page is 5.6 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 31.5 kB

  • Original 38.3 kB
  • After minification 21.8 kB
  • After compression 6.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. This page needs HTML code to be minified as it can gain 16.5 kB, which is 43% 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 31.5 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 126.1 kB

  • Original 5.2 MB
  • After minification 5.1 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. Cortese images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 58.1 kB

  • Original 280.6 kB
  • After minification 280.6 kB
  • After compression 222.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 58.1 kB or 21% of the original size.

CSS Optimization

-4%

Potential reduce by 2.9 kB

  • Original 78.1 kB
  • After minification 78.1 kB
  • After compression 75.2 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. Cortese.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 25 (42%)

Requests Now

59

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

cortese.jp

cortese.jp

523 ms

www.cortese.jp

www.cortese.jp

545 ms

ress.min.css

ress.min.css

52 ms

style.css

style.css

182 ms

css2

css2

43 ms

all.css

all.css

46 ms

jquery.min.js

jquery.min.js

38 ms

jquery-3.1.0.min.js

jquery-3.1.0.min.js

22 ms

jquery.min.js

jquery.min.js

21 ms

widgets.js

widgets.js

94 ms

ress.min.css

ress.min.css

19 ms

M9D21GpC6DY

M9D21GpC6DY

207 ms

page.php

page.php

107 ms

logo.png

logo.png

526 ms

f-icon.png

f-icon.png

524 ms

x-logo.jpg

x-logo.jpg

767 ms

i-icon.png

i-icon.png

525 ms

hiraoki.jpg

hiraoki.jpg

1049 ms

cora-san.jpg

cora-san.jpg

1574 ms

bt-n.png

bt-n.png

546 ms

%20%20import_f.jpg

%20%20import_f.jpg

1396 ms

r_toni-242-23.jpg

r_toni-242-23.jpg

1259 ms

ac.jpg

ac.jpg

1043 ms

book.jpg

book.jpg

1035 ms

senkensinbun_s.jpg

senkensinbun_s.jpg

1552 ms

white-shirt-min.jpg

white-shirt-min.jpg

1387 ms

bt-w.png

bt-w.png

1224 ms

price-bg-w-min.jpg

price-bg-w-min.jpg

1401 ms

bt-r.png

bt-r.png

1439 ms

bt-b.png

bt-b.png

1562 ms

facebook.png

facebook.png

1573 ms

insta.png

insta.png

1578 ms

preinsta.png

preinsta.png

1795 ms

nihonnbasibrog.png

nihonnbasibrog.png

1726 ms

hongo.jpg

hongo.jpg

1908 ms

komagomebrog.png

komagomebrog.png

1752 ms

mitablog.png

mitablog.png

1748 ms

eOzOzediAge.css

eOzOzediAge.css

24 ms

XVfyC-hY3iC.js

XVfyC-hY3iC.js

28 ms

4vv_Lf70fZS.js

4vv_Lf70fZS.js

19 ms

8O2J-mJIMh1.js

8O2J-mJIMh1.js

21 ms

Y4lQlibYsna.js

Y4lQlibYsna.js

22 ms

4aFcRp6-srT.js

4aFcRp6-srT.js

22 ms

Mgao39tvtRW.js

Mgao39tvtRW.js

24 ms

HYZXJ6lnRqE.js

HYZXJ6lnRqE.js

27 ms

p55HfXW__mM.js

p55HfXW__mM.js

57 ms

knF92sc18tr.js

knF92sc18tr.js

59 ms

0oAcl5WIW_m.js

0oAcl5WIW_m.js

57 ms

mtuC5ESzCwN.js

mtuC5ESzCwN.js

58 ms

www-player.css

www-player.css

73 ms

281178715_3255191041386119_1928745538644255244_n.jpg

281178715_3255191041386119_1928745538644255244_n.jpg

337 ms

mFWyxjCB51c.js

mFWyxjCB51c.js

34 ms

294597726_566811955135419_5779972708018197154_n.jpg

294597726_566811955135419_5779972708018197154_n.jpg

323 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

31 ms

www-embed-player.js

www-embed-player.js

43 ms

base.js

base.js

71 ms

ad_status.js

ad_status.js

147 ms

JmVHWlJsGZ7gACl_O_OPl3DM-f3eAs-2RE9hBJUXhqA.js

JmVHWlJsGZ7gACl_O_OPl3DM-f3eAs-2RE9hBJUXhqA.js

95 ms

embed.js

embed.js

34 ms

id

id

22 ms

Create

Create

100 ms

GenerateIT

GenerateIT

13 ms

Accessibility Review

cortese.jp accessibility score

72

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

cortese.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 Cortese.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 Cortese.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

cortese.jp

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