Tools & Wizards About Us
didi.jp screenshot

Report Summary

  • 44

    Performance

    Renders faster than
    63% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

didi.jp

C.C.E Creative Company Energy 株式会社 クリエイティブ カンパニー・エナジー

Page Load Speed

3.7 sec in total

First Response

319 ms

Resources Loaded

3.3 sec

Page Rendered

84 ms

didi.jp screenshot

About Website

Welcome to didi.jp homepage info - get ready to check Didi best content right away, or after learning these important things about didi.jp

Webサイト制作・広告代理店業務・システム開発・デザイン業務・インターネット関連のコンサルティングの、株式会社 クリエイティブ カンパニー・エナジーのWebサイトです。制作実績、会社案内、採用情報などをご紹介します。

Visit didi.jp

Key Findings

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

Performance Metrics

didi.jp performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

17/100

25%

SI (Speed Index)

Value9.9 s

10/100

10%

TBT (Total Blocking Time)

Value420 ms

66/100

30%

CLS (Cumulative Layout Shift)

Value0.063

97/100

15%

TTI (Time to Interactive)

Value8.7 s

36/100

10%

Network Requests Diagram

didi.jp

319 ms

www.didi.jp

1054 ms

CCE.min.css

335 ms

style.min.css

620 ms

typesquare.js

267 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 52% of them (12 requests) were addressed to the original Didi.jp, 17% (4 requests) were made to Fonts.gstatic.com and 13% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Didi.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 197.0 kB (71%)

Content Size

278.0 kB

After Optimization

80.9 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Didi.jp main page is 278.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Javascripts take 178.9 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 8.0 kB

  • Original 10.7 kB
  • After minification 9.5 kB
  • After compression 2.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 1.2 kB, which is 11% 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 8.0 kB or 74% of the original size.

JavaScript Optimization

-64%

Potential reduce by 114.2 kB

  • Original 178.9 kB
  • After minification 177.0 kB
  • After compression 64.7 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 114.2 kB or 64% of the original size.

CSS Optimization

-85%

Potential reduce by 74.9 kB

  • Original 88.4 kB
  • After minification 88.2 kB
  • After compression 13.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. Didi.jp needs all CSS files to be minified and compressed as it can save up to 74.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (59%)

Requests Now

17

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

didi.jp

didi.jp

319 ms

www.didi.jp

www.didi.jp

1054 ms

CCE.min.css

CCE.min.css

335 ms

style.min.css

style.min.css

620 ms

typesquare.js

typesquare.js

267 ms

utility.js

utility.js

467 ms

js

js

58 ms

js

js

101 ms

plugin.js

plugin.js

931 ms

CCE.min.js

CCE.min.js

642 ms

wp-embed.min.js

wp-embed.min.js

470 ms

css

css

21 ms

setting.css

setting.css

155 ms

analytics.js

analytics.js

25 ms

collect

collect

13 ms

js

js

51 ms

logo_corporate.gif

logo_corporate.gif

170 ms

loader.gif

loader.gif

170 ms

bg_panel.gif

bg_panel.gif

155 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf

63 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVcUwaEQXjM.ttf

62 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVcUwaEQXjM.ttf

62 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVcUwaEQXjM.ttf

61 ms

Accessibility Review

didi.jp accessibility score

93

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

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

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

didi.jp SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

didi.jp

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: