Tools & Wizards About Us
xmax.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

xmax.jp

xmax（クロスマックス）

Page Load Speed

6.7 sec in total

First Response

543 ms

Resources Loaded

5.3 sec

Page Rendered

829 ms

xmax.jp screenshot

About Website

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

アフィリエイトに本気で取り組むならxmax（クロスマックス）。登録料、手数料無料。高額報酬、好条件のアフィリエイト案件を多数取り揃えております。

Visit xmax.jp

Key Findings

We analyzed Xmax.jp page load time and found that the first response time was 543 ms and then it took 6.2 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

xmax.jp performance score

0

Network Requests Diagram

xmax.jp

543 ms

www.xmax.jp

1249 ms

jquery-ui-1.8.16.custom.css

343 ms

jquery.mouseinfobox.css

516 ms

basic.css

620 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 90% of them (47 requests) were addressed to the original Xmax.jp, 4% (2 requests) were made to Trusted-web-seal.cybertrust.ne.jp and 4% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Evup.cybertrust.ne.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 76.0 kB (52%)

Content Size

145.7 kB

After Optimization

69.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Xmax.jp main page is 145.7 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. CSS take 63.4 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 19.4 kB

  • Original 25.8 kB
  • After minification 21.9 kB
  • After compression 6.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 3.9 kB, which is 15% 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 19.4 kB or 75% of the original size.

Image Optimization

-9%

Potential reduce by 3.5 kB

  • Original 39.3 kB
  • After minification 35.8 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. Xmax images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 34 B

  • Original 17.2 kB
  • After minification 17.2 kB
  • After compression 17.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. This website has mostly compressed JavaScripts.

CSS Optimization

-84%

Potential reduce by 53.0 kB

  • Original 63.4 kB
  • After minification 46.0 kB
  • After compression 10.4 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. Xmax.jp needs all CSS files to be minified and compressed as it can save up to 53.0 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (46%)

Requests Now

48

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

xmax.jp

xmax.jp

543 ms

www.xmax.jp

www.xmax.jp

1249 ms

jquery-ui-1.8.16.custom.css

jquery-ui-1.8.16.custom.css

343 ms

jquery.mouseinfobox.css

jquery.mouseinfobox.css

516 ms

basic.css

basic.css

620 ms

common.css

common.css

697 ms

operation.css

operation.css

699 ms

top_freespace.css

top_freespace.css

700 ms

jquery-1.6.4.min.js

jquery-1.6.4.min.js

1080 ms

jquery-ui-1.8.16.custom.min.js

jquery-ui-1.8.16.custom.min.js

1429 ms

ui.datepicker-ja.js

ui.datepicker-ja.js

765 ms

jquery.popupwindow.js

jquery.popupwindow.js

864 ms

jquery.carthage.js

jquery.carthage.js

864 ms

thickbox.js

thickbox.js

864 ms

jquery.mouseinfobox.js

jquery.mouseinfobox.js

914 ms

slide-xmax.js

slide-xmax.js

1034 ms

getScript

getScript

1207 ms

ga.js

ga.js

140 ms

logo_xmax.gif

logo_xmax.gif

235 ms

bt_login_off.gif

bt_login_off.gif

229 ms

img_arrow.gif

img_arrow.gif

227 ms

gnavi_media_off.gif

gnavi_media_off.gif

226 ms

gnavi_client_off.gif

gnavi_client_off.gif

225 ms

1

1

330 ms

1

1

672 ms

xmax_expand.png

xmax_expand.png

505 ms

xmax_hapima.png

xmax_hapima.png

684 ms

bt_media_off.gif

bt_media_off.gif

425 ms

bt_client_off.gif

bt_client_off.gif

422 ms

title_top_affiliate.gif

title_top_affiliate.gif

456 ms

affiliate_image.gif

affiliate_image.gif

683 ms

title_top_knowhow.gif

title_top_knowhow.gif

513 ms

knowhow_image.gif

knowhow_image.gif

648 ms

title_top_service.gif

title_top_service.gif

664 ms

title_top_system.gif

title_top_system.gif

677 ms

btn_pagetop.gif

btn_pagetop.gif

846 ms

icon_sitemap.gif

icon_sitemap.gif

810 ms

icon_information.gif

icon_information.gif

836 ms

logo_xmax_jao.gif

logo_xmax_jao.gif

841 ms

top_twitter.gif

top_twitter.gif

847 ms

gnavi_home_now.gif

gnavi_home_now.gif

830 ms

s_navi_01.gif

s_navi_01.gif

933 ms

s_navi_02.gif

s_navi_02.gif

977 ms

s_navi_03.gif

s_navi_03.gif

983 ms

imac.png

imac.png

956 ms

bt_back_media.gif

bt_back_media.gif

933 ms

bt_back_client.gif

bt_back_client.gif

934 ms

__utm.gif

__utm.gif

20 ms

getSeal

getSeal

173 ms

evup.gif

evup.gif

1678 ms

loading.gif

loading.gif

708 ms

arrows.png

arrows.png

174 ms

SEO Factors

xmax.jp SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Xmax.jp can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Xmax.jp main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

xmax.jp

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