Tools & Wizards About Us
kaitomo.jp screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

kaitomo.jp

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

Page Load Speed

6.2 sec in total

First Response

883 ms

Resources Loaded

4.9 sec

Page Rendered

422 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 883 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

kaitomo.jp performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value930 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.7 s

45/100

10%

Network Requests Diagram

kaitomo.jp

883 ms

flash_check.js

367 ms

flash.js

375 ms

prototype.js

390 ms

scriptaculous.js

375 ms

Our browser made a total of 124 requests to load all elements on the main page. We found that 69% of them (85 requests) were addressed to the original Kaitomo.jp, 5% (6 requests) were made to C.betrad.com and 4% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Kaitomo.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 672.3 kB (55%)

Content Size

1.2 MB

After Optimization

557.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kaitomo.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. 55% of websites need less resources to load. Images take 855.4 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 31.6 kB

  • Original 39.5 kB
  • After minification 38.0 kB
  • After compression 7.9 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 31.6 kB or 80% of the original size.

Image Optimization

-47%

Potential reduce by 404.7 kB

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

JavaScript Optimization

-71%

Potential reduce by 232.0 kB

  • Original 329.0 kB
  • After minification 295.6 kB
  • After compression 96.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 232.0 kB or 71% of the original size.

CSS Optimization

-70%

Potential reduce by 3.9 kB

  • Original 5.6 kB
  • After minification 4.6 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 3.9 kB or 70% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (33%)

Requests Now

121

After Optimization

81

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 121 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 19 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

kaitomo.jp

kaitomo.jp

883 ms

flash_check.js

flash_check.js

367 ms

flash.js

flash.js

375 ms

prototype.js

prototype.js

390 ms

scriptaculous.js

scriptaculous.js

375 ms

lightbox.js

lightbox.js

399 ms

lightbox.css

lightbox.css

413 ms

show_ads.js

show_ads.js

7 ms

effects.js

effects.js

174 ms

style.css

style.css

177 ms

common.css

common.css

179 ms

spacer.gif

spacer.gif

203 ms

head_r1_c1.jpg

head_r1_c1.jpg

195 ms

head_r1_c3.jpg

head_r1_c3.jpg

207 ms

head_r1_c6.jpg

head_r1_c6.jpg

185 ms

head_r2_c6.jpg

head_r2_c6.jpg

205 ms

head_r3_c6.jpg

head_r3_c6.jpg

220 ms

head_r3_c7.jpg

head_r3_c7.jpg

363 ms

head_r3_c8.jpg

head_r3_c8.jpg

379 ms

head_r3_c9.jpg

head_r3_c9.jpg

533 ms

head_r3_c11.jpg

head_r3_c11.jpg

409 ms

head_r4_c1.jpg

head_r4_c1.jpg

395 ms

head_r4_c10.jpg

head_r4_c10.jpg

382 ms

head_r5_c2.jpg

head_r5_c2.jpg

509 ms

side_r1_c1.jpg

side_r1_c1.jpg

567 ms

spacer.gif

spacer.gif

569 ms

side_r2_c1.jpg

side_r2_c1.jpg

589 ms

side_r3_c1.jpg

side_r3_c1.jpg

589 ms

side_r4_c1.jpg

side_r4_c1.jpg

685 ms

side_r5_c1.jpg

side_r5_c1.jpg

699 ms

side_r6_c1.jpg

side_r6_c1.jpg

753 ms

side_r7_c1.jpg

side_r7_c1.jpg

752 ms

side_r8_c1.jpg

side_r8_c1.jpg

795 ms

side_r9_c1.jpg

side_r9_c1.jpg

782 ms

side_r10_c1.jpg

side_r10_c1.jpg

856 ms

side_r11_c1.jpg

side_r11_c1.jpg

893 ms

side_r12_c1.jpg

side_r12_c1.jpg

950 ms

side_r13_c1.jpg

side_r13_c1.jpg

1103 ms

BAR1.jpg

BAR1.jpg

1098 ms

35.jpg

35.jpg

971 ms

37.jpg

37.jpg

1155 ms

38.jpg

38.jpg

1044 ms

44.jpg

44.jpg

1121 ms

50.jpg

50.jpg

1338 ms

39.jpg

39.jpg

1378 ms

48.jpg

48.jpg

1277 ms

45.jpg

45.jpg

1278 ms

zrt_lookup.html

zrt_lookup.html

26 ms

show_ads_impl.js

show_ads_impl.js

45 ms

ads

ads

223 ms

osd.js

osd.js

24 ms

msg.htm

msg.htm

1153 ms

46.jpg

46.jpg

1451 ms

49.jpg

49.jpg

1280 ms

21.jpg

21.jpg

1288 ms

47.jpg

47.jpg

1280 ms

22.jpg

22.jpg

1486 ms

201 ms

adj

adj

88 ms

beacon

beacon

65 ms

51.jpg

51.jpg

1360 ms

124.jpg

124.jpg

1285 ms

32.jpg

32.jpg

1288 ms

127.jpg

127.jpg

1282 ms

129.jpg

129.jpg

1549 ms

BAR4.jpg

BAR4.jpg

1329 ms

BAR2.jpg

BAR2.jpg

1312 ms

75 ms

activityi;src=4236808;type=invmedia;cat=aoyjbkr6;ord=-1751669732

activityi;src=4236808;type=invmedia;cat=aoyjbkr6;ord=-1751669732

94 ms

activityi;src=4236808;type=invmedia;cat=qk1cfvwl;ord=-1751669732

activityi;src=4236808;type=invmedia;cat=qk1cfvwl;ord=-1751669732

101 ms

activityi;src=4236808;type=invmedia;cat=ijhardnr;ord=-1751669732

activityi;src=4236808;type=invmedia;cat=ijhardnr;ord=-1751669732

138 ms

activityi;src=4236808;type=invmedia;cat=4ztf2oue;ord=-1751669732

activityi;src=4236808;type=invmedia;cat=4ztf2oue;ord=-1751669732

136 ms

0

0

95 ms

surly.js

surly.js

170 ms

57.jpg

57.jpg

1615 ms

sp1.jpg

sp1.jpg

1317 ms

odemukae.jpg

odemukae.jpg

1473 ms

meguri.jpg

meguri.jpg

1587 ms

index.html

index.html

234 ms

verify_selector.js

verify_selector.js

185 ms

blank.gif

blank.gif

197 ms

96.jpg

96.jpg

1677 ms

BAR3.jpg

BAR3.jpg

1372 ms

ba.html

ba.html

63 ms

pixel

pixel

62 ms

4.gif

4.gif

95 ms

lidar.js

lidar.js

36 ms

sbhK2lTE.js

sbhK2lTE.js

97 ms

43.jpg

43.jpg

1517 ms

41.jpg

41.jpg

1642 ms

42.jpg

42.jpg

1470 ms

pixel

pixel

70 ms

pixel

pixel

94 ms

4311.js

4311.js

88 ms

verifyr.js

verifyr.js

51 ms

spacer.gif

spacer.gif

1538 ms

cTrvNaRi.html

cTrvNaRi.html

7 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

38 ms

setuid

setuid

105 ms

beacon.js

beacon.js

80 ms

0

0

20 ms

bg.png

bg.png

76 ms

adchoices.en.png

adchoices.en.png

105 ms

foot_r1_c1.jpg

foot_r1_c1.jpg

1477 ms

foot_r1_c2.jpg

foot_r1_c2.jpg

1544 ms

Rejuvenation_160x600_logo.gif

Rejuvenation_160x600_logo.gif

44 ms

MommyMakeover_160x600_bg.jpg

MommyMakeover_160x600_bg.jpg

73 ms

bar.gif

bar.gif

1491 ms

001.jpg

001.jpg

1711 ms

sd

sd

29 ms

box_19_top-right.png

box_19_top-right.png

30 ms

ci.png

ci.png

30 ms

loading.gif

loading.gif

179 ms

closelabel.gif

closelabel.gif

190 ms

side_r2_c1_2.jpg

side_r2_c1_2.jpg

188 ms

side_r3_c1_2.jpg

side_r3_c1_2.jpg

348 ms

side_r4_c1_2.jpg

side_r4_c1_2.jpg

187 ms

side_r5_c1_2.jpg

side_r5_c1_2.jpg

189 ms

side_r6_c1_b.jpg

side_r6_c1_b.jpg

513 ms

side_r7_c1_2.jpg

side_r7_c1_2.jpg

360 ms

side_r8_c1_2.jpg

side_r8_c1_2.jpg

374 ms

side_r10_c1_2.jpg

side_r10_c1_2.jpg

368 ms

side_r11_c1_2.jpg

side_r11_c1_2.jpg

361 ms

side_r12_c1_2.jpg

side_r12_c1_2.jpg

506 ms

Accessibility Review

kaitomo.jp accessibility score

69

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

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: