Tools & Wizards About Us
franchelippee.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

franchelippee.com

franchelippee.com – このドメインはお名前.comで取得されています。

Page Load Speed

5.1 sec in total

First Response

1.2 sec

Resources Loaded

3.6 sec

Page Rendered

189 ms

franchelippee.com screenshot

About Website

Welcome to franchelippee.com homepage info - get ready to check Franchelippee best content for Japan right away, or after learning these important things about franchelippee.com

アパレルブランド「フランシュリッペ」の公式ホームページ

Visit franchelippee.com

Key Findings

We analyzed Franchelippee.com page load time and found that the first response time was 1.2 sec and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

franchelippee.com performance score

0

Network Requests Diagram

franchelippee.com

1244 ms

ga.js

31 ms

wp-emoji-release.min.js

159 ms

skin.css

317 ms

colorbox.css

315 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 81% of them (52 requests) were addressed to the original Franchelippee.com, 6% (4 requests) were made to Google-analytics.com and 3% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Franchelippee.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 351.7 kB (43%)

Content Size

824.9 kB

After Optimization

473.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Franchelippee.com main page is 824.9 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. 45% of websites need less resources to load. Images take 341.2 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 25.7 kB

  • Original 34.4 kB
  • After minification 31.6 kB
  • After compression 8.7 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 25.7 kB or 75% of the original size.

Image Optimization

-8%

Potential reduce by 26.5 kB

  • Original 341.2 kB
  • After minification 314.7 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. Franchelippee images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 174.6 kB

  • Original 285.6 kB
  • After minification 282.1 kB
  • After compression 111.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 174.6 kB or 61% of the original size.

CSS Optimization

-76%

Potential reduce by 125.0 kB

  • Original 163.7 kB
  • After minification 139.2 kB
  • After compression 38.7 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. Franchelippee.com needs all CSS files to be minified and compressed as it can save up to 125.0 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (38%)

Requests Now

63

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

franchelippee.com

franchelippee.com

1244 ms

ga.js

ga.js

31 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

159 ms

skin.css

skin.css

317 ms

colorbox.css

colorbox.css

315 ms

styles.css

styles.css

335 ms

pagenavi-css.css

pagenavi-css.css

340 ms

css

css

25 ms

style.css

style.css

340 ms

genericons.css

genericons.css

543 ms

jetpack.css

jetpack.css

473 ms

jquery.js

jquery.js

630 ms

jquery-migrate.min.js

jquery-migrate.min.js

501 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

509 ms

jquery-colorbox-wrapper-min.js

jquery-colorbox-wrapper-min.js

511 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

627 ms

slidedeck.jquery.lite.pack.js

slidedeck.jquery.lite.pack.js

669 ms

jquery.form.min.js

jquery.form.min.js

679 ms

scripts.js

scripts.js

680 ms

devicepx-jetpack.js

devicepx-jetpack.js

57 ms

comment-reply.min.js

comment-reply.min.js

722 ms

navigation.js

navigation.js

782 ms

wp-embed.min.js

wp-embed.min.js

783 ms

e-201609.js

e-201609.js

4 ms

__utm.gif

__utm.gif

12 ms

style.css

style.css

501 ms

banar0229aa.jpg

banar0229aa.jpg

325 ms

recruit225-1.jpg

recruit225-1.jpg

324 ms

newopen_bn_3.jpg

newopen_bn_3.jpg

508 ms

bn_nisemonocyuui.jpg

bn_nisemonocyuui.jpg

169 ms

bn_webtsuhan.jpg

bn_webtsuhan.jpg

339 ms

bn_2016spring_cl.jpg

bn_2016spring_cl.jpg

183 ms

uroko_bn2.jpg

uroko_bn2.jpg

337 ms

bn_instagram.jpg

bn_instagram.jpg

364 ms

all.js

all.js

268 ms

fl_logo_pc3.jpg

fl_logo_pc3.jpg

473 ms

menu_001home_on.jpg

menu_001home_on.jpg

474 ms

menu_001home_off.jpg

menu_001home_off.jpg

498 ms

menu_002news_on.jpg

menu_002news_on.jpg

503 ms

menu_002news_off.jpg

menu_002news_off.jpg

537 ms

menu_003brand_on.jpg

menu_003brand_on.jpg

628 ms

menu_003brand_off.jpg

menu_003brand_off.jpg

629 ms

menu_004shoplist_on.jpg

menu_004shoplist_on.jpg

664 ms

menu_004shoplist_off.jpg

menu_004shoplist_off.jpg

670 ms

menu_005gallery_on.jpg

menu_005gallery_on.jpg

671 ms

menu_005gallery_off.jpg

menu_005gallery_off.jpg

719 ms

menu_006postcard_on.jpg

menu_006postcard_on.jpg

784 ms

menu_006postcard_off.jpg

menu_006postcard_off.jpg

784 ms

menu_007signboard_on.jpg

menu_007signboard_on.jpg

830 ms

menu_007signboard_off.jpg

menu_007signboard_off.jpg

837 ms

menu_008collection_on.jpg

menu_008collection_on.jpg

838 ms

menu_008collection_off.jpg

menu_008collection_off.jpg

897 ms

menu_009recruit_on.jpg

menu_009recruit_on.jpg

939 ms

menu_009recruit_off.jpg

menu_009recruit_off.jpg

940 ms

menu_010web_on.jpg

menu_010web_on.jpg

996 ms

menu_010web_off.jpg

menu_010web_off.jpg

1005 ms

pdd1.jpg

pdd1.jpg

1512 ms

fb_yeti_hinamaturi_3.jpg

fb_yeti_hinamaturi_3.jpg

1078 ms

analytics.js

analytics.js

58 ms

g.gif

g.gif

11 ms

collect

collect

11 ms

62 ms

xd_arbiter.php

xd_arbiter.php

224 ms

xd_arbiter.php

xd_arbiter.php

426 ms

SEO Factors

franchelippee.com SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

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

franchelippee.com

Open Graph data is detected on the main page of Franchelippee. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: