Tools & Wizards About Us
pliqua.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

pliqua.co.jp

パーティードレス・セレモニースーツ通販専門店｜プリカ

Page Load Speed

14 sec in total

First Response

728 ms

Resources Loaded

12.7 sec

Page Rendered

569 ms

pliqua.co.jp screenshot

About Website

Visit pliqua.co.jp now to see the best up-to-date Pliqua content and also check out these interesting facts you probably never knew about pliqua.co.jp

プリカは、パーティードレス通販専門店です。20代・30代・40代・50代の女性のための結婚式・披露宴・二次会・入卒式・七五三にふさわしいパーティードレスやセレモニースーツの通販を行っています。新宿フィッティングルームにおいて、試着＆購入も可能です。

Visit pliqua.co.jp

Key Findings

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

Performance Metrics

pliqua.co.jp performance score

0

Network Requests Diagram

pliqua.co.jp

728 ms

original.css

345 ms

info-slide.css

357 ms

201203added.css

360 ms

bxSlider.css

367 ms

Our browser made a total of 129 requests to load all elements on the main page. We found that 86% of them (111 requests) were addressed to the original Pliqua.co.jp, 12% (15 requests) were made to Secure.future-s.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (9.4 sec) belongs to the original domain Pliqua.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 246.3 kB (4%)

Content Size

5.5 MB

After Optimization

5.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pliqua.co.jp main page is 5.5 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. 45% of websites need less resources to load. Images take 5.2 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 20.0 kB

  • Original 26.2 kB
  • After minification 24.5 kB
  • After compression 6.2 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 20.0 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 69.1 kB

  • Original 5.2 MB
  • After minification 5.2 MB

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. Pliqua images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 123.5 kB

  • Original 196.5 kB
  • After minification 170.7 kB
  • After compression 73.0 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 123.5 kB or 63% of the original size.

CSS Optimization

-80%

Potential reduce by 33.8 kB

  • Original 42.4 kB
  • After minification 31.5 kB
  • After compression 8.6 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. Pliqua.co.jp needs all CSS files to be minified and compressed as it can save up to 33.8 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (27%)

Requests Now

127

After Optimization

93

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 127 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pliqua. 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 12 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

pliqua.co.jp

pliqua.co.jp

728 ms

original.css

original.css

345 ms

info-slide.css

info-slide.css

357 ms

201203added.css

201203added.css

360 ms

bxSlider.css

bxSlider.css

367 ms

jquery.js

jquery.js

767 ms

jcommon.js

jcommon.js

374 ms

scrollTo.js

scrollTo.js

515 ms

info-slide.js

info-slide.js

533 ms

jquery.min.js

jquery.min.js

33 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

1076 ms

jquery.bxSlider.js

jquery.bxSlider.js

762 ms

reset.css

reset.css

1248 ms

global.css

global.css

1439 ms

local.css

local.css

1759 ms

jquery.lightbox-0.5.css

jquery.lightbox-0.5.css

1413 ms

error.css

error.css

1426 ms

hack.css

hack.css

1437 ms

fjord.css

fjord.css

1423 ms

print.css

print.css

177 ms

logo_sitelogo03.gif

logo_sitelogo03.gif

497 ms

scr_ss01.jpg

scr_ss01.jpg

2012 ms

185 ms

header_txt02.gif

header_txt02.gif

354 ms

gnavi_001.gif

gnavi_001.gif

357 ms

gnavi_002.gif

gnavi_002.gif

359 ms

gnavi_004.gif

gnavi_004.gif

366 ms

gnavi_008.gif

gnavi_008.gif

369 ms

snavi_001.gif

snavi_001.gif

527 ms

snavi_002.gif

snavi_002.gif

533 ms

snavi_003.gif

snavi_003.gif

535 ms

snavi_004.gif

snavi_004.gif

546 ms

tryon.jpg

tryon.jpg

1139 ms

scr_ss009.jpg

scr_ss009.jpg

1983 ms

scr_ss004.jpg

scr_ss004.jpg

1747 ms

scr_ss010.jpg

scr_ss010.jpg

1771 ms

scr_ss004_02.jpg

scr_ss004_02.jpg

1775 ms

scr_ss005_02.jpg

scr_ss005_02.jpg

1817 ms

scr_ss006.jpg

scr_ss006.jpg

2608 ms

scr_ss007.jpg

scr_ss007.jpg

2271 ms

scr_ss008_02.jpg

scr_ss008_02.jpg

2305 ms

scr_ss002.jpg

scr_ss002.jpg

3025 ms

scr_ss003.jpg

scr_ss003.jpg

2365 ms

ti_news_02.gif

ti_news_02.gif

2173 ms

ranking_dress.gif

ranking_dress.gif

2363 ms

txt_rank_best1_02.gif

txt_rank_best1_02.gif

2448 ms

234_1.jpg

234_1.jpg

2660 ms

txt_rank_best2_02.gif

txt_rank_best2_02.gif

2553 ms

196_1.JPG

196_1.JPG

3276 ms

txt_rank_best3_02.gif

txt_rank_best3_02.gif

2622 ms

77_thumbnail.jpg

77_thumbnail.jpg

3118 ms

txt_rank_best4_02.gif

txt_rank_best4_02.gif

2977 ms

295_1.JPG

295_1.JPG

3321 ms

txt_rank_best5_02.gif

txt_rank_best5_02.gif

2905 ms

249_1.JPG

249_1.JPG

3439 ms

ranking_suits.gif

ranking_suits.gif

3161 ms

20_1.jpg

20_1.jpg

3551 ms

180_1.JPG

180_1.JPG

3684 ms

bg_header.gif

bg_header.gif

264 ms

bg_input.gif

bg_input.gif

252 ms

bg_submit.gif

bg_submit.gif

262 ms

icon_001_02.gif

icon_001_02.gif

250 ms

bg_footer.gif

bg_footer.gif

261 ms

scr_ss02.jpg

scr_ss02.jpg

1995 ms

scr_ss03.jpg

scr_ss03.jpg

2006 ms

scr_ss04.jpg

scr_ss04.jpg

2014 ms

scr_ss05.jpg

scr_ss05.jpg

2015 ms

scr_ss06.jpg

scr_ss06.jpg

1865 ms

scr_ss07.jpg

scr_ss07.jpg

2472 ms

scr_ss08.jpg

scr_ss08.jpg

2343 ms

scr_ss09.jpg

scr_ss09.jpg

2357 ms

scr_ss10.jpg

scr_ss10.jpg

2370 ms

title-welcome2.png

title-welcome2.png

2195 ms

back-welcome.png

back-welcome.png

2197 ms

title-hokori.png

title-hokori.png

2560 ms

title-madeinjapan.png

title-madeinjapan.png

2381 ms

title-voice.png

title-voice.png

2527 ms

title-fittingservice.png

title-fittingservice.png

2537 ms

ga.js

ga.js

5 ms

__utm.gif

__utm.gif

13 ms

cal.cgi

cal.cgi

431 ms

19_thumbnail.jpg

19_thumbnail.jpg

5200 ms

144_1.JPG

144_1.JPG

4202 ms

248_1.JPG

248_1.JPG

3497 ms

ranking_jacket.gif

ranking_jacket.gif

3266 ms

287_1.jpg

287_1.jpg

3733 ms

253_thumbnail.jpg

253_thumbnail.jpg

3513 ms

284_1.JPG

284_1.JPG

3552 ms

86_1.JPG

86_1.JPG

3675 ms

258_1.JPG

258_1.JPG

9428 ms

styleup04.jpg

styleup04.jpg

3736 ms

style.css

style.css

184 ms

combi02.jpg

combi02.jpg

3320 ms

10pix.jpg

10pix.jpg

2639 ms

haori.jpg

haori.jpg

2709 ms

airly06.jpg

airly06.jpg

2802 ms

side-1sttime.jpg

side-1sttime.jpg

2824 ms

shipping02.gif

shipping02.gif

2694 ms

sokujitsu02.gif

sokujitsu02.gif

2746 ms

info_tel02.gif

info_tel02.gif

2485 ms

info_mail02.gif

info_mail02.gif

2518 ms

nav_h2_02.gif

nav_h2_02.gif

2500 ms

nav_party_dress_02.jpg

nav_party_dress_02.jpg

2566 ms

nav_bolero_and_jackets_02.jpg

nav_bolero_and_jackets_02.jpg

2552 ms

nav_formal_suits_02.jpg

nav_formal_suits_02.jpg

2503 ms

nav_bag_02.jpg

nav_bag_02.jpg

2681 ms

nav_corsage_02.jpg

nav_corsage_02.jpg

2486 ms

nav_necklace_02.jpg

nav_necklace_02.jpg

2522 ms

fit_banner02.jpg

fit_banner02.jpg

2350 ms

side_ti_calenar_02.gif

side_ti_calenar_02.gif

2308 ms

voice04.gif

voice04.gif

2340 ms

suits.jpg

suits.jpg

2336 ms

MOVIE02.jpg

MOVIE02.jpg

2848 ms

facebook2.jpg

facebook2.jpg

2813 ms

blog03.jpg

blog03.jpg

2221 ms

gnavi_005.gif

gnavi_005.gif

2204 ms

gnavi_006.gif

gnavi_006.gif

2168 ms

gnavi_007.gif

gnavi_007.gif

2292 ms

footer_copy02.gif

footer_copy02.gif

2148 ms

thumb_scr_ss009.jpg

thumb_scr_ss009.jpg

2055 ms

thumb_scr_ss004.jpg

thumb_scr_ss004.jpg

2048 ms

thumb_scr_ss010.jpg

thumb_scr_ss010.jpg

2013 ms

thumb_scr_ss004_02.jpg

thumb_scr_ss004_02.jpg

2193 ms

thumb_scr_ss005_02.jpg

thumb_scr_ss005_02.jpg

2161 ms

thumb_scr_ss006.jpg

thumb_scr_ss006.jpg

1947 ms

thumb_scr_ss007.jpg

thumb_scr_ss007.jpg

1885 ms

thumb_scr_ss008_02.jpg

thumb_scr_ss008_02.jpg

1820 ms

thumb_scr_ss002.jpg

thumb_scr_ss002.jpg

1936 ms

thumb_scr_ss003.jpg

thumb_scr_ss003.jpg

1897 ms

SEO Factors

pliqua.co.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pliqua.co.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 Pliqua.co.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

pliqua.co.jp

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