8.5 sec in total
562 ms
7.3 sec
666 ms
Click here to check amazing 2XU content for Japan. Otherwise, check out these important facts you probably never knew about 2xu.jp
データが証明する超科学タイツ。最高のコンプレッション、スポーツタイツをトレーニング、ランニング、ワークアウト、フィットネスに。世界71カ国で販売され、数多くのトップアスリートが愛用。
Visit 2xu.jpWe analyzed 2xu.jp page load time and found that the first response time was 562 ms and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
2xu.jp performance score
562 ms
755 ms
362 ms
361 ms
902 ms
Our browser made a total of 84 requests to load all elements on the main page. We found that 89% of them (75 requests) were addressed to the original 2xu.jp, 4% (3 requests) were made to S.ytimg.com and 2% (2 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (4.4 sec) belongs to the original domain 2xu.jp.
Page size can be reduced by 1.1 MB (21%)
5.1 MB
4.0 MB
In fact, the total size of 2xu.jp main page is 5.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. 65% of websites need less resources to load. Images take 4.5 MB which makes up the majority of the site volume.
Potential reduce by 25.9 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 4.6 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 25.9 kB or 85% of the original size.
Potential reduce by 592.6 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, 2XU needs image optimization as it can save up to 592.6 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 218.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 218.2 kB or 66% of the original size.
Potential reduce by 214.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. 2xu.jp needs all CSS files to be minified and compressed as it can save up to 214.0 kB or 83% of the original size.
Number of requests can be reduced by 21 (27%)
79
58
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 2XU. 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.
2xu.jp
562 ms
www.2xu.jp
755 ms
import.css
362 ms
smoothscroll.js
361 ms
jquery-1.10.1.min.js
902 ms
jquery.bxslider.min.js
539 ms
matome.js
363 ms
menu.js
193 ms
contents.css
187 ms
reset.css
184 ms
jquery.bxslider.css
185 ms
menu.css
201 ms
1GEhjXHQR1I
117 ms
NKqe4UAAszQ
216 ms
bg.jpg
357 ms
header_bg.gif
354 ms
sns_bg.png
353 ms
facbook.jpg
354 ms
instagram.jpg
353 ms
logo.jpg
338 ms
bar_right.jpg
435 ms
i_search.jpg
436 ms
cart.jpg
434 ms
2016ss_men.jpg
1831 ms
2016ss_women.jpg
1826 ms
forwomen2.jpg
2062 ms
b_point1000-2.jpg
1312 ms
bg_middleX.jpg
1142 ms
b_human.jpg
998 ms
b_fabric.jpg
1352 ms
category_bg.jpg
1327 ms
b_corerange.jpg
1490 ms
yajirushi.png
1507 ms
b_Compression_l.jpg
1544 ms
b_accessories.jpg
1673 ms
b_running.jpg
1689 ms
b_running_l.jpg
1724 ms
b_runaccessories.jpg
1855 ms
b_wetsuits.jpg
2045 ms
contents_bg.png
2648 ms
top_shadow.png
2000 ms
t_m_hotitem.png
2006 ms
product001.jpg
2207 ms
product002.jpg
2367 ms
product003.jpg
2542 ms
product004.jpg
2756 ms
product005.jpg
2431 ms
product006.jpg
3483 ms
product007.jpg
2721 ms
product008.jpg
2756 ms
www-embed-player-vflfNyN_r.css
30 ms
www-embed-player.js
52 ms
base.js
103 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
44 ms
ad_status.js
115 ms
product009.jpg
4367 ms
product010.jpg
2854 ms
b_allitem.png
2556 ms
t_w_hotitem.png
2593 ms
product011.jpg
2848 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
85 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
86 ms
product012.jpg
2920 ms
product013.jpg
3043 ms
product014.jpg
3181 ms
product015.jpg
3477 ms
product016.jpg
2628 ms
product017.jpg
2544 ms
product018.jpg
3063 ms
product019.jpg
3847 ms
product020.jpg
2488 ms
movie_bg.jpg
2375 ms
t_movie.png
2511 ms
t_information.png
2502 ms
news0306.jpg
2419 ms
news0108.jpg
2510 ms
news1019.jpg
2503 ms
news1001_1.jpg
2453 ms
pagetop.jpg
2550 ms
copy_bg.jpg
2551 ms
bx_loader.gif
2464 ms
arrow.png
2544 ms
pre.png
2515 ms
bar_down.jpg
2529 ms
2xu.jp SEO score
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 2xu.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 2xu.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.
2xu.jp
Open Graph description is not detected on the main page of 2XU. 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: