Tools & Wizards About Us
gdl-j.co.jp screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 77% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

gdl-j.co.jp

人事コンサルティング・CUBIC適性検査の株式会社ジィ・ディー・エル（GDL）

Page Load Speed

4.4 sec in total

First Response

602 ms

Resources Loaded

3.5 sec

Page Rendered

225 ms

gdl-j.co.jp screenshot

About Website

Visit gdl-j.co.jp now to see the best up-to-date GDL J content for Japan and also check out these interesting facts you probably never knew about gdl-j.co.jp

株式会社ジィ・ディー・エル（GDL）では、効果的な目標管理・人事考課・人材教育支援ができるよう、人事コンサルタント・ファシリテーター・コーチの育成・CUBIC適性検査と、コンサルティング手法やソフトウェアの改良、革新を重ねています

Visit gdl-j.co.jp

Key Findings

We analyzed Gdl-j.co.jp page load time and found that the first response time was 602 ms and then it took 3.8 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

gdl-j.co.jp performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value12.7 s

0/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value2,480 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

gdl-j.co.jp

602 ms

style.css

626 ms

font.css.php

318 ms

header_search.js

336 ms

bsn.Crossfader.js

342 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 79% of them (71 requests) were addressed to the original Gdl-j.co.jp, 8% (7 requests) were made to Rs.adapf.com and 2% (2 requests) were made to Sitest.jp. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Sitest.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 240.3 kB (26%)

Content Size

919.9 kB

After Optimization

679.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gdl-j.co.jp main page is 919.9 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. Images take 752.7 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 21.1 kB

  • Original 28.7 kB
  • After minification 27.3 kB
  • After compression 7.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 21.1 kB or 73% of the original size.

Image Optimization

-18%

Potential reduce by 134.7 kB

  • Original 752.7 kB
  • After minification 618.0 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. Obviously, GDL J needs image optimization as it can save up to 134.7 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-47%

Potential reduce by 41.7 kB

  • Original 89.4 kB
  • After minification 88.4 kB
  • After compression 47.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 41.7 kB or 47% of the original size.

CSS Optimization

-87%

Potential reduce by 42.8 kB

  • Original 49.0 kB
  • After minification 39.8 kB
  • After compression 6.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. Gdl-j.co.jp needs all CSS files to be minified and compressed as it can save up to 42.8 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

87

After Optimization

63

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gdl-j.co.jp

gdl-j.co.jp

602 ms

style.css

style.css

626 ms

font.css.php

font.css.php

318 ms

header_search.js

header_search.js

336 ms

bsn.Crossfader.js

bsn.Crossfader.js

342 ms

css.js

css.js

537 ms

0380.js

0380.js

20 ms

conversion.js

conversion.js

17 ms

sitest_js

sitest_js

1891 ms

bg_01.jpg

bg_01.jpg

199 ms

logo_gdl.gif

logo_gdl.gif

164 ms

btn_inquiry01.gif

btn_inquiry01.gif

171 ms

header_menu2.gif

header_menu2.gif

162 ms

search_bg.jpg

search_bg.jpg

172 ms

btn_search.gif

btn_search.gif

322 ms

mainmenu_consulting.jpg

mainmenu_consulting.jpg

320 ms

mainmenu_job.jpg

mainmenu_job.jpg

338 ms

mainmenu_coaching.jpg

mainmenu_coaching.jpg

342 ms

mainmenu_insight.jpg

mainmenu_insight.jpg

528 ms

mainmenu_cubic.jpg

mainmenu_cubic.jpg

390 ms

mainmenu_compass.jpg

mainmenu_compass.jpg

473 ms

mainmenu_multi.jpg

mainmenu_multi.jpg

476 ms

mainmenu_top_bg.jpg

mainmenu_top_bg.jpg

839 ms

mainmenu_top_title.gif

mainmenu_top_title.gif

512 ms

mainmenu_testing_bg.jpg

mainmenu_testing_bg.jpg

819 ms

mainmenu_testing_title.gif

mainmenu_testing_title.gif

629 ms

mainmenu_testing_btn.gif

mainmenu_testing_btn.gif

631 ms

mainmenu_cubic_bg.jpg

mainmenu_cubic_bg.jpg

1196 ms

mainmenu_cubic_title.gif

mainmenu_cubic_title.gif

700 ms

mainmenu_cubic_btn.gif

mainmenu_cubic_btn.gif

784 ms

mainmenu_compass_bg.jpg

mainmenu_compass_bg.jpg

945 ms

mainmenu_compass_title.gif

mainmenu_compass_title.gif

876 ms

mainmenu_compass_btn.gif

mainmenu_compass_btn.gif

939 ms

mainmenu_multi_bg.jpg

mainmenu_multi_bg.jpg

1405 ms

mainmenu_multi_title.gif

mainmenu_multi_title.gif

1006 ms

mainmenu_multi_btn.gif

mainmenu_multi_btn.gif

1052 ms

bg_topcategory.gif

bg_topcategory.gif

1122 ms

toptitle_insight.gif

toptitle_insight.gif

1125 ms

icon_insight.gif

icon_insight.gif

1198 ms

topbtn_insight.gif

topbtn_insight.gif

1226 ms

toptitle_cubic.gif

toptitle_cubic.gif

1294 ms

icon_cubic.gif

icon_cubic.gif

1282 ms

topbtn_cubic.gif

topbtn_cubic.gif

1367 ms

toptitle_compass.gif

toptitle_compass.gif

1367 ms

icon_compass.gif

icon_compass.gif

1366 ms

analytics.js

analytics.js

6 ms

53 ms

aiom.js

aiom.js

428 ms

m.js

m.js

448 ms

collect

collect

28 ms

42 ms

topbtn_compass.gif

topbtn_compass.gif

1322 ms

toptitle_multi.gif

toptitle_multi.gif

1321 ms

icon_multi.gif

icon_multi.gif

1386 ms

topbtn_multi.gif

topbtn_multi.gif

1375 ms

topbtn_navi.jpg

topbtn_navi.jpg

1424 ms

topbtn_testing.jpg

topbtn_testing.jpg

1450 ms

topbtn_mental.jpg

topbtn_mental.jpg

1286 ms

topbtn_evaluation.jpg

topbtn_evaluation.jpg

1432 ms

bg_subcategory.gif

bg_subcategory.gif

1372 ms

topbtn_consulting.jpg

topbtn_consulting.jpg

1338 ms

topbtn_job.jpg

topbtn_job.jpg

1291 ms

topbtn_coach.jpg

topbtn_coach.jpg

1338 ms

aio

aio

169 ms

topbtn_hint.jpg

topbtn_hint.jpg

1369 ms

topneeds_title.jpg

topneeds_title.jpg

1375 ms

topneeds_bg.gif

topneeds_bg.gif

1291 ms

topneeds_title01.jpg

topneeds_title01.jpg

1292 ms

pixel

pixel

18 ms

csync

csync

716 ms

marking

marking

182 ms

csync

csync

176 ms

arrow_01.gif

arrow_01.gif

1243 ms

topneeds_title02.jpg

topneeds_title02.jpg

1227 ms

topneeds_title03.jpg

topneeds_title03.jpg

1231 ms

topneeds_title04.jpg

topneeds_title04.jpg

1240 ms

toptitle_information.gif

toptitle_information.gif

1204 ms

toptitle_update.gif

toptitle_update.gif

1144 ms

toptitle_books.gif

toptitle_books.gif

1178 ms

csync

csync

183 ms

book.jpg

book.jpg

1206 ms

topbanner_%20protection.gif

topbanner_%20protection.gif

1185 ms

privacymark.gif

privacymark.gif

1129 ms

topbanner_iso.gif

topbanner_iso.gif

1112 ms

bg_02.jpg

bg_02.jpg

1041 ms

arrow_02.gif

arrow_02.gif

1100 ms

arrow_03.gif

arrow_03.gif

1180 ms

555 ms

t.js

t.js

398 ms

r.js

r.js

597 ms

Accessibility Review

gdl-j.co.jp accessibility score

91

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

gdl-j.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

gdl-j.co.jp SEO score

100

Search Engine Optimization Advices

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 Gdl-j.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 Gdl-j.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

gdl-j.co.jp

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