Tools & Wizards About Us
wpx.ne.jp screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

wpx.ne.jp

WordPress専用クラウド型レンタルサーバー【wpX Speed】

Page Load Speed

7.9 sec in total

First Response

533 ms

Resources Loaded

6.8 sec

Page Rendered

568 ms

wpx.ne.jp screenshot

About Website

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

wpX SpeedはWordPressに最適化したクラウド型レンタルサーバーです。SSDの高速性を最大限に発揮する次世代の接続規格「NVMe」の採用をはじめ、キャッシュなしでWordPressを10倍以上高速化する機能などWordPressの高速化に徹底した環境を提供します。

Visit wpx.ne.jp

Key Findings

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

Performance Metrics

wpx.ne.jp performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value13.0 s

0/100

25%

SI (Speed Index)

Value8.0 s

21/100

10%

TBT (Total Blocking Time)

Value1,240 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.113

86/100

15%

TTI (Time to Interactive)

Value13.0 s

12/100

10%

Network Requests Diagram

wpx.ne.jp

533 ms

www.wpx.ne.jp

911 ms

gtm.js

77 ms

google.js

178 ms

a8sales.js

24 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 84% of them (43 requests) were addressed to the original Wpx.ne.jp, 4% (2 requests) were made to Statics.a8.net and 4% (2 requests) were made to B97.yahoo.co.jp. The less responsive or slowest element that took the longest time to load (4.8 sec) belongs to the original domain Wpx.ne.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 85.0 kB (13%)

Content Size

676.3 kB

After Optimization

591.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wpx.ne.jp main page is 676.3 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 481.7 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 41.8 kB

  • Original 50.6 kB
  • After minification 36.5 kB
  • After compression 8.8 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 14.1 kB, which is 28% 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 41.8 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 1.2 kB

  • Original 481.7 kB
  • After minification 480.5 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. WpX images are well optimized though.

JavaScript Optimization

-34%

Potential reduce by 41.9 kB

  • Original 124.9 kB
  • After minification 124.9 kB
  • After compression 83.1 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.9 kB or 34% of the original size.

CSS Optimization

-1%

Potential reduce by 185 B

  • Original 19.0 kB
  • After minification 19.0 kB
  • After compression 18.9 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. Wpx.ne.jp has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 20 (43%)

Requests Now

47

After Optimization

27

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wpx.ne.jp

wpx.ne.jp

533 ms

www.wpx.ne.jp

www.wpx.ne.jp

911 ms

gtm.js

gtm.js

77 ms

google.js

google.js

178 ms

a8sales.js

a8sales.js

24 ms

a8crossDomain.js

a8crossDomain.js

28 ms

site.css

site.css

361 ms

style.css

style.css

527 ms

ss_130-50.js

ss_130-50.js

907 ms

jquery-1.12.4.min.js

jquery-1.12.4.min.js

1511 ms

libs.js

libs.js

648 ms

common.js

common.js

649 ms

conversion.js

conversion.js

671 ms

s_retargeting.js

s_retargeting.js

869 ms

header-text.png

header-text.png

469 ms

img_siteid.png

img_siteid.png

470 ms

img_siteid.png

img_siteid.png

522 ms

txt_kv.png

txt_kv.png

527 ms

img_wp_cloud_l.png

img_wp_cloud_l.png

710 ms

img_speed_01_l.png

img_speed_01_l.png

711 ms

img_server.png

img_server.png

548 ms

img_speed_02.png

img_speed_02.png

696 ms

img_speed_03_l.png

img_speed_03_l.png

702 ms

img_speed_04.png

img_speed_04.png

730 ms

img_wp_transfer.png

img_wp_transfer.png

872 ms

img_waf.png

img_waf.png

877 ms

img_backup.png

img_backup.png

884 ms

img_func_01.png

img_func_01.png

888 ms

img_func_02.png

img_func_02.png

910 ms

img_func_03.png

img_func_03.png

1047 ms

img_sv_logo.png

img_sv_logo.png

1052 ms

img_cloud_logo.png

img_cloud_logo.png

1061 ms

img_siteid_white.png

img_siteid_white.png

1065 ms

bnr_affiliate.png

bnr_affiliate.png

1091 ms

ico_sns_facebook.svg

ico_sns_facebook.svg

1222 ms

ico_sns_x.svg

ico_sns_x.svg

1226 ms

btn_pagetop.png

btn_pagetop.png

1236 ms

ico_target_blank.png

ico_target_blank.png

893 ms

bg_gnav_item.png

bg_gnav_item.png

922 ms

ico_tri_down.png

ico_tri_down.png

1050 ms

ico_login.png

ico_login.png

1052 ms

ico_sign_up.png

ico_sign_up.png

1063 ms

bg_kv.png

bg_kv.png

4786 ms

bg_speed.png

bg_speed.png

1103 ms

bg_price.png

bg_price.png

1514 ms

ico_recommend.png

ico_recommend.png

1222 ms

bg_func.png

bg_func.png

1112 ms

img_sign_up.png

img_sign_up.png

1123 ms

xserver.ttf

xserver.ttf

1168 ms

conversion_async.js

conversion_async.js

1418 ms

601 ms

Accessibility Review

wpx.ne.jp accessibility score

74

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Best Practices

wpx.ne.jp best practices score

83

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

SEO Factors

wpx.ne.jp SEO score

81

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

wpx.ne.jp

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