Tools & Wizards About Us
xserver.ne.jp screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

xserver.ne.jp

エックスサーバー｜高速・安定の高性能レンタルサーバー

Page Load Speed

7.2 sec in total

First Response

554 ms

Resources Loaded

6 sec

Page Rendered

670 ms

xserver.ne.jp screenshot

About Website

Click here to check amazing Xserver content for Japan. Otherwise, check out these important facts you probably never knew about xserver.ne.jp

高速かつ高い安定性を誇る高性能レンタルサーバー【エックスサーバー】稼働率99.99％以上の高い安定性で、業界トップクラスの高コストパフォーマンスを誇る高品質レンタルサーバーです。月額990円(税込)から利用可能。まずは無料お試し10日間。

Visit xserver.ne.jp

Key Findings

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

Performance Metrics

xserver.ne.jp performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value14.4 s

0/100

25%

SI (Speed Index)

Value11.5 s

5/100

10%

TBT (Total Blocking Time)

Value3,140 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.051

99/100

15%

TTI (Time to Interactive)

Value19.8 s

2/100

10%

Network Requests Diagram

xserver.ne.jp

554 ms

www.xserver.ne.jp

1120 ms

gtm.js

50 ms

js

127 ms

js

128 ms

Our browser made a total of 118 requests to load all elements on the main page. We found that 75% of them (88 requests) were addressed to the original Xserver.ne.jp, 7% (8 requests) were made to Googletagmanager.com and 5% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Xserver.ne.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 239.9 kB (22%)

Content Size

1.1 MB

After Optimization

874.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Xserver.ne.jp main page is 1.1 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. Only a small number of websites need less resources to load. Images take 757.7 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 79.5 kB

  • Original 94.7 kB
  • After minification 75.0 kB
  • After compression 15.1 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 19.7 kB, which is 21% 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 79.5 kB or 84% of the original size.

Image Optimization

-15%

Potential reduce by 114.6 kB

  • Original 757.7 kB
  • After minification 643.1 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, Xserver needs image optimization as it can save up to 114.6 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-26%

Potential reduce by 45.2 kB

  • Original 172.4 kB
  • After minification 172.4 kB
  • After compression 127.2 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 45.2 kB or 26% of the original size.

CSS Optimization

-1%

Potential reduce by 577 B

  • Original 89.7 kB
  • After minification 89.7 kB
  • After compression 89.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. Xserver.ne.jp has all CSS files already compressed.

Requests Breakdown

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

Requests Now

108

After Optimization

71

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

xserver.ne.jp

xserver.ne.jp

554 ms

www.xserver.ne.jp

www.xserver.ne.jp

1120 ms

gtm.js

gtm.js

50 ms

js

js

127 ms

js

js

128 ms

jquery-1.12.4.min.js

jquery-1.12.4.min.js

617 ms

google.js

google.js

804 ms

a8sales.js

a8sales.js

35 ms

a8crossDomain.js

a8crossDomain.js

38 ms

errorlogger.js

errorlogger.js

799 ms

search_domain.js

search_domain.js

813 ms

css2

css2

45 ms

style.css

style.css

810 ms

site.css

site.css

1187 ms

js

js

103 ms

js

js

203 ms

js

js

198 ms

js

js

413 ms

js

js

415 ms

analytics.js

analytics.js

351 ms

ss_130-50.js

ss_130-50.js

1325 ms

libs.js

libs.js

606 ms

main.js

main.js

779 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

776 ms

conversion.js

conversion.js

975 ms

s_retargeting.js

s_retargeting.js

976 ms

js

js

59 ms

collect

collect

21 ms

collect

collect

16 ms

collect

collect

15 ms

ga-audiences

ga-audiences

75 ms

fbevents.js

fbevents.js

281 ms

bg_gray.png

bg_gray.png

667 ms

line_gray.png

line_gray.png

665 ms

ico_rentalserver.png

ico_rentalserver.png

666 ms

ico_shield.png

ico_shield.png

664 ms

ico_globe.png

ico_globe.png

665 ms

ico_vps.png

ico_vps.png

666 ms

ico_storage.png

ico_storage.png

750 ms

head_20th_s.svg

head_20th_s.svg

749 ms

img_siteid.svg

img_siteid.svg

753 ms

head_share_no1_s.svg

head_share_no1_s.svg

754 ms

ico_blank.svg

ico_blank.svg

758 ms

mv_headbnr_s.png

mv_headbnr_s.png

880 ms

bg_mv_l.png

bg_mv_l.png

1908 ms

mv_number1_ttl_s.png

mv_number1_ttl_s.png

898 ms

mv_pr_free.png

mv_pr_free.png

898 ms

mv_trials_image.svg

mv_trials_image.svg

904 ms

mv_pickup_daiko_l.png

mv_pickup_daiko_l.png

907 ms

mv_pickup_simple.png

mv_pickup_simple.png

1224 ms

mv_pickup_wptheme_s.png

mv_pickup_wptheme_s.png

1260 ms

mv_spec_amd_s.png

mv_spec_amd_s.png

1075 ms

mv_spec_wp.svg

mv_spec_wp.svg

1083 ms

mv_spec_kusanagi_s.png

mv_spec_kusanagi_s.png

1263 ms

mv_spec_resource.svg

mv_spec_resource.svg

1259 ms

feature_nav_box.png

feature_nav_box.png

1264 ms

feature_nav_01.svg

feature_nav_01.svg

1396 ms

feature_nav_02.svg

feature_nav_02.svg

1429 ms

feature_nav_03.svg

feature_nav_03.svg

1431 ms

feature_01_img_s.png

feature_01_img_s.png

1444 ms

bg_feature_02_img.svg

bg_feature_02_img.svg

1445 ms

feature_02_wp.svg

feature_02_wp.svg

1568 ms

feature_02_wptransfer.svg

feature_02_wptransfer.svg

1607 ms

feature_02_ssl.svg

feature_02_ssl.svg

1610 ms

feature_02_bk.svg

feature_02_bk.svg

1624 ms

feature_03_img.svg

feature_03_img.svg

1629 ms

xbiz_link_box_type04_bg.png

xbiz_link_box_type04_bg.png

1742 ms

xbiz_link_box_type04.png

xbiz_link_box_type04.png

1553 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

94 ms

KFOlCnqEu92Fr1MmEU9vAw.ttf

KFOlCnqEu92Fr1MmEU9vAw.ttf

292 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

426 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFPYk75s.ttf

535 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFCMj75s.ttf

524 ms

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf

-F6jfjtqLzI2JPCgQBnw7HFyzSD-AsregP8VFBEj75s.ttf

535 ms

conversion_async.js

conversion_async.js

1501 ms

xserver.ttf

xserver.ttf

1128 ms

flow_nav_01.svg

flow_nav_01.svg

1203 ms

flow_nav_02.svg

flow_nav_02.svg

1205 ms

flow_nav_03.svg

flow_nav_03.svg

1257 ms

flow_nav_04.svg

flow_nav_04.svg

1305 ms

bg_case.png

bg_case.png

1306 ms

img_case_ttl.svg

img_case_ttl.svg

1242 ms

img_case_num01.svg

img_case_num01.svg

1421 ms

img_case_num02.svg

img_case_num02.svg

1324 ms

img_case_logo_delltech.png

img_case_logo_delltech.png

1337 ms

img_case_logo_saison.png

img_case_logo_saison.png

1382 ms

img_case_logo_jrbus.png

img_case_logo_jrbus.png

1268 ms

img_case_logo_pizzahut.png

img_case_logo_pizzahut.png

1280 ms

img_case_logo_sokupri.png

img_case_logo_sokupri.png

1354 ms

img_case_logo_hugetsudo.png

img_case_logo_hugetsudo.png

1360 ms

img_case_logo_humantec.png

img_case_logo_humantec.png

1417 ms

img_case_logo_hatendo.png

img_case_logo_hatendo.png

1248 ms

img_case_logo_yamasa.png

img_case_logo_yamasa.png

1268 ms

img_case_logo_smacom.png

img_case_logo_smacom.png

1132 ms

img_case_logo_mktaxi.png

img_case_logo_mktaxi.png

1162 ms

footer_cta_bg.png

footer_cta_bg.png

1178 ms

img_help_phone.svg

img_help_phone.svg

1240 ms

img_help_phone_free.svg

img_help_phone_free.svg

1237 ms

bnr_beginner_daiko_cp_l.png

bnr_beginner_daiko_cp_l.png

1137 ms

bnr_beginner_wpblog_l.png

bnr_beginner_wpblog_l.png

1105 ms

bnr_beginner_transfer_l.png

bnr_beginner_transfer_l.png

1160 ms

bnr_beginner_blog_l.png

bnr_beginner_blog_l.png

1168 ms

bnr_beginner_hp_l.png

bnr_beginner_hp_l.png

1233 ms

bnr_recruiting_l.png

bnr_recruiting_l.png

1109 ms

bnr_friend_l.png

bnr_friend_l.png

1107 ms

bnr_partner.png

bnr_partner.png

1106 ms

img_isms.png

img_isms.png

1137 ms

img_privacymark.png

img_privacymark.png

1154 ms

ico_sns_facebook.svg

ico_sns_facebook.svg

1115 ms

ico_sns_x.svg

ico_sns_x.svg

1073 ms

campaign_side_banner.png

campaign_side_banner.png

1035 ms

campaign_side_banner.png

campaign_side_banner.png

1034 ms

img_modal_ttl.png

img_modal_ttl.png

1071 ms

img_modal_logo.png

img_modal_logo.png

1054 ms

bg_patern_line_blue.png

bg_patern_line_blue.png

1117 ms

604 ms

ico_blank_white.svg

ico_blank_white.svg

1071 ms

pd.js

pd.js

191 ms

Accessibility Review

xserver.ne.jp accessibility score

78

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

xserver.ne.jp best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

xserver.ne.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 Xserver.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 Xserver.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

xserver.ne.jp

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