Tools & Wizards About Us
frenchkiss.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

frenchkiss.jp

ロリポップ！レンタルサーバー | 利用実績170万人突破！無料SSLあり

Page Load Speed

9.4 sec in total

First Response

502 ms

Resources Loaded

8.5 sec

Page Rendered

388 ms

frenchkiss.jp screenshot

About Website

Welcome to frenchkiss.jp homepage info - get ready to check Frenchkiss best content for Japan right away, or after learning these important things about frenchkiss.jp

ホームページ運営なら、ずっと使えるレンタルサーバー「ロリポップ！」簡単、無料SSL、充実サポート、高速性能で、初心者から商用サイトまで安心してご利用いただけます。WordPress、EC-CUBEもたったの60秒で設置可能。無料お試し10日間。

Visit frenchkiss.jp

Key Findings

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

Performance Metrics

frenchkiss.jp performance score

0

Network Requests Diagram

frenchkiss.jp

502 ms

lolipop.jp

1385 ms

default.css

346 ms

common.css

635 ms

background.css

486 ms

Our browser made a total of 138 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Frenchkiss.jp, 51% (71 requests) were made to Lolipop.jp and 9% (12 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Lolipop.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 454.7 kB (37%)

Content Size

1.2 MB

After Optimization

777.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Frenchkiss.jp main page is 1.2 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. 40% of websites need less resources to load. Images take 707.6 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 144.1 kB

  • Original 169.1 kB
  • After minification 159.0 kB
  • After compression 25.0 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 144.1 kB or 85% of the original size.

Image Optimization

-18%

Potential reduce by 125.4 kB

  • Original 707.6 kB
  • After minification 582.1 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, Frenchkiss needs image optimization as it can save up to 125.4 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-36%

Potential reduce by 86.7 kB

  • Original 239.1 kB
  • After minification 238.4 kB
  • After compression 152.4 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 86.7 kB or 36% of the original size.

CSS Optimization

-85%

Potential reduce by 98.4 kB

  • Original 116.5 kB
  • After minification 86.2 kB
  • After compression 18.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. Frenchkiss.jp needs all CSS files to be minified and compressed as it can save up to 98.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 65 (56%)

Requests Now

116

After Optimization

51

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

frenchkiss.jp

frenchkiss.jp

502 ms

lolipop.jp

lolipop.jp

1385 ms

default.css

default.css

346 ms

common.css

common.css

635 ms

background.css

background.css

486 ms

text_m.css

text_m.css

501 ms

home.css

home.css

502 ms

lightbox.css

lightbox.css

514 ms

owl.carousel.css

owl.carousel.css

519 ms

jquery.min.js

jquery.min.js

79 ms

base.js

base.js

645 ms

lightbox.min.js

lightbox.min.js

582 ms

owl.carousel.min.js

owl.carousel.min.js

581 ms

home.js

home.js

581 ms

scrollreveal.min.js

scrollreveal.min.js

581 ms

pixel.js

pixel.js

717 ms

mixpanel.js

mixpanel.js

629 ms

fbds.js

fbds.js

297 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

113 ms

bg_night.gif

bg_night.gif

288 ms

close.png

close.png

287 ms

loading.gif

loading.gif

286 ms

prev.png

prev.png

286 ms

next.png

next.png

307 ms

bg_content_side.png

bg_content_side.png

323 ms

bg_main_bottom.gif

bg_main_bottom.gif

414 ms

bg_main_1column.png

bg_main_1column.png

415 ms

bg_submenu_top.gif

bg_submenu_top.gif

416 ms

h2_home_title.png

h2_home_title.png

594 ms

megaphone.svg

megaphone.svg

465 ms

obj_home_plan_economy.svg

obj_home_plan_economy.svg

482 ms

obj_home_plan_lite.svg

obj_home_plan_lite.svg

584 ms

obj_home_plan_standard.svg

obj_home_plan_standard.svg

582 ms

obj_home_plan_ribbon.svg

obj_home_plan_ribbon.svg

584 ms

obj_home_plan_enterprise.svg

obj_home_plan_enterprise.svg

624 ms

btn_home_plan_function_detail.png

btn_home_plan_function_detail.png

802 ms

btn_home_plan_price_detail.png

btn_home_plan_price_detail.png

749 ms

bnr_lolipop_nextgen_201601.png

bnr_lolipop_nextgen_201601.png

1251 ms

h3_home_title.png

h3_home_title.png

1250 ms

obj_home_feature_wordpress.png

obj_home_feature_wordpress.png

936 ms

line_dot_11.gif

line_dot_11.gif

783 ms

obj_home_feature_backup.png

obj_home_feature_backup.png

1249 ms

obj_home_feature_utilization.png

obj_home_feature_utilization.png

1099 ms

obj_home_feature_support.png

obj_home_feature_support.png

1282 ms

h3_home_functions.png

h3_home_functions.png

1109 ms

obj_home_functions_list.png

obj_home_functions_list.png

1421 ms

btn_feature._function_detail.png

btn_feature._function_detail.png

1283 ms

btn_infomation_more.png

btn_infomation_more.png

1423 ms

badge_light.png

badge_light.png

111 ms

widgets.js

widgets.js

61 ms

line_dot_02.gif

line_dot_02.gif

1367 ms

icon_star.gif

icon_star.gif

1334 ms

btn_h_serch.png

btn_h_serch.png

1364 ms

line_dot_08.gif

line_dot_08.gif

1372 ms

btn_pagetop.gif

btn_pagetop.gif

1490 ms

23 ms

obj_lolipop_logo.png

obj_lolipop_logo.png

1451 ms

dc.js

dc.js

68 ms

obj_ojisan_normal.png

obj_ojisan_normal.png

1579 ms

__utm.gif

__utm.gif

20 ms

__utm.gif

__utm.gif

11 ms

__utm.gif

__utm.gif

21 ms

__utm.gif

__utm.gif

28 ms

obj_header_banner_text.png

obj_header_banner_text.png

1618 ms

97 ms

btn_header_order.png

btn_header_order.png

1709 ms

bg_header_simple.png

bg_header_simple.png

1780 ms

obj_ppb_by_logo.png

obj_ppb_by_logo.png

1510 ms

obj_order_count_text.png

obj_order_count_text.png

1515 ms

obj_numbers.png

obj_numbers.png

1550 ms

menu_btn.png

menu_btn.png

1739 ms

menu_dot.gif

menu_dot.gif

1514 ms

arrow_menu.gif

arrow_menu.gif

1513 ms

obj_logo_ppb.png

obj_logo_ppb.png

1600 ms

pixel

pixel

151 ms

pixel

pixel

87 ms

Pug

Pug

60 ms

sync.ad-stir.com

sync.ad-stir.com

643 ms

sync

sync

1033 ms

is

is

1212 ms

headerstyle.min.css

headerstyle.min.css

212 ms

sd

sd

7 ms

sync

sync

28 ms

pixel

pixel

26 ms

google

google

148 ms

tag.js

tag.js

225 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

7 ms

obj_prev_item_icon.png

obj_prev_item_icon.png

947 ms

obj_next_item_icon.png

obj_next_item_icon.png

1025 ms

obj_dhw_ac_jp_thumb.jpg

obj_dhw_ac_jp_thumb.jpg

1187 ms

obj_mtblanc_jp_thumb.jpg

obj_mtblanc_jp_thumb.jpg

1271 ms

obj_foresthuntingone_com_thumb.jpg

obj_foresthuntingone_com_thumb.jpg

1269 ms

obj_sakelife_jp_thumb.jpg

obj_sakelife_jp_thumb.jpg

1282 ms

follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

follow_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

12 ms

jot

jot

96 ms

tag

tag

30 ms

mapuser

mapuser

153 ms

lolipop.jp

lolipop.jp

1496 ms

lolipop.jp

lolipop.jp

1813 ms

lolipop.jp

lolipop.jp

2381 ms

lolipop.jp

lolipop.jp

1997 ms

lolipop.jp

lolipop.jp

1750 ms

nr-892.min.js

nr-892.min.js

108 ms

roundtrip.js

roundtrip.js

42 ms

btn.png

btn.png

41 ms

conversion_async.js

conversion_async.js

72 ms

34 ms

logo201601.png

logo201601.png

52 ms

open_footer.png

open_footer.png

83 ms

close_footer.png

close_footer.png

114 ms

33 ms

conversion.js

conversion.js

1637 ms

QGNG2UAG2ZAKJNSEXUXBMN.js

QGNG2UAG2ZAKJNSEXUXBMN.js

102 ms

15936ac739

15936ac739

105 ms

38 ms

fbevents.hashing.js

fbevents.hashing.js

76 ms

out

out

10 ms

35 ms

out

out

6 ms

out

out

14 ms

out

out

29 ms

out

out

29 ms

out

out

28 ms

out

out

28 ms

out

out

28 ms

out

out

29 ms

out

out

30 ms

u.php

u.php

67 ms

sd

sd

40 ms

sd

sd

26 ms

30 ms

pixel

pixel

38 ms

Pug

Pug

37 ms

tap.php

tap.php

22 ms

377928.gif

377928.gif

15 ms

in

in

9 ms

23 ms

in

in

6 ms

SEO Factors

frenchkiss.jp 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 Frenchkiss.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 Frenchkiss.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

frenchkiss.jp

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