Tools & Wizards About Us
oops.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

oops.jp

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

Page Load Speed

10.3 sec in total

First Response

531 ms

Resources Loaded

9.2 sec

Page Rendered

538 ms

oops.jp screenshot

About Website

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

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

Visit oops.jp

Key Findings

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

oops.jp performance score

0

Network Requests Diagram

oops.jp

531 ms

lolipop.jp

1363 ms

default.css

329 ms

common.css

963 ms

background.css

503 ms

Our browser made a total of 133 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Oops.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 (2.9 sec) relates to the external source Lolipop.jp.

Page Optimization Overview & Recommendations

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

Content Size

1.2 MB

After Optimization

762.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oops.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. 45% 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 142.9 kB

  • Original 167.5 kB
  • After minification 157.4 kB
  • After compression 24.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 142.9 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, Oops 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

-35%

Potential reduce by 73.0 kB

  • Original 211.0 kB
  • After minification 210.3 kB
  • After compression 138.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 35% 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. Oops.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 64 (56%)

Requests Now

114

After Optimization

50

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Oops. 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.

Network Requests Diagram

oops.jp

oops.jp

531 ms

lolipop.jp

lolipop.jp

1363 ms

default.css

default.css

329 ms

common.css

common.css

963 ms

background.css

background.css

503 ms

text_m.css

text_m.css

509 ms

home.css

home.css

729 ms

lightbox.css

lightbox.css

538 ms

owl.carousel.css

owl.carousel.css

554 ms

jquery.min.js

jquery.min.js

87 ms

base.js

base.js

677 ms

lightbox.min.js

lightbox.min.js

1083 ms

owl.carousel.min.js

owl.carousel.min.js

1103 ms

home.js

home.js

964 ms

scrollReveal.min.js

scrollReveal.min.js

1092 ms

pixel.js

pixel.js

669 ms

mixpanel.js

mixpanel.js

962 ms

fbds.js

fbds.js

157 ms

mixpanel-2-latest.min.js

mixpanel-2-latest.min.js

126 ms

bg_night.gif

bg_night.gif

184 ms

close.png

close.png

1117 ms

loading.gif

loading.gif

1078 ms

prev.png

prev.png

1087 ms

next.png

next.png

1116 ms

bg_content_side.png

bg_content_side.png

1116 ms

bg_main_bottom.gif

bg_main_bottom.gif

1123 ms

bg_main_1column.png

bg_main_1column.png

1243 ms

bg_submenu_top.gif

bg_submenu_top.gif

1244 ms

h2_home_title.png

h2_home_title.png

1628 ms

megaphone.svg

megaphone.svg

1487 ms

obj_home_plan_economy.svg

obj_home_plan_economy.svg

1306 ms

obj_home_plan_lite.svg

obj_home_plan_lite.svg

1318 ms

obj_home_plan_standard.svg

obj_home_plan_standard.svg

1576 ms

obj_home_plan_ribbon.svg

obj_home_plan_ribbon.svg

1403 ms

obj_home_plan_enterprise.svg

obj_home_plan_enterprise.svg

1464 ms

btn_home_plan_function_detail.png

btn_home_plan_function_detail.png

1670 ms

btn_home_plan_price_detail.png

btn_home_plan_price_detail.png

2077 ms

bnr_lolipop_nextgen_201601.png

bnr_lolipop_nextgen_201601.png

2593 ms

h3_home_title.png

h3_home_title.png

2506 ms

obj_home_feature_wordpress.png

obj_home_feature_wordpress.png

2402 ms

line_dot_11.gif

line_dot_11.gif

2088 ms

obj_home_feature_backup.png

obj_home_feature_backup.png

2628 ms

obj_home_feature_utilization.png

obj_home_feature_utilization.png

2392 ms

obj_home_feature_support.png

obj_home_feature_support.png

2599 ms

h3_home_functions.png

h3_home_functions.png

2552 ms

obj_home_functions_list.png

obj_home_functions_list.png

2729 ms

btn_feature._function_detail.png

btn_feature._function_detail.png

2690 ms

btn_infomation_more.png

btn_infomation_more.png

2710 ms

line_dot_02.gif

line_dot_02.gif

2761 ms

badge_light.png

badge_light.png

107 ms

widgets.js

widgets.js

88 ms

icon_star.gif

icon_star.gif

2709 ms

dc.js

dc.js

84 ms

51 ms

btn_h_serch.png

btn_h_serch.png

2679 ms

line_dot_08.gif

line_dot_08.gif

2750 ms

122 ms

btn_pagetop.gif

btn_pagetop.gif

2694 ms

__utm.gif

__utm.gif

39 ms

__utm.gif

__utm.gif

23 ms

__utm.gif

__utm.gif

33 ms

__utm.gif

__utm.gif

34 ms

obj_lolipop_logo.png

obj_lolipop_logo.png

2646 ms

obj_ojisan_normal.png

obj_ojisan_normal.png

2852 ms

obj_header_banner_text.png

obj_header_banner_text.png

2842 ms

pixel

pixel

164 ms

Pug

Pug

86 ms

sync.ad-stir.com

sync.ad-stir.com

671 ms

sync

sync

47 ms

sync

sync

1059 ms

is

is

1220 ms

headerstyle.min.css

headerstyle.min.css

154 ms

btn_header_order.png

btn_header_order.png

2332 ms

bg_header_simple.png

bg_header_simple.png

2339 ms

sd

sd

21 ms

pixel

pixel

22 ms

google

google

164 ms

obj_ppb_by_logo.png

obj_ppb_by_logo.png

2051 ms

obj_order_count_text.png

obj_order_count_text.png

2049 ms

tag.js

tag.js

50 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

9 ms

obj_numbers.png

obj_numbers.png

2064 ms

menu_btn.png

menu_btn.png

2202 ms

tag

tag

40 ms

follow_button.6a78875565a912489e9aef879c881358.ja.html

follow_button.6a78875565a912489e9aef879c881358.ja.html

30 ms

menu_dot.gif

menu_dot.gif

2050 ms

arrow_menu.gif

arrow_menu.gif

2000 ms

jot

jot

89 ms

obj_logo_ppb.png

obj_logo_ppb.png

2073 ms

obj_prev_item_icon.png

obj_prev_item_icon.png

2051 ms

obj_next_item_icon.png

obj_next_item_icon.png

1988 ms

obj_dhw_ac_jp_thumb.jpg

obj_dhw_ac_jp_thumb.jpg

2136 ms

obj_mtblanc_jp_thumb.jpg

obj_mtblanc_jp_thumb.jpg

1730 ms

obj_foresthuntingone_com_thumb.jpg

obj_foresthuntingone_com_thumb.jpg

1762 ms

obj_sakelife_jp_thumb.jpg

obj_sakelife_jp_thumb.jpg

1540 ms

lolipop.jp

lolipop.jp

1258 ms

lolipop.jp

lolipop.jp

1752 ms

lolipop.jp

lolipop.jp

1975 ms

lolipop.jp

lolipop.jp

1402 ms

lolipop.jp

lolipop.jp

1543 ms

nr-768.min.js

nr-768.min.js

70 ms

roundtrip.js

roundtrip.js

61 ms

btn.png

btn.png

34 ms

conversion_async.js

conversion_async.js

64 ms

38 ms

logo201601.png

logo201601.png

57 ms

open_footer.png

open_footer.png

87 ms

close_footer.png

close_footer.png

119 ms

15936ac739

15936ac739

172 ms

42 ms

conversion.js

conversion.js

996 ms

QGNG2UAG2ZAKJNSEXUXBMN.js

QGNG2UAG2ZAKJNSEXUXBMN.js

29 ms

91 ms

out

out

17 ms

tr

tr

32 ms

32 ms

out

out

20 ms

out

out

22 ms

out

out

28 ms

out

out

27 ms

out

out

28 ms

out

out

27 ms

out

out

28 ms

out

out

30 ms

u.php

u.php

61 ms

60 ms

sync

sync

13 ms

sd

sd

41 ms

sd

sd

66 ms

in

in

11 ms

tap.php

tap.php

20 ms

377928.gif

377928.gif

7 ms

in

in

5 ms

SEO Factors

oops.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 Oops.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 Oops.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

oops.jp

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