Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

courrier.jp

クーリエ・ジャポン

Page Load Speed

18.1 sec in total

First Response

342 ms

Resources Loaded

16.3 sec

Page Rendered

1.4 sec

courrier.jp screenshot

About Website

Welcome to courrier.jp homepage info - get ready to check Courrier best content for Japan right away, or after learning these important things about courrier.jp

クーリエ・ジャポンは世界中のメディアから記事を厳選し、日本語に翻訳して掲載しています。グローバルな視点で物事を考える習慣が身につきます。

Visit courrier.jp

Key Findings

We analyzed Courrier.jp page load time and found that the first response time was 342 ms and then it took 17.8 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

courrier.jp performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value29.3 s

0/100

25%

SI (Speed Index)

Value20.8 s

0/100

10%

TBT (Total Blocking Time)

Value3,250 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value38.0 s

0/100

10%

Network Requests Diagram

courrier.jp

342 ms

courrier.jp

2292 ms

css

62 ms

icon

67 ms

animate.css@3.7.0

57 ms

Our browser made a total of 288 requests to load all elements on the main page. We found that 77% of them (221 requests) were addressed to the original Courrier.jp, 3% (8 requests) were made to Google.com and 3% (8 requests) were made to World.courrier.jp. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Courrier.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 546.1 kB (9%)

Content Size

5.9 MB

After Optimization

5.4 MB

In fact, the total size of Courrier.jp main page is 5.9 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 4.6 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 307.7 kB

  • Original 362.1 kB
  • After minification 302.2 kB
  • After compression 54.4 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 59.8 kB, which is 17% 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 307.7 kB or 85% of the original size.

Image Optimization

-4%

Potential reduce by 168.0 kB

  • Original 4.6 MB
  • After minification 4.4 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. Courrier images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 57.8 kB

  • Original 912.3 kB
  • After minification 912.0 kB
  • After compression 854.6 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

-12%

Potential reduce by 12.6 kB

  • Original 104.5 kB
  • After minification 104.2 kB
  • After compression 91.9 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. Courrier.jp needs all CSS files to be minified and compressed as it can save up to 12.6 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 95 (34%)

Requests Now

278

After Optimization

183

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

Accessibility Review

courrier.jp accessibility score

80

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

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

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

courrier.jp SEO score

91

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

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 Courrier.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 Courrier.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 Courrier. 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: