Report Summary

  • 52

    Performance

    Renders faster than
    69% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 50

    SEO

    Google-friendlier than
    18% of websites

cgl.co.jp

[ダイヤモンドのグレーディング・宝石の鑑定、鑑別・宝石鑑定書] 中央宝石研究所(CGL)

Page Load Speed

10.9 sec in total

First Response

543 ms

Resources Loaded

10.2 sec

Page Rendered

219 ms

cgl.co.jp screenshot

About Website

Click here to check amazing CGL content for India. Otherwise, check out these important facts you probably never knew about cgl.co.jp

ダイヤモンド・宝石鑑定のエキスパート、中央宝石研究所

Visit cgl.co.jp

Key Findings

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

Performance Metrics

cgl.co.jp performance score

52

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.042

99/100

15%

TTI (Time to Interactive)

Value7.3 s

50/100

10%

Network Requests Diagram

cgl.co.jp

543 ms

cgl.co.jp

5629 ms

common.css

514 ms

layout.css

495 ms

jquery-1.8.2.min.js

1196 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 98% of them (91 requests) were addressed to the original Cgl.co.jp, 2% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (5.6 sec) belongs to the original domain Cgl.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 189.9 kB (15%)

Content Size

1.2 MB

After Optimization

1.1 MB

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

HTML Optimization

-85%

Potential reduce by 25.9 kB

  • Original 30.7 kB
  • After minification 24.1 kB
  • After compression 4.7 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 6.5 kB, which is 21% 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 25.9 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 35.6 kB

  • Original 1.0 MB
  • After minification 989.8 kB

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. CGL images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 85.5 kB

  • Original 140.3 kB
  • After minification 130.3 kB
  • After compression 54.8 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 85.5 kB or 61% of the original size.

CSS Optimization

-84%

Potential reduce by 42.9 kB

  • Original 51.3 kB
  • After minification 42.5 kB
  • After compression 8.4 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. Cgl.co.jp needs all CSS files to be minified and compressed as it can save up to 42.9 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

91

After Optimization

67

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

Accessibility Review

cgl.co.jp accessibility score

54

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

cgl.co.jp SEO score

50

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 Cgl.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 Cgl.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 CGL. 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: