Tools & Wizards About Us
drecom.co.jp screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    66% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

drecom.co.jp

株式会社ドリコム

Page Load Speed

11.6 sec in total

First Response

339 ms

Resources Loaded

7.2 sec

Page Rendered

4.1 sec

drecom.co.jp screenshot

About Website

Click here to check amazing Drecom content for Japan. Otherwise, check out these important facts you probably never knew about drecom.co.jp

ドリコムは、毎日のワクワクを発明するwith entertainment企業です。ドリコムが常に目指しているのは、新しい体験やサービスを発明し、人をワクワクさせること。スマートフォン向けのゲーム開発や運営。広告・メディア事業を展開しています。

Visit drecom.co.jp

Key Findings

We analyzed Drecom.co.jp page load time and found that the first response time was 339 ms and then it took 11.2 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

drecom.co.jp performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value34.4 s

0/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.2 s

15/100

10%

Network Requests Diagram

drecom.co.jp

339 ms

www.drecom.co.jp

684 ms

mootools-core.js

1120 ms

mootools-more.js

476 ms

common.js

709 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 88% of them (86 requests) were addressed to the original Drecom.co.jp, 3% (3 requests) were made to Facebook.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Drecom.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 797.0 kB (21%)

Content Size

3.9 MB

After Optimization

3.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 24.4 kB

  • Original 31.9 kB
  • After minification 31.7 kB
  • After compression 7.5 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 24.4 kB or 76% of the original size.

Image Optimization

-17%

Potential reduce by 630.4 kB

  • Original 3.6 MB
  • After minification 3.0 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. Obviously, Drecom needs image optimization as it can save up to 630.4 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 111.2 kB

  • Original 170.0 kB
  • After minification 157.8 kB
  • After compression 58.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 111.2 kB or 65% of the original size.

CSS Optimization

-82%

Potential reduce by 30.9 kB

  • Original 37.6 kB
  • After minification 29.5 kB
  • After compression 6.6 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. Drecom.co.jp needs all CSS files to be minified and compressed as it can save up to 30.9 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (31%)

Requests Now

95

After Optimization

66

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Drecom. 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 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

drecom.co.jp

drecom.co.jp

339 ms

www.drecom.co.jp

www.drecom.co.jp

684 ms

mootools-core.js

mootools-core.js

1120 ms

mootools-more.js

mootools-more.js

476 ms

common.js

common.js

709 ms

common.css

common.css

358 ms

top_2014.css

top_2014.css

538 ms

top.js

top.js

896 ms

top_summary.js

top_summary.js

537 ms

init.css

init.css

163 ms

main.css

main.css

183 ms

css

css

64 ms

logo.png

logo.png

178 ms

icon_mail.gif

icon_mail.gif

204 ms

bn_recruit.jpg

bn_recruit.jpg

481 ms

bn_sbg50.png

bn_sbg50.png

802 ms

2nd-anniv-thumb-326xauto-2477.jpg

2nd-anniv-thumb-326xauto-2477.jpg

1087 ms

%E5%A4%A7%E7%BD%AATOP-thumb-157xauto-2470.png

%E5%A4%A7%E7%BD%AATOP-thumb-157xauto-2470.png

1267 ms

20160218_%E3%83%89%E3%83%AA%E3%82%B3%E3%83%A0TOP-thumb-157xauto-2469.png

20160218_%E3%83%89%E3%83%AA%E3%82%B3%E3%83%A0TOP-thumb-157xauto-2469.png

1267 ms

IR%E6%83%85%E5%A0%B1-thumb-157xauto-1906.jpg

IR%E6%83%85%E5%A0%B1-thumb-157xauto-1906.jpg

538 ms

%E9%99%B0%E9%99%BDmixiTOP-thumb-157xauto-2464.jpeg

%E9%99%B0%E9%99%BDmixiTOP-thumb-157xauto-2464.jpeg

642 ms

FateTOP-thumb-157xauto-2448.png

FateTOP-thumb-157xauto-2448.png

1445 ms

earth.png

earth.png

1123 ms

title1.png

title1.png

1121 ms

1_1.png

1_1.png

1805 ms

1_2.png

1_2.png

1441 ms

1_3.png

1_3.png

1283 ms

1_4.png

1_4.png

2310 ms

1_5.png

1_5.png

2600 ms

1_6.png

1_6.png

1764 ms

shadow1.png

shadow1.png

1602 ms

toolbox.png

toolbox.png

2161 ms

title2.png

title2.png

1762 ms

2.png

2.png

2564 ms

shadow2.png

shadow2.png

1924 ms

pench.png

pench.png

1982 ms

driver.png

driver.png

2085 ms

scale.png

scale.png

2340 ms

spana.png

spana.png

2244 ms

curry.png

curry.png

2877 ms

title3.png

title3.png

2405 ms

3.png

3.png

2941 ms

shadow3.png

shadow3.png

2519 ms

roupe.png

roupe.png

2724 ms

key.png

key.png

2698 ms

title4.png

title4.png

2723 ms

4_1.png

4_1.png

3304 ms

map.png

map.png

3057 ms

ga.js

ga.js

74 ms

all.js

all.js

166 ms

MYWJ4lYm5dbZ1UBuYox79CZ2oysoEQEeKwjgmXLRnTc.ttf

MYWJ4lYm5dbZ1UBuYox79CZ2oysoEQEeKwjgmXLRnTc.ttf

64 ms

__utm.gif

__utm.gif

28 ms

compass.png

compass.png

3199 ms

134 ms

title5.png

title5.png

2681 ms

xd_arbiter.php

xd_arbiter.php

119 ms

xd_arbiter.php

xd_arbiter.php

232 ms

5.png

5.png

2760 ms

shadow5.png

shadow5.png

2513 ms

btn_attention.png

btn_attention.png

2465 ms

nav_border_wide_end.png

nav_border_wide_end.png

2415 ms

nav_border_wide.png

nav_border_wide.png

2156 ms

sprite_nav.png

sprite_nav.png

2142 ms

arrow_nano.png

arrow_nano.png

2253 ms

icon_topics_info_g2.gif

icon_topics_info_g2.gif

2155 ms

icon_topics_pr_g2.gif

icon_topics_pr_g2.gif

2157 ms

icon_topics_ir_g2.gif

icon_topics_ir_g2.gif

2139 ms

bg_28000.png

bg_28000.png

2046 ms

catch.png

catch.png

2089 ms

content1.png

content1.png

2093 ms

content2.png

content2.png

1836 ms

content3.png

content3.png

1972 ms

content4.png

content4.png

1976 ms

content5.png

content5.png

1916 ms

white_20.png

white_20.png

1711 ms

arrow_top_white.png

arrow_top_white.png

1693 ms

separator_shadow.png

separator_shadow.png

1693 ms

black_20.png

black_20.png

1611 ms

arrow_bottom_white.png

arrow_bottom_white.png

1587 ms

motion_1.png

motion_1.png

1616 ms

motion_2.png

motion_2.png

1553 ms

motion_3.png

motion_3.png

1497 ms

motion_4.png

motion_4.png

1450 ms

motion_5.png

motion_5.png

1417 ms

motion_6.png

motion_6.png

1352 ms

motion_7.png

motion_7.png

1411 ms

motion_8.png

motion_8.png

1411 ms

2.png

2.png

1297 ms

3.png

3.png

1287 ms

4.png

4.png

1251 ms

5.png

5.png

1163 ms

6.png

6.png

1256 ms

7.png

7.png

1215 ms

8.png

8.png

1124 ms

ping

ping

64 ms

like.php

like.php

88 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

308 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

341 ms

Accessibility Review

drecom.co.jp accessibility score

92

Accessibility Issues

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

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

drecom.co.jp best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

drecom.co.jp SEO score

92

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Drecom.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Drecom.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

drecom.co.jp

Open Graph data is detected on the main page of Drecom. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: