10.3 sec in total
563 ms
9.3 sec
389 ms
Visit lovepop.jp now to see the best up-to-date Lovepop content for Japan and also check out these interesting facts you probably never knew about lovepop.jp
Visit lovepop.jpWe analyzed Lovepop.jp page load time and found that the first response time was 563 ms and then it took 9.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
lovepop.jp performance score
563 ms
1195 ms
325 ms
631 ms
492 ms
Our browser made a total of 135 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lovepop.jp, 53% (71 requests) were made to Lolipop.jp and 8% (11 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (3 sec) relates to the external source Lolipop.jp.
Page size can be reduced by 440.1 kB (36%)
1.2 MB
781.0 kB
In fact, the total size of Lovepop.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.
Potential reduce by 143.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 143.2 kB or 85% of the original size.
Potential reduce by 125.4 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, Lovepop 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.
Potential reduce by 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 73.0 kB or 32% of the original size.
Potential reduce by 98.4 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. Lovepop.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.
Number of requests can be reduced by 64 (56%)
114
50
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lovepop. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
lovepop.jp
563 ms
lolipop.jp
1195 ms
default.css
325 ms
common.css
631 ms
background.css
492 ms
text_m.css
492 ms
home.css
507 ms
lightbox.css
518 ms
owl.carousel.css
520 ms
jquery.min.js
64 ms
base.js
600 ms
lightbox.min.js
598 ms
owl.carousel.min.js
596 ms
home.js
596 ms
scrollReveal.min.js
596 ms
pixel.js
779 ms
mixpanel.js
628 ms
fbds.js
329 ms
mixpanel-2-latest.min.js
138 ms
bg_night.gif
283 ms
close.png
284 ms
loading.gif
286 ms
prev.png
288 ms
next.png
288 ms
bg_content_side.png
307 ms
bg_main_bottom.gif
448 ms
bg_main_1column.png
450 ms
bg_submenu_top.gif
456 ms
h2_home_title.png
799 ms
megaphone.svg
456 ms
obj_home_plan_economy.svg
481 ms
obj_home_plan_lite.svg
615 ms
obj_home_plan_standard.svg
618 ms
obj_home_plan_ribbon.svg
652 ms
obj_home_plan_enterprise.svg
657 ms
btn_home_plan_function_detail.png
800 ms
btn_home_plan_price_detail.png
782 ms
bnr_lolipop_nextgen_201601.png
1274 ms
h3_home_title.png
1170 ms
obj_home_feature_wordpress.png
1173 ms
line_dot_11.gif
949 ms
obj_home_feature_backup.png
1152 ms
obj_home_feature_utilization.png
1130 ms
obj_home_feature_support.png
1453 ms
h3_home_functions.png
1652 ms
obj_home_functions_list.png
1840 ms
btn_feature._function_detail.png
1675 ms
btn_infomation_more.png
1683 ms
badge_light.png
123 ms
widgets.js
87 ms
line_dot_02.gif
1607 ms
icon_star.gif
1575 ms
btn_h_serch.png
1707 ms
line_dot_08.gif
1732 ms
dc.js
70 ms
btn_pagetop.gif
1718 ms
obj_lolipop_logo.png
1881 ms
37 ms
obj_ojisan_normal.png
1869 ms
__utm.gif
13 ms
__utm.gif
11 ms
__utm.gif
22 ms
__utm.gif
32 ms
obj_header_banner_text.png
2548 ms
btn_header_order.png
2789 ms
117 ms
bg_header_simple.png
3022 ms
obj_ppb_by_logo.png
2517 ms
obj_order_count_text.png
2535 ms
obj_numbers.png
2539 ms
menu_btn.png
2955 ms
menu_dot.gif
2539 ms
arrow_menu.gif
2549 ms
obj_logo_ppb.png
2510 ms
pixel
163 ms
pixel
69 ms
Pug
77 ms
sync.ad-stir.com
672 ms
sync
956 ms
is
725 ms
headerstyle.min.css
232 ms
sync
4 ms
sd
5 ms
pixel
16 ms
197 ms
tag.js
39 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
6 ms
obj_prev_item_icon.png
2297 ms
obj_next_item_icon.png
2281 ms
obj_dhw_ac_jp_thumb.jpg
2609 ms
obj_mtblanc_jp_thumb.jpg
2461 ms
obj_foresthuntingone_com_thumb.jpg
2450 ms
obj_sakelife_jp_thumb.jpg
2475 ms
tag
44 ms
follow_button.6a78875565a912489e9aef879c881358.ja.html
26 ms
jot
85 ms
lolipop.jp
1643 ms
lolipop.jp
1889 ms
lolipop.jp
2208 ms
lolipop.jp
2340 ms
lolipop.jp
1654 ms
nr-768.min.js
69 ms
roundtrip.js
170 ms
btn.png
46 ms
conversion_async.js
34 ms
32 ms
logo201601.png
61 ms
open_footer.png
91 ms
close_footer.png
117 ms
35 ms
conversion.js
1413 ms
15936ac739
120 ms
49 ms
QGNG2UAG2ZAKJNSEXUXBMN.js
38 ms
out
10 ms
tr
33 ms
33 ms
out
5 ms
out
23 ms
out
22 ms
out
22 ms
out
28 ms
out
27 ms
out
27 ms
out
28 ms
u.php
72 ms
sync
20 ms
33 ms
sd
11 ms
sd
41 ms
pixel
29 ms
in
6 ms
377928.gif
10 ms
tap.php
18 ms
in
5 ms
lovepop.jp SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lovepop.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 Lovepop.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.
lovepop.jp
Open Graph data is detected on the main page of Lovepop. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: