Tools & Wizards About Us
kaitomo.jp screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

kaitomo.jp

韓国通販・個人輸入代行 かいとも - kaitomo.jp -

Page Load Speed

4.8 sec in total

First Response

644 ms

Resources Loaded

3.8 sec

Page Rendered

317 ms

kaitomo.jp screenshot

About Website

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

かいともドットジェイピーでは韓国の通販買い物代行をいたします。ネット購入や直接購入まで実績と長年の信頼がありますので、ご相談いただければ迅速かつ丁寧に対応いたします。

Visit kaitomo.jp

Key Findings

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

Performance Metrics

kaitomo.jp performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

49/100

25%

SI (Speed Index)

Value6.4 s

41/100

10%

TBT (Total Blocking Time)

Value930 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.053

98/100

15%

TTI (Time to Interactive)

Value8.9 s

34/100

10%

Network Requests Diagram

kaitomo.jp

644 ms

flash_check.js

177 ms

flash.js

332 ms

prototype.js

336 ms

scriptaculous.js

333 ms

Our browser made a total of 113 requests to load all elements on the main page. We found that 75% of them (85 requests) were addressed to the original Kaitomo.jp, 8% (9 requests) were made to Pagead2.googlesyndication.com and 6% (7 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Kaitomo.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 78.4 kB (8%)

Content Size

927.6 kB

After Optimization

849.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kaitomo.jp main page is 927.6 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. 65% of websites need less resources to load. Javascripts take 542.3 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 37.7 kB

  • Original 47.3 kB
  • After minification 45.8 kB
  • After compression 9.6 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 37.7 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 960 B

  • Original 336.0 kB
  • After minification 335.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. Kaitomo images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 39.4 kB

  • Original 542.3 kB
  • After minification 541.7 kB
  • After compression 502.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-16%

Potential reduce by 322 B

  • Original 2.0 kB
  • After minification 2.0 kB
  • After compression 1.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. Kaitomo.jp needs all CSS files to be minified and compressed as it can save up to 322 B or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 39 (35%)

Requests Now

110

After Optimization

71

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kaitomo.jp

kaitomo.jp

644 ms

flash_check.js

flash_check.js

177 ms

flash.js

flash.js

332 ms

prototype.js

prototype.js

336 ms

scriptaculous.js

scriptaculous.js

333 ms

lightbox.js

lightbox.js

341 ms

lightbox.css

lightbox.css

340 ms

show_ads.js

show_ads.js

74 ms

adsbygoogle.js

adsbygoogle.js

210 ms

effects.js

effects.js

183 ms

style.css

style.css

175 ms

common.css

common.css

176 ms

spacer.gif

spacer.gif

180 ms

head_r1_c1.jpg

head_r1_c1.jpg

176 ms

head_r1_c3.jpg

head_r1_c3.jpg

169 ms

head_r1_c6.jpg

head_r1_c6.jpg

167 ms

head_r2_c6.jpg

head_r2_c6.jpg

168 ms

head_r3_c6.jpg

head_r3_c6.jpg

171 ms

head_r3_c7.jpg

head_r3_c7.jpg

335 ms

head_r3_c8.jpg

head_r3_c8.jpg

336 ms

head_r3_c9.jpg

head_r3_c9.jpg

334 ms

head_r3_c11.jpg

head_r3_c11.jpg

341 ms

head_r4_c1.jpg

head_r4_c1.jpg

345 ms

head_r4_c10.jpg

head_r4_c10.jpg

354 ms

head_r5_c2.jpg

head_r5_c2.jpg

502 ms

side_r1_c1.jpg

side_r1_c1.jpg

503 ms

spacer.gif

spacer.gif

502 ms

side_r2_c1.jpg

side_r2_c1.jpg

512 ms

side_r3_c1.jpg

side_r3_c1.jpg

514 ms

side_r4_c1.jpg

side_r4_c1.jpg

530 ms

side_r5_c1.jpg

side_r5_c1.jpg

666 ms

side_r6_c1.jpg

side_r6_c1.jpg

667 ms

side_r7_c1.jpg

side_r7_c1.jpg

667 ms

side_r8_c1.jpg

side_r8_c1.jpg

681 ms

side_r9_c1.jpg

side_r9_c1.jpg

685 ms

side_r10_c1.jpg

side_r10_c1.jpg

702 ms

side_r11_c1.jpg

side_r11_c1.jpg

838 ms

side_r12_c1.jpg

side_r12_c1.jpg

831 ms

side_r13_c1.jpg

side_r13_c1.jpg

833 ms

BAR1.jpg

BAR1.jpg

851 ms

35.jpg

35.jpg

855 ms

37.jpg

37.jpg

878 ms

38.jpg

38.jpg

1225 ms

44.jpg

44.jpg

1225 ms

50.jpg

50.jpg

1226 ms

39.jpg

39.jpg

1227 ms

48.jpg

48.jpg

1227 ms

45.jpg

45.jpg

1195 ms

adsbygoogle.js

adsbygoogle.js

211 ms

show_ads_impl.js

show_ads_impl.js

261 ms

msg.htm

msg.htm

1076 ms

46.jpg

46.jpg

1076 ms

49.jpg

49.jpg

1075 ms

21.jpg

21.jpg

1072 ms

47.jpg

47.jpg

1067 ms

22.jpg

22.jpg

1066 ms

51.jpg

51.jpg

1085 ms

124.jpg

124.jpg

1065 ms

32.jpg

32.jpg

1065 ms

127.jpg

127.jpg

1060 ms

129.jpg

129.jpg

1059 ms

BAR4.jpg

BAR4.jpg

1059 ms

zrt_lookup.html

zrt_lookup.html

35 ms

ads

ads

441 ms

ads

ads

450 ms

BAR2.jpg

BAR2.jpg

1065 ms

57.jpg

57.jpg

1227 ms

sp1.jpg

sp1.jpg

1064 ms

odemukae.jpg

odemukae.jpg

1063 ms

meguri.jpg

meguri.jpg

1074 ms

96.jpg

96.jpg

1227 ms

BAR3.jpg

BAR3.jpg

1065 ms

43.jpg

43.jpg

1065 ms

41.jpg

41.jpg

1078 ms

42.jpg

42.jpg

1082 ms

spacer.gif

spacer.gif

1210 ms

foot_r1_c1.jpg

foot_r1_c1.jpg

1192 ms

foot_r1_c2.jpg

foot_r1_c2.jpg

1065 ms

bar.gif

bar.gif

1083 ms

001.jpg

001.jpg

1092 ms

7f032190f136c4d8e9a385e88120dc8d.js

7f032190f136c4d8e9a385e88120dc8d.js

39 ms

load_preloaded_resource.js

load_preloaded_resource.js

46 ms

af5cf33f216dd68f5f355584e69bf9d6.js

af5cf33f216dd68f5f355584e69bf9d6.js

46 ms

abg_lite.js

abg_lite.js

74 ms

window_focus.js

window_focus.js

74 ms

qs_click_protection.js

qs_click_protection.js

88 ms

ufs_web_display.js

ufs_web_display.js

25 ms

5f7468413707c3abfd197d65a482477f.js

5f7468413707c3abfd197d65a482477f.js

72 ms

s

s

5 ms

icon.png

icon.png

21 ms

15339366028764686641

15339366028764686641

64 ms

css

css

173 ms

activeview

activeview

62 ms

ckySkFmwfmQXT3S4i881M7X0Dq040p3kAeEpVWKJmn8.js

ckySkFmwfmQXT3S4i881M7X0Dq040p3kAeEpVWKJmn8.js

34 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

23 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

24 ms

activeview

activeview

63 ms

sodar

sodar

71 ms

loading.gif

loading.gif

178 ms

closelabel.gif

closelabel.gif

172 ms

side_r2_c1_2.jpg

side_r2_c1_2.jpg

169 ms

side_r3_c1_2.jpg

side_r3_c1_2.jpg

167 ms

side_r4_c1_2.jpg

side_r4_c1_2.jpg

168 ms

side_r5_c1_2.jpg

side_r5_c1_2.jpg

172 ms

side_r6_c1_b.jpg

side_r6_c1_b.jpg

341 ms

side_r7_c1_2.jpg

side_r7_c1_2.jpg

342 ms

side_r8_c1_2.jpg

side_r8_c1_2.jpg

341 ms

side_r10_c1_2.jpg

side_r10_c1_2.jpg

351 ms

side_r11_c1_2.jpg

side_r11_c1_2.jpg

351 ms

side_r12_c1_2.jpg

side_r12_c1_2.jpg

363 ms

sodar2.js

sodar2.js

4 ms

runner.html

runner.html

11 ms

aframe

aframe

25 ms

Accessibility Review

kaitomo.jp accessibility score

81

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

kaitomo.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

kaitomo.jp SEO score

67

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Kaitomo.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 Kaitomo.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

kaitomo.jp

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