Report Summary

  • 37

    Performance

    Renders faster than
    57% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

wpx.ne.jp

国内最速レンタルサーバーをはじめ多彩なサービスがつかえる【wpX】

Page Load Speed

4.7 sec in total

First Response

568 ms

Resources Loaded

4 sec

Page Rendered

158 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」のサイトです。

Visit wpx.ne.jp

Key Findings

We analyzed Wpx.ne.jp page load time and found that the first response time was 568 ms and then it took 4.1 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

wpx.ne.jp performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value6.9 s

33/100

10%

TBT (Total Blocking Time)

Value590 ms

50/100

30%

CLS (Cumulative Layout Shift)

Value0.123

83/100

15%

TTI (Time to Interactive)

Value7.8 s

44/100

10%

Network Requests Diagram

wpx.ne.jp

568 ms

wpx.ne.jp

786 ms

www.wpx.ne.jp

936 ms

top_layout.css

180 ms

smartRollover.js

358 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 86% of them (25 requests) were addressed to the original Wpx.ne.jp, 7% (2 requests) were made to Google-analytics.com and 3% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Wpx.ne.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 46.4 kB (33%)

Content Size

140.4 kB

After Optimization

94.0 kB

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

HTML Optimization

-73%

Potential reduce by 5.2 kB

  • Original 7.1 kB
  • After minification 6.1 kB
  • After compression 2.0 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 965 B, which is 14% 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 5.2 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 827 B

  • Original 69.4 kB
  • After minification 68.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

-60%

Potential reduce by 32.6 kB

  • Original 54.1 kB
  • After minification 54.0 kB
  • After compression 21.5 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 32.6 kB or 60% of the original size.

CSS Optimization

-80%

Potential reduce by 7.8 kB

  • Original 9.8 kB
  • After minification 7.0 kB
  • After compression 2.0 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 needs all CSS files to be minified and compressed as it can save up to 7.8 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (33%)

Requests Now

24

After Optimization

16

The browser has sent 24 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 and as a result speed up the page load time.

Accessibility Review

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

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

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

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: