Tools & Wizards About Us
poolside.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

poolside.jp

POOLSIDE SHOES OUTLET｜POOLSIDE(プールサイド)のアウトレット通販サイト

Page Load Speed

6.3 sec in total

First Response

530 ms

Resources Loaded

5.3 sec

Page Rendered

420 ms

poolside.jp screenshot

About Website

Welcome to poolside.jp homepage info - get ready to check POOLSIDE best content right away, or after learning these important things about poolside.jp

POOLSIDE SHOES OUTLETは、プールサイドの靴がお得な価格で購入できるアウトレット通販サイトです。人気の靴、トレンドの靴を割引価格でご提供します。今しか手に入らない商品をお見逃しなく！

Visit poolside.jp

Key Findings

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

Performance Metrics

poolside.jp performance score

0

Network Requests Diagram

poolside.jp

530 ms

default.aspx

652 ms

style.css

334 ms

index.css

350 ms

jquery.js

840 ms

Our browser made a total of 149 requests to load all elements on the main page. We found that 85% of them (127 requests) were addressed to the original Poolside.jp, 13% (19 requests) were made to Shoesconcierge-img.jp and 1% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Poolside.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 201.8 kB (19%)

Content Size

1.1 MB

After Optimization

853.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Poolside.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. 30% of websites need less resources to load. Images take 818.5 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 35.9 kB

  • Original 44.0 kB
  • After minification 40.8 kB
  • After compression 8.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 35.9 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 30.2 kB

  • Original 818.5 kB
  • After minification 788.3 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. POOLSIDE images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 49.1 kB

  • Original 88.9 kB
  • After minification 82.1 kB
  • After compression 39.8 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 49.1 kB or 55% of the original size.

CSS Optimization

-84%

Potential reduce by 86.6 kB

  • Original 103.4 kB
  • After minification 68.9 kB
  • After compression 16.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. Poolside.jp needs all CSS files to be minified and compressed as it can save up to 86.6 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 69 (47%)

Requests Now

147

After Optimization

78

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

poolside.jp

poolside.jp

530 ms

default.aspx

default.aspx

652 ms

style.css

style.css

334 ms

index.css

index.css

350 ms

jquery.js

jquery.js

840 ms

lookupzip.js

lookupzip.js

340 ms

common.js

common.js

522 ms

default.js

default.js

498 ms

scope.js

scope.js

511 ms

jquery.flatheights.js

jquery.flatheights.js

509 ms

angle-0.1.0.js

angle-0.1.0.js

516 ms

reset.css

reset.css

330 ms

s_lmr.css

s_lmr.css

344 ms

common.css

common.css

357 ms

sidebox.css

sidebox.css

350 ms

category.css

category.css

359 ms

goods.css

goods.css

494 ms

order.css

order.css

509 ms

customer.css

customer.css

518 ms

etc.css

etc.css

526 ms

quickorder.css

quickorder.css

528 ms

userreview.css

userreview.css

657 ms

core.css

core.css

671 ms

skin.css

skin.css

676 ms

dropframe.css

dropframe.css

684 ms

user.css

user.css

698 ms

freepage.css

freepage.css

700 ms

spin.css

spin.css

820 ms

0.jpg

0.jpg

886 ms

bg_header.jpg

bg_header.jpg

179 ms

line_header.gif

line_header.gif

166 ms

logo.png

logo.png

186 ms

btn_cart_off.png

btn_cart_off.png

172 ms

btn_fav_off.png

btn_fav_off.png

169 ms

btn_login_off.png

btn_login_off.png

176 ms

icn_guide.png

icn_guide.png

385 ms

icn_questions.png

icn_questions.png

386 ms

btn_register_off.png

btn_register_off.png

411 ms

bg_search.gif

bg_search.gif

410 ms

btn_search_off.png

btn_search_off.png

411 ms

bg_news.gif

bg_news.gif

410 ms

bg_balloon_01.png

bg_balloon_01.png

550 ms

bg_mainimg.jpg

bg_mainimg.jpg

1071 ms

bg_mainimg_search01.png

bg_mainimg_search01.png

589 ms

btn_ps_01.gif

btn_ps_01.gif

580 ms

btn_ms_01.gif

btn_ms_01.gif

579 ms

bg_mainimg_search02.png

bg_mainimg_search02.png

574 ms

btn_type_01.gif

btn_type_01.gif

706 ms

btn_type_02.gif

btn_type_02.gif

742 ms

btn_type_03.gif

btn_type_03.gif

750 ms

btn_type_04.gif

btn_type_04.gif

746 ms

bg_mainimg_search03.png

bg_mainimg_search03.png

754 ms

btn_mainimg_off.png

btn_mainimg_off.png

870 ms

h_special-bunner.gif

h_special-bunner.gif

915 ms

bnr_20160302_psosigoto.jpg

bnr_20160302_psosigoto.jpg

1259 ms

bnr_20160302_psrowheel.jpg

bnr_20160302_psrowheel.jpg

1443 ms

bnr_20160217_psnew.jpg

bnr_20160217_psnew.jpg

1451 ms

h_pickup.png

h_pickup.png

1042 ms

h_ps.jpg

h_ps.jpg

1083 ms

little.gif

little.gif

1206 ms

bg_img_01.gif

bg_img_01.gif

1228 ms

P.gif

P.gif

1254 ms

h_ms.jpg

h_ms.jpg

1367 ms

M.gif

M.gif

1398 ms

0.jpg

0.jpg

908 ms

0.jpg

0.jpg

918 ms

0.jpg

0.jpg

908 ms

0.jpg

0.jpg

928 ms

0.jpg

0.jpg

942 ms

0.jpg

0.jpg

1015 ms

0.jpg

0.jpg

1076 ms

0.jpg

0.jpg

1077 ms

0.jpg

0.jpg

1092 ms

0.jpg

0.jpg

1104 ms

0.jpg

0.jpg

1129 ms

0.jpg

0.jpg

1189 ms

0.jpg

0.jpg

1248 ms

0.jpg

0.jpg

1253 ms

0.jpg

0.jpg

1266 ms

0.jpg

0.jpg

1286 ms

0.jpg

0.jpg

1310 ms

0.jpg

0.jpg

1360 ms

c

c

558 ms

h_ranking.jpg

h_ranking.jpg

1381 ms

ga.js

ga.js

13 ms

__utm.gif

__utm.gif

13 ms

item.txt

item.txt

1275 ms

news.txt

news.txt

1382 ms

bg_ranking.gif

bg_ranking.gif

1414 ms

bg_img_02.gif

bg_img_02.gif

1430 ms

icn_ranking_01.gif

icn_ranking_01.gif

1440 ms

icn_ranking_02.gif

icn_ranking_02.gif

1444 ms

icn_ranking_03.gif

icn_ranking_03.gif

1250 ms

h_scene.gif

h_scene.gif

1332 ms

bnr_scene_01.jpg

bnr_scene_01.jpg

1343 ms

bnr_scene_02.jpg

bnr_scene_02.jpg

1365 ms

bnr_scene_03.jpg

bnr_scene_03.jpg

1379 ms

bnr_scene_04.jpg

bnr_scene_04.jpg

1393 ms

bnr_scene_05.jpg

bnr_scene_05.jpg

1258 ms

bnr_scene_06.jpg

bnr_scene_06.jpg

1300 ms

h_info.gif

h_info.gif

1332 ms

h_info_01.gif

h_info_01.gif

1356 ms

line_01.jpg

line_01.jpg

1368 ms

btn_info_01_off.gif

btn_info_01_off.gif

1255 ms

btn_info_03_off.gif

btn_info_03_off.gif

1228 ms

h_info_02.gif

h_info_02.gif

1291 ms

line_02.gif

line_02.gif

1329 ms

img_info.jpg

img_info.jpg

1349 ms

h_info_03.gif

h_info_03.gif

1245 ms

h_info_05.gif

h_info_05.gif

1214 ms

h_info_04.gif

h_info_04.gif

1098 ms

bg_side_top.gif

bg_side_top.gif

1139 ms

bg_side.gif

bg_side.gif

1162 ms

h_brand.jpg

h_brand.jpg

1063 ms

icn_arrow_01.gif

icn_arrow_01.gif

1050 ms

h_shoes.jpg

h_shoes.jpg

1041 ms

h_type.gif

h_type.gif

1058 ms

h_size.gif

h_size.gif

1000 ms

h_price.gif

h_price.gif

1009 ms

h_color.gif

h_color.gif

1018 ms

btn_wht.gif

btn_wht.gif

1013 ms

btn_gry.gif

btn_gry.gif

1030 ms

btn_blk.gif

btn_blk.gif

1036 ms

btn_red.gif

btn_red.gif

1000 ms

btn_pik.gif

btn_pik.gif

1010 ms

btn_win.gif

btn_win.gif

1013 ms

btn_brw.gif

btn_brw.gif

1013 ms

btn_beg.gif

btn_beg.gif

1029 ms

btn_ore.gif

btn_ore.gif

1035 ms

btn_yel.gif

btn_yel.gif

994 ms

btn_grn.gif

btn_grn.gif

1007 ms

btn_blu.gif

btn_blu.gif

1008 ms

btn_ppl.gif

btn_ppl.gif

1006 ms

btn_etn.gif

btn_etn.gif

1021 ms

btn_slv.gif

btn_slv.gif

1033 ms

btn_gld.gif

btn_gld.gif

995 ms

btn_bbz.gif

btn_bbz.gif

1007 ms

btn_oth.gif

btn_oth.gif

1007 ms

h_heel.gif

h_heel.gif

1011 ms

bg_side_bottom.gif

bg_side_bottom.gif

1027 ms

bg_s_search.jpg

bg_s_search.jpg

1034 ms

btn_s_search_off.jpg

btn_s_search_off.jpg

996 ms

bnr_mb.gif

bnr_mb.gif

1007 ms

bg_web.gif

bg_web.gif

1007 ms

bnr_sc_01.jpg

bnr_sc_01.jpg

1018 ms

bnr_ps_01.jpg

bnr_ps_01.jpg

1028 ms

bnr_ms_01.jpg

bnr_ms_01.jpg

1035 ms

sticker_m.gif

sticker_m.gif

998 ms

btn_pagetop_off.gif

btn_pagetop_off.gif

1007 ms

SEO Factors

poolside.jp SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Poolside.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), while the claimed language is Japanese. Our system also found out that Poolside.jp main page’s claimed encoding is shift_jis. 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

poolside.jp

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