Tools & Wizards About Us
drivee.ne.jp screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    58% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

drivee.ne.jp

ユーザー数無制限の法人向けクラウドストレージ｜Xserverドライブ(旧エックスドライブ)

Page Load Speed

4.9 sec in total

First Response

576 ms

Resources Loaded

4.2 sec

Page Rendered

170 ms

drivee.ne.jp screenshot

About Website

Visit drivee.ne.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.ne.jp

Xserverドライブは、ユーザー数無制限で高いコストパフォーマンスを誇る法人向けの高速クラウドストレージです。社内のファイルの一元管理や、離れた拠点間でのデータ共有・管理などが可能で、テレワークでの利用にも最適です。

Visit drivee.ne.jp

Key Findings

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

Performance Metrics

drivee.ne.jp performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value8.8 s

15/100

10%

TBT (Total Blocking Time)

Value210 ms

88/100

30%

CLS (Cumulative Layout Shift)

Value0.32

36/100

15%

TTI (Time to Interactive)

Value7.6 s

47/100

10%

Network Requests Diagram

drivee.ne.jp

576 ms

www.drivee.ne.jp

601 ms

basic.css

804 ms

base.css

1805 ms

layout.css

1816 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 62% of them (36 requests) were addressed to the original Drivee.ne.jp, 33% (19 requests) were made to Drivee.jp and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Drivee.ne.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 68.6 kB (27%)

Content Size

255.1 kB

After Optimization

186.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 11.6 kB

  • Original 15.2 kB
  • After minification 13.6 kB
  • After compression 3.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.7 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 11.6 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 1.1 kB

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

JavaScript Optimization

-60%

Potential reduce by 33.2 kB

  • Original 54.9 kB
  • After minification 54.4 kB
  • After compression 21.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 33.2 kB or 60% of the original size.

CSS Optimization

-82%

Potential reduce by 22.7 kB

  • Original 27.8 kB
  • After minification 21.3 kB
  • After compression 5.1 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.ne.jp needs all CSS files to be minified and compressed as it can save up to 22.7 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (35%)

Requests Now

54

After Optimization

35

  • Images
  • JavaScript
  • CSS

The browser has sent 54 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 4 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

drivee.ne.jp

drivee.ne.jp

576 ms

www.drivee.ne.jp

www.drivee.ne.jp

601 ms

basic.css

basic.css

804 ms

base.css

base.css

1805 ms

layout.css

layout.css

1816 ms

alphafilter.js

alphafilter.js

187 ms

switching.js

switching.js

374 ms

smartRollover.js

smartRollover.js

381 ms

google.js

google.js

377 ms

header_logo.png

header_logo.png

378 ms

login_button_off.png

login_button_off.png

389 ms

main_menu_home_on.png

main_menu_home_on.png

803 ms

main_menu_service_off.png

main_menu_service_off.png

551 ms

main_menu_plan_off.png

main_menu_plan_off.png

556 ms

main_menu_application_off.png

main_menu_application_off.png

564 ms

main_menu_support_off.png

main_menu_support_off.png

568 ms

main_menu_news_off.png

main_menu_news_off.png

583 ms

top_img.png

top_img.png

1473 ms

top_img_button_service_off.png

top_img_button_service_off.png

741 ms

top_img_button_plan_off.png

top_img_button_plan_off.png

753 ms

top_feature_list_copy_function.png

top_feature_list_copy_function.png

758 ms

top_feature_list_img_function.png

top_feature_list_img_function.png

779 ms

top_feature_list_copy_highspec.png

top_feature_list_copy_highspec.png

926 ms

top_feature_list_img_highspec.png

top_feature_list_img_highspec.png

944 ms

top_feature_list_copy_backup.png

top_feature_list_copy_backup.png

948 ms

top_feature_list_img_backup.png

top_feature_list_img_backup.png

974 ms

top_about_drivee_copy.png

top_about_drivee_copy.png

995 ms

top_about_drivee_img.png

top_about_drivee_img.png

1295 ms

facebook_banner_mini.png

facebook_banner_mini.png

1135 ms

sub_contents_trial_banner_off.png

sub_contents_trial_banner_off.png

1329 ms

sub_contents_application_button_off.png

sub_contents_application_button_off.png

1170 ms

sub_contents_tel_contact.png

sub_contents_tel_contact.png

1420 ms

sub_contents_mail_support_button_off.png

sub_contents_mail_support_button_off.png

1324 ms

sub_contents_affiliate_banner_off.png

sub_contents_affiliate_banner_off.png

1365 ms

drivee_banner_166-160.gif

drivee_banner_166-160.gif

1847 ms

facebook_banner_side.png

facebook_banner_side.png

1513 ms

recruiting_banner.jpg

recruiting_banner.jpg

1708 ms

president_blog_banner.png

president_blog_banner.png

1561 ms

privacy_mark.gif

privacy_mark.gif

1614 ms

analytics.js

analytics.js

21 ms

collect

collect

13 ms

collect

collect

56 ms

background_html2.png

background_html2.png

173 ms

background_footer.png

background_footer.png

195 ms

background_base.png

background_base.png

172 ms

main_menu_back.png

main_menu_back.png

342 ms

arrow_marker_green_square.png

arrow_marker_green_square.png

343 ms

h2_back.png

h2_back.png

354 ms

link_arrow.png

link_arrow.png

354 ms

sub_contents_mail_support_back.png

sub_contents_mail_support_back.png

1176 ms

dot_line_x.gif

dot_line_x.gif

385 ms

arrow_marker_yellow.png

arrow_marker_yellow.png

508 ms

footer_back.png

footer_back.png

509 ms

favicon_xserver.png

favicon_xserver.png

526 ms

favicon_sixcore.png

favicon_sixcore.png

525 ms

favicon_wpx.png

favicon_wpx.png

574 ms

favicon_xdomain.png

favicon_xdomain.png

677 ms

favicon_drivee.png

favicon_drivee.png

678 ms

Accessibility Review

drivee.ne.jp accessibility score

96

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.

Best Practices

drivee.ne.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.ne.jp SEO score

90

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

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.ne.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.ne.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.ne.jp

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