Tools & Wizards About Us
drivee.jp screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

drivee.jp

XServerドライブ | 「簡単操作」でファイル共有を効率化でき、「はじめて」のクラウド化にも最適な、国内運営の法人向けクラウドストレージ

Page Load Speed

6.2 sec in total

First Response

528 ms

Resources Loaded

5.1 sec

Page Rendered

586 ms

drivee.jp screenshot

About Website

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

XServerドライブは、国内シェアNo.1の実績を誇る「エックスサーバー」が提供するオンラインでファイルの保管、共有、編集が可能な国内運営の法人向けクラウドストレージサービスです。社内のファイルの一元管理や、URLでファイル共有、バックアップ機能など、業務における共同作業をよりスムーズに行えます。

Visit drivee.jp

Key Findings

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

Performance Metrics

drivee.jp performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.4 s

2/100

10%

LCP (Largest Contentful Paint)

Value13.2 s

0/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value1,110 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.228

55/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

drivee.jp

528 ms

www.xdrive.ne.jp

881 ms

drive.xserver.ne.jp

913 ms

js

53 ms

gtm.js

94 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Drivee.jp, 74% (52 requests) were made to Drive.xserver.ne.jp and 10% (7 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Drive.xserver.ne.jp.

Page Optimization Overview & Recommendations

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

Content Size

680.6 kB

After Optimization

538.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Drivee.jp main page is 680.6 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. 65% of websites need less resources to load. Images take 443.3 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 49.6 kB

  • Original 59.1 kB
  • After minification 40.3 kB
  • After compression 9.4 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 18.8 kB, which is 32% 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 49.6 kB or 84% of the original size.

Image Optimization

-5%

Potential reduce by 23.5 kB

  • Original 443.3 kB
  • After minification 419.9 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. Drivee images are well optimized though.

JavaScript Optimization

-43%

Potential reduce by 68.6 kB

  • Original 158.4 kB
  • After minification 158.4 kB
  • After compression 89.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 68.6 kB or 43% of the original size.

CSS Optimization

-1%

Potential reduce by 282 B

  • Original 19.8 kB
  • After minification 19.8 kB
  • After compression 19.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. Drivee.jp has all CSS files already compressed.

Requests Breakdown

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

Requests Now

65

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

drivee.jp

drivee.jp

528 ms

www.xdrive.ne.jp

www.xdrive.ne.jp

881 ms

drive.xserver.ne.jp

drive.xserver.ne.jp

913 ms

js

js

53 ms

gtm.js

gtm.js

94 ms

google.js

google.js

196 ms

style.css

style.css

563 ms

site.css

site.css

908 ms

ss_130-50.js

ss_130-50.js

1219 ms

jquery-1.12.4.min.js

jquery-1.12.4.min.js

1040 ms

libs.js

libs.js

740 ms

common.js

common.js

738 ms

conversion.js

conversion.js

1045 ms

s_retargeting.js

s_retargeting.js

1059 ms

affiliatea8.js

affiliatea8.js

741 ms

analytics.js

analytics.js

54 ms

js

js

55 ms

js

js

121 ms

js

js

118 ms

js

js

194 ms

js

js

191 ms

collect

collect

171 ms

collect

collect

137 ms

img_siteid.png

img_siteid.png

539 ms

img_mv_ttl_l.png

img_mv_ttl_l.png

889 ms

btn_icon_pdf.png

btn_icon_pdf.png

843 ms

ico_result.png

ico_result.png

847 ms

img_feature_main.png

img_feature_main.png

946 ms

img_feature_user.png

img_feature_user.png

880 ms

img_feature_share.png

img_feature_share.png

882 ms

img_feature_staff.png

img_feature_staff.png

891 ms

img_feature_smartphone.png

img_feature_smartphone.png

1047 ms

img_feature_log.png

img_feature_log.png

1078 ms

ico_webdav.png

ico_webdav.png

1078 ms

ico_comment.png

ico_comment.png

1078 ms

ico_customize.png

ico_customize.png

1078 ms

ico_file.png

ico_file.png

1125 ms

ico_domain.png

ico_domain.png

1195 ms

ico_login.png

ico_login.png

1221 ms

img_manual_bnr_l.png

img_manual_bnr_l.png

1395 ms

img_security_ssl.png

img_security_ssl.png

1238 ms

img_security_access.png

img_security_access.png

1240 ms

img_security_version.png

img_security_version.png

1305 ms

ico_verification.png

ico_verification.png

1369 ms

ico_secomlogo.png

ico_secomlogo.png

1391 ms

img_highspeed_knowhow.jpg

img_highspeed_knowhow.jpg

1761 ms

img_highspeed_highspec.png

img_highspeed_highspec.png

1416 ms

img_highspeed_network.png

img_highspeed_network.png

1485 ms

img_highspeed_domestic.png

img_highspeed_domestic.png

1545 ms

img_support_mail.png

img_support_mail.png

1562 ms

img_support_tel.png

img_support_tel.png

1565 ms

bnr_affiliate.png

bnr_affiliate.png

1591 ms

bnr_footer_partner.png

bnr_footer_partner.png

1665 ms

collect

collect

263 ms

img_isms.png

img_isms.png

1362 ms

ga-audiences

ga-audiences

76 ms

img_pmark.png

img_pmark.png

1198 ms

img_siteid.png

img_siteid.png

1201 ms

bg_gray.png

bg_gray.png

1049 ms

line_gray.png

line_gray.png

1128 ms

ico_rentalserver.png

ico_rentalserver.png

1059 ms

ico_shield.png

ico_shield.png

1065 ms

xserver.ttf

xserver.ttf

1068 ms

ico_globe.png

ico_globe.png

1099 ms

ico_vps.png

ico_vps.png

1066 ms

ico_storage.png

ico_storage.png

1148 ms

img_mv_bg_l.jpg

img_mv_bg_l.jpg

1538 ms

bg_diagonal_green.png

bg_diagonal_green.png

1187 ms

ico_question.png

ico_question.png

1137 ms

conversion_async.js

conversion_async.js

1524 ms

Accessibility Review

drivee.jp accessibility score

81

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.

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

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

drivee.jp SEO score

82

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    EUC-JP

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

drivee.jp

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