Tools & Wizards About Us
crodot.jp screenshot

Report Summary

  • 64

    Performance

    Renders faster than
    78% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

crodot.jp

DOTワールド株式会社

Page Load Speed

3.7 sec in total

First Response

628 ms

Resources Loaded

2.9 sec

Page Rendered

175 ms

crodot.jp screenshot

About Website

Visit crodot.jp now to see the best up-to-date Crodot content and also check out these interesting facts you probably never knew about crodot.jp

CRO の DOTワールド株式会社は治験（製造承認申請を目的とした臨床試験）の支援業務を中心に、医薬品の効果を科学的に裏付ける臨床試験（治験）をサポートする会社です。

Visit crodot.jp

Key Findings

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

Performance Metrics

crodot.jp performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

69/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value230 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.367

29/100

15%

TTI (Time to Interactive)

Value4.4 s

83/100

10%

Network Requests Diagram

crodot.jp

628 ms

top.css

408 ms

top_image.jpg

1036 ms

common.css

417 ms

bg01.jpg

351 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that all of those requests were addressed to Crodot.jp and no external sources were called. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Crodot.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 12.4 kB (5%)

Content Size

263.4 kB

After Optimization

251.0 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Crodot.jp main page is 263.4 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Images take 246.5 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 6.3 kB

  • Original 9.6 kB
  • After minification 7.8 kB
  • After compression 3.3 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 1.8 kB, which is 19% 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 6.3 kB or 66% of the original size.

Image Optimization

-0%

Potential reduce by 319 B

  • Original 246.5 kB
  • After minification 246.2 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. Crodot images are well optimized though.

CSS Optimization

-79%

Potential reduce by 5.8 kB

  • Original 7.3 kB
  • After minification 5.5 kB
  • After compression 1.5 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. Crodot.jp needs all CSS files to be minified and compressed as it can save up to 5.8 kB or 79% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

13

After Optimization

13

  • Images
  • CSS

The browser has sent 13 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Crodot. According to our analytics all requests are already optimized.

Network Requests Diagram

crodot.jp

crodot.jp

628 ms

top.css

top.css

408 ms

top_image.jpg

top_image.jpg

1036 ms

common.css

common.css

417 ms

bg01.jpg

bg01.jpg

351 ms

logo.jpg

logo.jpg

393 ms

navi.jpg

navi.jpg

400 ms

g_menu.jpg

g_menu.jpg

610 ms

bg01.jpg

bg01.jpg

417 ms

bg02.jpg

bg02.jpg

619 ms

h2_header.jpg

h2_header.jpg

737 ms

icon.jpg

icon.jpg

758 ms

top_link.jpg

top_link.jpg

1403 ms

bg03.jpg

bg03.jpg

776 ms

Accessibility Review

crodot.jp accessibility score

74

Accessibility Issues

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

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

    SHIFT_JIS

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

crodot.jp

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